You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Log extra information on each item that is required for a task.
Description
Implementation Notes: Potential option to log extra info from task method (not necessarily from the iotaa framework). The first item yielded could contain the key name for the descriptive element. Probably want it to be optional.
When an input file that goes into the chgres_cube's namelist is missing, the user debugging experience would be improved by knowing which key path is related to the missing file. Given that we may have unrendered values in the input config, and that users don't know which keys are being checked as external assets, we'd need to dig into the driver code to understand which of the three empty-string-valued keys (lines 348-350 in the YAML example below) are turned into external assets. As it turns out, there are only two external assets that aren't ready because there's a typo in the key name that includes a '. The schema should catch this and will be fixed as part of the updates needed for SRW integration.
It's also challenging to figure out which key (orog_files_target_grid) has a value that renders to C403_oro_data.tile7.halo4.nc.
Here's an example with the interesting snippet from the full log (below):
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube namelist file fort.41: Checking requirements
[2024-10-07T21:50:19] WARNING File .: State: Not Ready (external asset)
[2024-10-07T21:50:19] WARNING File .: State: Not Ready (external asset)
[2024-10-07T21:50:19] WARNING File C403_oro_data.tile7.halo4.nc: State: Not Ready (external asset)
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube namelist file fort.41: Requirement(s) not ready
The UW YAML for the namelist section that triggered this log message:
[2024-10-07T21:50:18] INFO Validating config against internal schema: chgres-cube
[2024-10-07T21:50:18] INFO 0 UW schema-validation errors found in chgres_cube config
[2024-10-07T21:50:18] INFO Validating config against internal schema: platform
[2024-10-07T21:50:18] INFO 0 UW schema-validation errors found in platform config
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube run: Initial state: Not Ready
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube run: Checking requirements
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube run via local execution: Initial state: Not Ready
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube run via local execution: Checking requirements
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube provisioned run directory: Checking requirements
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube namelist file fort.41: Initial state: Not Ready
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube namelist file fort.41: Checking requirements
[2024-10-07T21:50:19] WARNING File .: State: Not Ready (external asset)
[2024-10-07T21:50:19] WARNING File .: State: Not Ready (external asset)
[2024-10-07T21:50:19] WARNING File C403_oro_data.tile7.halo4.nc: State: Not Ready (external asset)
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube namelist file fort.41: Requirement(s) not ready
[2024-10-07T21:50:19] WARNING 20200810 00Z chgres_cube namelist file fort.41: Final state: Not Ready**
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube runscript.chgres_cube: Initial state: Not Ready
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube runscript.chgres_cube: Checking requirements
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube runscript.chgres_cube: Requirement(s) ready
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube runscript.chgres_cube: Executing
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube runscript.chgres_cube: Final state: Ready
[2024-10-07T21:50:19] WARNING 20200810 00Z chgres_cube provisioned run directory: Final state: Not Ready
[2024-10-07T21:50:19] INFO 20200810 00Z chgres_cube run via local execution: Requirement(s) not ready
[2024-10-07T21:50:19] WARNING 20200810 00Z chgres_cube run via local execution: Final state: Not Ready
[2024-10-07T21:50:19] WARNING 20200810 00Z chgres_cube run: Final state: Not Ready
Will run in /scratch2/NAGAPE/epic/Brian.Weir/expt_dirs/grid_RRFS_CONUScompact_25km_ics_HRRR_lbcs_RAP_suite_RRFS_v1beta/2020081000/tmp_MAKE_ICS
Error occurred running chgres_cube. Please see component error logs.
The text was updated successfully, but these errors were encountered:
AC
Description
Implementation Notes: Potential option to log extra info from task method (not necessarily from the iotaa framework). The first item yielded could contain the key name for the descriptive element. Probably want it to be optional.
When an input file that goes into the chgres_cube's namelist is missing, the user debugging experience would be improved by knowing which key path is related to the missing file. Given that we may have unrendered values in the input config, and that users don't know which keys are being checked as external assets, we'd need to dig into the driver code to understand which of the three empty-string-valued keys (lines 348-350 in the YAML example below) are turned into external assets. As it turns out, there are only two external assets that aren't ready because there's a typo in the key name that includes a
'
. The schema should catch this and will be fixed as part of the updates needed for SRW integration.It's also challenging to figure out which key (
orog_files_target_grid
) has a value that renders toC403_oro_data.tile7.halo4.nc
.Here's an example with the interesting snippet from the full log (below):
The UW YAML for the namelist section that triggered this log message:
Full log for reference:
The text was updated successfully, but these errors were encountered: