Project

General

Profile

Bug #2789

mdrun gives error about input when GPU hardware does not support PME

Added by Berk Hess 9 months ago. Updated 6 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
mdrun
Target version:
Affected version - extra info:
Affected version:
Difficulty:
uncategorized
Close

Description

There are separate checks for hardware and input support for PME on GPU, but the results are merged in a single boolean and the error message printed later always complains about the input, even when the input does support PME but the build or GPU does not.

Additionally, all error message of GPU support issues for non-bonded, bonded and PME are never used and printed, so it's difficult for the user to diagnose anything. My fix for #2779 at least prints the input issue for GPU PME to the log file.


Related issues

Related to GROMACS - Bug #2823: mdrun issues note about input not supporting a GPU with a non-GPU buildClosed

Associated revisions

Revision 0b84efb5 (diff)
Added by Mark Abraham 6 months ago

Improved diagnostics when PME cannot run on GPUs

Fixes #2789, #2823

Change-Id: Iff7609a3774c11329d36bd8557b741a4d29f7c5a

History

#1 Updated by Mark Abraham 8 months ago

  • Status changed from New to Feedback wanted

Berk, can you clarify "and the error message printed later always complains about the input, even when the input does support PME but the build or GPU does not" please?

On a non-GPU build with a normal PME .tpr, I get

GROMACS:      gmx mdrun, version 2019.1-dev-20190102-75ad9eb22
Executable:   /home/marklocal/git/r2019/build-cmake-clang-debug/install/bin/gmx
Data prefix:  /home/marklocal/git/r2019/build-cmake-clang-debug/install
Working dir:  /tmp
Command line:
  gmx mdrun -nb gpu

Reading file topol.tpr, VERSION 2016-beta1-dev-20160524-3a9e67d (single precision)
Note: file tpx version 110, software tpx version 116

-------------------------------------------------------
Program:     gmx mdrun, version 2019.1-dev-20190102-75ad9eb22
Source file: src/gromacs/taskassignment/decidegpuusage.cpp (line 263)
Function:    bool gmx::decideWhetherToUseGpusForNonbonded(const gmx::TaskTarget, const std::vector<int> &, const EmulateGpuNonbonded, const bool, const bool, const bool, const bool)

Inconsistency in user input:
Nonbonded interactions on the GPU were requested with -nb gpu, but the GROMACS
binary has been built without GPU support. Either run without selecting GPU
options, or recompile GROMACS with GPU support enabled

For more information and tips for troubleshooting, please check the GROMACS
website at http://www.gromacs.org/Documentation/Errors
-------------------------------------------------------

I definitely agree that the user reporting can be improved in general.

#2 Updated by Berk Hess 8 months ago

  • Related to Bug #2823: mdrun issues note about input not supporting a GPU with a non-GPU build added

#3 Updated by Mark Abraham 8 months ago

Some relevant code was at https://gerrit.gromacs.org/#/c/8782/ but the overall patch was abandoned

#4 Updated by Berk Hess 8 months ago

I thought I had a different message, but what I can generate now is:

With opencl and nvidia and -pme gpu:
Feature not implemented:
The input simulation did not use PME in a way that is supported on the GPU.

Without GPU support and -pme gpu with(out) -nb gpu:
Feature not implemented:
The PME on the GPU is only supported when nonbonded interactions run on GPUs
also.

The code separate checks for build and input support. If the build has no (PME) GPU support, mdrun should note this and not mention the input.

#5 Updated by Mark Abraham 7 months ago

  • Assignee set to Mark Abraham
  • Target version set to 2019.1

#6 Updated by Gerrit Code Review Bot 6 months ago

Gerrit received a related patchset '1' for Issue #2789.
Uploader: Mark Abraham ()
Change-Id: gromacs~release-2019~Iff7609a3774c11329d36bd8557b741a4d29f7c5a
Gerrit URL: https://gerrit.gromacs.org/9158

#7 Updated by Mark Abraham 6 months ago

  • Status changed from Feedback wanted to Fix uploaded

#8 Updated by Mark Abraham 6 months ago

  • Status changed from Fix uploaded to Resolved

#9 Updated by Paul Bauer 6 months ago

  • Status changed from Resolved to Closed

Also available in: Atom PDF