-
Notifications
You must be signed in to change notification settings - Fork 10
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
Accuracy function #54
base: master
Are you sure you want to change the base?
Accuracy function #54
Conversation
Now, instead of the default accuracy for schedule, one can choose precision, recall, balanced-accuracy or f1 as a metric for devset fitting.
The LR Scheduler does not seem to update with this PR. I need to get into the details here but I got 25 steps for lemmatization with lr_patience 10 and patience 8 which definitely does not seem right. |
Did you find out why? |
I'll go back into having a look at this. |
This is good to go. |
I was a bit surprised (also) by the fact we still print threshold value of LROnPlateau but we do not set it. Lines 202 to 204 in 230e0e6
Lines 154 to 155 in 230e0e6
It feels to me we should forward the value of the target task but :) |
What was the issue? Re: threshold. You are right. I never got to use it and was kept a 0.0. However, note that there are 2 thresholds here. One is for the LR schedule, the other is for the task schedule. Just saying because it's not very well documented... |
I don't know, probably had a misunderstanding or did not check correctly.
There is basically no reason it should affect lr schedule...
As for the second comment, yes, maybe we should have a lr_threshold?
Le mar. 4 août 2020 à 5:10 PM, Enrique Manjavacas <notifications@github.com>
a écrit :
… What was the issue?
Re: threshold. You are right. I never got to use it and was kept a 0.0.
However, note that there are 2 thresholds here. One is for the LR schedule,
the other is for the task schedule. Just saying because it's not very well
documented...
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#54 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAOXEZXJWKZQUM6OJHAZBBDR7AQHZANCNFSM4LEMOL6Q>
.
|
Note: I think if you merge this Optuna will need to be changed a litte :) |
Actually duplicates in part #53 because I forgot to go back to master...
This adds the ability to chose on which metric to fit in regard to devset: accuracy, f1, precision, recall, balanced-accuracy.
Default value should not change pas behaviours.