Gromacs
2025.1
|
This method doesn't currently work in all cases with multipoint data or with multiple data sets. In particular, if the added module requests storage and uses getDataFrame(), it will behave unpredictably (most likely asserts).
Generalize this method to multiple data sets (e.g., for adding modules that only process a single data set).
Generalize this method to multiple data sets (e.g., for adding modules that only process a single data set).
Generalize this method to multiple data sets (e.g., for adding modules that only process a single data set).
Generalize this method to multiple data sets (e.g., for adding modules that only process a single data set).
Generalize this method to multiple data sets (e.g., for adding modules that only process a single data set).
Generalize this method to multiple data sets (e.g., for adding modules that only process a single data set).
Generalize this method to multiple data sets (e.g., for adding modules that only process a single data set).
Generalize this method to multiple data sets (e.g., for adding modules that only process a single data set).
Generalize this method to multiple data sets (e.g., for adding modules that only process a single data set).
Generalize this method to multiple data sets (e.g., for adding modules that only process a single data set).
Generalize this method to multiple data sets (e.g., for adding modules that only process a single data set).
Generalize this method to multiple data sets (e.g., for adding modules that only process a single data set).
module
requests storage (addModule() has the same problem if called after data is started). Make it such that reset() is not necessary to call in code that repeatedly assigns the result of AnalysisNeighborhood::initSearch() to the same variable (see sm_distance.cpp).
Consider removing minimumDistance(), as nearestPoint() already returns the distance.
Factor the distributed data aspects of simulation input data into the SimulationInput implementation.
Consider refactoring to decouple the checkpoint facility from its consumers (state, observablesHistory, mdModulesNotifiers, and parts of ir).
Consider refactoring to decouple the checkpoint facility from its consumers (state, observablesHistory, mdModulesNotifiers, and parts of ir).
Consider refactoring to decouple the checkpoint facility from its consumers (state, observablesHistory, mdModulesNotifiers, and parts of ir).
Remove didNeighborSearch, which is used incorrectly.
Convert all other algorithms called here to ForceProviders.
commandline
module. Reduce synchronization overhead. Some ideas are:
The use of restrict for gm_xp and gm_v causes failure, probably because of the atomic operations. Investigate this issue further.
Support for specifying that an option accepts, e.g., two to four selections. Currently, only a fixed count or any number of selections is possible.
docs/doxygen/lib/modularsimulator.md
?