ESCOMP / ESCOMP/mizuRoute

Controlling mizuRoute Output Related to Water Balance Print, and Possibility of Keeping Them in Output Files

Open
#538 3 comments 1 reaction 0 assignees View on GitHub
bug question
Dominant language
Fortran
Stars
59
Forks
73
Avg merge
5d 22h
Merged PRs (30d)
2

Description

Hi @nmizukami,

It appears we're encountering an issue where the processor hangs after a successful mizuRoute simulation. From what I can tell, this is likely caused by excessive output being written to the log file (inside Python) — particularly due to a large number of warning messages printed at each time step for segments and lakes exceeding the water balance tolerance.

I also came across the `checkMassBalance` flag in the control file. However, it’s unclear whether this flag is intended to control verbosity, or if it only activates the mass balance check logic internally without affecting print behavior (for example, this [line](https://github.com/ESCOMP/mizuRoute/blob/cesm-coupling/route/build/src/water_balance.f90#L90) can still print even if verbose is false).

Do we currently have such an output feature in mizuRoute? I couldn’t find anything related in the control file, but I apologize if I’ve overlooked something. It would be very useful to have the water balance, per seg and time, and also per segment for the entire simulation time, in the output file.

Thank you in advance!

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.