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

tweak GROMACS demo so it doesn't fail when lots of cores are available #27

Open
boegel opened this issue Nov 14, 2023 · 2 comments
Open

Comments

@boegel
Copy link
Collaborator

boegel commented Nov 14, 2023

Our current GROMACS demo fails when a significant number of cores are available, basically we don't run enough steps:

Fatal error: PME tuning was still active when attempting to reset mdrun counters at step 500.
Try resetting counters later in the run, e.g. with gmx mdrun -resetstep.

We could simply bump the -nsteps 1000, but that's also moving the goal posts, and it will result in runs on a low number of cores to take longer.

Another option could be to try and determine how many cores are available (via the nprocs command?), and scale up the number of step being run based on that (N * 500 steps?).

@boegel
Copy link
Collaborator Author

boegel commented Nov 14, 2023

Any suggestions here @victorusu?

@al42and
Copy link

al42and commented Nov 16, 2023

One option is -notunepme to disable PME tuning, since it is unlikely to work well for short runs. Alternatively, one can set -resetstep 100 instead of -resethway, to reset the performance counters earlier, before the PME tuning kicks in.

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

No branches or pull requests

2 participants