Closed georgemccabe closed 4 months ago
@georgemccabe Also please note that the following was also written out as part of this bug (or separate) - but also saw this using the beta versions:
PB2NC_SKIP_TIMES is deprecated. Please use PB2NC_SKIP_VALID_TIMES
Is this something we should be changing on our end?
Thanks!
Perry
@PerryShafran-NOAA, yes, you should change any instance of PB2NC_SKIP_TIMES
to PB2NC_SKIP_VALID_TIMES
to resolve those warnings. The wrappers now support skipping times based in initialization times as well, so the config variables were renamed to be more explicit.
@georgemccabe Thank you! Here are some other warnings noticed during our test:
WARNING: Both POINT_STAT_CLIMO_MEAN_INPUT_TEMPLATE and POINT_STAT_CLIMO_MEAN_FILE_NAME are set. Using value set in POINT_STAT_CLIMO_MEAN_FILENAME (/lfs/h2/emc/vpppg/noscrub/emc.vpppg/EVS/fix/climos/atmos/era5/mean{valid?fmt=%m%d})
WARNING: Both POINT_STAT_CLIMO_STDEV_INPUT_TEMPLATE and POINT_STAT_CLIMO_STDEV_FILE_NAME are set. Using value set in POINT_STAT_CLIMO_STDEV_FILENAME (/lfs/h2/ emc/vpppg/noscrub/emc.vpppg/EVS/fix/climos/atmos/era5/stdev{valid?fmt=%m%d}).
WARNING: Both GRID_STAT_CLIMO_MEAN_INPUT_TEMPLATE and GRID_STAT_CLIMO_MEAN_FILE_NAME are set. Using value set in GRID_STAT_CLIMO_MEAN_FILE_NAME (/lfs/h2/emc/vpppg/noscrub/emc.vpppg/EVS/fix/climos/atmos/ccpa/ccpa_24hr_1p0prob{valid?fmt=%m%d}.grib2).
Can you comment on these?
Should we open a GitHub Discussion for these? These aren't related to the ASCII2NC file window issue.
Yes, @PerryShafran-NOAA , could you please create a new METplus Discussion and I can address these warnings there?
Done. These have already been commented on in a separate email exchange, but the discussion is better had on the METplus discussion page.
The warnings relating to the climo variables ending with _INPUT_TEMPLATE
and _FILE_NAME
can appear due to the bug described in this issue when the _FILE_NAME
variables are not set.
While testing the METplus 6.0.0-beta3 release, @malloryprow discovered a bug:
Describe the Problem
A quick solution would be to change the logic in ascii2nc_wrapper that handles file_window variables to use the function that handles it from command_builder. However, it appears that the wrapper initialization is run twice -- once when checking for deprecated environment variables and again to set up the wrapper to run. The first initialization is run just to get the class variable that holds the list of deprecated environment variables. That logic should be updated to read the class variable without initializing the wrapper, since a class variable can be read without creating an instance of it.
Expected Behavior
Running an ASCII2NC use case with
ASCII2NC_FILE_WINDOW_BEGIN
andASCII2NC_FILE_WINDOW_END
unset should run without error.Environment
Describe your runtime environment: 1. Machine: (e.g. HPC name, Linux Workstation, Mac Laptop) 2. OS: (e.g. RedHat Linux, MacOS) 3. Software version number(s)
To Reproduce
Describe the steps to reproduce the behavior: 1. Go to '...' 2. Click on '....' 3. Scroll down to '....' 4. See error Post relevant sample data following these instructions: https://dtcenter.org/community-code/model-evaluation-tools-met/met-help-desk#ftp
Relevant Deadlines
List relevant project deadlines here or state NONE.
Funding Source
Define the source of funding and account keys here or state NONE.
Define the Metadata
Assignee
Labels
Projects and Milestone
Define Related Issue(s)
Consider the impact to the other METplus components.
Bugfix Checklist
See the METplus Workflow for details.
bugfix_<Issue Number>_main_<Version>_<Description>
bugfix <Issue Number> main_<Version> <Description>
bugfix_<Issue Number>_develop_<Description>
Pull request:bugfix <Issue Number> develop <Description>
Select: Reviewer(s) and Development issues Select: Repository level development cycle Project for the next official release Select: Milestone as the next official version