Would be nice to add a kwarg to the MonitorMetric callback which makes it only compute the metric on validation data every n epochs, instead of every single epoch.
Course then you'll (ie users) will have to be careful when using it in combo w/ EarlyStopping (since if you have EarlyStopping w/ patience of, say, 5, and have it take a MonitorMetric which is only checking the metric every 5 epochs, then it'll stop after the first 5 epochs because the metric "hasn't changed"!)
Would be nice to add a kwarg to the
MonitorMetriccallback which makes it only compute the metric on validation data everynepochs, instead of every single epoch.Course then you'll (ie users) will have to be careful when using it in combo w/ EarlyStopping (since if you have EarlyStopping w/ patience of, say, 5, and have it take a MonitorMetric which is only checking the metric every 5 epochs, then it'll stop after the first 5 epochs because the metric "hasn't changed"!)