Updating early stopping for more intuitive use - #2051
Conversation
|
Wondering if this PR should attempt to address #1939 as well. The issue I guess is that |
|
I think it makes sense to add the fix in this PR too. |
|
Depends on #2053 or something like it |
|
#2059 just landed, and I think it fixes the DDP bug without having to change anything, because now the I don't have easy access to multi-gpu machine right now, so if anyone else can test that would be welcome. |
Adel-Moumen
left a comment
There was a problem hiding this comment.
LGTM.
I'm going to try with multiple GPUs.
|
@Adel-Moumen, any news? |
|
I don't know if it's because of
However, now, my training is stopped. I can't do anything. Nothing show up. Additionally, the recipe doesn't seem to save the stopping information, when I kill the program an re run it, I am going back to training while it should skip it as we reached the patience limit... What do you think @pplantinga ? |
|
Ah yes, the I can add this. As for the other issue, I don't immediately know what's wrong. |
|
It is working! Thanks. I will open an issue related to the G2P recipe. There's a lot of problems when using it with DDP.... |
|
Yes, confirmed it worked for me. Sorry for the late reply |
Contribution in a nutshell
This addresses issue #1914 . Early stopping was already available with
EpochCounterWithStopperbut the use was quite unintuitive. I've updated to be more intuitive and updated the single recipe that used it.