Better log outputs for ecm_prep.py

trynthink / scout

A tool for estimating the future energy use, carbon emissions, and capital and operating cost impacts of energy efficiency and demand flexibility technologies in the U.S. residential and commercial building sectors.

https://scout.energy.gov

Other

61 stars 23 forks source link

Better log outputs for ecm_prep.py #404

Open aspeake opened 2 months ago

aspeake commented 2 months ago

To help with debugging, update the following behavior for log messages:

write the ecm_prep log file (added here: https://github.com/trynthink/scout/pull/402) to CI artifacts after the integration test is run.
Enable log messages in ecm_prep.py to be optionally output to the console with the --verbose argument

trynthink commented 2 months ago

@aspeake We also discussed exposing the log file contents in the STDOUT so that it would be immediately visible in the runner logs, possibly by using verbose mode (which doesn't currently have this behavior, but could be changed to support it). Did you conclude that it would be preferable to write the log file as an artifact instead?

aspeake commented 2 months ago

@aspeake We also discussed exposing the log file contents in the STDOUT so that it would be immediately visible in the runner logs, possibly by using verbose mode (which doesn't currently have this behavior, but could be changed to support it). Did you conclude that it would be preferable to write the log file as an artifact instead?

Actually we did decide to output to the console with --verbose, I updated the issue to address both