Question About Checkout Logic about keepsake HOT 2 OPEN

Hi @fishbotics, good question! The documentation could probably be more clear around this.

Keepsake doesn't store diffs like Git, for each experiment and checkpoint it stores the whole files and directories that you specify with the path= argument. When you check out a checkpoint, it first copies all the experiment files, and then it copies the checkpoint files on top of that.

So I wouldn't stop using GitHub to manage my repository, do pull requests, etc. Keepsake is more like a "time machine" that lets you jump to any point during the training process. I've also been in situations where I've started training something, changed the code on my local machine without committing, then once the model has finished training I don't know what code produced the model. In that case Keepsake is almost like a backup system that makes sure you never lose the code that produced the model weights.

Feel free to join our Discord to chat more about this in real-time: https://discord.gg/QmzJApGjyE

from keepsake.

Hi @fishbotics 👋🏼

The Keepsake project is no longer actively maintained. If you're interested in helping maintain it, please let us know.

from keepsake.