-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support for circular dependencies - eg have model
as both input and ouput of train
stage
#4724
Comments
I have the same problem. Currently, I didn't put |
@davesteps @karajan1001 We have an upcoming experimental feature for experiment checkpoints #4498 , maybe it would be useful in your scenario as well? |
@efiop It sounds like the checkpoints feature is very close to what I would like to achieve. I'm certainly willing to give it a try when it is available. I also wasn't aware of the |
@davesteps There is no official documentation yet and it is still an experimental feature, but we have a wiki for it https://github.com/iterative/dvc/wiki/Experiments#checkpoint-experiments . Feel free to give it a try 🙂 |
@davesteps Checkpoints have been released in 2.0, did you have a chance to try them? |
Closing as stale for now. |
It quite common when training deep learning models not to start training from scratch every time but rather use a previous model as initial starting weights. For example you may train an basic model then make some adjustments to your training data or your loss function or adjust some other parameter and continue training.
I am currently using a solution suggested on the forum of using
import
to import a previous version of my model. However, it was also suggested that a better solution could be supported where themodel
object could be both an input and output of yourtrain
stage.The original question for more context:
https://discuss.dvc.org/t/use-previous-version-of-model-as-initial-weights/525/2
The text was updated successfully, but these errors were encountered: