Is your feature request related to a problem? Please describe.
When writing a warning or error message, FMS adds both a leading and a trailing blank line; on derecho, the cesm.log prepends the node and core writing the message leading to blocks like
dec2361.hsn.de.hpc.ucar.edu 2661:
dec2361.hsn.de.hpc.ucar.edu 2661: WARNING from PE 2149: {some warning message}
dec2361.hsn.de.hpc.ucar.edu 2661
The MARBL carbonate solver is currently printing out a very large number of warnings in coupled runs; while we hope to reduce the number of warnings, I think the cesm log would be much more readable without the "blank" lines.
Describe the solution you'd like
Just print warnings and errors to stderr() on a single line
Describe alternatives you've considered
We could leave the white space around error messages, since those will be followed by an abort they won't be nearly as numerous as the error messages
Additional context
I'm testing a fix now, and will open a PR when I confirm it works
Is your feature request related to a problem? Please describe.
When writing a warning or error message, FMS adds both a leading and a trailing blank line; on derecho, the
cesm.logprepends the node and core writing the message leading to blocks likeThe MARBL carbonate solver is currently printing out a very large number of warnings in coupled runs; while we hope to reduce the number of warnings, I think the cesm log would be much more readable without the "blank" lines.
Describe the solution you'd like
Just print warnings and errors to
stderr()on a single lineDescribe alternatives you've considered
We could leave the white space around error messages, since those will be followed by an abort they won't be nearly as numerous as the error messages
Additional context
I'm testing a fix now, and will open a PR when I confirm it works