Improve the workload flag naming consistency
More consistent and better self-documenting naming would be useful; e.g. we should make sure we use verb prefixes uniformly in StepWorkload
in particular when these flags can refer to work that may not be performed every step (e.g. those affected by computeSlowForces
).
The following discussion from !2246 (merged) should be addressed:
-
@pszilard started a discussion: (+2 comments) I agree, we should not be repeating
computeSlowForces
. The naming is perhaps not ideal; both because it does not follow the naming patters ofhaveGpuPmeOnThisRank
nor does the name seem as intuitive (i.e. if we ask "do we compute Pme On Separate Rank?", the intuitive answer is "yes" even if we only do so on some steps).We also need something like this when merging !2226 (merged) into this branch, although there a
havePmeWorkThisStep
may be more useful.