Passing wrong strings for scheduler interval doesn't throw an error #5548
Labels
bug
Something isn't working
good first issue
Good for newcomers
help wanted
Open to be worked on
priority: 2
Low priority task
I noticed that when you pass an interval as scheduler parameter that is not 'step' or 'epoch' (for example 'batch') there's no error, it just trains without ever calling the scheduler. Had to look into the source code because I didn't find much info about it in the documentation
The text was updated successfully, but these errors were encountered: