use maximum rather than minimum decimation factor for DFT convergence criteria #1796
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
The
stop_when_dft_decayed
convergence-criteria function introduced in #1740 uses a measurement interval (in number of timesteps) which is the maximum of two quantities: (1) the period of the largest frequency or (2) the smallest DFT decimation factor. However, (2) is incorrect because it could mean that not all the DFT fields have been updated before checking for convergence. The correct approach would be to use the largest DFT decimation factor.