Open
Conversation
Now, instead of the default accuracy for schedule, one can choose precision, recall, balanced-accuracy or f1 as a metric for devset fitting.
Contributor
Author
|
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. |
Owner
|
Did you find out why? |
Contributor
Author
|
I'll go back into having a look at this. |
Contributor
Author
|
This is good to go. |
Owner
|
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... |
Contributor
Author
|
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 <[email protected]>
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>
.
|
Contributor
Author
|
Note: I think if you merge this Optuna will need to be changed a litte :) |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
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.