Skip to content

Stop when loss is NaN

Created by: VolodyaCO

Closes #1222

This PR includes the InvalidLossStopping callback. As mentioned in #1222, I once saw energy going to NaN and back to being finite. Thus, we might want to not have this as default. I was thinking, however, that we can have a "default" callback that checks for NaNs in the loss value, and if it sees NaNs, it raises a warning, telling the user that they might want to include this callback.

Seems too cumbersome, though. What do you think about it?

Merge request reports