Following uwtools integration, the workflow generation log is quite large now, and the process to generate the workflow takes a bit longer.
13M Apr 16 22:00 log.generate_FV3LAM_wflow
There appears to be some jinja debugging flag turned on? Miles of dereferencing statements:
...
root DEBUG [dereference] memory: 120G
root DEBUG [dereference] nodes: 1
root DEBUG [dereference] tasks_per_node: 1
root DEBUG [dereference] walltime: 00:30:00
...
I'm wondering if the longer runtime is related to this as well. The log is a bit much to digest now. Would we want to turn off this debug output by default?
Expected behavior
- Reduce log file size by limiting debug output.
Current behavior
- A lot of debug output that is mostly irrelevant to users unless debugging jinja.
Machines affected
- Current SRW develop branch.
Steps To Reproduce
Following
uwtoolsintegration, the workflow generation log is quite large now, and the process to generate the workflow takes a bit longer.There appears to be some jinja debugging flag turned on? Miles of dereferencing statements:
I'm wondering if the longer runtime is related to this as well. The log is a bit much to digest now. Would we want to turn off this debug output by default?
Expected behavior
Current behavior
Machines affected
Steps To Reproduce