You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Expose max_neighbors argument for batch_naive_neighbor_list #545
There are plenty of other examples of useful arguments in the neighbor list functions from nvalchemi-toolkit-ops. Vesin doesn't look like it has as many additional options.
A possible solution might be to support argument pass-through in torchsim_nl by including a **kwargs that gets forwarded all the way down to _batch_naive_neighbor_list. While this would throw an error if a user provides an invalid argument, it would still be quite convenient. However, I'm not sure what other areas of torch-sim it might affect.
Would be glad to look at a PR for this. I only saw this edge case in very extreme skewed unit cells we had in the old test suite and so I am unsure how common a failure mode it is. If there's a clean pathway to expose then we should expose it. Ideally we would like to try keep as much typing as possible so potentially a discriminated union of dataclasses for each of the fallbacks might be the way to do it.
Activity
CompRhys commentedon Apr 16, 2026
Would be glad to look at a PR for this. I only saw this edge case in very extreme skewed unit cells we had in the old test suite and so I am unsure how common a failure mode it is. If there's a clean pathway to expose then we should expose it. Ideally we would like to try keep as much typing as possible so potentially a discriminated union of dataclasses for each of the fallbacks might be the way to do it.