We would like to support setting MET config variables through the wrappers for values that are likely to be changed from the default. This will reduce the need for user's to create their own wrapped MET config files to configure.

Here is a list of variables from @malloryprow that she has changed:

GridStat: model, desc, obtype, regrid, fcst, obs, climo_mean, mask,
fourier, output_flag, grid_weight_flag, tmp_dir, output_prefix, version
StatAnalysis: model, fcst_lead, fcst_valid_beg, fcst_valid_end,
fcst_valid_hour, fcst_init_beg, fcst_init_end, fcst_init_hour, fcst_var,
obs_var, fcst_lev, obs_lev, obtype, vx_mask, interp_mthd, fcst_thresh,
line_type, jobs, tmp_dir, version
PB2NC: message_type, obs_window, pb_report_type, level_category,
obs_bufr_var, obs_prepbufr_map, quality_mark_thresh, tmp_dir, version
PointStat: model, regrid, fcst, obs, message_type, obs_window, mask,
output_flag, tmp_dir, version
TcPairs: model, storm_id, basin, cyclone, storm_name, init_beg, init_end,
init_inc, init_exc, valid_beg, valid_end, check_dup, interp12,
match_points, version
SerisAnalysis: model, obtype, regrid, fcst, obs, block_size,
output_stats, tmp_dir, version

Describe the Enhancement

Add support for setting environment variables from METplus config settings.

Time Estimate

3 days - we should divide this into sub-tasks for different tools.

Sub-Issues

Consider breaking the enhancement down into sub-issues.

• Add a checkbox for each sub-issue here.

Relevant Deadlines

Ideally for 4.0.0

Funding Source

2791541 and 2799991

Define the Metadata

Assignee

• Select engineer(s) or no engineer required
• Select scientist(s) or no scientist required

Labels

• Select component(s)
• Select priority
• Select requestor(s)

Projects and Milestone

• Review projects and select relevant Repository and Organization ones or add "alert:NEED PROJECT ASSIGNMENT" label
• Select milestone to next major version milestone or "Future Versions"

Define Related Issue(s)

Consider the impact to the other METplus components.

• METplus, MET, METdatadb, METviewer, METexpress, METcalcpy, METplotpy

Enhancement Checklist

See the METplus Workflow for details.

• Complete the issue definition above, including the Time Estimate and Funding Source.
• Fork this repository or create a branch of develop.
  Branch name: feature_<Issue Number>_<Description>
• Complete the development and test your changes.
• Add/update log messages for easier debugging.
• Add/update unit tests.
• Add/update documentation.
• Push local changes to GitHub.
• Submit a pull request to merge into develop.
  Pull request: feature <Issue Number> <Description>
• Define the pull request metadata, as permissions allow.
  Select: Reviewer(s), Project(s), Milestone, and Linked issues
• Iterate until the reviewer(s) accept and merge your changes.
• Delete your fork or branch.
• Close this issue.