Skip to content
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

[BREAKING] Remove parametric modeling code #367

Merged
merged 1 commit into from
Jan 14, 2024
Merged

[BREAKING] Remove parametric modeling code #367

merged 1 commit into from
Jan 14, 2024

Conversation

sdatkinson
Copy link
Owner

Resolves #334.

This doesn't make NAM incompatible with parametric modeling. It just moves the implementation downstream, with the intent that users would register their implementations using Model.register_net_initializer() and nam.data.register_dataset_initializer(). If you like the code I wrote, you should be able to re-register it with little trouble and continue on as you were.

This also results in some nice simplifications like the removal of the separate "export" script since all models are assumed to be compatible with the Exportable.export() interface. Now, you get the .nam model at the end of CLI training immediately without a separate step 🙂 (parametric modeling folks will need to make changes here to pull in the extra needed configuration info at the time of the model's initialization so that it can be accessed here since it's no longer an input argument to the export method.)

@sdatkinson sdatkinson merged commit 090fd22 into main Jan 14, 2024
3 checks passed
@sdatkinson sdatkinson deleted the issue-334 branch January 14, 2024 21:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Remove parametric modeling code
1 participant