google-deepmind / google-deepmind/fusion_surrogates

Best practices for distributing NN model weights

Open
#22 5 comments 0 reactions 0 assignees View on GitHub
Dominant language
Python
Stars
41
Forks
9
Avg merge
1h 50m
Merged PRs (30d)
1

Description

If I understand correctly, the model weights for the new QLKNN are in one of these files ?

https://github.com/google-deepmind/fusion_surrogates/tree/main/fusion_surrogates/qlknn/models

As a community, we have growing collection of surrogate models and the distribution and packaging of their weights could do with some standardisation / best practices. Maybe you have thought about this more than the wider fusion community...

Some questions
* Are model weights best distributed via `git`, `git lfs`, or something else ?
* I don't want to be continually downloading unrelated git histories and working trees that I don't really need
* Is it good to use git submodules to pull these weights into my code that uses them? Upside is good provenance tracking, downside is continually cloning other stuff we don't need, and submodules are not well suited to managing optional dependencies
* Do we all agree on ONNX format as best for moving between frameworks?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.