-
Notifications
You must be signed in to change notification settings - Fork 1
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
Revamped tuning #130
base: main
Are you sure you want to change the base?
Revamped tuning #130
Conversation
def grid_search( | ||
method: str, | ||
charges: torch.Tensor, |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I would turn the logic around and keep the tune_XXX
method. Also, grid_search
is a very common name. It is not really clear from this that this will find the optimal parameters for the methods.
367f147
to
f554b70
Compare
@@ -515,3 +518,82 @@ def forward(self, positions, cell, charges): | |||
print(f"Evaluation time:\nPytorch: {time_python}ms\nJitted: {time_jit}ms") | |||
|
|||
# %% | |||
# Other auto-differentiation ideas |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
IMHO opinion I wouldn't put this example here - even though I think it is good to have it. The tutorial is already 500 lines and with this super long. I rather vote for smaller examples tackling one specific tasks. Finding solutions is much easier if they are shorter. See also the beloved matplotlib examples.
This PR introduces two things:
Still more works need to be done, like writing documentations, fixing the pytests and the example, before this PR is ready.
Contributor (creator of pull-request) checklist
Reviewer checklist
📚 Documentation preview 📚: https://torch-pme--130.org.readthedocs.build/en/130/