[rrfs-nco] Add a clear WARNING message for missing RAVE data#1566
[rrfs-nco] Add a clear WARNING message for missing RAVE data#1566ShunLiu-NOAA wants to merge 1 commit into
Conversation
|
@ShunLiu-NOAA there are other warning prints in the python code. I started some work on it (on dogwood) as /lfs/h2/emc/lam/noscrub/Matthew.Pyle/rrfs-workflow_ravefix/ush/generate_fire_emissions.py, but haven't finished it yet. |
@MatthewPyle-NOAA , @WeiWei-NCO and @JamesPolly-NCO , Will it be clear enough if we only give one WARNING from "exrrfs_process_smoke.sh"? |
|
@ShunLiu-NOAA thank you for checking. We recently made some changes to the process_smoke jobs that result in both an email and warning messages in the output job log (example path shown below). I personally feel that no more functionality is needed here given these updates. /lfs/h1/ops/test/output/20260623/rrfs_det_process_smoke_spinup_03.o270526814 |
|
@JamesPolly-NCO To clarify, does generate_fire_emissions.py handle the warning adequately on its own, meaning we don't need to update exrrfs_process_smoke.sh? Additionally, I don't think we need to email this warning message to the team. The workflow should continue running successfully even without this job. |
|
@ShunLiu-NOAA Let's separate your concerns:
|
|
Thanks for the clarification. I'll go ahead and close this PR. |
DESCRIPTION OF CHANGES:
TESTS CONDUCTED:
Machines/Platforms:
Test cases:
ISSUE:
CONTRIBUTORS (optional):