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
Describe the behavior you would like added to mBuild
Need to make the jump to numpy 2.0. This should happen across all of the MoSDeF packages. Here is a link to the migration guide.
Describe the solution you'd like
Support for numpy 2.0.
Describe alternatives you've considered
N/A
Additional context
A few things that are preventing an immediate change
I haven't looked into numpy 2.0 that much yet. Do you know if there are changes that give improved performance, and might require some refactoring on our end to take advantage of that, or are most of the changes API related?
As far as I can tell, the main changes relevant to this package are API improvements and further extensibility of the codebase. Performance improvements include some better sorting functions, numpy.save pickling, and some stuff for macOS >=14.
Some of the dependencies that more heavily rely on numpy, such as openMM and parmed see some improvements. When I was lookiing through their code, OpenMM mentioned improved energy minimization, which would be great.
Describe the behavior you would like added to mBuild
Need to make the jump to numpy 2.0. This should happen across all of the MoSDeF packages. Here is a link to the migration guide.
Describe the solution you'd like
Support for numpy 2.0.
Describe alternatives you've considered
N/A
Additional context
A few things that are preventing an immediate change
The text was updated successfully, but these errors were encountered: