Open nsenno-dbr opened 1 month ago
Reflecting on this issue, I'm thinking to add a parameter "register
" or "dev
" to the run_forecast()
function that prevents MMF from registering the model. If we take the "dev
" route, we can switch off bunch of other stuffs that are not really important during the iteration: e.g. scoring_output
table.
Currently the solution creates a new registered model every time it is run. This can get confusing when running many cycles in development. It would be better if we just saved the model in the experiment then push to the registry when we were happy with the solution