-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
textrecipes tuning parameters #16
Comments
Could you change
Sure. We have qualitative parameters in other models too. |
Done. Changed to *_times.
Then I have these additions.
|
Would a whole step be |
I've thought about the issue of including a step or not. We could add an |
That would be great! |
Should |
Mainly |
Mind if I default |
That should be fine. |
Take a look at this commit and let me know if the default ranges (or anything else) should be changed. |
Looks good. |
Gak. I think that we need large numbers instead of > max_times
Maximum Token Frequency (quantitative)
Range: [1, Inf]
> grid_random(max_times, size = 5)
Show Traceback
Rerun with Debug
Error in min(unlist(object$range)):max(unlist(object$range)) :
result would be too long a vector What should we put in? We could do: > .Machine$integer.max
[1] 2147483647
> library(dials)
> max_times
Maximum Token Frequency (quantitative)
Range: [1, 2147483647]
> grid_random(max_times, size = 5)
# A tibble: 5 x 1
max_times
<int>
1 1024987753
2 2080355927
3 1342632065
4 48813909
5 85432412 Maybe something smaller like |
So in essence |
merged PR |
This issue has been automatically locked. If you believe you have found a related problem, please file a new issue (with a reprex: https://reprex.tidyverse.org) and link to this issue. |
In accordance to tidymodels/textrecipes#14 here are my thoughts on what should be tunable.
step_texthash
:num_terms
integer.step_tf
:weight
numeric.step_tokenfilter
:max
numeric.min
numeric.max_tokens
integer.Question.
Would something like
weight_scheme
instep_tf
be tunable as it takes a couple of different (method as characters) values?The text was updated successfully, but these errors were encountered: