What do you mean? every Model has a unique ID, what do you consider a version?
And anyway once a model is published can’t update it right?
Correct, and also the creating Task is published (i.e. locked)
And anyway once a model is published can’t update it right? Which means there will be atleast multiple published models entries of same model over time?
each of it gets pushed as a separate Model entity right?
Correct
But there’s only one unique model with multiple different version of it
Do you see multiple lines in the Model repository ? (every line is an entity) basically if you store it under the same local file, it will override the model entry (i.e. reuse it and upgrade the file itself), otherwise you are creating a new model, "version" will be progress in time ?
If i publish a keras_mnist model and experiment on, each of it gets pushed as a separate Model entity right? But there’s only one unique model with multiple different version of it
Which means there will be atleast multiple published models entries of same model over time?
Only the specific one will be published (not all the Models the Task created)
Do people generally update the same model “entry”? That feels so wrong to me…how do you reproduce a older model version or do a rollback etc?
Correct, they do not 🙂 On the Task itself the output models will reflect the diff filenames you saved, usually ppl just add a running number.
Do people generally update the same model “entry”? That feels so wrong to me…how do you reproduce a older model version or do a rollback etc?