Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

output prefix METplus configuration #351

Closed
georgemccabe opened this issue Jan 8, 2020 · 0 comments
Closed

output prefix METplus configuration #351

georgemccabe opened this issue Jan 8, 2020 · 0 comments
Assignees
Labels
MET: Configuration type: enhancement Improve something that it is currently doing

Comments

@georgemccabe
Copy link
Collaborator

I added <APP_NAME>_OUTPUT_PREFIX (i.e. GRID_STAT_OUTPUT_PREFIX) in the METplus config for all MET tools that have output_prefix in their MET config files. This was done so users can configure their output prefix from the METplus config file instead of having to go into the MET config file and modify the variable.

Previously a few wrappers (GridStat, MODE, and MTD) set environment variables that were referenced in the MET config file output_prefix, like FCST_VAR, OBS_VAR, and LEVEL (which was always forecast level but unclear that it was). In these wrappers, the following METplus config variables are set for each iteration of the fcst/obs name/level loop:
CURRENT_FCST_NAME
CURRENT_FCST_LEVEL
CURRENT_OBS_NAME
CURRENT_OBS_LEVEL

These can be referenced in the [GRID_STAT/MODE/MTD]OUTPUT_PREFIX, i.e.
MODE_OUTPUT_PREFIX = {MODEL}
{CURRENT_FCST_NAME}vs{OBTYPE}{CURRENT_OBS_NAME}{CURRENT_OBS_LEVEL}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
MET: Configuration type: enhancement Improve something that it is currently doing
Projects
None yet
Development

No branches or pull requests

2 participants