Viewing a single comment thread. View all comments

DingusFamilyVacation t1_j6waih9 wrote

I'm excited to try this out. I'm doing most of the ML development on my team. I'll iterate on code development and retrain, multiple times over. Oftentimes, my team members will jump in and want to use a trained model to run some downstream analyses. If the library API has changed, or the model architecture has been tweaked, loading the state_dicts of earlier models becomes nearly impossible without checking out old commits. Even then, storing the results and associating them w commit numbers is super annoying.

Thanks for the tool!

1

latefordinnerstudios OP t1_j6wvy0u wrote

This is exactly the kind of problems I’m trying to fix! Let me know how it works for you!

1