You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
One monitor for ranking. Set monitor(e) = :metric => :mode (or the Nitro keyword monitor) once. Checkpointer, TopKCheckpointer, EarlyStopping and the new Plateau follow it unless given both their own metric and mode. Giving only one of the two is now an error.
No default when it might not exist.monitor defaults to :loss => :min only when the experiment defines no metrics or sets eval_loss = true. Otherwise a checkpointer with a Best selector, EarlyStopping or Plateau fails at setup until monitor is declared.
val_loss is now loss. Metric names carry no split. The framework loss is loss on every split, and :val_loss is accepted with a warning until 1.0.0. Manifests from before 0.2.0 are read as loss, so old runs keep ranking.
History column renamed. In history(nitro) the train loss column is now train_loss, and h.loss is the validation loss.
EarlyStopping() used outside a Nitro has no metric until setup fills it in. Give it metric and mode to call should_stop directly.
New
Plateau(inner; factor, patience, ...): PyTorch's ReduceLROnPlateau for any schedule key. Its state is saved with the checkpoint, so a resume continues it.
loss may return (l, terms). Each term is logged as loss/<term> on train, validation and test (#48 - @benjwweber)
eval_loss = true reports the loss beside user metrics on eval splits. A key reported by both is an error.
Fixed
Resuming from a mid-run checkpoint no longer loses one epoch of early-stopping patience.