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.
Issue addressed
Explanation
If dtmaxout is larger then tstop-tstart, SFINCS writes the maximum outputs over the entire simulation. However, if dtmaxout is smaller than this, it only seems to write the outputs for the 2nd and higher intervals if the entire interval passed. The default value of the dtmaxout was 99999, which is only slightly more than 1 day. For simulations longer than 1 day, but less than x*99999, with the peak water levels in the x'th interval, this resulted in missing the peak water levels in the zsmax output.
Checklist
main
Additional Notes (optional)
The new default value might still be small? Are there more elegant ways to do this, instead of just making it even bigger? And shouldn't we ensure in SFINCS that even when the last interval is not fully finished, it still writes away the maximum outputs over the unfinished interval?