[Met_help] [rt.rap.ucar.edu #100108] History for config file changes for MET 10.0.0
George McCabe via RT
met_help at ucar.edu
Mon Jul 12 12:24:43 MDT 2021
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hi, all,
I'm trying to convert to MET 10.0.0, and it looks like things have changed
for the MET config files. Can you take a look at my config files and
explain what would need to be changed? I think you had discussed this
before in a prior METplus user's meeting, but that was so long ago that I
don't quite remember.
The files to examine are both in the directory:
/gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-4.0.0/parm/met_config
and would be PB2NCConfig_cam and PointStatConfig_cam.
What would be the best resource to compare the old with the new? Can you
find that in the User's Guide?
Thanks!
Perry
--
Perry C. Shafran
Verification/MEG Group Leader for IMSG
VPPPG Branch of EMC/NCEP/NOAA/NWS
Office: 301-683-3765
Cell: 301-717-6454
(he/him/his)
perry.shafran at noaa.gov
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: config file changes for MET 10.0.0
From: perry.shafran at noaa.gov
Time: Fri Jun 04 09:27:04 2021
I think that I'm OK - the problem is that I had a directory set wrong.
I
am running now and think that nothing needs to be changed.
Thanks!
Perry
On Fri, Jun 4, 2021 at 11:18 AM met_help at ucar.edu via RT
<met_help at ucar.edu>
wrote:
> ***** ALERT: We are transitioning support of the METplus
verification
> system from met_help at ucar.edu to the GitHub Discussions forum in the
> METplus repository (https://github.com/dtcenter/METplus/discussions)
and
> plan to fully transition to Discussions in July, 2021. Users are
welcome
> and encouraged to answer or address each other’s questions there!
For more
> information, please read “Welcome to the METplus Components
Discussions!” (
> https://github.com/dtcenter/METplus/discussions/939). *****
>
> Greetings,
>
> This message has been automatically generated in response to the
creation
> of a trouble ticket regarding:
> "config file changes for MET 10.0.0",
> a summary of which appears below.
>
> There is no need to reply to this message right now. Your ticket
has been
> assigned an ID of [rt.rap.ucar.edu #100108].
>
> Please include the string:
>
> [rt.rap.ucar.edu #100108]
>
> in the subject line of all future correspondence about this issue.
To do
> so, you may reply to this message.
>
> For more information, please see:
>
> MET Online Tutorial:
>
> https://dtcenter.org/community-code/model-evaluation-tools-
met/online-tutorial
>
> MET Users Guide:
> https://www.dtcenter.org/met/users/docs/overview.php
>
> MET FAQs:
> https://dtcenter.org/community-code/model-evaluation-tools-
met/faqs
>
> MET-Help Email Archive:
> http://mailman.ucar.edu/pipermail/met_help
>
> Thank you,
> met_help at ucar.edu
>
>
-------------------------------------------------------------------------
> Hi, all,
>
> I'm trying to convert to MET 10.0.0, and it looks like things have
changed
> for the MET config files. Can you take a look at my config files
and
> explain what would need to be changed? I think you had discussed
this
> before in a prior METplus user's meeting, but that was so long ago
that I
> don't quite remember.
>
> The files to examine are both in the directory:
>
>
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
>
> and would be PB2NCConfig_cam and PointStatConfig_cam.
>
> What would be the best resource to compare the old with the new?
Can you
> find that in the User's Guide?
>
> Thanks!
>
> Perry
>
> --
> Perry C. Shafran
> Verification/MEG Group Leader for IMSG
> VPPPG Branch of EMC/NCEP/NOAA/NWS
> Office: 301-683-3765
> Cell: 301-717-6454
> (he/him/his)
> perry.shafran at noaa.gov
>
>
--
Perry C. Shafran
Verification/MEG Group Leader for IMSG
VPPPG Branch of EMC/NCEP/NOAA/NWS
Office: 301-683-3765
Cell: 301-717-6454
(he/him/his)
perry.shafran at noaa.gov
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: John Opatz
Time: Fri Jun 04 10:19:37 2021
Hi Perry,
Glad to hear this was just a path error and not something more.
If you do have future questions about the changes to configuration
files in
new METplus releases, you can see all of the updates here
<https://metplus.readthedocs.io/en/latest/Users_Guide/release-
notes.html>,
in the Release Notes section of the METplus User's Guide. For METplus
4.0.0, the first item under Bugfixes is "Changed default values in
wrapped
MET config files to align with actual default values in MET config
files",
which links to a section describing all of the wrapper configuration
updates. There's also a few Github issues in the Enhancement section
that
concern changes to available configuration variables.
If you don't have any further issues at this time, I'll go ahead and
close
this ticket.
-John O.
On Fri, Jun 4, 2021 at 9:27 AM perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
>
> I think that I'm OK - the problem is that I had a directory set
wrong. I
> am running now and think that nothing needs to be changed.
>
> Thanks!
>
> Perry
>
> On Fri, Jun 4, 2021 at 11:18 AM met_help at ucar.edu via RT <
> met_help at ucar.edu>
> wrote:
>
> > ***** ALERT: We are transitioning support of the METplus
verification
> > system from met_help at ucar.edu to the GitHub Discussions forum in
the
> > METplus repository
(https://github.com/dtcenter/METplus/discussions) and
> > plan to fully transition to Discussions in July, 2021. Users are
welcome
> > and encouraged to answer or address each other’s questions there!
For
> more
> > information, please read “Welcome to the METplus Components
> Discussions!” (
> > https://github.com/dtcenter/METplus/discussions/939). *****
> >
> > Greetings,
> >
> > This message has been automatically generated in response to the
creation
> > of a trouble ticket regarding:
> > "config file changes for MET 10.0.0",
> > a summary of which appears below.
> >
> > There is no need to reply to this message right now. Your ticket
has
> been
> > assigned an ID of [rt.rap.ucar.edu #100108].
> >
> > Please include the string:
> >
> > [rt.rap.ucar.edu #100108]
> >
> > in the subject line of all future correspondence about this issue.
To do
> > so, you may reply to this message.
> >
> > For more information, please see:
> >
> > MET Online Tutorial:
> >
> >
> https://dtcenter.org/community-code/model-evaluation-tools-
met/online-tutorial
> >
> > MET Users Guide:
> > https://www.dtcenter.org/met/users/docs/overview.php
> >
> > MET FAQs:
> > https://dtcenter.org/community-code/model-evaluation-tools-
met/faqs
> >
> > MET-Help Email Archive:
> > http://mailman.ucar.edu/pipermail/met_help
> >
> > Thank you,
> > met_help at ucar.edu
> >
> >
-------------------------------------------------------------------------
> > Hi, all,
> >
> > I'm trying to convert to MET 10.0.0, and it looks like things have
> changed
> > for the MET config files. Can you take a look at my config files
and
> > explain what would need to be changed? I think you had discussed
this
> > before in a prior METplus user's meeting, but that was so long ago
that I
> > don't quite remember.
> >
> > The files to examine are both in the directory:
> >
> >
> >
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
> >
> > and would be PB2NCConfig_cam and PointStatConfig_cam.
> >
> > What would be the best resource to compare the old with the new?
Can you
> > find that in the User's Guide?
> >
> > Thanks!
> >
> > Perry
> >
> > --
> > Perry C. Shafran
> > Verification/MEG Group Leader for IMSG
> > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > Office: 301-683-3765
> > Cell: 301-717-6454
> > (he/him/his)
> > perry.shafran at noaa.gov
> >
> >
>
> --
> Perry C. Shafran
> Verification/MEG Group Leader for IMSG
> VPPPG Branch of EMC/NCEP/NOAA/NWS
> Office: 301-683-3765
> Cell: 301-717-6454
> (he/him/his)
> perry.shafran at noaa.gov
>
>
--
John Opatz
Associate Scientist III
NCAR RAL and DTC
Boulder, Colorado
+1 303-497-8305
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: perry.shafran at noaa.gov
Time: Fri Jun 04 10:24:17 2021
Yes, please close, and feel free to forget that this ticket ever
existed.
;)
All looks to be working well.
Perry
On Fri, Jun 4, 2021 at 12:19 PM John Opatz via RT <met_help at ucar.edu>
wrote:
> Hi Perry,
>
> Glad to hear this was just a path error and not something more.
>
> If you do have future questions about the changes to configuration
files in
> new METplus releases, you can see all of the updates here
> <https://metplus.readthedocs.io/en/latest/Users_Guide/release-
notes.html>,
> in the Release Notes section of the METplus User's Guide. For
METplus
> 4.0.0, the first item under Bugfixes is "Changed default values in
wrapped
> MET config files to align with actual default values in MET config
files",
> which links to a section describing all of the wrapper configuration
> updates. There's also a few Github issues in the Enhancement section
that
> concern changes to available configuration variables.
>
> If you don't have any further issues at this time, I'll go ahead and
close
> this ticket.
>
> -John O.
>
> On Fri, Jun 4, 2021 at 9:27 AM perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> >
> > I think that I'm OK - the problem is that I had a directory set
wrong. I
> > am running now and think that nothing needs to be changed.
> >
> > Thanks!
> >
> > Perry
> >
> > On Fri, Jun 4, 2021 at 11:18 AM met_help at ucar.edu via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > ***** ALERT: We are transitioning support of the METplus
verification
> > > system from met_help at ucar.edu to the GitHub Discussions forum in
the
> > > METplus repository
(https://github.com/dtcenter/METplus/discussions)
> and
> > > plan to fully transition to Discussions in July, 2021. Users are
> welcome
> > > and encouraged to answer or address each other’s questions
there! For
> > more
> > > information, please read “Welcome to the METplus Components
> > Discussions!” (
> > > https://github.com/dtcenter/METplus/discussions/939). *****
> > >
> > > Greetings,
> > >
> > > This message has been automatically generated in response to the
> creation
> > > of a trouble ticket regarding:
> > > "config file changes for MET 10.0.0",
> > > a summary of which appears below.
> > >
> > > There is no need to reply to this message right now. Your
ticket has
> > been
> > > assigned an ID of [rt.rap.ucar.edu #100108].
> > >
> > > Please include the string:
> > >
> > > [rt.rap.ucar.edu #100108]
> > >
> > > in the subject line of all future correspondence about this
issue. To
> do
> > > so, you may reply to this message.
> > >
> > > For more information, please see:
> > >
> > > MET Online Tutorial:
> > >
> > >
> >
> https://dtcenter.org/community-code/model-evaluation-tools-
met/online-tutorial
> > >
> > > MET Users Guide:
> > > https://www.dtcenter.org/met/users/docs/overview.php
> > >
> > > MET FAQs:
> > > https://dtcenter.org/community-code/model-evaluation-tools-
met/faqs
> > >
> > > MET-Help Email Archive:
> > > http://mailman.ucar.edu/pipermail/met_help
> > >
> > > Thank you,
> > > met_help at ucar.edu
> > >
> > >
>
-------------------------------------------------------------------------
> > > Hi, all,
> > >
> > > I'm trying to convert to MET 10.0.0, and it looks like things
have
> > changed
> > > for the MET config files. Can you take a look at my config
files and
> > > explain what would need to be changed? I think you had
discussed this
> > > before in a prior METplus user's meeting, but that was so long
ago
> that I
> > > don't quite remember.
> > >
> > > The files to examine are both in the directory:
> > >
> > >
> > >
> >
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
> > >
> > > and would be PB2NCConfig_cam and PointStatConfig_cam.
> > >
> > > What would be the best resource to compare the old with the new?
Can
> you
> > > find that in the User's Guide?
> > >
> > > Thanks!
> > >
> > > Perry
> > >
> > > --
> > > Perry C. Shafran
> > > Verification/MEG Group Leader for IMSG
> > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > Office: 301-683-3765
> > > Cell: 301-717-6454
> > > (he/him/his)
> > > perry.shafran at noaa.gov
> > >
> > >
> >
> > --
> > Perry C. Shafran
> > Verification/MEG Group Leader for IMSG
> > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > Office: 301-683-3765
> > Cell: 301-717-6454
> > (he/him/his)
> > perry.shafran at noaa.gov
> >
> >
>
> --
> John Opatz
> Associate Scientist III
> NCAR RAL and DTC
> Boulder, Colorado
> +1 303-497-8305
>
>
--
Perry C. Shafran
Verification/MEG Group Leader for IMSG
VPPPG Branch of EMC/NCEP/NOAA/NWS
Office: 301-683-3765
Cell: 301-717-6454
(he/him/his)
perry.shafran at noaa.gov
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: John Halley Gotway
Time: Mon Jun 07 09:44:55 2021
Perry,
There have been no changes to the PB2NC config file between MET
version 9.1
and 10.0.0. Personally, I think the easiest way to see changes is to
just
diff the default PB2NC configuration files between those versions.
*diff met-9.1/data/config/PB2NCConfig_default
met-10.0.0/data/config/PB2NCConfig_default*
5c5
< // For additional information, see the MET_BASE/config/README file.
---
> // For additional information, please see the MET User's Guide.
156c156
< version = "V9.1";
---
> version = "V10.0.0";
You see the only differences are in comments and the version number
listed.
When the MET tools are run with a config file, they compare the
version
number listed in the config file to the current version of the code
being
run. If the minor version numbers differ (e.g. 9.0 vs 9.1), it'll run
without complaining. If the major version numbers differ (e.g. 9
versus
10), it'll tell you about that difference. The purpose for this is to
alert
users that as software version numbers change, the config files may
have as
well. So they should check.
In this case, they haven't.
You have 2 choices. You could either change "V9.1" to "V10.0.0" in the
config file... or you could just comment out that "version" line. If
you do
the latter, then you'll no longer receive that warning message in
future
versions. Instead, when pb2nc runs, it'll read it's default config
file
which defines the version string... and then it'll read your user-
specific
config file. If "version" is comment out in your config file, it won't
override the default string... and that's why the warning will be
suppressed.
Thanks,
John
On Fri, Jun 4, 2021 at 9:26 AM perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> Fri Jun 04 09:18:47 2021: Request 100108 was acted upon.
> Transaction: Ticket created by perry.shafran at noaa.gov
> Queue: met_help
> Subject: config file changes for MET 10.0.0
> Owner: Nobody
> Requestors: perry.shafran at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
>
>
> Hi, all,
>
> I'm trying to convert to MET 10.0.0, and it looks like things have
changed
> for the MET config files. Can you take a look at my config files
and
> explain what would need to be changed? I think you had discussed
this
> before in a prior METplus user's meeting, but that was so long ago
that I
> don't quite remember.
>
> The files to examine are both in the directory:
>
>
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
>
> and would be PB2NCConfig_cam and PointStatConfig_cam.
>
> What would be the best resource to compare the old with the new?
Can you
> find that in the User's Guide?
>
> Thanks!
>
> Perry
>
> --
> Perry C. Shafran
> Verification/MEG Group Leader for IMSG
> VPPPG Branch of EMC/NCEP/NOAA/NWS
> Office: 301-683-3765
> Cell: 301-717-6454
> (he/him/his)
> perry.shafran at noaa.gov
>
>
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: George McCabe
Time: Mon Jun 07 09:51:47 2021
Hi Perry,
Are these paths on WCOSS? If so, could you send me the config files?
With the new approach, you will no longer have to create your own
wrapped
config files. You will always use the versions in the METplus
repository
(parm/met_config). Many of the settings that you would change are now
supported via the METplus config files and any that are not can be set
in
the METplus config file as well. Your _cam config files should still
work
the same as they did before, but it would be a good idea to update
your
METplus configs to avoid using them.
I will write up some suggestions to update your config files to use
the new
approach and reply here with the steps. If you'd prefer, we could set
up a
working session to go through them.
Thanks,
George
On Fri, Jun 4, 2021 at 9:26 AM perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> Fri Jun 04 09:18:47 2021: Request 100108 was acted upon.
> Transaction: Ticket created by perry.shafran at noaa.gov
> Queue: met_help
> Subject: config file changes for MET 10.0.0
> Owner: Nobody
> Requestors: perry.shafran at noaa.gov
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
>
>
> Hi, all,
>
> I'm trying to convert to MET 10.0.0, and it looks like things have
changed
> for the MET config files. Can you take a look at my config files
and
> explain what would need to be changed? I think you had discussed
this
> before in a prior METplus user's meeting, but that was so long ago
that I
> don't quite remember.
>
> The files to examine are both in the directory:
>
>
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
>
> and would be PB2NCConfig_cam and PointStatConfig_cam.
>
> What would be the best resource to compare the old with the new?
Can you
> find that in the User's Guide?
>
> Thanks!
>
> Perry
>
> --
> Perry C. Shafran
> Verification/MEG Group Leader for IMSG
> VPPPG Branch of EMC/NCEP/NOAA/NWS
> Office: 301-683-3765
> Cell: 301-717-6454
> (he/him/his)
> perry.shafran at noaa.gov
>
>
--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
---
My working day may not be your working day. Please do not feel obliged
to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: perry.shafran at noaa.gov
Time: Mon Jun 07 09:54:26 2021
This ticket should be closed by now. John O answered this and closed
the
ticket after I realized that my problem is that I had a directory
mislabeled in my script. Once I fixed that to work in the proper
directory, I had no further problems. There is no need for any
further
action on this question.
Thanks!
Perry
On Mon, Jun 7, 2021 at 11:51 AM George McCabe via RT
<met_help at ucar.edu>
wrote:
> Hi Perry,
>
> Are these paths on WCOSS? If so, could you send me the config files?
>
> With the new approach, you will no longer have to create your own
wrapped
> config files. You will always use the versions in the METplus
repository
> (parm/met_config). Many of the settings that you would change are
now
> supported via the METplus config files and any that are not can be
set in
> the METplus config file as well. Your _cam config files should still
work
> the same as they did before, but it would be a good idea to update
your
> METplus configs to avoid using them.
>
> I will write up some suggestions to update your config files to use
the new
> approach and reply here with the steps. If you'd prefer, we could
set up a
> working session to go through them.
>
> Thanks,
> George
>
> On Fri, Jun 4, 2021 at 9:26 AM perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > Fri Jun 04 09:18:47 2021: Request 100108 was acted upon.
> > Transaction: Ticket created by perry.shafran at noaa.gov
> > Queue: met_help
> > Subject: config file changes for MET 10.0.0
> > Owner: Nobody
> > Requestors: perry.shafran at noaa.gov
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> >
> >
> > Hi, all,
> >
> > I'm trying to convert to MET 10.0.0, and it looks like things have
> changed
> > for the MET config files. Can you take a look at my config files
and
> > explain what would need to be changed? I think you had discussed
this
> > before in a prior METplus user's meeting, but that was so long ago
that I
> > don't quite remember.
> >
> > The files to examine are both in the directory:
> >
> >
> >
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
> >
> > and would be PB2NCConfig_cam and PointStatConfig_cam.
> >
> > What would be the best resource to compare the old with the new?
Can you
> > find that in the User's Guide?
> >
> > Thanks!
> >
> > Perry
> >
> > --
> > Perry C. Shafran
> > Verification/MEG Group Leader for IMSG
> > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > Office: 301-683-3765
> > Cell: 301-717-6454
> > (he/him/his)
> > perry.shafran at noaa.gov
> >
> >
>
> --
> George McCabe - Software Engineer III
> National Center for Atmospheric Research
> Research Applications Laboratory
> 303-497-2768
> ---
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
>
--
Perry C. Shafran
Verification/MEG Group Leader for IMSG
VPPPG Branch of EMC/NCEP/NOAA/NWS
Office: 301-683-3765
Cell: 301-717-6454
(he/him/his)
perry.shafran at noaa.gov
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: George McCabe
Time: Mon Jun 07 10:22:41 2021
Hi Perry,
It is good to hear that your issue was resolved. Your _cam config
files
should work fine with 4.0.0, but it would still be a good idea to
update
your use cases to use the new approach. It will be a lot easier to
debug
issues and update your configs to change settings. Also, we can't
guarantee
that things won't break in future versions if you are using old MET
config
files that reference the old environment variables.
If you'd rather just send me your MET config files and the .conf files
used, I can update them for you. I could also have someone pull them
from
WCOSS this afternoon. Below is some info on how to update them
yourself.
The process is a little confusing, but once it is done then it is
much,
much easier to update and keep track of settings going forward.
1a. Diff your MET config files (PB2NCConfig_cam and
PointStatConfig_cam)
against the wrapped MET config files in the repository for *v3.1*
(i.e.
METplus-3.1/parm/met_config/PB2NCConfig_wrapped and
PointStatConfig_wrapped). This will tell you which values you had to
override in your config file because they weren't supported in 3.1.
1b. Note that we discovered that there were some incorrect default
values
used here that have since been changed to match the MET config
defaults (in
share/met/config). These are outlined in the User's Guide here:
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#pb2ncconfig
Referring to this list, if your MET config file matches the "New
(Correct)"
value and the 3.1 wrapped config matches the "Old (Incorrect)" value,
then
you don't need to add anything to your METplus config for that item.
For example, if your file has:
*level_category = [];*
and the wrapped config file has:
*level_category = [0, 1, 4, 5, 6];*
then you don't need to do anything in the METplus config. Your value
matches the new default and will be used. If your version had
something
like:
* level_category = [2, 3]; *
then in your METplus .conf file you would need to set:
PB2NC_LEVEL_CATEGORY = 2, 3
1c. Info about the METplus conf variables that are available for each
wrapper can be found here:
https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#pb2nc-
met-conf
If there is a conf variable that corresponds to the value you need to
override in the MET config file, you can use that instead. If support
for a
variable in the MET config is not listed, then you can override the
values
using PB2NC_MET_CONFIG_OVERRIDES (see
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#overriding-
unsupported-met-configuration-variables
).
2. In your METplus .conf file, you will need to set PB2NC_CONFIG_FILE
and
POINT_STAT_CONFIG_FILE to point to the wrapped version that is in the
parm
directory.
*PB2NC_CONFIG_FILE = {PARM_BASE}/met_config/PB2NCConfig_wrapped*
*POINT_STAT_CONFIG_FILE
={PARM_BASE}/met_config/PointStatConfig_wrapped*
You will never need to change these values going forward, as any
unsupported MET variables overrides can be done directly in the
METplus
.conf file.
Again, I know this process can be confusing, so I am happy to make the
updates for you if you send me or point me to your files.
Thanks,
George
On Mon, Jun 7, 2021 at 9:51 AM George McCabe <mccabe at ucar.edu> wrote:
> Hi Perry,
>
> Are these paths on WCOSS? If so, could you send me the config files?
>
> With the new approach, you will no longer have to create your own
wrapped
> config files. You will always use the versions in the METplus
repository
> (parm/met_config). Many of the settings that you would change are
now
> supported via the METplus config files and any that are not can be
set in
> the METplus config file as well. Your _cam config files should still
work
> the same as they did before, but it would be a good idea to update
your
> METplus configs to avoid using them.
>
> I will write up some suggestions to update your config files to use
the
> new approach and reply here with the steps. If you'd prefer, we
could set
> up a working session to go through them.
>
> Thanks,
> George
>
> On Fri, Jun 4, 2021 at 9:26 AM perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
>>
>> Fri Jun 04 09:18:47 2021: Request 100108 was acted upon.
>> Transaction: Ticket created by perry.shafran at noaa.gov
>> Queue: met_help
>> Subject: config file changes for MET 10.0.0
>> Owner: Nobody
>> Requestors: perry.shafran at noaa.gov
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
>>
>>
>> Hi, all,
>>
>> I'm trying to convert to MET 10.0.0, and it looks like things have
changed
>> for the MET config files. Can you take a look at my config files
and
>> explain what would need to be changed? I think you had discussed
this
>> before in a prior METplus user's meeting, but that was so long ago
that I
>> don't quite remember.
>>
>> The files to examine are both in the directory:
>>
>>
>> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
>>
>> and would be PB2NCConfig_cam and PointStatConfig_cam.
>>
>> What would be the best resource to compare the old with the new?
Can you
>> find that in the User's Guide?
>>
>> Thanks!
>>
>> Perry
>>
>> --
>> Perry C. Shafran
>> Verification/MEG Group Leader for IMSG
>> VPPPG Branch of EMC/NCEP/NOAA/NWS
>> Office: 301-683-3765
>> Cell: 301-717-6454
>> (he/him/his)
>> perry.shafran at noaa.gov
>>
>>
>
> --
> George McCabe - Software Engineer III
> National Center for Atmospheric Research
> Research Applications Laboratory
> 303-497-2768
> ---
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
---
My working day may not be your working day. Please do not feel obliged
to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: perry.shafran at noaa.gov
Time: Mon Jun 07 13:29:46 2021
Hi, George,
OK, now I understand what you are trying to say. You're not trying to
fix
a current problem, you are looking to help update my files to be more
efficient. Then yes, let's be sure that we update the config files so
that
we have the best set up going forward.
It's probably better for you to make these changes, so I'll send you
my
config files and we'll go forward from there. I'm doing a few other
things
to wrap up the day, so I'll send them along tomorrow.
Thanks!
Perry
On Mon, Jun 7, 2021 at 12:22 PM George McCabe via RT
<met_help at ucar.edu>
wrote:
> Hi Perry,
>
> It is good to hear that your issue was resolved. Your _cam config
files
> should work fine with 4.0.0, but it would still be a good idea to
update
> your use cases to use the new approach. It will be a lot easier to
debug
> issues and update your configs to change settings. Also, we can't
guarantee
> that things won't break in future versions if you are using old MET
config
> files that reference the old environment variables.
>
> If you'd rather just send me your MET config files and the .conf
files
> used, I can update them for you. I could also have someone pull them
from
> WCOSS this afternoon. Below is some info on how to update them
yourself.
> The process is a little confusing, but once it is done then it is
much,
> much easier to update and keep track of settings going forward.
>
> 1a. Diff your MET config files (PB2NCConfig_cam and
PointStatConfig_cam)
> against the wrapped MET config files in the repository for *v3.1*
(i.e.
> METplus-3.1/parm/met_config/PB2NCConfig_wrapped and
> PointStatConfig_wrapped). This will tell you which values you had to
> override in your config file because they weren't supported in 3.1.
>
> 1b. Note that we discovered that there were some incorrect default
values
> used here that have since been changed to match the MET config
defaults (in
> share/met/config). These are outlined in the User's Guide here:
>
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#pb2ncconfig
>
> Referring to this list, if your MET config file matches the "New
(Correct)"
> value and the 3.1 wrapped config matches the "Old (Incorrect)"
value, then
> you don't need to add anything to your METplus config for that item.
> For example, if your file has:
>
> *level_category = [];*
>
> and the wrapped config file has:
>
> *level_category = [0, 1, 4, 5, 6];*
>
> then you don't need to do anything in the METplus config. Your value
> matches the new default and will be used. If your version had
something
> like:
>
> * level_category = [2, 3]; *
>
> then in your METplus .conf file you would need to set:
>
> PB2NC_LEVEL_CATEGORY = 2, 3
>
> 1c. Info about the METplus conf variables that are available for
each
> wrapper can be found here:
>
>
>
https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#pb2nc-
met-conf
>
> If there is a conf variable that corresponds to the value you need
to
> override in the MET config file, you can use that instead. If
support for a
> variable in the MET config is not listed, then you can override the
values
> using PB2NC_MET_CONFIG_OVERRIDES (see
>
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#overriding-
unsupported-met-configuration-variables
> ).
>
> 2. In your METplus .conf file, you will need to set
PB2NC_CONFIG_FILE and
> POINT_STAT_CONFIG_FILE to point to the wrapped version that is in
the parm
> directory.
>
> *PB2NC_CONFIG_FILE = {PARM_BASE}/met_config/PB2NCConfig_wrapped*
>
> *POINT_STAT_CONFIG_FILE
={PARM_BASE}/met_config/PointStatConfig_wrapped*
>
> You will never need to change these values going forward, as any
> unsupported MET variables overrides can be done directly in the
METplus
> .conf file.
>
> Again, I know this process can be confusing, so I am happy to make
the
> updates for you if you send me or point me to your files.
>
> Thanks,
> George
>
>
> On Mon, Jun 7, 2021 at 9:51 AM George McCabe <mccabe at ucar.edu>
wrote:
>
> > Hi Perry,
> >
> > Are these paths on WCOSS? If so, could you send me the config
files?
> >
> > With the new approach, you will no longer have to create your own
wrapped
> > config files. You will always use the versions in the METplus
repository
> > (parm/met_config). Many of the settings that you would change are
now
> > supported via the METplus config files and any that are not can be
set in
> > the METplus config file as well. Your _cam config files should
still work
> > the same as they did before, but it would be a good idea to update
your
> > METplus configs to avoid using them.
> >
> > I will write up some suggestions to update your config files to
use the
> > new approach and reply here with the steps. If you'd prefer, we
could set
> > up a working session to go through them.
> >
> > Thanks,
> > George
> >
> > On Fri, Jun 4, 2021 at 9:26 AM perry.shafran at noaa.gov via RT <
> > met_help at ucar.edu> wrote:
> >
> >>
> >> Fri Jun 04 09:18:47 2021: Request 100108 was acted upon.
> >> Transaction: Ticket created by perry.shafran at noaa.gov
> >> Queue: met_help
> >> Subject: config file changes for MET 10.0.0
> >> Owner: Nobody
> >> Requestors: perry.shafran at noaa.gov
> >> Status: new
> >> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> >
> >>
> >>
> >> Hi, all,
> >>
> >> I'm trying to convert to MET 10.0.0, and it looks like things
have
> changed
> >> for the MET config files. Can you take a look at my config files
and
> >> explain what would need to be changed? I think you had discussed
this
> >> before in a prior METplus user's meeting, but that was so long
ago that
> I
> >> don't quite remember.
> >>
> >> The files to examine are both in the directory:
> >>
> >>
> >>
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
> >>
> >> and would be PB2NCConfig_cam and PointStatConfig_cam.
> >>
> >> What would be the best resource to compare the old with the new?
Can
> you
> >> find that in the User's Guide?
> >>
> >> Thanks!
> >>
> >> Perry
> >>
> >> --
> >> Perry C. Shafran
> >> Verification/MEG Group Leader for IMSG
> >> VPPPG Branch of EMC/NCEP/NOAA/NWS
> >> Office: 301-683-3765
> >> Cell: 301-717-6454
> >> (he/him/his)
> >> perry.shafran at noaa.gov
> >>
> >>
> >
> > --
> > George McCabe - Software Engineer III
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > 303-497-2768
> > ---
> > My working day may not be your working day. Please do not feel
obliged to
> > reply to this email outside of your normal working hours.
> >
>
>
> --
> George McCabe - Software Engineer III
> National Center for Atmospheric Research
> Research Applications Laboratory
> 303-497-2768
> ---
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
>
--
Perry C. Shafran
Verification/MEG Group Leader for IMSG
VPPPG Branch of EMC/NCEP/NOAA/NWS
Office: 301-683-3765
Cell: 301-717-6454
(he/him/his)
perry.shafran at noaa.gov
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: George McCabe
Time: Mon Jun 07 13:35:47 2021
Hi Perry,
I was originally trying to fix the current problem until I learned
that it
was already fixed! Sounds good about sending over your files, no rush.
Thanks,
George
On Mon, Jun 7, 2021 at 1:30 PM perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
>
> Hi, George,
>
> OK, now I understand what you are trying to say. You're not trying
to fix
> a current problem, you are looking to help update my files to be
more
> efficient. Then yes, let's be sure that we update the config files
so that
> we have the best set up going forward.
>
> It's probably better for you to make these changes, so I'll send you
my
> config files and we'll go forward from there. I'm doing a few other
things
> to wrap up the day, so I'll send them along tomorrow.
>
> Thanks!
>
> Perry
>
> On Mon, Jun 7, 2021 at 12:22 PM George McCabe via RT
<met_help at ucar.edu>
> wrote:
>
> > Hi Perry,
> >
> > It is good to hear that your issue was resolved. Your _cam config
files
> > should work fine with 4.0.0, but it would still be a good idea to
update
> > your use cases to use the new approach. It will be a lot easier to
debug
> > issues and update your configs to change settings. Also, we can't
> guarantee
> > that things won't break in future versions if you are using old
MET
> config
> > files that reference the old environment variables.
> >
> > If you'd rather just send me your MET config files and the .conf
files
> > used, I can update them for you. I could also have someone pull
them from
> > WCOSS this afternoon. Below is some info on how to update them
yourself.
> > The process is a little confusing, but once it is done then it is
much,
> > much easier to update and keep track of settings going forward.
> >
> > 1a. Diff your MET config files (PB2NCConfig_cam and
PointStatConfig_cam)
> > against the wrapped MET config files in the repository for *v3.1*
(i.e.
> > METplus-3.1/parm/met_config/PB2NCConfig_wrapped and
> > PointStatConfig_wrapped). This will tell you which values you had
to
> > override in your config file because they weren't supported in
3.1.
> >
> > 1b. Note that we discovered that there were some incorrect default
values
> > used here that have since been changed to match the MET config
defaults
> (in
> > share/met/config). These are outlined in the User's Guide here:
> >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#pb2ncconfig
> >
> > Referring to this list, if your MET config file matches the "New
> (Correct)"
> > value and the 3.1 wrapped config matches the "Old (Incorrect)"
value,
> then
> > you don't need to add anything to your METplus config for that
item.
> > For example, if your file has:
> >
> > *level_category = [];*
> >
> > and the wrapped config file has:
> >
> > *level_category = [0, 1, 4, 5, 6];*
> >
> > then you don't need to do anything in the METplus config. Your
value
> > matches the new default and will be used. If your version had
something
> > like:
> >
> > * level_category = [2, 3]; *
> >
> > then in your METplus .conf file you would need to set:
> >
> > PB2NC_LEVEL_CATEGORY = 2, 3
> >
> > 1c. Info about the METplus conf variables that are available for
each
> > wrapper can be found here:
> >
> >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#pb2nc-
met-conf
> >
> > If there is a conf variable that corresponds to the value you need
to
> > override in the MET config file, you can use that instead. If
support
> for a
> > variable in the MET config is not listed, then you can override
the
> values
> > using PB2NC_MET_CONFIG_OVERRIDES (see
> >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#overriding-
unsupported-met-configuration-variables
> > ).
> >
> > 2. In your METplus .conf file, you will need to set
PB2NC_CONFIG_FILE and
> > POINT_STAT_CONFIG_FILE to point to the wrapped version that is in
the
> parm
> > directory.
> >
> > *PB2NC_CONFIG_FILE = {PARM_BASE}/met_config/PB2NCConfig_wrapped*
> >
> > *POINT_STAT_CONFIG_FILE
={PARM_BASE}/met_config/PointStatConfig_wrapped*
> >
> > You will never need to change these values going forward, as any
> > unsupported MET variables overrides can be done directly in the
METplus
> > .conf file.
> >
> > Again, I know this process can be confusing, so I am happy to make
the
> > updates for you if you send me or point me to your files.
> >
> > Thanks,
> > George
> >
> >
> > On Mon, Jun 7, 2021 at 9:51 AM George McCabe <mccabe at ucar.edu>
wrote:
> >
> > > Hi Perry,
> > >
> > > Are these paths on WCOSS? If so, could you send me the config
files?
> > >
> > > With the new approach, you will no longer have to create your
own
> wrapped
> > > config files. You will always use the versions in the METplus
> repository
> > > (parm/met_config). Many of the settings that you would change
are now
> > > supported via the METplus config files and any that are not can
be set
> in
> > > the METplus config file as well. Your _cam config files should
still
> work
> > > the same as they did before, but it would be a good idea to
update your
> > > METplus configs to avoid using them.
> > >
> > > I will write up some suggestions to update your config files to
use the
> > > new approach and reply here with the steps. If you'd prefer, we
could
> set
> > > up a working session to go through them.
> > >
> > > Thanks,
> > > George
> > >
> > > On Fri, Jun 4, 2021 at 9:26 AM perry.shafran at noaa.gov via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > >>
> > >> Fri Jun 04 09:18:47 2021: Request 100108 was acted upon.
> > >> Transaction: Ticket created by perry.shafran at noaa.gov
> > >> Queue: met_help
> > >> Subject: config file changes for MET 10.0.0
> > >> Owner: Nobody
> > >> Requestors: perry.shafran at noaa.gov
> > >> Status: new
> > >> Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> > >
> > >>
> > >>
> > >> Hi, all,
> > >>
> > >> I'm trying to convert to MET 10.0.0, and it looks like things
have
> > changed
> > >> for the MET config files. Can you take a look at my config
files and
> > >> explain what would need to be changed? I think you had
discussed this
> > >> before in a prior METplus user's meeting, but that was so long
ago
> that
> > I
> > >> don't quite remember.
> > >>
> > >> The files to examine are both in the directory:
> > >>
> > >>
> > >>
> >
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
> > >>
> > >> and would be PB2NCConfig_cam and PointStatConfig_cam.
> > >>
> > >> What would be the best resource to compare the old with the
new? Can
> > you
> > >> find that in the User's Guide?
> > >>
> > >> Thanks!
> > >>
> > >> Perry
> > >>
> > >> --
> > >> Perry C. Shafran
> > >> Verification/MEG Group Leader for IMSG
> > >> VPPPG Branch of EMC/NCEP/NOAA/NWS
> > >> Office: 301-683-3765
> > >> Cell: 301-717-6454
> > >> (he/him/his)
> > >> perry.shafran at noaa.gov
> > >>
> > >>
> > >
> > > --
> > > George McCabe - Software Engineer III
> > > National Center for Atmospheric Research
> > > Research Applications Laboratory
> > > 303-497-2768
> > > ---
> > > My working day may not be your working day. Please do not feel
obliged
> to
> > > reply to this email outside of your normal working hours.
> > >
> >
> >
> > --
> > George McCabe - Software Engineer III
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > 303-497-2768
> > ---
> > My working day may not be your working day. Please do not feel
obliged to
> > reply to this email outside of your normal working hours.
> >
> >
>
> --
> Perry C. Shafran
> Verification/MEG Group Leader for IMSG
> VPPPG Branch of EMC/NCEP/NOAA/NWS
> Office: 301-683-3765
> Cell: 301-717-6454
> (he/him/his)
> perry.shafran at noaa.gov
>
>
--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
---
My working day may not be your working day. Please do not feel obliged
to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: perry.shafran at noaa.gov
Time: Tue Jun 08 07:58:46 2021
Hi, George,
You can find my MET config files
here: /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
Specifically, the PB2NC and PointStat files that end with the letters
"cam"
are your best bet to look at.
Do you need to look at METplus config files too for this?
Thanks!
Perry
On Mon, Jun 7, 2021 at 3:35 PM George McCabe via RT
<met_help at ucar.edu>
wrote:
> Hi Perry,
>
> I was originally trying to fix the current problem until I learned
that it
> was already fixed! Sounds good about sending over your files, no
rush.
>
> Thanks,
> George
>
> On Mon, Jun 7, 2021 at 1:30 PM perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> >
> > Hi, George,
> >
> > OK, now I understand what you are trying to say. You're not
trying to
> fix
> > a current problem, you are looking to help update my files to be
more
> > efficient. Then yes, let's be sure that we update the config
files so
> that
> > we have the best set up going forward.
> >
> > It's probably better for you to make these changes, so I'll send
you my
> > config files and we'll go forward from there. I'm doing a few
other
> things
> > to wrap up the day, so I'll send them along tomorrow.
> >
> > Thanks!
> >
> > Perry
> >
> > On Mon, Jun 7, 2021 at 12:22 PM George McCabe via RT
<met_help at ucar.edu>
> > wrote:
> >
> > > Hi Perry,
> > >
> > > It is good to hear that your issue was resolved. Your _cam
config files
> > > should work fine with 4.0.0, but it would still be a good idea
to
> update
> > > your use cases to use the new approach. It will be a lot easier
to
> debug
> > > issues and update your configs to change settings. Also, we
can't
> > guarantee
> > > that things won't break in future versions if you are using old
MET
> > config
> > > files that reference the old environment variables.
> > >
> > > If you'd rather just send me your MET config files and the .conf
files
> > > used, I can update them for you. I could also have someone pull
them
> from
> > > WCOSS this afternoon. Below is some info on how to update them
> yourself.
> > > The process is a little confusing, but once it is done then it
is much,
> > > much easier to update and keep track of settings going forward.
> > >
> > > 1a. Diff your MET config files (PB2NCConfig_cam and
> PointStatConfig_cam)
> > > against the wrapped MET config files in the repository for
*v3.1* (i.e.
> > > METplus-3.1/parm/met_config/PB2NCConfig_wrapped and
> > > PointStatConfig_wrapped). This will tell you which values you
had to
> > > override in your config file because they weren't supported in
3.1.
> > >
> > > 1b. Note that we discovered that there were some incorrect
default
> values
> > > used here that have since been changed to match the MET config
defaults
> > (in
> > > share/met/config). These are outlined in the User's Guide here:
> > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#pb2ncconfig
> > >
> > > Referring to this list, if your MET config file matches the "New
> > (Correct)"
> > > value and the 3.1 wrapped config matches the "Old (Incorrect)"
value,
> > then
> > > you don't need to add anything to your METplus config for that
item.
> > > For example, if your file has:
> > >
> > > *level_category = [];*
> > >
> > > and the wrapped config file has:
> > >
> > > *level_category = [0, 1, 4, 5, 6];*
> > >
> > > then you don't need to do anything in the METplus config. Your
value
> > > matches the new default and will be used. If your version had
something
> > > like:
> > >
> > > * level_category = [2, 3]; *
> > >
> > > then in your METplus .conf file you would need to set:
> > >
> > > PB2NC_LEVEL_CATEGORY = 2, 3
> > >
> > > 1c. Info about the METplus conf variables that are available for
each
> > > wrapper can be found here:
> > >
> > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#pb2nc-
met-conf
> > >
> > > If there is a conf variable that corresponds to the value you
need to
> > > override in the MET config file, you can use that instead. If
support
> > for a
> > > variable in the MET config is not listed, then you can override
the
> > values
> > > using PB2NC_MET_CONFIG_OVERRIDES (see
> > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#overriding-
unsupported-met-configuration-variables
> > > ).
> > >
> > > 2. In your METplus .conf file, you will need to set
PB2NC_CONFIG_FILE
> and
> > > POINT_STAT_CONFIG_FILE to point to the wrapped version that is
in the
> > parm
> > > directory.
> > >
> > > *PB2NC_CONFIG_FILE = {PARM_BASE}/met_config/PB2NCConfig_wrapped*
> > >
> > > *POINT_STAT_CONFIG_FILE
> ={PARM_BASE}/met_config/PointStatConfig_wrapped*
> > >
> > > You will never need to change these values going forward, as any
> > > unsupported MET variables overrides can be done directly in the
METplus
> > > .conf file.
> > >
> > > Again, I know this process can be confusing, so I am happy to
make the
> > > updates for you if you send me or point me to your files.
> > >
> > > Thanks,
> > > George
> > >
> > >
> > > On Mon, Jun 7, 2021 at 9:51 AM George McCabe <mccabe at ucar.edu>
wrote:
> > >
> > > > Hi Perry,
> > > >
> > > > Are these paths on WCOSS? If so, could you send me the config
files?
> > > >
> > > > With the new approach, you will no longer have to create your
own
> > wrapped
> > > > config files. You will always use the versions in the METplus
> > repository
> > > > (parm/met_config). Many of the settings that you would change
are now
> > > > supported via the METplus config files and any that are not
can be
> set
> > in
> > > > the METplus config file as well. Your _cam config files should
still
> > work
> > > > the same as they did before, but it would be a good idea to
update
> your
> > > > METplus configs to avoid using them.
> > > >
> > > > I will write up some suggestions to update your config files
to use
> the
> > > > new approach and reply here with the steps. If you'd prefer,
we could
> > set
> > > > up a working session to go through them.
> > > >
> > > > Thanks,
> > > > George
> > > >
> > > > On Fri, Jun 4, 2021 at 9:26 AM perry.shafran at noaa.gov via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > >>
> > > >> Fri Jun 04 09:18:47 2021: Request 100108 was acted upon.
> > > >> Transaction: Ticket created by perry.shafran at noaa.gov
> > > >> Queue: met_help
> > > >> Subject: config file changes for MET 10.0.0
> > > >> Owner: Nobody
> > > >> Requestors: perry.shafran at noaa.gov
> > > >> Status: new
> > > >> Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> > > >
> > > >>
> > > >>
> > > >> Hi, all,
> > > >>
> > > >> I'm trying to convert to MET 10.0.0, and it looks like things
have
> > > changed
> > > >> for the MET config files. Can you take a look at my config
files
> and
> > > >> explain what would need to be changed? I think you had
discussed
> this
> > > >> before in a prior METplus user's meeting, but that was so
long ago
> > that
> > > I
> > > >> don't quite remember.
> > > >>
> > > >> The files to examine are both in the directory:
> > > >>
> > > >>
> > > >>
> > >
> >
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
> > > >>
> > > >> and would be PB2NCConfig_cam and PointStatConfig_cam.
> > > >>
> > > >> What would be the best resource to compare the old with the
new?
> Can
> > > you
> > > >> find that in the User's Guide?
> > > >>
> > > >> Thanks!
> > > >>
> > > >> Perry
> > > >>
> > > >> --
> > > >> Perry C. Shafran
> > > >> Verification/MEG Group Leader for IMSG
> > > >> VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > >> Office: 301-683-3765
> > > >> Cell: 301-717-6454
> > > >> (he/him/his)
> > > >> perry.shafran at noaa.gov
> > > >>
> > > >>
> > > >
> > > > --
> > > > George McCabe - Software Engineer III
> > > > National Center for Atmospheric Research
> > > > Research Applications Laboratory
> > > > 303-497-2768
> > > > ---
> > > > My working day may not be your working day. Please do not feel
> obliged
> > to
> > > > reply to this email outside of your normal working hours.
> > > >
> > >
> > >
> > > --
> > > George McCabe - Software Engineer III
> > > National Center for Atmospheric Research
> > > Research Applications Laboratory
> > > 303-497-2768
> > > ---
> > > My working day may not be your working day. Please do not feel
obliged
> to
> > > reply to this email outside of your normal working hours.
> > >
> > >
> >
> > --
> > Perry C. Shafran
> > Verification/MEG Group Leader for IMSG
> > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > Office: 301-683-3765
> > Cell: 301-717-6454
> > (he/him/his)
> > perry.shafran at noaa.gov
> >
> >
>
> --
> George McCabe - Software Engineer III
> National Center for Atmospheric Research
> Research Applications Laboratory
> 303-497-2768
> ---
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
>
--
Perry C. Shafran
Verification/MEG Group Leader for IMSG
VPPPG Branch of EMC/NCEP/NOAA/NWS
Office: 301-683-3765
Cell: 301-717-6454
(he/him/his)
perry.shafran at noaa.gov
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: George McCabe
Time: Tue Jun 08 08:03:37 2021
Hi Perry,
Is that a path on WCOSS? I don't have access, so I will have to ask
someone
on the team to pull the files for me.
Yes, I need the corresponding METplus config files because I will need
to
add variables to those files. I recall some of your use cases run by
passing in multiple config files. If that is still the case, please
send
the command that is run so I know the order in which the files are
read.
Thanks,
George
On Tue, Jun 8, 2021 at 7:59 AM perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
>
> Hi, George,
>
> You can find my MET config files
> here:
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
>
> Specifically, the PB2NC and PointStat files that end with the
letters "cam"
> are your best bet to look at.
>
> Do you need to look at METplus config files too for this?
>
> Thanks!
>
> Perry
>
> On Mon, Jun 7, 2021 at 3:35 PM George McCabe via RT
<met_help at ucar.edu>
> wrote:
>
> > Hi Perry,
> >
> > I was originally trying to fix the current problem until I learned
that
> it
> > was already fixed! Sounds good about sending over your files, no
rush.
> >
> > Thanks,
> > George
> >
> > On Mon, Jun 7, 2021 at 1:30 PM perry.shafran at noaa.gov via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> > >
> > > Hi, George,
> > >
> > > OK, now I understand what you are trying to say. You're not
trying to
> > fix
> > > a current problem, you are looking to help update my files to be
more
> > > efficient. Then yes, let's be sure that we update the config
files so
> > that
> > > we have the best set up going forward.
> > >
> > > It's probably better for you to make these changes, so I'll send
you my
> > > config files and we'll go forward from there. I'm doing a few
other
> > things
> > > to wrap up the day, so I'll send them along tomorrow.
> > >
> > > Thanks!
> > >
> > > Perry
> > >
> > > On Mon, Jun 7, 2021 at 12:22 PM George McCabe via RT <
> met_help at ucar.edu>
> > > wrote:
> > >
> > > > Hi Perry,
> > > >
> > > > It is good to hear that your issue was resolved. Your _cam
config
> files
> > > > should work fine with 4.0.0, but it would still be a good idea
to
> > update
> > > > your use cases to use the new approach. It will be a lot
easier to
> > debug
> > > > issues and update your configs to change settings. Also, we
can't
> > > guarantee
> > > > that things won't break in future versions if you are using
old MET
> > > config
> > > > files that reference the old environment variables.
> > > >
> > > > If you'd rather just send me your MET config files and the
.conf
> files
> > > > used, I can update them for you. I could also have someone
pull them
> > from
> > > > WCOSS this afternoon. Below is some info on how to update them
> > yourself.
> > > > The process is a little confusing, but once it is done then it
is
> much,
> > > > much easier to update and keep track of settings going
forward.
> > > >
> > > > 1a. Diff your MET config files (PB2NCConfig_cam and
> > PointStatConfig_cam)
> > > > against the wrapped MET config files in the repository for
*v3.1*
> (i.e.
> > > > METplus-3.1/parm/met_config/PB2NCConfig_wrapped and
> > > > PointStatConfig_wrapped). This will tell you which values you
had to
> > > > override in your config file because they weren't supported in
3.1.
> > > >
> > > > 1b. Note that we discovered that there were some incorrect
default
> > values
> > > > used here that have since been changed to match the MET config
> defaults
> > > (in
> > > > share/met/config). These are outlined in the User's Guide
here:
> > > >
> > > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#pb2ncconfig
> > > >
> > > > Referring to this list, if your MET config file matches the
"New
> > > (Correct)"
> > > > value and the 3.1 wrapped config matches the "Old (Incorrect)"
value,
> > > then
> > > > you don't need to add anything to your METplus config for that
item.
> > > > For example, if your file has:
> > > >
> > > > *level_category = [];*
> > > >
> > > > and the wrapped config file has:
> > > >
> > > > *level_category = [0, 1, 4, 5, 6];*
> > > >
> > > > then you don't need to do anything in the METplus config. Your
value
> > > > matches the new default and will be used. If your version had
> something
> > > > like:
> > > >
> > > > * level_category = [2, 3]; *
> > > >
> > > > then in your METplus .conf file you would need to set:
> > > >
> > > > PB2NC_LEVEL_CATEGORY = 2, 3
> > > >
> > > > 1c. Info about the METplus conf variables that are available
for each
> > > > wrapper can be found here:
> > > >
> > > >
> > > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#pb2nc-
met-conf
> > > >
> > > > If there is a conf variable that corresponds to the value you
need to
> > > > override in the MET config file, you can use that instead. If
support
> > > for a
> > > > variable in the MET config is not listed, then you can
override the
> > > values
> > > > using PB2NC_MET_CONFIG_OVERRIDES (see
> > > >
> > > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#overriding-
unsupported-met-configuration-variables
> > > > ).
> > > >
> > > > 2. In your METplus .conf file, you will need to set
PB2NC_CONFIG_FILE
> > and
> > > > POINT_STAT_CONFIG_FILE to point to the wrapped version that is
in the
> > > parm
> > > > directory.
> > > >
> > > > *PB2NC_CONFIG_FILE =
{PARM_BASE}/met_config/PB2NCConfig_wrapped*
> > > >
> > > > *POINT_STAT_CONFIG_FILE
> > ={PARM_BASE}/met_config/PointStatConfig_wrapped*
> > > >
> > > > You will never need to change these values going forward, as
any
> > > > unsupported MET variables overrides can be done directly in
the
> METplus
> > > > .conf file.
> > > >
> > > > Again, I know this process can be confusing, so I am happy to
make
> the
> > > > updates for you if you send me or point me to your files.
> > > >
> > > > Thanks,
> > > > George
> > > >
> > > >
> > > > On Mon, Jun 7, 2021 at 9:51 AM George McCabe <mccabe at ucar.edu>
> wrote:
> > > >
> > > > > Hi Perry,
> > > > >
> > > > > Are these paths on WCOSS? If so, could you send me the
config
> files?
> > > > >
> > > > > With the new approach, you will no longer have to create
your own
> > > wrapped
> > > > > config files. You will always use the versions in the
METplus
> > > repository
> > > > > (parm/met_config). Many of the settings that you would
change are
> now
> > > > > supported via the METplus config files and any that are not
can be
> > set
> > > in
> > > > > the METplus config file as well. Your _cam config files
should
> still
> > > work
> > > > > the same as they did before, but it would be a good idea to
update
> > your
> > > > > METplus configs to avoid using them.
> > > > >
> > > > > I will write up some suggestions to update your config files
to use
> > the
> > > > > new approach and reply here with the steps. If you'd prefer,
we
> could
> > > set
> > > > > up a working session to go through them.
> > > > >
> > > > > Thanks,
> > > > > George
> > > > >
> > > > > On Fri, Jun 4, 2021 at 9:26 AM perry.shafran at noaa.gov via RT
<
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > >>
> > > > >> Fri Jun 04 09:18:47 2021: Request 100108 was acted upon.
> > > > >> Transaction: Ticket created by perry.shafran at noaa.gov
> > > > >> Queue: met_help
> > > > >> Subject: config file changes for MET 10.0.0
> > > > >> Owner: Nobody
> > > > >> Requestors: perry.shafran at noaa.gov
> > > > >> Status: new
> > > > >> Ticket <URL:
> > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> > > > >
> > > > >>
> > > > >>
> > > > >> Hi, all,
> > > > >>
> > > > >> I'm trying to convert to MET 10.0.0, and it looks like
things have
> > > > changed
> > > > >> for the MET config files. Can you take a look at my config
files
> > and
> > > > >> explain what would need to be changed? I think you had
discussed
> > this
> > > > >> before in a prior METplus user's meeting, but that was so
long ago
> > > that
> > > > I
> > > > >> don't quite remember.
> > > > >>
> > > > >> The files to examine are both in the directory:
> > > > >>
> > > > >>
> > > > >>
> > > >
> > >
> >
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
> > > > >>
> > > > >> and would be PB2NCConfig_cam and PointStatConfig_cam.
> > > > >>
> > > > >> What would be the best resource to compare the old with the
new?
> > Can
> > > > you
> > > > >> find that in the User's Guide?
> > > > >>
> > > > >> Thanks!
> > > > >>
> > > > >> Perry
> > > > >>
> > > > >> --
> > > > >> Perry C. Shafran
> > > > >> Verification/MEG Group Leader for IMSG
> > > > >> VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > >> Office: 301-683-3765
> > > > >> Cell: 301-717-6454
> > > > >> (he/him/his)
> > > > >> perry.shafran at noaa.gov
> > > > >>
> > > > >>
> > > > >
> > > > > --
> > > > > George McCabe - Software Engineer III
> > > > > National Center for Atmospheric Research
> > > > > Research Applications Laboratory
> > > > > 303-497-2768
> > > > > ---
> > > > > My working day may not be your working day. Please do not
feel
> > obliged
> > > to
> > > > > reply to this email outside of your normal working hours.
> > > > >
> > > >
> > > >
> > > > --
> > > > George McCabe - Software Engineer III
> > > > National Center for Atmospheric Research
> > > > Research Applications Laboratory
> > > > 303-497-2768
> > > > ---
> > > > My working day may not be your working day. Please do not feel
> obliged
> > to
> > > > reply to this email outside of your normal working hours.
> > > >
> > > >
> > >
> > > --
> > > Perry C. Shafran
> > > Verification/MEG Group Leader for IMSG
> > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > Office: 301-683-3765
> > > Cell: 301-717-6454
> > > (he/him/his)
> > > perry.shafran at noaa.gov
> > >
> > >
> >
> > --
> > George McCabe - Software Engineer III
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > 303-497-2768
> > ---
> > My working day may not be your working day. Please do not feel
obliged to
> > reply to this email outside of your normal working hours.
> >
> >
>
> --
> Perry C. Shafran
> Verification/MEG Group Leader for IMSG
> VPPPG Branch of EMC/NCEP/NOAA/NWS
> Office: 301-683-3765
> Cell: 301-717-6454
> (he/him/his)
> perry.shafran at noaa.gov
>
>
--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
---
My working day may not be your working day. Please do not feel obliged
to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: perry.shafran at noaa.gov
Time: Tue Jun 08 08:21:51 2021
Hi, George,
OK great! I'm not entirely sure, but I think that my run command
contains
too many files because some of the files I had in there I believe are
unchanged from the standard METplus config files (from early in my
usage of
METplus). I'll show you some of that.
Yes, these are paths on WCOSS. I thought you had access to this.
The METplus config files
are /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/use_cases/perry,
pb2nc_cam.conf and point_stat_cam.conf.
The command used is:
/gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/ush/master_metplus.py
-c
/gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
-c
/gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
-c
/gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/parm/use_cases/perry/pb2nc_cam.conf
-c
/gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/parm/use_cases/perry/point_stat_cam.conf
-c /gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/nam.conf -c
/gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/parm/use_cases/perry/shared.conf
-c /gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/shared_nam.conf -c
/gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/parm/use_cases/perry/system_cam.conf
You may replace the 3.1's with 4.0.0's as it would be the same (and
change
master_metplus to run_metplus).
Perry
On Tue, Jun 8, 2021 at 10:03 AM George McCabe via RT
<met_help at ucar.edu>
wrote:
> Hi Perry,
>
> Is that a path on WCOSS? I don't have access, so I will have to ask
someone
> on the team to pull the files for me.
>
> Yes, I need the corresponding METplus config files because I will
need to
> add variables to those files. I recall some of your use cases run by
> passing in multiple config files. If that is still the case, please
send
> the command that is run so I know the order in which the files are
read.
>
> Thanks,
> George
>
> On Tue, Jun 8, 2021 at 7:59 AM perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> >
> > Hi, George,
> >
> > You can find my MET config files
> > here:
> >
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
> >
> > Specifically, the PB2NC and PointStat files that end with the
letters
> "cam"
> > are your best bet to look at.
> >
> > Do you need to look at METplus config files too for this?
> >
> > Thanks!
> >
> > Perry
> >
> > On Mon, Jun 7, 2021 at 3:35 PM George McCabe via RT
<met_help at ucar.edu>
> > wrote:
> >
> > > Hi Perry,
> > >
> > > I was originally trying to fix the current problem until I
learned that
> > it
> > > was already fixed! Sounds good about sending over your files, no
rush.
> > >
> > > Thanks,
> > > George
> > >
> > > On Mon, Jun 7, 2021 at 1:30 PM perry.shafran at noaa.gov via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
>
> > > >
> > > > Hi, George,
> > > >
> > > > OK, now I understand what you are trying to say. You're not
trying
> to
> > > fix
> > > > a current problem, you are looking to help update my files to
be more
> > > > efficient. Then yes, let's be sure that we update the config
files
> so
> > > that
> > > > we have the best set up going forward.
> > > >
> > > > It's probably better for you to make these changes, so I'll
send you
> my
> > > > config files and we'll go forward from there. I'm doing a few
other
> > > things
> > > > to wrap up the day, so I'll send them along tomorrow.
> > > >
> > > > Thanks!
> > > >
> > > > Perry
> > > >
> > > > On Mon, Jun 7, 2021 at 12:22 PM George McCabe via RT <
> > met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > > Hi Perry,
> > > > >
> > > > > It is good to hear that your issue was resolved. Your _cam
config
> > files
> > > > > should work fine with 4.0.0, but it would still be a good
idea to
> > > update
> > > > > your use cases to use the new approach. It will be a lot
easier to
> > > debug
> > > > > issues and update your configs to change settings. Also, we
can't
> > > > guarantee
> > > > > that things won't break in future versions if you are using
old MET
> > > > config
> > > > > files that reference the old environment variables.
> > > > >
> > > > > If you'd rather just send me your MET config files and the
.conf
> > files
> > > > > used, I can update them for you. I could also have someone
pull
> them
> > > from
> > > > > WCOSS this afternoon. Below is some info on how to update
them
> > > yourself.
> > > > > The process is a little confusing, but once it is done then
it is
> > much,
> > > > > much easier to update and keep track of settings going
forward.
> > > > >
> > > > > 1a. Diff your MET config files (PB2NCConfig_cam and
> > > PointStatConfig_cam)
> > > > > against the wrapped MET config files in the repository for
*v3.1*
> > (i.e.
> > > > > METplus-3.1/parm/met_config/PB2NCConfig_wrapped and
> > > > > PointStatConfig_wrapped). This will tell you which values
you had
> to
> > > > > override in your config file because they weren't supported
in 3.1.
> > > > >
> > > > > 1b. Note that we discovered that there were some incorrect
default
> > > values
> > > > > used here that have since been changed to match the MET
config
> > defaults
> > > > (in
> > > > > share/met/config). These are outlined in the User's Guide
here:
> > > > >
> > > > >
> > > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#pb2ncconfig
> > > > >
> > > > > Referring to this list, if your MET config file matches the
"New
> > > > (Correct)"
> > > > > value and the 3.1 wrapped config matches the "Old
(Incorrect)"
> value,
> > > > then
> > > > > you don't need to add anything to your METplus config for
that
> item.
> > > > > For example, if your file has:
> > > > >
> > > > > *level_category = [];*
> > > > >
> > > > > and the wrapped config file has:
> > > > >
> > > > > *level_category = [0, 1, 4, 5, 6];*
> > > > >
> > > > > then you don't need to do anything in the METplus config.
Your
> value
> > > > > matches the new default and will be used. If your version
had
> > something
> > > > > like:
> > > > >
> > > > > * level_category = [2, 3]; *
> > > > >
> > > > > then in your METplus .conf file you would need to set:
> > > > >
> > > > > PB2NC_LEVEL_CATEGORY = 2, 3
> > > > >
> > > > > 1c. Info about the METplus conf variables that are available
for
> each
> > > > > wrapper can be found here:
> > > > >
> > > > >
> > > > >
> > > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#pb2nc-
met-conf
> > > > >
> > > > > If there is a conf variable that corresponds to the value
you need
> to
> > > > > override in the MET config file, you can use that instead.
If
> support
> > > > for a
> > > > > variable in the MET config is not listed, then you can
override the
> > > > values
> > > > > using PB2NC_MET_CONFIG_OVERRIDES (see
> > > > >
> > > > >
> > > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#overriding-
unsupported-met-configuration-variables
> > > > > ).
> > > > >
> > > > > 2. In your METplus .conf file, you will need to set
> PB2NC_CONFIG_FILE
> > > and
> > > > > POINT_STAT_CONFIG_FILE to point to the wrapped version that
is in
> the
> > > > parm
> > > > > directory.
> > > > >
> > > > > *PB2NC_CONFIG_FILE =
{PARM_BASE}/met_config/PB2NCConfig_wrapped*
> > > > >
> > > > > *POINT_STAT_CONFIG_FILE
> > > ={PARM_BASE}/met_config/PointStatConfig_wrapped*
> > > > >
> > > > > You will never need to change these values going forward, as
any
> > > > > unsupported MET variables overrides can be done directly in
the
> > METplus
> > > > > .conf file.
> > > > >
> > > > > Again, I know this process can be confusing, so I am happy
to make
> > the
> > > > > updates for you if you send me or point me to your files.
> > > > >
> > > > > Thanks,
> > > > > George
> > > > >
> > > > >
> > > > > On Mon, Jun 7, 2021 at 9:51 AM George McCabe
<mccabe at ucar.edu>
> > wrote:
> > > > >
> > > > > > Hi Perry,
> > > > > >
> > > > > > Are these paths on WCOSS? If so, could you send me the
config
> > files?
> > > > > >
> > > > > > With the new approach, you will no longer have to create
your own
> > > > wrapped
> > > > > > config files. You will always use the versions in the
METplus
> > > > repository
> > > > > > (parm/met_config). Many of the settings that you would
change are
> > now
> > > > > > supported via the METplus config files and any that are
not can
> be
> > > set
> > > > in
> > > > > > the METplus config file as well. Your _cam config files
should
> > still
> > > > work
> > > > > > the same as they did before, but it would be a good idea
to
> update
> > > your
> > > > > > METplus configs to avoid using them.
> > > > > >
> > > > > > I will write up some suggestions to update your config
files to
> use
> > > the
> > > > > > new approach and reply here with the steps. If you'd
prefer, we
> > could
> > > > set
> > > > > > up a working session to go through them.
> > > > > >
> > > > > > Thanks,
> > > > > > George
> > > > > >
> > > > > > On Fri, Jun 4, 2021 at 9:26 AM perry.shafran at noaa.gov via
RT <
> > > > > > met_help at ucar.edu> wrote:
> > > > > >
> > > > > >>
> > > > > >> Fri Jun 04 09:18:47 2021: Request 100108 was acted upon.
> > > > > >> Transaction: Ticket created by perry.shafran at noaa.gov
> > > > > >> Queue: met_help
> > > > > >> Subject: config file changes for MET 10.0.0
> > > > > >> Owner: Nobody
> > > > > >> Requestors: perry.shafran at noaa.gov
> > > > > >> Status: new
> > > > > >> Ticket <URL:
> > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> > > > > >
> > > > > >>
> > > > > >>
> > > > > >> Hi, all,
> > > > > >>
> > > > > >> I'm trying to convert to MET 10.0.0, and it looks like
things
> have
> > > > > changed
> > > > > >> for the MET config files. Can you take a look at my
config
> files
> > > and
> > > > > >> explain what would need to be changed? I think you had
> discussed
> > > this
> > > > > >> before in a prior METplus user's meeting, but that was so
long
> ago
> > > > that
> > > > > I
> > > > > >> don't quite remember.
> > > > > >>
> > > > > >> The files to examine are both in the directory:
> > > > > >>
> > > > > >>
> > > > > >>
> > > > >
> > > >
> > >
> >
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
> > > > > >>
> > > > > >> and would be PB2NCConfig_cam and PointStatConfig_cam.
> > > > > >>
> > > > > >> What would be the best resource to compare the old with
the new?
> > > Can
> > > > > you
> > > > > >> find that in the User's Guide?
> > > > > >>
> > > > > >> Thanks!
> > > > > >>
> > > > > >> Perry
> > > > > >>
> > > > > >> --
> > > > > >> Perry C. Shafran
> > > > > >> Verification/MEG Group Leader for IMSG
> > > > > >> VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > >> Office: 301-683-3765
> > > > > >> Cell: 301-717-6454
> > > > > >> (he/him/his)
> > > > > >> perry.shafran at noaa.gov
> > > > > >>
> > > > > >>
> > > > > >
> > > > > > --
> > > > > > George McCabe - Software Engineer III
> > > > > > National Center for Atmospheric Research
> > > > > > Research Applications Laboratory
> > > > > > 303-497-2768
> > > > > > ---
> > > > > > My working day may not be your working day. Please do not
feel
> > > obliged
> > > > to
> > > > > > reply to this email outside of your normal working hours.
> > > > > >
> > > > >
> > > > >
> > > > > --
> > > > > George McCabe - Software Engineer III
> > > > > National Center for Atmospheric Research
> > > > > Research Applications Laboratory
> > > > > 303-497-2768
> > > > > ---
> > > > > My working day may not be your working day. Please do not
feel
> > obliged
> > > to
> > > > > reply to this email outside of your normal working hours.
> > > > >
> > > > >
> > > >
> > > > --
> > > > Perry C. Shafran
> > > > Verification/MEG Group Leader for IMSG
> > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > Office: 301-683-3765
> > > > Cell: 301-717-6454
> > > > (he/him/his)
> > > > perry.shafran at noaa.gov
> > > >
> > > >
> > >
> > > --
> > > George McCabe - Software Engineer III
> > > National Center for Atmospheric Research
> > > Research Applications Laboratory
> > > 303-497-2768
> > > ---
> > > My working day may not be your working day. Please do not feel
obliged
> to
> > > reply to this email outside of your normal working hours.
> > >
> > >
> >
> > --
> > Perry C. Shafran
> > Verification/MEG Group Leader for IMSG
> > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > Office: 301-683-3765
> > Cell: 301-717-6454
> > (he/him/his)
> > perry.shafran at noaa.gov
> >
> >
>
> --
> George McCabe - Software Engineer III
> National Center for Atmospheric Research
> Research Applications Laboratory
> 303-497-2768
> ---
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
>
--
Perry C. Shafran
Verification/MEG Group Leader for IMSG
VPPPG Branch of EMC/NCEP/NOAA/NWS
Office: 301-683-3765
Cell: 301-717-6454
(he/him/his)
perry.shafran at noaa.gov
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: George McCabe
Time: Tue Jun 08 14:00:34 2021
Thanks, Perry. I retrieved the files and will take a look. I am going
on
vacation this week so I likely won't get to it until after I return.
- George
On Tue, Jun 8, 2021 at 8:22 AM perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
>
> Hi, George,
>
> OK great! I'm not entirely sure, but I think that my run command
contains
> too many files because some of the files I had in there I believe
are
> unchanged from the standard METplus config files (from early in my
usage of
> METplus). I'll show you some of that.
>
> Yes, these are paths on WCOSS. I thought you had access to this.
>
> The METplus config files
> are
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/use_cases/perry,
> pb2nc_cam.conf and point_stat_cam.conf.
>
> The command used is:
>
>
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/ush/master_metplus.py
> -c
>
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
> -c
>
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
> -c
>
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/parm/use_cases/perry/pb2nc_cam.conf
> -c
>
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/parm/use_cases/perry/point_stat_cam.conf
> -c /gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/nam.conf -c
>
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/parm/use_cases/perry/shared.conf
> -c /gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/shared_nam.conf -c
>
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
3.1/parm/use_cases/perry/system_cam.conf
>
> You may replace the 3.1's with 4.0.0's as it would be the same (and
change
> master_metplus to run_metplus).
>
> Perry
>
> On Tue, Jun 8, 2021 at 10:03 AM George McCabe via RT
<met_help at ucar.edu>
> wrote:
>
> > Hi Perry,
> >
> > Is that a path on WCOSS? I don't have access, so I will have to
ask
> someone
> > on the team to pull the files for me.
> >
> > Yes, I need the corresponding METplus config files because I will
need to
> > add variables to those files. I recall some of your use cases run
by
> > passing in multiple config files. If that is still the case,
please send
> > the command that is run so I know the order in which the files are
read.
> >
> > Thanks,
> > George
> >
> > On Tue, Jun 8, 2021 at 7:59 AM perry.shafran at noaa.gov via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> > >
> > > Hi, George,
> > >
> > > You can find my MET config files
> > > here:
> > >
> >
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
> > >
> > > Specifically, the PB2NC and PointStat files that end with the
letters
> > "cam"
> > > are your best bet to look at.
> > >
> > > Do you need to look at METplus config files too for this?
> > >
> > > Thanks!
> > >
> > > Perry
> > >
> > > On Mon, Jun 7, 2021 at 3:35 PM George McCabe via RT
<met_help at ucar.edu
> >
> > > wrote:
> > >
> > > > Hi Perry,
> > > >
> > > > I was originally trying to fix the current problem until I
learned
> that
> > > it
> > > > was already fixed! Sounds good about sending over your files,
no
> rush.
> > > >
> > > > Thanks,
> > > > George
> > > >
> > > > On Mon, Jun 7, 2021 at 1:30 PM perry.shafran at noaa.gov via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> > > > >
> > > > > Hi, George,
> > > > >
> > > > > OK, now I understand what you are trying to say. You're not
trying
> > to
> > > > fix
> > > > > a current problem, you are looking to help update my files
to be
> more
> > > > > efficient. Then yes, let's be sure that we update the
config files
> > so
> > > > that
> > > > > we have the best set up going forward.
> > > > >
> > > > > It's probably better for you to make these changes, so I'll
send
> you
> > my
> > > > > config files and we'll go forward from there. I'm doing a
few
> other
> > > > things
> > > > > to wrap up the day, so I'll send them along tomorrow.
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Perry
> > > > >
> > > > > On Mon, Jun 7, 2021 at 12:22 PM George McCabe via RT <
> > > met_help at ucar.edu>
> > > > > wrote:
> > > > >
> > > > > > Hi Perry,
> > > > > >
> > > > > > It is good to hear that your issue was resolved. Your _cam
config
> > > files
> > > > > > should work fine with 4.0.0, but it would still be a good
idea to
> > > > update
> > > > > > your use cases to use the new approach. It will be a lot
easier
> to
> > > > debug
> > > > > > issues and update your configs to change settings. Also,
we can't
> > > > > guarantee
> > > > > > that things won't break in future versions if you are
using old
> MET
> > > > > config
> > > > > > files that reference the old environment variables.
> > > > > >
> > > > > > If you'd rather just send me your MET config files and the
.conf
> > > files
> > > > > > used, I can update them for you. I could also have someone
pull
> > them
> > > > from
> > > > > > WCOSS this afternoon. Below is some info on how to update
them
> > > > yourself.
> > > > > > The process is a little confusing, but once it is done
then it is
> > > much,
> > > > > > much easier to update and keep track of settings going
forward.
> > > > > >
> > > > > > 1a. Diff your MET config files (PB2NCConfig_cam and
> > > > PointStatConfig_cam)
> > > > > > against the wrapped MET config files in the repository for
*v3.1*
> > > (i.e.
> > > > > > METplus-3.1/parm/met_config/PB2NCConfig_wrapped and
> > > > > > PointStatConfig_wrapped). This will tell you which values
you had
> > to
> > > > > > override in your config file because they weren't
supported in
> 3.1.
> > > > > >
> > > > > > 1b. Note that we discovered that there were some incorrect
> default
> > > > values
> > > > > > used here that have since been changed to match the MET
config
> > > defaults
> > > > > (in
> > > > > > share/met/config). These are outlined in the User's Guide
here:
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#pb2ncconfig
> > > > > >
> > > > > > Referring to this list, if your MET config file matches
the "New
> > > > > (Correct)"
> > > > > > value and the 3.1 wrapped config matches the "Old
(Incorrect)"
> > value,
> > > > > then
> > > > > > you don't need to add anything to your METplus config for
that
> > item.
> > > > > > For example, if your file has:
> > > > > >
> > > > > > *level_category = [];*
> > > > > >
> > > > > > and the wrapped config file has:
> > > > > >
> > > > > > *level_category = [0, 1, 4, 5, 6];*
> > > > > >
> > > > > > then you don't need to do anything in the METplus config.
Your
> > value
> > > > > > matches the new default and will be used. If your version
had
> > > something
> > > > > > like:
> > > > > >
> > > > > > * level_category = [2, 3]; *
> > > > > >
> > > > > > then in your METplus .conf file you would need to set:
> > > > > >
> > > > > > PB2NC_LEVEL_CATEGORY = 2, 3
> > > > > >
> > > > > > 1c. Info about the METplus conf variables that are
available for
> > each
> > > > > > wrapper can be found here:
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#pb2nc-
met-conf
> > > > > >
> > > > > > If there is a conf variable that corresponds to the value
you
> need
> > to
> > > > > > override in the MET config file, you can use that instead.
If
> > support
> > > > > for a
> > > > > > variable in the MET config is not listed, then you can
override
> the
> > > > > values
> > > > > > using PB2NC_MET_CONFIG_OVERRIDES (see
> > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#overriding-
unsupported-met-configuration-variables
> > > > > > ).
> > > > > >
> > > > > > 2. In your METplus .conf file, you will need to set
> > PB2NC_CONFIG_FILE
> > > > and
> > > > > > POINT_STAT_CONFIG_FILE to point to the wrapped version
that is in
> > the
> > > > > parm
> > > > > > directory.
> > > > > >
> > > > > > *PB2NC_CONFIG_FILE =
{PARM_BASE}/met_config/PB2NCConfig_wrapped*
> > > > > >
> > > > > > *POINT_STAT_CONFIG_FILE
> > > > ={PARM_BASE}/met_config/PointStatConfig_wrapped*
> > > > > >
> > > > > > You will never need to change these values going forward,
as any
> > > > > > unsupported MET variables overrides can be done directly
in the
> > > METplus
> > > > > > .conf file.
> > > > > >
> > > > > > Again, I know this process can be confusing, so I am happy
to
> make
> > > the
> > > > > > updates for you if you send me or point me to your files.
> > > > > >
> > > > > > Thanks,
> > > > > > George
> > > > > >
> > > > > >
> > > > > > On Mon, Jun 7, 2021 at 9:51 AM George McCabe
<mccabe at ucar.edu>
> > > wrote:
> > > > > >
> > > > > > > Hi Perry,
> > > > > > >
> > > > > > > Are these paths on WCOSS? If so, could you send me the
config
> > > files?
> > > > > > >
> > > > > > > With the new approach, you will no longer have to create
your
> own
> > > > > wrapped
> > > > > > > config files. You will always use the versions in the
METplus
> > > > > repository
> > > > > > > (parm/met_config). Many of the settings that you would
change
> are
> > > now
> > > > > > > supported via the METplus config files and any that are
not can
> > be
> > > > set
> > > > > in
> > > > > > > the METplus config file as well. Your _cam config files
should
> > > still
> > > > > work
> > > > > > > the same as they did before, but it would be a good idea
to
> > update
> > > > your
> > > > > > > METplus configs to avoid using them.
> > > > > > >
> > > > > > > I will write up some suggestions to update your config
files to
> > use
> > > > the
> > > > > > > new approach and reply here with the steps. If you'd
prefer, we
> > > could
> > > > > set
> > > > > > > up a working session to go through them.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > George
> > > > > > >
> > > > > > > On Fri, Jun 4, 2021 at 9:26 AM perry.shafran at noaa.gov
via RT <
> > > > > > > met_help at ucar.edu> wrote:
> > > > > > >
> > > > > > >>
> > > > > > >> Fri Jun 04 09:18:47 2021: Request 100108 was acted
upon.
> > > > > > >> Transaction: Ticket created by perry.shafran at noaa.gov
> > > > > > >> Queue: met_help
> > > > > > >> Subject: config file changes for MET 10.0.0
> > > > > > >> Owner: Nobody
> > > > > > >> Requestors: perry.shafran at noaa.gov
> > > > > > >> Status: new
> > > > > > >> Ticket <URL:
> > > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> > > > > > >
> > > > > > >>
> > > > > > >>
> > > > > > >> Hi, all,
> > > > > > >>
> > > > > > >> I'm trying to convert to MET 10.0.0, and it looks like
things
> > have
> > > > > > changed
> > > > > > >> for the MET config files. Can you take a look at my
config
> > files
> > > > and
> > > > > > >> explain what would need to be changed? I think you had
> > discussed
> > > > this
> > > > > > >> before in a prior METplus user's meeting, but that was
so long
> > ago
> > > > > that
> > > > > > I
> > > > > > >> don't quite remember.
> > > > > > >>
> > > > > > >> The files to examine are both in the directory:
> > > > > > >>
> > > > > > >>
> > > > > > >>
> > > > > >
> > > > >
> > > >
> > >
> >
> /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
4.0.0/parm/met_config
> > > > > > >>
> > > > > > >> and would be PB2NCConfig_cam and PointStatConfig_cam.
> > > > > > >>
> > > > > > >> What would be the best resource to compare the old with
the
> new?
> > > > Can
> > > > > > you
> > > > > > >> find that in the User's Guide?
> > > > > > >>
> > > > > > >> Thanks!
> > > > > > >>
> > > > > > >> Perry
> > > > > > >>
> > > > > > >> --
> > > > > > >> Perry C. Shafran
> > > > > > >> Verification/MEG Group Leader for IMSG
> > > > > > >> VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > >> Office: 301-683-3765
> > > > > > >> Cell: 301-717-6454
> > > > > > >> (he/him/his)
> > > > > > >> perry.shafran at noaa.gov
> > > > > > >>
> > > > > > >>
> > > > > > >
> > > > > > > --
> > > > > > > George McCabe - Software Engineer III
> > > > > > > National Center for Atmospheric Research
> > > > > > > Research Applications Laboratory
> > > > > > > 303-497-2768
> > > > > > > ---
> > > > > > > My working day may not be your working day. Please do
not feel
> > > > obliged
> > > > > to
> > > > > > > reply to this email outside of your normal working
hours.
> > > > > > >
> > > > > >
> > > > > >
> > > > > > --
> > > > > > George McCabe - Software Engineer III
> > > > > > National Center for Atmospheric Research
> > > > > > Research Applications Laboratory
> > > > > > 303-497-2768
> > > > > > ---
> > > > > > My working day may not be your working day. Please do not
feel
> > > obliged
> > > > to
> > > > > > reply to this email outside of your normal working hours.
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Perry C. Shafran
> > > > > Verification/MEG Group Leader for IMSG
> > > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > Office: 301-683-3765
> > > > > Cell: 301-717-6454
> > > > > (he/him/his)
> > > > > perry.shafran at noaa.gov
> > > > >
> > > > >
> > > >
> > > > --
> > > > George McCabe - Software Engineer III
> > > > National Center for Atmospheric Research
> > > > Research Applications Laboratory
> > > > 303-497-2768
> > > > ---
> > > > My working day may not be your working day. Please do not feel
> obliged
> > to
> > > > reply to this email outside of your normal working hours.
> > > >
> > > >
> > >
> > > --
> > > Perry C. Shafran
> > > Verification/MEG Group Leader for IMSG
> > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > Office: 301-683-3765
> > > Cell: 301-717-6454
> > > (he/him/his)
> > > perry.shafran at noaa.gov
> > >
> > >
> >
> > --
> > George McCabe - Software Engineer III
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > 303-497-2768
> > ---
> > My working day may not be your working day. Please do not feel
obliged to
> > reply to this email outside of your normal working hours.
> >
> >
>
> --
> Perry C. Shafran
> Verification/MEG Group Leader for IMSG
> VPPPG Branch of EMC/NCEP/NOAA/NWS
> Office: 301-683-3765
> Cell: 301-717-6454
> (he/him/his)
> perry.shafran at noaa.gov
>
>
--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
---
My working day may not be your working day. Please do not feel obliged
to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: George McCabe
Time: Mon Jul 12 11:50:48 2021
Hi Perry,
I haven't forgotten about reviewing your config files, but I also
haven't had a chance to take care of the task yet. I am going to close
this ticket since the original issue was resolved and will correspond
with you via email. Please create a GitHub Discussions post if this
needs to be addressed sooner than later.
Thanks,
George
On Tue Jun 08 14:00:34 2021, mccabe wrote:
> Thanks, Perry. I retrieved the files and will take a look. I am
going
> on
> vacation this week so I likely won't get to it until after I return.
>
> - George
>
> On Tue, Jun 8, 2021 at 8:22 AM perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> >
> > Hi, George,
> >
> > OK great! I'm not entirely sure, but I think that my run command
> > contains
> > too many files because some of the files I had in there I believe
are
> > unchanged from the standard METplus config files (from early in my
> > usage of
> > METplus). I'll show you some of that.
> >
> > Yes, these are paths on WCOSS. I thought you had access to this.
> >
> > The METplus config files
> > are
> > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > 4.0.0/parm/use_cases/perry,
> > pb2nc_cam.conf and point_stat_cam.conf.
> >
> > The command used is:
> >
> >
> > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > 3.1/ush/master_metplus.py
> > -c
> >
> > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > 3.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
> > -c
> >
> > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > 3.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
> > -c
> >
> > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > 3.1/parm/use_cases/perry/pb2nc_cam.conf
> > -c
> >
> > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > 3.1/parm/use_cases/perry/point_stat_cam.conf
> > -c /gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/nam.conf -c
> >
> > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > 3.1/parm/use_cases/perry/shared.conf
> > -c /gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/shared_nam.conf -c
> >
> > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > 3.1/parm/use_cases/perry/system_cam.conf
> >
> > You may replace the 3.1's with 4.0.0's as it would be the same
(and
> > change
> > master_metplus to run_metplus).
> >
> > Perry
> >
> > On Tue, Jun 8, 2021 at 10:03 AM George McCabe via RT
> > <met_help at ucar.edu>
> > wrote:
> >
> > > Hi Perry,
> > >
> > > Is that a path on WCOSS? I don't have access, so I will have to
ask
> > someone
> > > on the team to pull the files for me.
> > >
> > > Yes, I need the corresponding METplus config files because I
will
> > > need to
> > > add variables to those files. I recall some of your use cases
run
> > > by
> > > passing in multiple config files. If that is still the case,
please
> > > send
> > > the command that is run so I know the order in which the files
are
> > > read.
> > >
> > > Thanks,
> > > George
> > >
> > > On Tue, Jun 8, 2021 at 7:59 AM perry.shafran at noaa.gov via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
>
> > > >
> > > > Hi, George,
> > > >
> > > > You can find my MET config files
> > > > here:
> > > >
> > >
> > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > 4.0.0/parm/met_config
> > > >
> > > > Specifically, the PB2NC and PointStat files that end with the
> > > > letters
> > > "cam"
> > > > are your best bet to look at.
> > > >
> > > > Do you need to look at METplus config files too for this?
> > > >
> > > > Thanks!
> > > >
> > > > Perry
> > > >
> > > > On Mon, Jun 7, 2021 at 3:35 PM George McCabe via RT
> > > > <met_help at ucar.edu
> > >
> > > > wrote:
> > > >
> > > > > Hi Perry,
> > > > >
> > > > > I was originally trying to fix the current problem until I
> > > > > learned
> > that
> > > > it
> > > > > was already fixed! Sounds good about sending over your
files,
> > > > > no
> > rush.
> > > > >
> > > > > Thanks,
> > > > > George
> > > > >
> > > > > On Mon, Jun 7, 2021 at 1:30 PM perry.shafran at noaa.gov via RT
<
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > > >
> > > > > > <URL:
> > > > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> > > > > >
> > > > > > Hi, George,
> > > > > >
> > > > > > OK, now I understand what you are trying to say. You're
not
> > > > > > trying
> > > to
> > > > > fix
> > > > > > a current problem, you are looking to help update my files
to
> > > > > > be
> > more
> > > > > > efficient. Then yes, let's be sure that we update the
config
> > > > > > files
> > > so
> > > > > that
> > > > > > we have the best set up going forward.
> > > > > >
> > > > > > It's probably better for you to make these changes, so
I'll
> > > > > > send
> > you
> > > my
> > > > > > config files and we'll go forward from there. I'm doing a
> > > > > > few
> > other
> > > > > things
> > > > > > to wrap up the day, so I'll send them along tomorrow.
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > Perry
> > > > > >
> > > > > > On Mon, Jun 7, 2021 at 12:22 PM George McCabe via RT <
> > > > met_help at ucar.edu>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Perry,
> > > > > > >
> > > > > > > It is good to hear that your issue was resolved. Your
_cam
> > > > > > > config
> > > > files
> > > > > > > should work fine with 4.0.0, but it would still be a
good
> > > > > > > idea to
> > > > > update
> > > > > > > your use cases to use the new approach. It will be a lot
> > > > > > > easier
> > to
> > > > > debug
> > > > > > > issues and update your configs to change settings. Also,
we
> > > > > > > can't
> > > > > > guarantee
> > > > > > > that things won't break in future versions if you are
using
> > > > > > > old
> > MET
> > > > > > config
> > > > > > > files that reference the old environment variables.
> > > > > > >
> > > > > > > If you'd rather just send me your MET config files and
the
> > > > > > > .conf
> > > > files
> > > > > > > used, I can update them for you. I could also have
someone
> > > > > > > pull
> > > them
> > > > > from
> > > > > > > WCOSS this afternoon. Below is some info on how to
update
> > > > > > > them
> > > > > yourself.
> > > > > > > The process is a little confusing, but once it is done
then
> > > > > > > it is
> > > > much,
> > > > > > > much easier to update and keep track of settings going
> > > > > > > forward.
> > > > > > >
> > > > > > > 1a. Diff your MET config files (PB2NCConfig_cam and
> > > > > PointStatConfig_cam)
> > > > > > > against the wrapped MET config files in the repository
for
> > > > > > > *v3.1*
> > > > (i.e.
> > > > > > > METplus-3.1/parm/met_config/PB2NCConfig_wrapped and
> > > > > > > PointStatConfig_wrapped). This will tell you which
values
> > > > > > > you had
> > > to
> > > > > > > override in your config file because they weren't
supported
> > > > > > > in
> > 3.1.
> > > > > > >
> > > > > > > 1b. Note that we discovered that there were some
incorrect
> > default
> > > > > values
> > > > > > > used here that have since been changed to match the MET
> > > > > > > config
> > > > defaults
> > > > > > (in
> > > > > > > share/met/config). These are outlined in the User's
Guide
> > > > > > > here:
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#pb2ncconfig
> > > > > > >
> > > > > > > Referring to this list, if your MET config file matches
the
> > > > > > > "New
> > > > > > (Correct)"
> > > > > > > value and the 3.1 wrapped config matches the "Old
> > > > > > > (Incorrect)"
> > > value,
> > > > > > then
> > > > > > > you don't need to add anything to your METplus config
for
> > > > > > > that
> > > item.
> > > > > > > For example, if your file has:
> > > > > > >
> > > > > > > *level_category = [];*
> > > > > > >
> > > > > > > and the wrapped config file has:
> > > > > > >
> > > > > > > *level_category = [0, 1, 4, 5, 6];*
> > > > > > >
> > > > > > > then you don't need to do anything in the METplus
config.
> > > > > > > Your
> > > value
> > > > > > > matches the new default and will be used. If your
version
> > > > > > > had
> > > > something
> > > > > > > like:
> > > > > > >
> > > > > > > * level_category = [2, 3]; *
> > > > > > >
> > > > > > > then in your METplus .conf file you would need to set:
> > > > > > >
> > > > > > > PB2NC_LEVEL_CATEGORY = 2, 3
> > > > > > >
> > > > > > > 1c. Info about the METplus conf variables that are
> > > > > > > available for
> > > each
> > > > > > > wrapper can be found here:
> > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#pb2nc-
> > met-conf
> > > > > > >
> > > > > > > If there is a conf variable that corresponds to the
value
> > > > > > > you
> > need
> > > to
> > > > > > > override in the MET config file, you can use that
instead.
> > > > > > > If
> > > support
> > > > > > for a
> > > > > > > variable in the MET config is not listed, then you can
> > > > > > > override
> > the
> > > > > > values
> > > > > > > using PB2NC_MET_CONFIG_OVERRIDES (see
> > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> >
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#overriding-
> > unsupported-met-configuration-variables
> > > > > > > ).
> > > > > > >
> > > > > > > 2. In your METplus .conf file, you will need to set
> > > PB2NC_CONFIG_FILE
> > > > > and
> > > > > > > POINT_STAT_CONFIG_FILE to point to the wrapped version
that
> > > > > > > is in
> > > the
> > > > > > parm
> > > > > > > directory.
> > > > > > >
> > > > > > > *PB2NC_CONFIG_FILE =
> > > > > > > {PARM_BASE}/met_config/PB2NCConfig_wrapped*
> > > > > > >
> > > > > > > *POINT_STAT_CONFIG_FILE
> > > > > ={PARM_BASE}/met_config/PointStatConfig_wrapped*
> > > > > > >
> > > > > > > You will never need to change these values going
forward,
> > > > > > > as any
> > > > > > > unsupported MET variables overrides can be done directly
in
> > > > > > > the
> > > > METplus
> > > > > > > .conf file.
> > > > > > >
> > > > > > > Again, I know this process can be confusing, so I am
happy
> > > > > > > to
> > make
> > > > the
> > > > > > > updates for you if you send me or point me to your
files.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > George
> > > > > > >
> > > > > > >
> > > > > > > On Mon, Jun 7, 2021 at 9:51 AM George McCabe
> > > > > > > <mccabe at ucar.edu>
> > > > wrote:
> > > > > > >
> > > > > > > > Hi Perry,
> > > > > > > >
> > > > > > > > Are these paths on WCOSS? If so, could you send me the
> > > > > > > > config
> > > > files?
> > > > > > > >
> > > > > > > > With the new approach, you will no longer have to
create
> > > > > > > > your
> > own
> > > > > > wrapped
> > > > > > > > config files. You will always use the versions in the
> > > > > > > > METplus
> > > > > > repository
> > > > > > > > (parm/met_config). Many of the settings that you would
> > > > > > > > change
> > are
> > > > now
> > > > > > > > supported via the METplus config files and any that
are
> > > > > > > > not can
> > > be
> > > > > set
> > > > > > in
> > > > > > > > the METplus config file as well. Your _cam config
files
> > > > > > > > should
> > > > still
> > > > > > work
> > > > > > > > the same as they did before, but it would be a good
idea
> > > > > > > > to
> > > update
> > > > > your
> > > > > > > > METplus configs to avoid using them.
> > > > > > > >
> > > > > > > > I will write up some suggestions to update your config
> > > > > > > > files to
> > > use
> > > > > the
> > > > > > > > new approach and reply here with the steps. If you'd
> > > > > > > > prefer, we
> > > > could
> > > > > > set
> > > > > > > > up a working session to go through them.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > George
> > > > > > > >
> > > > > > > > On Fri, Jun 4, 2021 at 9:26 AM perry.shafran at noaa.gov
via
> > > > > > > > RT <
> > > > > > > > met_help at ucar.edu> wrote:
> > > > > > > >
> > > > > > > >>
> > > > > > > >> Fri Jun 04 09:18:47 2021: Request 100108 was acted
upon.
> > > > > > > >> Transaction: Ticket created by perry.shafran at noaa.gov
> > > > > > > >> Queue: met_help
> > > > > > > >> Subject: config file changes for MET 10.0.0
> > > > > > > >> Owner: Nobody
> > > > > > > >> Requestors: perry.shafran at noaa.gov
> > > > > > > >> Status: new
> > > > > > > >> Ticket <URL:
> > > > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> > > > > > > >
> > > > > > > >>
> > > > > > > >>
> > > > > > > >> Hi, all,
> > > > > > > >>
> > > > > > > >> I'm trying to convert to MET 10.0.0, and it looks
like
> > > > > > > >> things
> > > have
> > > > > > > changed
> > > > > > > >> for the MET config files. Can you take a look at my
> > > > > > > >> config
> > > files
> > > > > and
> > > > > > > >> explain what would need to be changed? I think you
had
> > > discussed
> > > > > this
> > > > > > > >> before in a prior METplus user's meeting, but that
was
> > > > > > > >> so long
> > > ago
> > > > > > that
> > > > > > > I
> > > > > > > >> don't quite remember.
> > > > > > > >>
> > > > > > > >> The files to examine are both in the directory:
> > > > > > > >>
> > > > > > > >>
> > > > > > > >>
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
> > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > 4.0.0/parm/met_config
> > > > > > > >>
> > > > > > > >> and would be PB2NCConfig_cam and PointStatConfig_cam.
> > > > > > > >>
> > > > > > > >> What would be the best resource to compare the old
with
> > > > > > > >> the
> > new?
> > > > > Can
> > > > > > > you
> > > > > > > >> find that in the User's Guide?
> > > > > > > >>
> > > > > > > >> Thanks!
> > > > > > > >>
> > > > > > > >> Perry
> > > > > > > >>
> > > > > > > >> --
> > > > > > > >> Perry C. Shafran
> > > > > > > >> Verification/MEG Group Leader for IMSG
> > > > > > > >> VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > > >> Office: 301-683-3765
> > > > > > > >> Cell: 301-717-6454
> > > > > > > >> (he/him/his)
> > > > > > > >> perry.shafran at noaa.gov
> > > > > > > >>
> > > > > > > >>
> > > > > > > >
> > > > > > > > --
> > > > > > > > George McCabe - Software Engineer III
> > > > > > > > National Center for Atmospheric Research
> > > > > > > > Research Applications Laboratory
> > > > > > > > 303-497-2768
> > > > > > > > ---
> > > > > > > > My working day may not be your working day. Please do
not
> > > > > > > > feel
> > > > > obliged
> > > > > > to
> > > > > > > > reply to this email outside of your normal working
hours.
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > George McCabe - Software Engineer III
> > > > > > > National Center for Atmospheric Research
> > > > > > > Research Applications Laboratory
> > > > > > > 303-497-2768
> > > > > > > ---
> > > > > > > My working day may not be your working day. Please do
not
> > > > > > > feel
> > > > obliged
> > > > > to
> > > > > > > reply to this email outside of your normal working
hours.
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > Perry C. Shafran
> > > > > > Verification/MEG Group Leader for IMSG
> > > > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > Office: 301-683-3765
> > > > > > Cell: 301-717-6454
> > > > > > (he/him/his)
> > > > > > perry.shafran at noaa.gov
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > George McCabe - Software Engineer III
> > > > > National Center for Atmospheric Research
> > > > > Research Applications Laboratory
> > > > > 303-497-2768
> > > > > ---
> > > > > My working day may not be your working day. Please do not
feel
> > obliged
> > > to
> > > > > reply to this email outside of your normal working hours.
> > > > >
> > > > >
> > > >
> > > > --
> > > > Perry C. Shafran
> > > > Verification/MEG Group Leader for IMSG
> > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > Office: 301-683-3765
> > > > Cell: 301-717-6454
> > > > (he/him/his)
> > > > perry.shafran at noaa.gov
> > > >
> > > >
> > >
> > > --
> > > George McCabe - Software Engineer III
> > > National Center for Atmospheric Research
> > > Research Applications Laboratory
> > > 303-497-2768
> > > ---
> > > My working day may not be your working day. Please do not feel
> > > obliged to
> > > reply to this email outside of your normal working hours.
> > >
> > >
> >
> > --
> > Perry C. Shafran
> > Verification/MEG Group Leader for IMSG
> > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > Office: 301-683-3765
> > Cell: 301-717-6454
> > (he/him/his)
> > perry.shafran at noaa.gov
> >
> >
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: perry.shafran at noaa.gov
Time: Mon Jul 12 12:04:41 2021
Hi, George,
I will do so. Can you review with me the issue that we are talking
about
with wrapped MET config files vs unwrapped? I need to be able to
describe
it in the GitHub Discussion post.
Thanks!
Perry
On Mon, Jul 12, 2021 at 1:57 PM George McCabe via RT
<met_help at ucar.edu>
wrote:
> Hi Perry,
>
> I haven't forgotten about reviewing your config files, but I also
haven't
> had a chance to take care of the task yet. I am going to close this
ticket
> since the original issue was resolved and will correspond with you
via
> email. Please create a GitHub Discussions post if this needs to be
> addressed sooner than later.
>
> Thanks,
> George
>
> On Tue Jun 08 14:00:34 2021, mccabe wrote:
> > Thanks, Perry. I retrieved the files and will take a look. I am
going
> > on
> > vacation this week so I likely won't get to it until after I
return.
> >
> > - George
> >
> > On Tue, Jun 8, 2021 at 8:22 AM perry.shafran at noaa.gov via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> > >
> > > Hi, George,
> > >
> > > OK great! I'm not entirely sure, but I think that my run
command
> > > contains
> > > too many files because some of the files I had in there I
believe are
> > > unchanged from the standard METplus config files (from early in
my
> > > usage of
> > > METplus). I'll show you some of that.
> > >
> > > Yes, these are paths on WCOSS. I thought you had access to
this.
> > >
> > > The METplus config files
> > > are
> > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > 4.0.0/parm/use_cases/perry,
> > > pb2nc_cam.conf and point_stat_cam.conf.
> > >
> > > The command used is:
> > >
> > >
> > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > 3.1/ush/master_metplus.py
> > > -c
> > >
> > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > 3.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
> > > -c
> > >
> > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > 3.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
> > > -c
> > >
> > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > 3.1/parm/use_cases/perry/pb2nc_cam.conf
> > > -c
> > >
> > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > 3.1/parm/use_cases/perry/point_stat_cam.conf
> > > -c /gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/nam.conf -c
> > >
> > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > 3.1/parm/use_cases/perry/shared.conf
> > > -c /gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/shared_nam.conf -c
> > >
> > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > 3.1/parm/use_cases/perry/system_cam.conf
> > >
> > > You may replace the 3.1's with 4.0.0's as it would be the same
(and
> > > change
> > > master_metplus to run_metplus).
> > >
> > > Perry
> > >
> > > On Tue, Jun 8, 2021 at 10:03 AM George McCabe via RT
> > > <met_help at ucar.edu>
> > > wrote:
> > >
> > > > Hi Perry,
> > > >
> > > > Is that a path on WCOSS? I don't have access, so I will have
to ask
> > > someone
> > > > on the team to pull the files for me.
> > > >
> > > > Yes, I need the corresponding METplus config files because I
will
> > > > need to
> > > > add variables to those files. I recall some of your use cases
run
> > > > by
> > > > passing in multiple config files. If that is still the case,
please
> > > > send
> > > > the command that is run so I know the order in which the files
are
> > > > read.
> > > >
> > > > Thanks,
> > > > George
> > > >
> > > > On Tue, Jun 8, 2021 at 7:59 AM perry.shafran at noaa.gov via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> > > > >
> > > > > Hi, George,
> > > > >
> > > > > You can find my MET config files
> > > > > here:
> > > > >
> > > >
> > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > 4.0.0/parm/met_config
> > > > >
> > > > > Specifically, the PB2NC and PointStat files that end with
the
> > > > > letters
> > > > "cam"
> > > > > are your best bet to look at.
> > > > >
> > > > > Do you need to look at METplus config files too for this?
> > > > >
> > > > > Thanks!
> > > > >
> > > > > Perry
> > > > >
> > > > > On Mon, Jun 7, 2021 at 3:35 PM George McCabe via RT
> > > > > <met_help at ucar.edu
> > > >
> > > > > wrote:
> > > > >
> > > > > > Hi Perry,
> > > > > >
> > > > > > I was originally trying to fix the current problem until I
> > > > > > learned
> > > that
> > > > > it
> > > > > > was already fixed! Sounds good about sending over your
files,
> > > > > > no
> > > rush.
> > > > > >
> > > > > > Thanks,
> > > > > > George
> > > > > >
> > > > > > On Mon, Jun 7, 2021 at 1:30 PM perry.shafran at noaa.gov via
RT <
> > > > > > met_help at ucar.edu> wrote:
> > > > > >
> > > > > > >
> > > > > > > <URL:
> > > > > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
>
> > > > > > >
> > > > > > > Hi, George,
> > > > > > >
> > > > > > > OK, now I understand what you are trying to say. You're
not
> > > > > > > trying
> > > > to
> > > > > > fix
> > > > > > > a current problem, you are looking to help update my
files to
> > > > > > > be
> > > more
> > > > > > > efficient. Then yes, let's be sure that we update the
config
> > > > > > > files
> > > > so
> > > > > > that
> > > > > > > we have the best set up going forward.
> > > > > > >
> > > > > > > It's probably better for you to make these changes, so
I'll
> > > > > > > send
> > > you
> > > > my
> > > > > > > config files and we'll go forward from there. I'm doing
a
> > > > > > > few
> > > other
> > > > > > things
> > > > > > > to wrap up the day, so I'll send them along tomorrow.
> > > > > > >
> > > > > > > Thanks!
> > > > > > >
> > > > > > > Perry
> > > > > > >
> > > > > > > On Mon, Jun 7, 2021 at 12:22 PM George McCabe via RT <
> > > > > met_help at ucar.edu>
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Perry,
> > > > > > > >
> > > > > > > > It is good to hear that your issue was resolved. Your
_cam
> > > > > > > > config
> > > > > files
> > > > > > > > should work fine with 4.0.0, but it would still be a
good
> > > > > > > > idea to
> > > > > > update
> > > > > > > > your use cases to use the new approach. It will be a
lot
> > > > > > > > easier
> > > to
> > > > > > debug
> > > > > > > > issues and update your configs to change settings.
Also, we
> > > > > > > > can't
> > > > > > > guarantee
> > > > > > > > that things won't break in future versions if you are
using
> > > > > > > > old
> > > MET
> > > > > > > config
> > > > > > > > files that reference the old environment variables.
> > > > > > > >
> > > > > > > > If you'd rather just send me your MET config files and
the
> > > > > > > > .conf
> > > > > files
> > > > > > > > used, I can update them for you. I could also have
someone
> > > > > > > > pull
> > > > them
> > > > > > from
> > > > > > > > WCOSS this afternoon. Below is some info on how to
update
> > > > > > > > them
> > > > > > yourself.
> > > > > > > > The process is a little confusing, but once it is done
then
> > > > > > > > it is
> > > > > much,
> > > > > > > > much easier to update and keep track of settings going
> > > > > > > > forward.
> > > > > > > >
> > > > > > > > 1a. Diff your MET config files (PB2NCConfig_cam and
> > > > > > PointStatConfig_cam)
> > > > > > > > against the wrapped MET config files in the repository
for
> > > > > > > > *v3.1*
> > > > > (i.e.
> > > > > > > > METplus-3.1/parm/met_config/PB2NCConfig_wrapped and
> > > > > > > > PointStatConfig_wrapped). This will tell you which
values
> > > > > > > > you had
> > > > to
> > > > > > > > override in your config file because they weren't
supported
> > > > > > > > in
> > > 3.1.
> > > > > > > >
> > > > > > > > 1b. Note that we discovered that there were some
incorrect
> > > default
> > > > > > values
> > > > > > > > used here that have since been changed to match the
MET
> > > > > > > > config
> > > > > defaults
> > > > > > > (in
> > > > > > > > share/met/config). These are outlined in the User's
Guide
> > > > > > > > here:
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#pb2ncconfig
> > > > > > > >
> > > > > > > > Referring to this list, if your MET config file
matches the
> > > > > > > > "New
> > > > > > > (Correct)"
> > > > > > > > value and the 3.1 wrapped config matches the "Old
> > > > > > > > (Incorrect)"
> > > > value,
> > > > > > > then
> > > > > > > > you don't need to add anything to your METplus config
for
> > > > > > > > that
> > > > item.
> > > > > > > > For example, if your file has:
> > > > > > > >
> > > > > > > > *level_category = [];*
> > > > > > > >
> > > > > > > > and the wrapped config file has:
> > > > > > > >
> > > > > > > > *level_category = [0, 1, 4, 5, 6];*
> > > > > > > >
> > > > > > > > then you don't need to do anything in the METplus
config.
> > > > > > > > Your
> > > > value
> > > > > > > > matches the new default and will be used. If your
version
> > > > > > > > had
> > > > > something
> > > > > > > > like:
> > > > > > > >
> > > > > > > > * level_category = [2, 3]; *
> > > > > > > >
> > > > > > > > then in your METplus .conf file you would need to set:
> > > > > > > >
> > > > > > > > PB2NC_LEVEL_CATEGORY = 2, 3
> > > > > > > >
> > > > > > > > 1c. Info about the METplus conf variables that are
> > > > > > > > available for
> > > > each
> > > > > > > > wrapper can be found here:
> > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#pb2nc-
> > > met-conf
> > > > > > > >
> > > > > > > > If there is a conf variable that corresponds to the
value
> > > > > > > > you
> > > need
> > > > to
> > > > > > > > override in the MET config file, you can use that
instead.
> > > > > > > > If
> > > > support
> > > > > > > for a
> > > > > > > > variable in the MET config is not listed, then you can
> > > > > > > > override
> > > the
> > > > > > > values
> > > > > > > > using PB2NC_MET_CONFIG_OVERRIDES (see
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#overriding-
> > > unsupported-met-configuration-variables
> > > > > > > > ).
> > > > > > > >
> > > > > > > > 2. In your METplus .conf file, you will need to set
> > > > PB2NC_CONFIG_FILE
> > > > > > and
> > > > > > > > POINT_STAT_CONFIG_FILE to point to the wrapped version
that
> > > > > > > > is in
> > > > the
> > > > > > > parm
> > > > > > > > directory.
> > > > > > > >
> > > > > > > > *PB2NC_CONFIG_FILE =
> > > > > > > > {PARM_BASE}/met_config/PB2NCConfig_wrapped*
> > > > > > > >
> > > > > > > > *POINT_STAT_CONFIG_FILE
> > > > > > ={PARM_BASE}/met_config/PointStatConfig_wrapped*
> > > > > > > >
> > > > > > > > You will never need to change these values going
forward,
> > > > > > > > as any
> > > > > > > > unsupported MET variables overrides can be done
directly in
> > > > > > > > the
> > > > > METplus
> > > > > > > > .conf file.
> > > > > > > >
> > > > > > > > Again, I know this process can be confusing, so I am
happy
> > > > > > > > to
> > > make
> > > > > the
> > > > > > > > updates for you if you send me or point me to your
files.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > George
> > > > > > > >
> > > > > > > >
> > > > > > > > On Mon, Jun 7, 2021 at 9:51 AM George McCabe
> > > > > > > > <mccabe at ucar.edu>
> > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Perry,
> > > > > > > > >
> > > > > > > > > Are these paths on WCOSS? If so, could you send me
the
> > > > > > > > > config
> > > > > files?
> > > > > > > > >
> > > > > > > > > With the new approach, you will no longer have to
create
> > > > > > > > > your
> > > own
> > > > > > > wrapped
> > > > > > > > > config files. You will always use the versions in
the
> > > > > > > > > METplus
> > > > > > > repository
> > > > > > > > > (parm/met_config). Many of the settings that you
would
> > > > > > > > > change
> > > are
> > > > > now
> > > > > > > > > supported via the METplus config files and any that
are
> > > > > > > > > not can
> > > > be
> > > > > > set
> > > > > > > in
> > > > > > > > > the METplus config file as well. Your _cam config
files
> > > > > > > > > should
> > > > > still
> > > > > > > work
> > > > > > > > > the same as they did before, but it would be a good
idea
> > > > > > > > > to
> > > > update
> > > > > > your
> > > > > > > > > METplus configs to avoid using them.
> > > > > > > > >
> > > > > > > > > I will write up some suggestions to update your
config
> > > > > > > > > files to
> > > > use
> > > > > > the
> > > > > > > > > new approach and reply here with the steps. If you'd
> > > > > > > > > prefer, we
> > > > > could
> > > > > > > set
> > > > > > > > > up a working session to go through them.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > George
> > > > > > > > >
> > > > > > > > > On Fri, Jun 4, 2021 at 9:26 AM
perry.shafran at noaa.gov via
> > > > > > > > > RT <
> > > > > > > > > met_help at ucar.edu> wrote:
> > > > > > > > >
> > > > > > > > >>
> > > > > > > > >> Fri Jun 04 09:18:47 2021: Request 100108 was acted
upon.
> > > > > > > > >> Transaction: Ticket created by
perry.shafran at noaa.gov
> > > > > > > > >> Queue: met_help
> > > > > > > > >> Subject: config file changes for MET 10.0.0
> > > > > > > > >> Owner: Nobody
> > > > > > > > >> Requestors: perry.shafran at noaa.gov
> > > > > > > > >> Status: new
> > > > > > > > >> Ticket <URL:
> > > > > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> > > > > > > > >
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >> Hi, all,
> > > > > > > > >>
> > > > > > > > >> I'm trying to convert to MET 10.0.0, and it looks
like
> > > > > > > > >> things
> > > > have
> > > > > > > > changed
> > > > > > > > >> for the MET config files. Can you take a look at
my
> > > > > > > > >> config
> > > > files
> > > > > > and
> > > > > > > > >> explain what would need to be changed? I think you
had
> > > > discussed
> > > > > > this
> > > > > > > > >> before in a prior METplus user's meeting, but that
was
> > > > > > > > >> so long
> > > > ago
> > > > > > > that
> > > > > > > > I
> > > > > > > > >> don't quite remember.
> > > > > > > > >>
> > > > > > > > >> The files to examine are both in the directory:
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > 4.0.0/parm/met_config
> > > > > > > > >>
> > > > > > > > >> and would be PB2NCConfig_cam and
PointStatConfig_cam.
> > > > > > > > >>
> > > > > > > > >> What would be the best resource to compare the old
with
> > > > > > > > >> the
> > > new?
> > > > > > Can
> > > > > > > > you
> > > > > > > > >> find that in the User's Guide?
> > > > > > > > >>
> > > > > > > > >> Thanks!
> > > > > > > > >>
> > > > > > > > >> Perry
> > > > > > > > >>
> > > > > > > > >> --
> > > > > > > > >> Perry C. Shafran
> > > > > > > > >> Verification/MEG Group Leader for IMSG
> > > > > > > > >> VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > > > >> Office: 301-683-3765
> > > > > > > > >> Cell: 301-717-6454
> > > > > > > > >> (he/him/his)
> > > > > > > > >> perry.shafran at noaa.gov
> > > > > > > > >>
> > > > > > > > >>
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > George McCabe - Software Engineer III
> > > > > > > > > National Center for Atmospheric Research
> > > > > > > > > Research Applications Laboratory
> > > > > > > > > 303-497-2768
> > > > > > > > > ---
> > > > > > > > > My working day may not be your working day. Please
do not
> > > > > > > > > feel
> > > > > > obliged
> > > > > > > to
> > > > > > > > > reply to this email outside of your normal working
hours.
> > > > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > George McCabe - Software Engineer III
> > > > > > > > National Center for Atmospheric Research
> > > > > > > > Research Applications Laboratory
> > > > > > > > 303-497-2768
> > > > > > > > ---
> > > > > > > > My working day may not be your working day. Please do
not
> > > > > > > > feel
> > > > > obliged
> > > > > > to
> > > > > > > > reply to this email outside of your normal working
hours.
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Perry C. Shafran
> > > > > > > Verification/MEG Group Leader for IMSG
> > > > > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > > Office: 301-683-3765
> > > > > > > Cell: 301-717-6454
> > > > > > > (he/him/his)
> > > > > > > perry.shafran at noaa.gov
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > George McCabe - Software Engineer III
> > > > > > National Center for Atmospheric Research
> > > > > > Research Applications Laboratory
> > > > > > 303-497-2768
> > > > > > ---
> > > > > > My working day may not be your working day. Please do not
feel
> > > obliged
> > > > to
> > > > > > reply to this email outside of your normal working hours.
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Perry C. Shafran
> > > > > Verification/MEG Group Leader for IMSG
> > > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > Office: 301-683-3765
> > > > > Cell: 301-717-6454
> > > > > (he/him/his)
> > > > > perry.shafran at noaa.gov
> > > > >
> > > > >
> > > >
> > > > --
> > > > George McCabe - Software Engineer III
> > > > National Center for Atmospheric Research
> > > > Research Applications Laboratory
> > > > 303-497-2768
> > > > ---
> > > > My working day may not be your working day. Please do not feel
> > > > obliged to
> > > > reply to this email outside of your normal working hours.
> > > >
> > > >
> > >
> > > --
> > > Perry C. Shafran
> > > Verification/MEG Group Leader for IMSG
> > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > Office: 301-683-3765
> > > Cell: 301-717-6454
> > > (he/him/his)
> > > perry.shafran at noaa.gov
> > >
> > >
>
>
>
>
--
Perry C. Shafran
Verification/MEG Group Leader for IMSG
VPPPG Branch of EMC/NCEP/NOAA/NWS
Office: 301-683-3765
Cell: 301-717-6454
(he/him/his)
perry.shafran at noaa.gov
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: George McCabe
Time: Mon Jul 12 12:16:32 2021
Hi Perry,
Your current METplus configurations that use MET configuration files
that
have been modified to fit various needs still work fine using METplus
4.0.0. However, changes to the wrappers in this latest version remove
the
need to maintain these MET configuration files. All value overrides
needed
in MET configuration files can now be handled via METplus
configuration
variables. Updating your configuration files to use the new approach
will
make it easier for us to debug issues and easier for you to utilize
new
enhancements to the tools.
- George
On Mon, Jul 12, 2021 at 12:04 PM perry.shafran at noaa.gov via RT <
met_help at ucar.edu> wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
>
> Hi, George,
>
> I will do so. Can you review with me the issue that we are talking
about
> with wrapped MET config files vs unwrapped? I need to be able to
describe
> it in the GitHub Discussion post.
>
> Thanks!
>
> Perry
>
> On Mon, Jul 12, 2021 at 1:57 PM George McCabe via RT
<met_help at ucar.edu>
> wrote:
>
> > Hi Perry,
> >
> > I haven't forgotten about reviewing your config files, but I also
haven't
> > had a chance to take care of the task yet. I am going to close
this
> ticket
> > since the original issue was resolved and will correspond with you
via
> > email. Please create a GitHub Discussions post if this needs to be
> > addressed sooner than later.
> >
> > Thanks,
> > George
> >
> > On Tue Jun 08 14:00:34 2021, mccabe wrote:
> > > Thanks, Perry. I retrieved the files and will take a look. I am
going
> > > on
> > > vacation this week so I likely won't get to it until after I
return.
> > >
> > > - George
> > >
> > > On Tue, Jun 8, 2021 at 8:22 AM perry.shafran at noaa.gov via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
>
> > > >
> > > > Hi, George,
> > > >
> > > > OK great! I'm not entirely sure, but I think that my run
command
> > > > contains
> > > > too many files because some of the files I had in there I
believe are
> > > > unchanged from the standard METplus config files (from early
in my
> > > > usage of
> > > > METplus). I'll show you some of that.
> > > >
> > > > Yes, these are paths on WCOSS. I thought you had access to
this.
> > > >
> > > > The METplus config files
> > > > are
> > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > 4.0.0/parm/use_cases/perry,
> > > > pb2nc_cam.conf and point_stat_cam.conf.
> > > >
> > > > The command used is:
> > > >
> > > >
> > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > 3.1/ush/master_metplus.py
> > > > -c
> > > >
> > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > 3.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
> > > > -c
> > > >
> > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > 3.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
> > > > -c
> > > >
> > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > 3.1/parm/use_cases/perry/pb2nc_cam.conf
> > > > -c
> > > >
> > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > 3.1/parm/use_cases/perry/point_stat_cam.conf
> > > > -c /gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/nam.conf -c
> > > >
> > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > 3.1/parm/use_cases/perry/shared.conf
> > > > -c /gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/shared_nam.conf
-c
> > > >
> > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > 3.1/parm/use_cases/perry/system_cam.conf
> > > >
> > > > You may replace the 3.1's with 4.0.0's as it would be the same
(and
> > > > change
> > > > master_metplus to run_metplus).
> > > >
> > > > Perry
> > > >
> > > > On Tue, Jun 8, 2021 at 10:03 AM George McCabe via RT
> > > > <met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > > Hi Perry,
> > > > >
> > > > > Is that a path on WCOSS? I don't have access, so I will have
to ask
> > > > someone
> > > > > on the team to pull the files for me.
> > > > >
> > > > > Yes, I need the corresponding METplus config files because I
will
> > > > > need to
> > > > > add variables to those files. I recall some of your use
cases run
> > > > > by
> > > > > passing in multiple config files. If that is still the case,
please
> > > > > send
> > > > > the command that is run so I know the order in which the
files are
> > > > > read.
> > > > >
> > > > > Thanks,
> > > > > George
> > > > >
> > > > > On Tue, Jun 8, 2021 at 7:59 AM perry.shafran at noaa.gov via RT
<
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > > >
> > > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> > > > > >
> > > > > > Hi, George,
> > > > > >
> > > > > > You can find my MET config files
> > > > > > here:
> > > > > >
> > > > >
> > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > 4.0.0/parm/met_config
> > > > > >
> > > > > > Specifically, the PB2NC and PointStat files that end with
the
> > > > > > letters
> > > > > "cam"
> > > > > > are your best bet to look at.
> > > > > >
> > > > > > Do you need to look at METplus config files too for this?
> > > > > >
> > > > > > Thanks!
> > > > > >
> > > > > > Perry
> > > > > >
> > > > > > On Mon, Jun 7, 2021 at 3:35 PM George McCabe via RT
> > > > > > <met_help at ucar.edu
> > > > >
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Perry,
> > > > > > >
> > > > > > > I was originally trying to fix the current problem until
I
> > > > > > > learned
> > > > that
> > > > > > it
> > > > > > > was already fixed! Sounds good about sending over your
files,
> > > > > > > no
> > > > rush.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > George
> > > > > > >
> > > > > > > On Mon, Jun 7, 2021 at 1:30 PM perry.shafran at noaa.gov
via RT <
> > > > > > > met_help at ucar.edu> wrote:
> > > > > > >
> > > > > > > >
> > > > > > > > <URL:
> > > > > > > >
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> > > > > > > >
> > > > > > > > Hi, George,
> > > > > > > >
> > > > > > > > OK, now I understand what you are trying to say.
You're not
> > > > > > > > trying
> > > > > to
> > > > > > > fix
> > > > > > > > a current problem, you are looking to help update my
files to
> > > > > > > > be
> > > > more
> > > > > > > > efficient. Then yes, let's be sure that we update the
config
> > > > > > > > files
> > > > > so
> > > > > > > that
> > > > > > > > we have the best set up going forward.
> > > > > > > >
> > > > > > > > It's probably better for you to make these changes, so
I'll
> > > > > > > > send
> > > > you
> > > > > my
> > > > > > > > config files and we'll go forward from there. I'm
doing a
> > > > > > > > few
> > > > other
> > > > > > > things
> > > > > > > > to wrap up the day, so I'll send them along tomorrow.
> > > > > > > >
> > > > > > > > Thanks!
> > > > > > > >
> > > > > > > > Perry
> > > > > > > >
> > > > > > > > On Mon, Jun 7, 2021 at 12:22 PM George McCabe via RT <
> > > > > > met_help at ucar.edu>
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Perry,
> > > > > > > > >
> > > > > > > > > It is good to hear that your issue was resolved.
Your _cam
> > > > > > > > > config
> > > > > > files
> > > > > > > > > should work fine with 4.0.0, but it would still be a
good
> > > > > > > > > idea to
> > > > > > > update
> > > > > > > > > your use cases to use the new approach. It will be a
lot
> > > > > > > > > easier
> > > > to
> > > > > > > debug
> > > > > > > > > issues and update your configs to change settings.
Also, we
> > > > > > > > > can't
> > > > > > > > guarantee
> > > > > > > > > that things won't break in future versions if you
are using
> > > > > > > > > old
> > > > MET
> > > > > > > > config
> > > > > > > > > files that reference the old environment variables.
> > > > > > > > >
> > > > > > > > > If you'd rather just send me your MET config files
and the
> > > > > > > > > .conf
> > > > > > files
> > > > > > > > > used, I can update them for you. I could also have
someone
> > > > > > > > > pull
> > > > > them
> > > > > > > from
> > > > > > > > > WCOSS this afternoon. Below is some info on how to
update
> > > > > > > > > them
> > > > > > > yourself.
> > > > > > > > > The process is a little confusing, but once it is
done then
> > > > > > > > > it is
> > > > > > much,
> > > > > > > > > much easier to update and keep track of settings
going
> > > > > > > > > forward.
> > > > > > > > >
> > > > > > > > > 1a. Diff your MET config files (PB2NCConfig_cam and
> > > > > > > PointStatConfig_cam)
> > > > > > > > > against the wrapped MET config files in the
repository for
> > > > > > > > > *v3.1*
> > > > > > (i.e.
> > > > > > > > > METplus-3.1/parm/met_config/PB2NCConfig_wrapped and
> > > > > > > > > PointStatConfig_wrapped). This will tell you which
values
> > > > > > > > > you had
> > > > > to
> > > > > > > > > override in your config file because they weren't
supported
> > > > > > > > > in
> > > > 3.1.
> > > > > > > > >
> > > > > > > > > 1b. Note that we discovered that there were some
incorrect
> > > > default
> > > > > > > values
> > > > > > > > > used here that have since been changed to match the
MET
> > > > > > > > > config
> > > > > > defaults
> > > > > > > > (in
> > > > > > > > > share/met/config). These are outlined in the User's
Guide
> > > > > > > > > here:
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#pb2ncconfig
> > > > > > > > >
> > > > > > > > > Referring to this list, if your MET config file
matches the
> > > > > > > > > "New
> > > > > > > > (Correct)"
> > > > > > > > > value and the 3.1 wrapped config matches the "Old
> > > > > > > > > (Incorrect)"
> > > > > value,
> > > > > > > > then
> > > > > > > > > you don't need to add anything to your METplus
config for
> > > > > > > > > that
> > > > > item.
> > > > > > > > > For example, if your file has:
> > > > > > > > >
> > > > > > > > > *level_category = [];*
> > > > > > > > >
> > > > > > > > > and the wrapped config file has:
> > > > > > > > >
> > > > > > > > > *level_category = [0, 1, 4, 5, 6];*
> > > > > > > > >
> > > > > > > > > then you don't need to do anything in the METplus
config.
> > > > > > > > > Your
> > > > > value
> > > > > > > > > matches the new default and will be used. If your
version
> > > > > > > > > had
> > > > > > something
> > > > > > > > > like:
> > > > > > > > >
> > > > > > > > > * level_category = [2, 3]; *
> > > > > > > > >
> > > > > > > > > then in your METplus .conf file you would need to
set:
> > > > > > > > >
> > > > > > > > > PB2NC_LEVEL_CATEGORY = 2, 3
> > > > > > > > >
> > > > > > > > > 1c. Info about the METplus conf variables that are
> > > > > > > > > available for
> > > > > each
> > > > > > > > > wrapper can be found here:
> > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#pb2nc-
> > > > met-conf
> > > > > > > > >
> > > > > > > > > If there is a conf variable that corresponds to the
value
> > > > > > > > > you
> > > > need
> > > > > to
> > > > > > > > > override in the MET config file, you can use that
instead.
> > > > > > > > > If
> > > > > support
> > > > > > > > for a
> > > > > > > > > variable in the MET config is not listed, then you
can
> > > > > > > > > override
> > > > the
> > > > > > > > values
> > > > > > > > > using PB2NC_MET_CONFIG_OVERRIDES (see
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#overriding-
> > > > unsupported-met-configuration-variables
> > > > > > > > > ).
> > > > > > > > >
> > > > > > > > > 2. In your METplus .conf file, you will need to set
> > > > > PB2NC_CONFIG_FILE
> > > > > > > and
> > > > > > > > > POINT_STAT_CONFIG_FILE to point to the wrapped
version that
> > > > > > > > > is in
> > > > > the
> > > > > > > > parm
> > > > > > > > > directory.
> > > > > > > > >
> > > > > > > > > *PB2NC_CONFIG_FILE =
> > > > > > > > > {PARM_BASE}/met_config/PB2NCConfig_wrapped*
> > > > > > > > >
> > > > > > > > > *POINT_STAT_CONFIG_FILE
> > > > > > > ={PARM_BASE}/met_config/PointStatConfig_wrapped*
> > > > > > > > >
> > > > > > > > > You will never need to change these values going
forward,
> > > > > > > > > as any
> > > > > > > > > unsupported MET variables overrides can be done
directly in
> > > > > > > > > the
> > > > > > METplus
> > > > > > > > > .conf file.
> > > > > > > > >
> > > > > > > > > Again, I know this process can be confusing, so I am
happy
> > > > > > > > > to
> > > > make
> > > > > > the
> > > > > > > > > updates for you if you send me or point me to your
files.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > George
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > On Mon, Jun 7, 2021 at 9:51 AM George McCabe
> > > > > > > > > <mccabe at ucar.edu>
> > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi Perry,
> > > > > > > > > >
> > > > > > > > > > Are these paths on WCOSS? If so, could you send me
the
> > > > > > > > > > config
> > > > > > files?
> > > > > > > > > >
> > > > > > > > > > With the new approach, you will no longer have to
create
> > > > > > > > > > your
> > > > own
> > > > > > > > wrapped
> > > > > > > > > > config files. You will always use the versions in
the
> > > > > > > > > > METplus
> > > > > > > > repository
> > > > > > > > > > (parm/met_config). Many of the settings that you
would
> > > > > > > > > > change
> > > > are
> > > > > > now
> > > > > > > > > > supported via the METplus config files and any
that are
> > > > > > > > > > not can
> > > > > be
> > > > > > > set
> > > > > > > > in
> > > > > > > > > > the METplus config file as well. Your _cam config
files
> > > > > > > > > > should
> > > > > > still
> > > > > > > > work
> > > > > > > > > > the same as they did before, but it would be a
good idea
> > > > > > > > > > to
> > > > > update
> > > > > > > your
> > > > > > > > > > METplus configs to avoid using them.
> > > > > > > > > >
> > > > > > > > > > I will write up some suggestions to update your
config
> > > > > > > > > > files to
> > > > > use
> > > > > > > the
> > > > > > > > > > new approach and reply here with the steps. If
you'd
> > > > > > > > > > prefer, we
> > > > > > could
> > > > > > > > set
> > > > > > > > > > up a working session to go through them.
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > > George
> > > > > > > > > >
> > > > > > > > > > On Fri, Jun 4, 2021 at 9:26 AM
perry.shafran at noaa.gov
> via
> > > > > > > > > > RT <
> > > > > > > > > > met_help at ucar.edu> wrote:
> > > > > > > > > >
> > > > > > > > > >>
> > > > > > > > > >> Fri Jun 04 09:18:47 2021: Request 100108 was
acted upon.
> > > > > > > > > >> Transaction: Ticket created by
perry.shafran at noaa.gov
> > > > > > > > > >> Queue: met_help
> > > > > > > > > >> Subject: config file changes for MET 10.0.0
> > > > > > > > > >> Owner: Nobody
> > > > > > > > > >> Requestors: perry.shafran at noaa.gov
> > > > > > > > > >> Status: new
> > > > > > > > > >> Ticket <URL:
> > > > > > > >
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> > > > > > > > > >
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >> Hi, all,
> > > > > > > > > >>
> > > > > > > > > >> I'm trying to convert to MET 10.0.0, and it looks
like
> > > > > > > > > >> things
> > > > > have
> > > > > > > > > changed
> > > > > > > > > >> for the MET config files. Can you take a look at
my
> > > > > > > > > >> config
> > > > > files
> > > > > > > and
> > > > > > > > > >> explain what would need to be changed? I think
you had
> > > > > discussed
> > > > > > > this
> > > > > > > > > >> before in a prior METplus user's meeting, but
that was
> > > > > > > > > >> so long
> > > > > ago
> > > > > > > > that
> > > > > > > > > I
> > > > > > > > > >> don't quite remember.
> > > > > > > > > >>
> > > > > > > > > >> The files to examine are both in the directory:
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > 4.0.0/parm/met_config
> > > > > > > > > >>
> > > > > > > > > >> and would be PB2NCConfig_cam and
PointStatConfig_cam.
> > > > > > > > > >>
> > > > > > > > > >> What would be the best resource to compare the
old with
> > > > > > > > > >> the
> > > > new?
> > > > > > > Can
> > > > > > > > > you
> > > > > > > > > >> find that in the User's Guide?
> > > > > > > > > >>
> > > > > > > > > >> Thanks!
> > > > > > > > > >>
> > > > > > > > > >> Perry
> > > > > > > > > >>
> > > > > > > > > >> --
> > > > > > > > > >> Perry C. Shafran
> > > > > > > > > >> Verification/MEG Group Leader for IMSG
> > > > > > > > > >> VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > > > > >> Office: 301-683-3765
> > > > > > > > > >> Cell: 301-717-6454
> > > > > > > > > >> (he/him/his)
> > > > > > > > > >> perry.shafran at noaa.gov
> > > > > > > > > >>
> > > > > > > > > >>
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > George McCabe - Software Engineer III
> > > > > > > > > > National Center for Atmospheric Research
> > > > > > > > > > Research Applications Laboratory
> > > > > > > > > > 303-497-2768
> > > > > > > > > > ---
> > > > > > > > > > My working day may not be your working day. Please
do not
> > > > > > > > > > feel
> > > > > > > obliged
> > > > > > > > to
> > > > > > > > > > reply to this email outside of your normal working
hours.
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > George McCabe - Software Engineer III
> > > > > > > > > National Center for Atmospheric Research
> > > > > > > > > Research Applications Laboratory
> > > > > > > > > 303-497-2768
> > > > > > > > > ---
> > > > > > > > > My working day may not be your working day. Please
do not
> > > > > > > > > feel
> > > > > > obliged
> > > > > > > to
> > > > > > > > > reply to this email outside of your normal working
hours.
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Perry C. Shafran
> > > > > > > > Verification/MEG Group Leader for IMSG
> > > > > > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > > > Office: 301-683-3765
> > > > > > > > Cell: 301-717-6454
> > > > > > > > (he/him/his)
> > > > > > > > perry.shafran at noaa.gov
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > George McCabe - Software Engineer III
> > > > > > > National Center for Atmospheric Research
> > > > > > > Research Applications Laboratory
> > > > > > > 303-497-2768
> > > > > > > ---
> > > > > > > My working day may not be your working day. Please do
not feel
> > > > obliged
> > > > > to
> > > > > > > reply to this email outside of your normal working
hours.
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > Perry C. Shafran
> > > > > > Verification/MEG Group Leader for IMSG
> > > > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > Office: 301-683-3765
> > > > > > Cell: 301-717-6454
> > > > > > (he/him/his)
> > > > > > perry.shafran at noaa.gov
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > George McCabe - Software Engineer III
> > > > > National Center for Atmospheric Research
> > > > > Research Applications Laboratory
> > > > > 303-497-2768
> > > > > ---
> > > > > My working day may not be your working day. Please do not
feel
> > > > > obliged to
> > > > > reply to this email outside of your normal working hours.
> > > > >
> > > > >
> > > >
> > > > --
> > > > Perry C. Shafran
> > > > Verification/MEG Group Leader for IMSG
> > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > Office: 301-683-3765
> > > > Cell: 301-717-6454
> > > > (he/him/his)
> > > > perry.shafran at noaa.gov
> > > >
> > > >
> >
> >
> >
> >
>
> --
> Perry C. Shafran
> Verification/MEG Group Leader for IMSG
> VPPPG Branch of EMC/NCEP/NOAA/NWS
> Office: 301-683-3765
> Cell: 301-717-6454
> (he/him/his)
> perry.shafran at noaa.gov
>
>
--
George McCabe - Software Engineer III
National Center for Atmospheric Research
Research Applications Laboratory
303-497-2768
---
My working day may not be your working day. Please do not feel obliged
to
reply to this email outside of your normal working hours.
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: perry.shafran at noaa.gov
Time: Mon Jul 12 12:17:31 2021
Right-o, thanks! I'll characterize that as a GitHub question, thanks!
Perry
On Mon, Jul 12, 2021 at 2:16 PM George McCabe via RT
<met_help at ucar.edu>
wrote:
> Hi Perry,
>
> Your current METplus configurations that use MET configuration files
that
> have been modified to fit various needs still work fine using
METplus
> 4.0.0. However, changes to the wrappers in this latest version
remove the
> need to maintain these MET configuration files. All value overrides
needed
> in MET configuration files can now be handled via METplus
configuration
> variables. Updating your configuration files to use the new approach
will
> make it easier for us to debug issues and easier for you to utilize
new
> enhancements to the tools.
>
> - George
>
> On Mon, Jul 12, 2021 at 12:04 PM perry.shafran at noaa.gov via RT <
> met_help at ucar.edu> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> >
> > Hi, George,
> >
> > I will do so. Can you review with me the issue that we are
talking about
> > with wrapped MET config files vs unwrapped? I need to be able to
> describe
> > it in the GitHub Discussion post.
> >
> > Thanks!
> >
> > Perry
> >
> > On Mon, Jul 12, 2021 at 1:57 PM George McCabe via RT
<met_help at ucar.edu>
> > wrote:
> >
> > > Hi Perry,
> > >
> > > I haven't forgotten about reviewing your config files, but I
also
> haven't
> > > had a chance to take care of the task yet. I am going to close
this
> > ticket
> > > since the original issue was resolved and will correspond with
you via
> > > email. Please create a GitHub Discussions post if this needs to
be
> > > addressed sooner than later.
> > >
> > > Thanks,
> > > George
> > >
> > > On Tue Jun 08 14:00:34 2021, mccabe wrote:
> > > > Thanks, Perry. I retrieved the files and will take a look. I
am going
> > > > on
> > > > vacation this week so I likely won't get to it until after I
return.
> > > >
> > > > - George
> > > >
> > > > On Tue, Jun 8, 2021 at 8:22 AM perry.shafran at noaa.gov via RT <
> > > > met_help at ucar.edu> wrote:
> > > >
> > > > >
> > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> > > > >
> > > > > Hi, George,
> > > > >
> > > > > OK great! I'm not entirely sure, but I think that my run
command
> > > > > contains
> > > > > too many files because some of the files I had in there I
believe
> are
> > > > > unchanged from the standard METplus config files (from early
in my
> > > > > usage of
> > > > > METplus). I'll show you some of that.
> > > > >
> > > > > Yes, these are paths on WCOSS. I thought you had access to
this.
> > > > >
> > > > > The METplus config files
> > > > > are
> > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > 4.0.0/parm/use_cases/perry,
> > > > > pb2nc_cam.conf and point_stat_cam.conf.
> > > > >
> > > > > The command used is:
> > > > >
> > > > >
> > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > 3.1/ush/master_metplus.py
> > > > > -c
> > > > >
> > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > 3.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
> > > > > -c
> > > > >
> > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > 3.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
> > > > > -c
> > > > >
> > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > 3.1/parm/use_cases/perry/pb2nc_cam.conf
> > > > > -c
> > > > >
> > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > 3.1/parm/use_cases/perry/point_stat_cam.conf
> > > > > -c /gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/nam.conf -c
> > > > >
> > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > 3.1/parm/use_cases/perry/shared.conf
> > > > > -c
/gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/shared_nam.conf -c
> > > > >
> > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > 3.1/parm/use_cases/perry/system_cam.conf
> > > > >
> > > > > You may replace the 3.1's with 4.0.0's as it would be the
same (and
> > > > > change
> > > > > master_metplus to run_metplus).
> > > > >
> > > > > Perry
> > > > >
> > > > > On Tue, Jun 8, 2021 at 10:03 AM George McCabe via RT
> > > > > <met_help at ucar.edu>
> > > > > wrote:
> > > > >
> > > > > > Hi Perry,
> > > > > >
> > > > > > Is that a path on WCOSS? I don't have access, so I will
have to
> ask
> > > > > someone
> > > > > > on the team to pull the files for me.
> > > > > >
> > > > > > Yes, I need the corresponding METplus config files because
I will
> > > > > > need to
> > > > > > add variables to those files. I recall some of your use
cases run
> > > > > > by
> > > > > > passing in multiple config files. If that is still the
case,
> please
> > > > > > send
> > > > > > the command that is run so I know the order in which the
files
> are
> > > > > > read.
> > > > > >
> > > > > > Thanks,
> > > > > > George
> > > > > >
> > > > > > On Tue, Jun 8, 2021 at 7:59 AM perry.shafran at noaa.gov via
RT <
> > > > > > met_help at ucar.edu> wrote:
> > > > > >
> > > > > > >
> > > > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> >
> > > > > > >
> > > > > > > Hi, George,
> > > > > > >
> > > > > > > You can find my MET config files
> > > > > > > here:
> > > > > > >
> > > > > >
> > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > 4.0.0/parm/met_config
> > > > > > >
> > > > > > > Specifically, the PB2NC and PointStat files that end
with the
> > > > > > > letters
> > > > > > "cam"
> > > > > > > are your best bet to look at.
> > > > > > >
> > > > > > > Do you need to look at METplus config files too for
this?
> > > > > > >
> > > > > > > Thanks!
> > > > > > >
> > > > > > > Perry
> > > > > > >
> > > > > > > On Mon, Jun 7, 2021 at 3:35 PM George McCabe via RT
> > > > > > > <met_help at ucar.edu
> > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > > Hi Perry,
> > > > > > > >
> > > > > > > > I was originally trying to fix the current problem
until I
> > > > > > > > learned
> > > > > that
> > > > > > > it
> > > > > > > > was already fixed! Sounds good about sending over your
files,
> > > > > > > > no
> > > > > rush.
> > > > > > > >
> > > > > > > > Thanks,
> > > > > > > > George
> > > > > > > >
> > > > > > > > On Mon, Jun 7, 2021 at 1:30 PM perry.shafran at noaa.gov
via
> RT <
> > > > > > > > met_help at ucar.edu> wrote:
> > > > > > > >
> > > > > > > > >
> > > > > > > > > <URL:
> > > > > > > > >
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> > > > > > > > >
> > > > > > > > > Hi, George,
> > > > > > > > >
> > > > > > > > > OK, now I understand what you are trying to say.
You're
> not
> > > > > > > > > trying
> > > > > > to
> > > > > > > > fix
> > > > > > > > > a current problem, you are looking to help update my
files
> to
> > > > > > > > > be
> > > > > more
> > > > > > > > > efficient. Then yes, let's be sure that we update
the
> config
> > > > > > > > > files
> > > > > > so
> > > > > > > > that
> > > > > > > > > we have the best set up going forward.
> > > > > > > > >
> > > > > > > > > It's probably better for you to make these changes,
so I'll
> > > > > > > > > send
> > > > > you
> > > > > > my
> > > > > > > > > config files and we'll go forward from there. I'm
doing a
> > > > > > > > > few
> > > > > other
> > > > > > > > things
> > > > > > > > > to wrap up the day, so I'll send them along
tomorrow.
> > > > > > > > >
> > > > > > > > > Thanks!
> > > > > > > > >
> > > > > > > > > Perry
> > > > > > > > >
> > > > > > > > > On Mon, Jun 7, 2021 at 12:22 PM George McCabe via RT
<
> > > > > > > met_help at ucar.edu>
> > > > > > > > > wrote:
> > > > > > > > >
> > > > > > > > > > Hi Perry,
> > > > > > > > > >
> > > > > > > > > > It is good to hear that your issue was resolved.
Your
> _cam
> > > > > > > > > > config
> > > > > > > files
> > > > > > > > > > should work fine with 4.0.0, but it would still be
a good
> > > > > > > > > > idea to
> > > > > > > > update
> > > > > > > > > > your use cases to use the new approach. It will be
a lot
> > > > > > > > > > easier
> > > > > to
> > > > > > > > debug
> > > > > > > > > > issues and update your configs to change settings.
Also,
> we
> > > > > > > > > > can't
> > > > > > > > > guarantee
> > > > > > > > > > that things won't break in future versions if you
are
> using
> > > > > > > > > > old
> > > > > MET
> > > > > > > > > config
> > > > > > > > > > files that reference the old environment
variables.
> > > > > > > > > >
> > > > > > > > > > If you'd rather just send me your MET config files
and
> the
> > > > > > > > > > .conf
> > > > > > > files
> > > > > > > > > > used, I can update them for you. I could also have
> someone
> > > > > > > > > > pull
> > > > > > them
> > > > > > > > from
> > > > > > > > > > WCOSS this afternoon. Below is some info on how to
update
> > > > > > > > > > them
> > > > > > > > yourself.
> > > > > > > > > > The process is a little confusing, but once it is
done
> then
> > > > > > > > > > it is
> > > > > > > much,
> > > > > > > > > > much easier to update and keep track of settings
going
> > > > > > > > > > forward.
> > > > > > > > > >
> > > > > > > > > > 1a. Diff your MET config files (PB2NCConfig_cam
and
> > > > > > > > PointStatConfig_cam)
> > > > > > > > > > against the wrapped MET config files in the
repository
> for
> > > > > > > > > > *v3.1*
> > > > > > > (i.e.
> > > > > > > > > > METplus-3.1/parm/met_config/PB2NCConfig_wrapped
and
> > > > > > > > > > PointStatConfig_wrapped). This will tell you which
values
> > > > > > > > > > you had
> > > > > > to
> > > > > > > > > > override in your config file because they weren't
> supported
> > > > > > > > > > in
> > > > > 3.1.
> > > > > > > > > >
> > > > > > > > > > 1b. Note that we discovered that there were some
> incorrect
> > > > > default
> > > > > > > > values
> > > > > > > > > > used here that have since been changed to match
the MET
> > > > > > > > > > config
> > > > > > > defaults
> > > > > > > > > (in
> > > > > > > > > > share/met/config). These are outlined in the
User's Guide
> > > > > > > > > > here:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#pb2ncconfig
> > > > > > > > > >
> > > > > > > > > > Referring to this list, if your MET config file
matches
> the
> > > > > > > > > > "New
> > > > > > > > > (Correct)"
> > > > > > > > > > value and the 3.1 wrapped config matches the "Old
> > > > > > > > > > (Incorrect)"
> > > > > > value,
> > > > > > > > > then
> > > > > > > > > > you don't need to add anything to your METplus
config for
> > > > > > > > > > that
> > > > > > item.
> > > > > > > > > > For example, if your file has:
> > > > > > > > > >
> > > > > > > > > > *level_category = [];*
> > > > > > > > > >
> > > > > > > > > > and the wrapped config file has:
> > > > > > > > > >
> > > > > > > > > > *level_category = [0, 1, 4, 5, 6];*
> > > > > > > > > >
> > > > > > > > > > then you don't need to do anything in the METplus
config.
> > > > > > > > > > Your
> > > > > > value
> > > > > > > > > > matches the new default and will be used. If your
version
> > > > > > > > > > had
> > > > > > > something
> > > > > > > > > > like:
> > > > > > > > > >
> > > > > > > > > > * level_category = [2, 3]; *
> > > > > > > > > >
> > > > > > > > > > then in your METplus .conf file you would need to
set:
> > > > > > > > > >
> > > > > > > > > > PB2NC_LEVEL_CATEGORY = 2, 3
> > > > > > > > > >
> > > > > > > > > > 1c. Info about the METplus conf variables that are
> > > > > > > > > > available for
> > > > > > each
> > > > > > > > > > wrapper can be found here:
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#pb2nc-
> > > > > met-conf
> > > > > > > > > >
> > > > > > > > > > If there is a conf variable that corresponds to
the value
> > > > > > > > > > you
> > > > > need
> > > > > > to
> > > > > > > > > > override in the MET config file, you can use that
> instead.
> > > > > > > > > > If
> > > > > > support
> > > > > > > > > for a
> > > > > > > > > > variable in the MET config is not listed, then you
can
> > > > > > > > > > override
> > > > > the
> > > > > > > > > values
> > > > > > > > > > using PB2NC_MET_CONFIG_OVERRIDES (see
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > >
> > >
> >
>
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#overriding-
> > > > > unsupported-met-configuration-variables
> > > > > > > > > > ).
> > > > > > > > > >
> > > > > > > > > > 2. In your METplus .conf file, you will need to
set
> > > > > > PB2NC_CONFIG_FILE
> > > > > > > > and
> > > > > > > > > > POINT_STAT_CONFIG_FILE to point to the wrapped
version
> that
> > > > > > > > > > is in
> > > > > > the
> > > > > > > > > parm
> > > > > > > > > > directory.
> > > > > > > > > >
> > > > > > > > > > *PB2NC_CONFIG_FILE =
> > > > > > > > > > {PARM_BASE}/met_config/PB2NCConfig_wrapped*
> > > > > > > > > >
> > > > > > > > > > *POINT_STAT_CONFIG_FILE
> > > > > > > > ={PARM_BASE}/met_config/PointStatConfig_wrapped*
> > > > > > > > > >
> > > > > > > > > > You will never need to change these values going
forward,
> > > > > > > > > > as any
> > > > > > > > > > unsupported MET variables overrides can be done
directly
> in
> > > > > > > > > > the
> > > > > > > METplus
> > > > > > > > > > .conf file.
> > > > > > > > > >
> > > > > > > > > > Again, I know this process can be confusing, so I
am
> happy
> > > > > > > > > > to
> > > > > make
> > > > > > > the
> > > > > > > > > > updates for you if you send me or point me to your
files.
> > > > > > > > > >
> > > > > > > > > > Thanks,
> > > > > > > > > > George
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > On Mon, Jun 7, 2021 at 9:51 AM George McCabe
> > > > > > > > > > <mccabe at ucar.edu>
> > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi Perry,
> > > > > > > > > > >
> > > > > > > > > > > Are these paths on WCOSS? If so, could you send
me the
> > > > > > > > > > > config
> > > > > > > files?
> > > > > > > > > > >
> > > > > > > > > > > With the new approach, you will no longer have
to
> create
> > > > > > > > > > > your
> > > > > own
> > > > > > > > > wrapped
> > > > > > > > > > > config files. You will always use the versions
in the
> > > > > > > > > > > METplus
> > > > > > > > > repository
> > > > > > > > > > > (parm/met_config). Many of the settings that you
would
> > > > > > > > > > > change
> > > > > are
> > > > > > > now
> > > > > > > > > > > supported via the METplus config files and any
that are
> > > > > > > > > > > not can
> > > > > > be
> > > > > > > > set
> > > > > > > > > in
> > > > > > > > > > > the METplus config file as well. Your _cam
config files
> > > > > > > > > > > should
> > > > > > > still
> > > > > > > > > work
> > > > > > > > > > > the same as they did before, but it would be a
good
> idea
> > > > > > > > > > > to
> > > > > > update
> > > > > > > > your
> > > > > > > > > > > METplus configs to avoid using them.
> > > > > > > > > > >
> > > > > > > > > > > I will write up some suggestions to update your
config
> > > > > > > > > > > files to
> > > > > > use
> > > > > > > > the
> > > > > > > > > > > new approach and reply here with the steps. If
you'd
> > > > > > > > > > > prefer, we
> > > > > > > could
> > > > > > > > > set
> > > > > > > > > > > up a working session to go through them.
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > > George
> > > > > > > > > > >
> > > > > > > > > > > On Fri, Jun 4, 2021 at 9:26 AM
perry.shafran at noaa.gov
> > via
> > > > > > > > > > > RT <
> > > > > > > > > > > met_help at ucar.edu> wrote:
> > > > > > > > > > >
> > > > > > > > > > >>
> > > > > > > > > > >> Fri Jun 04 09:18:47 2021: Request 100108 was
acted
> upon.
> > > > > > > > > > >> Transaction: Ticket created by
perry.shafran at noaa.gov
> > > > > > > > > > >> Queue: met_help
> > > > > > > > > > >> Subject: config file changes for MET
10.0.0
> > > > > > > > > > >> Owner: Nobody
> > > > > > > > > > >> Requestors: perry.shafran at noaa.gov
> > > > > > > > > > >> Status: new
> > > > > > > > > > >> Ticket <URL:
> > > > > > > > >
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> > > > > > > > > > >
> > > > > > > > > > >>
> > > > > > > > > > >>
> > > > > > > > > > >> Hi, all,
> > > > > > > > > > >>
> > > > > > > > > > >> I'm trying to convert to MET 10.0.0, and it
looks like
> > > > > > > > > > >> things
> > > > > > have
> > > > > > > > > > changed
> > > > > > > > > > >> for the MET config files. Can you take a look
at my
> > > > > > > > > > >> config
> > > > > > files
> > > > > > > > and
> > > > > > > > > > >> explain what would need to be changed? I think
you
> had
> > > > > > discussed
> > > > > > > > this
> > > > > > > > > > >> before in a prior METplus user's meeting, but
that was
> > > > > > > > > > >> so long
> > > > > > ago
> > > > > > > > > that
> > > > > > > > > > I
> > > > > > > > > > >> don't quite remember.
> > > > > > > > > > >>
> > > > > > > > > > >> The files to examine are both in the directory:
> > > > > > > > > > >>
> > > > > > > > > > >>
> > > > > > > > > > >>
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > 4.0.0/parm/met_config
> > > > > > > > > > >>
> > > > > > > > > > >> and would be PB2NCConfig_cam and
PointStatConfig_cam.
> > > > > > > > > > >>
> > > > > > > > > > >> What would be the best resource to compare the
old
> with
> > > > > > > > > > >> the
> > > > > new?
> > > > > > > > Can
> > > > > > > > > > you
> > > > > > > > > > >> find that in the User's Guide?
> > > > > > > > > > >>
> > > > > > > > > > >> Thanks!
> > > > > > > > > > >>
> > > > > > > > > > >> Perry
> > > > > > > > > > >>
> > > > > > > > > > >> --
> > > > > > > > > > >> Perry C. Shafran
> > > > > > > > > > >> Verification/MEG Group Leader for IMSG
> > > > > > > > > > >> VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > > > > > >> Office: 301-683-3765
> > > > > > > > > > >> Cell: 301-717-6454
> > > > > > > > > > >> (he/him/his)
> > > > > > > > > > >> perry.shafran at noaa.gov
> > > > > > > > > > >>
> > > > > > > > > > >>
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > George McCabe - Software Engineer III
> > > > > > > > > > > National Center for Atmospheric Research
> > > > > > > > > > > Research Applications Laboratory
> > > > > > > > > > > 303-497-2768
> > > > > > > > > > > ---
> > > > > > > > > > > My working day may not be your working day.
Please do
> not
> > > > > > > > > > > feel
> > > > > > > > obliged
> > > > > > > > > to
> > > > > > > > > > > reply to this email outside of your normal
working
> hours.
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > George McCabe - Software Engineer III
> > > > > > > > > > National Center for Atmospheric Research
> > > > > > > > > > Research Applications Laboratory
> > > > > > > > > > 303-497-2768
> > > > > > > > > > ---
> > > > > > > > > > My working day may not be your working day. Please
do not
> > > > > > > > > > feel
> > > > > > > obliged
> > > > > > > > to
> > > > > > > > > > reply to this email outside of your normal working
hours.
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > Perry C. Shafran
> > > > > > > > > Verification/MEG Group Leader for IMSG
> > > > > > > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > > > > Office: 301-683-3765
> > > > > > > > > Cell: 301-717-6454
> > > > > > > > > (he/him/his)
> > > > > > > > > perry.shafran at noaa.gov
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > George McCabe - Software Engineer III
> > > > > > > > National Center for Atmospheric Research
> > > > > > > > Research Applications Laboratory
> > > > > > > > 303-497-2768
> > > > > > > > ---
> > > > > > > > My working day may not be your working day. Please do
not
> feel
> > > > > obliged
> > > > > > to
> > > > > > > > reply to this email outside of your normal working
hours.
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > Perry C. Shafran
> > > > > > > Verification/MEG Group Leader for IMSG
> > > > > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > > Office: 301-683-3765
> > > > > > > Cell: 301-717-6454
> > > > > > > (he/him/his)
> > > > > > > perry.shafran at noaa.gov
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > George McCabe - Software Engineer III
> > > > > > National Center for Atmospheric Research
> > > > > > Research Applications Laboratory
> > > > > > 303-497-2768
> > > > > > ---
> > > > > > My working day may not be your working day. Please do not
feel
> > > > > > obliged to
> > > > > > reply to this email outside of your normal working hours.
> > > > > >
> > > > > >
> > > > >
> > > > > --
> > > > > Perry C. Shafran
> > > > > Verification/MEG Group Leader for IMSG
> > > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > Office: 301-683-3765
> > > > > Cell: 301-717-6454
> > > > > (he/him/his)
> > > > > perry.shafran at noaa.gov
> > > > >
> > > > >
> > >
> > >
> > >
> > >
> >
> > --
> > Perry C. Shafran
> > Verification/MEG Group Leader for IMSG
> > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > Office: 301-683-3765
> > Cell: 301-717-6454
> > (he/him/his)
> > perry.shafran at noaa.gov
> >
> >
>
> --
> George McCabe - Software Engineer III
> National Center for Atmospheric Research
> Research Applications Laboratory
> 303-497-2768
> ---
> My working day may not be your working day. Please do not feel
obliged to
> reply to this email outside of your normal working hours.
>
>
--
Perry C. Shafran
Verification/MEG Group Leader for IMSG
VPPPG Branch of EMC/NCEP/NOAA/NWS
Office: 301-683-3765
Cell: 301-717-6454
(he/him/his)
perry.shafran at noaa.gov
------------------------------------------------
Subject: config file changes for MET 10.0.0
From: George McCabe
Time: Mon Jul 12 12:24:32 2021
Sounds good, thank you!
- George
On Mon Jul 12 12:17:31 2021, perry.shafran at noaa.gov wrote:
> Right-o, thanks! I'll characterize that as a GitHub question,
thanks!
>
> Perry
>
> On Mon, Jul 12, 2021 at 2:16 PM George McCabe via RT
> <met_help at ucar.edu>
> wrote:
>
> > Hi Perry,
> >
> > Your current METplus configurations that use MET configuration
files
> > that
> > have been modified to fit various needs still work fine using
METplus
> > 4.0.0. However, changes to the wrappers in this latest version
remove
> > the
> > need to maintain these MET configuration files. All value
overrides
> > needed
> > in MET configuration files can now be handled via METplus
> > configuration
> > variables. Updating your configuration files to use the new
approach
> > will
> > make it easier for us to debug issues and easier for you to
utilize
> > new
> > enhancements to the tools.
> >
> > - George
> >
> > On Mon, Jul 12, 2021 at 12:04 PM perry.shafran at noaa.gov via RT <
> > met_help at ucar.edu> wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> > >
> > > Hi, George,
> > >
> > > I will do so. Can you review with me the issue that we are
talking
> > > about
> > > with wrapped MET config files vs unwrapped? I need to be able
to
> > describe
> > > it in the GitHub Discussion post.
> > >
> > > Thanks!
> > >
> > > Perry
> > >
> > > On Mon, Jul 12, 2021 at 1:57 PM George McCabe via RT
> > > <met_help at ucar.edu>
> > > wrote:
> > >
> > > > Hi Perry,
> > > >
> > > > I haven't forgotten about reviewing your config files, but I
also
> > haven't
> > > > had a chance to take care of the task yet. I am going to close
> > > > this
> > > ticket
> > > > since the original issue was resolved and will correspond with
> > > > you via
> > > > email. Please create a GitHub Discussions post if this needs
to
> > > > be
> > > > addressed sooner than later.
> > > >
> > > > Thanks,
> > > > George
> > > >
> > > > On Tue Jun 08 14:00:34 2021, mccabe wrote:
> > > > > Thanks, Perry. I retrieved the files and will take a look. I
am
> > > > > going
> > > > > on
> > > > > vacation this week so I likely won't get to it until after I
> > > > > return.
> > > > >
> > > > > - George
> > > > >
> > > > > On Tue, Jun 8, 2021 at 8:22 AM perry.shafran at noaa.gov via RT
<
> > > > > met_help at ucar.edu> wrote:
> > > > >
> > > > > >
> > > > > > <URL:
> > > > > > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108 >
> > > > > >
> > > > > > Hi, George,
> > > > > >
> > > > > > OK great! I'm not entirely sure, but I think that my run
> > > > > > command
> > > > > > contains
> > > > > > too many files because some of the files I had in there I
> > > > > > believe
> > are
> > > > > > unchanged from the standard METplus config files (from
early
> > > > > > in my
> > > > > > usage of
> > > > > > METplus). I'll show you some of that.
> > > > > >
> > > > > > Yes, these are paths on WCOSS. I thought you had access
to
> > > > > > this.
> > > > > >
> > > > > > The METplus config files
> > > > > > are
> > > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > > 4.0.0/parm/use_cases/perry,
> > > > > > pb2nc_cam.conf and point_stat_cam.conf.
> > > > > >
> > > > > > The command used is:
> > > > > >
> > > > > >
> > > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > > 3.1/ush/master_metplus.py
> > > > > > -c
> > > > > >
> > > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > > 3.1/parm/use_cases/grid_to_obs/grid_to_obs.conf
> > > > > > -c
> > > > > >
> > > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > > 3.1/parm/use_cases/grid_to_obs/examples/conus_surface.conf
> > > > > > -c
> > > > > >
> > > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > > 3.1/parm/use_cases/perry/pb2nc_cam.conf
> > > > > > -c
> > > > > >
> > > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > > 3.1/parm/use_cases/perry/point_stat_cam.conf
> > > > > > -c /gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/nam.conf -c
> > > > > >
> > > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > > 3.1/parm/use_cases/perry/shared.conf
> > > > > > -c
/gpfs/dell2/ptmp/Perry.Shafran/metplus_nam/shared_nam.conf
> > > > > > -c
> > > > > >
> > > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > > 3.1/parm/use_cases/perry/system_cam.conf
> > > > > >
> > > > > > You may replace the 3.1's with 4.0.0's as it would be the
> > > > > > same (and
> > > > > > change
> > > > > > master_metplus to run_metplus).
> > > > > >
> > > > > > Perry
> > > > > >
> > > > > > On Tue, Jun 8, 2021 at 10:03 AM George McCabe via RT
> > > > > > <met_help at ucar.edu>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Perry,
> > > > > > >
> > > > > > > Is that a path on WCOSS? I don't have access, so I will
> > > > > > > have to
> > ask
> > > > > > someone
> > > > > > > on the team to pull the files for me.
> > > > > > >
> > > > > > > Yes, I need the corresponding METplus config files
because
> > > > > > > I will
> > > > > > > need to
> > > > > > > add variables to those files. I recall some of your use
> > > > > > > cases run
> > > > > > > by
> > > > > > > passing in multiple config files. If that is still the
> > > > > > > case,
> > please
> > > > > > > send
> > > > > > > the command that is run so I know the order in which the
> > > > > > > files
> > are
> > > > > > > read.
> > > > > > >
> > > > > > > Thanks,
> > > > > > > George
> > > > > > >
> > > > > > > On Tue, Jun 8, 2021 at 7:59 AM perry.shafran at noaa.gov
via
> > > > > > > RT <
> > > > > > > met_help at ucar.edu> wrote:
> > > > > > >
> > > > > > > >
> > > > > > > > <URL:
> > > > > > > >
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> > >
> > > > > > > >
> > > > > > > > Hi, George,
> > > > > > > >
> > > > > > > > You can find my MET config files
> > > > > > > > here:
> > > > > > > >
> > > > > > >
> > > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > > 4.0.0/parm/met_config
> > > > > > > >
> > > > > > > > Specifically, the PB2NC and PointStat files that end
with
> > > > > > > > the
> > > > > > > > letters
> > > > > > > "cam"
> > > > > > > > are your best bet to look at.
> > > > > > > >
> > > > > > > > Do you need to look at METplus config files too for
this?
> > > > > > > >
> > > > > > > > Thanks!
> > > > > > > >
> > > > > > > > Perry
> > > > > > > >
> > > > > > > > On Mon, Jun 7, 2021 at 3:35 PM George McCabe via RT
> > > > > > > > <met_help at ucar.edu
> > > > > > >
> > > > > > > > wrote:
> > > > > > > >
> > > > > > > > > Hi Perry,
> > > > > > > > >
> > > > > > > > > I was originally trying to fix the current problem
> > > > > > > > > until I
> > > > > > > > > learned
> > > > > > that
> > > > > > > > it
> > > > > > > > > was already fixed! Sounds good about sending over
your
> > > > > > > > > files,
> > > > > > > > > no
> > > > > > rush.
> > > > > > > > >
> > > > > > > > > Thanks,
> > > > > > > > > George
> > > > > > > > >
> > > > > > > > > On Mon, Jun 7, 2021 at 1:30 PM
perry.shafran at noaa.gov
> > > > > > > > > via
> > RT <
> > > > > > > > > met_help at ucar.edu> wrote:
> > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > <URL:
> > > > > > > > > >
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > Hi, George,
> > > > > > > > > >
> > > > > > > > > > OK, now I understand what you are trying to say.
> > > > > > > > > > You're
> > not
> > > > > > > > > > trying
> > > > > > > to
> > > > > > > > > fix
> > > > > > > > > > a current problem, you are looking to help update
my
> > > > > > > > > > files
> > to
> > > > > > > > > > be
> > > > > > more
> > > > > > > > > > efficient. Then yes, let's be sure that we update
> > > > > > > > > > the
> > config
> > > > > > > > > > files
> > > > > > > so
> > > > > > > > > that
> > > > > > > > > > we have the best set up going forward.
> > > > > > > > > >
> > > > > > > > > > It's probably better for you to make these
changes,
> > > > > > > > > > so I'll
> > > > > > > > > > send
> > > > > > you
> > > > > > > my
> > > > > > > > > > config files and we'll go forward from there. I'm
> > > > > > > > > > doing a
> > > > > > > > > > few
> > > > > > other
> > > > > > > > > things
> > > > > > > > > > to wrap up the day, so I'll send them along
tomorrow.
> > > > > > > > > >
> > > > > > > > > > Thanks!
> > > > > > > > > >
> > > > > > > > > > Perry
> > > > > > > > > >
> > > > > > > > > > On Mon, Jun 7, 2021 at 12:22 PM George McCabe via
RT
> > > > > > > > > > <
> > > > > > > > met_help at ucar.edu>
> > > > > > > > > > wrote:
> > > > > > > > > >
> > > > > > > > > > > Hi Perry,
> > > > > > > > > > >
> > > > > > > > > > > It is good to hear that your issue was resolved.
> > > > > > > > > > > Your
> > _cam
> > > > > > > > > > > config
> > > > > > > > files
> > > > > > > > > > > should work fine with 4.0.0, but it would still
be
> > > > > > > > > > > a good
> > > > > > > > > > > idea to
> > > > > > > > > update
> > > > > > > > > > > your use cases to use the new approach. It will
be
> > > > > > > > > > > a lot
> > > > > > > > > > > easier
> > > > > > to
> > > > > > > > > debug
> > > > > > > > > > > issues and update your configs to change
settings.
> > > > > > > > > > > Also,
> > we
> > > > > > > > > > > can't
> > > > > > > > > > guarantee
> > > > > > > > > > > that things won't break in future versions if
you
> > > > > > > > > > > are
> > using
> > > > > > > > > > > old
> > > > > > MET
> > > > > > > > > > config
> > > > > > > > > > > files that reference the old environment
variables.
> > > > > > > > > > >
> > > > > > > > > > > If you'd rather just send me your MET config
files
> > > > > > > > > > > and
> > the
> > > > > > > > > > > .conf
> > > > > > > > files
> > > > > > > > > > > used, I can update them for you. I could also
have
> > someone
> > > > > > > > > > > pull
> > > > > > > them
> > > > > > > > > from
> > > > > > > > > > > WCOSS this afternoon. Below is some info on how
to
> > > > > > > > > > > update
> > > > > > > > > > > them
> > > > > > > > > yourself.
> > > > > > > > > > > The process is a little confusing, but once it
is
> > > > > > > > > > > done
> > then
> > > > > > > > > > > it is
> > > > > > > > much,
> > > > > > > > > > > much easier to update and keep track of settings
> > > > > > > > > > > going
> > > > > > > > > > > forward.
> > > > > > > > > > >
> > > > > > > > > > > 1a. Diff your MET config files (PB2NCConfig_cam
and
> > > > > > > > > PointStatConfig_cam)
> > > > > > > > > > > against the wrapped MET config files in the
> > > > > > > > > > > repository
> > for
> > > > > > > > > > > *v3.1*
> > > > > > > > (i.e.
> > > > > > > > > > > METplus-3.1/parm/met_config/PB2NCConfig_wrapped
and
> > > > > > > > > > > PointStatConfig_wrapped). This will tell you
which
> > > > > > > > > > > values
> > > > > > > > > > > you had
> > > > > > > to
> > > > > > > > > > > override in your config file because they
weren't
> > supported
> > > > > > > > > > > in
> > > > > > 3.1.
> > > > > > > > > > >
> > > > > > > > > > > 1b. Note that we discovered that there were some
> > incorrect
> > > > > > default
> > > > > > > > > values
> > > > > > > > > > > used here that have since been changed to match
the
> > > > > > > > > > > MET
> > > > > > > > > > > config
> > > > > > > > defaults
> > > > > > > > > > (in
> > > > > > > > > > > share/met/config). These are outlined in the
User's
> > > > > > > > > > > Guide
> > > > > > > > > > > here:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > >
> > >
> >
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#pb2ncconfig
> > > > > > > > > > >
> > > > > > > > > > > Referring to this list, if your MET config file
> > > > > > > > > > > matches
> > the
> > > > > > > > > > > "New
> > > > > > > > > > (Correct)"
> > > > > > > > > > > value and the 3.1 wrapped config matches the
"Old
> > > > > > > > > > > (Incorrect)"
> > > > > > > value,
> > > > > > > > > > then
> > > > > > > > > > > you don't need to add anything to your METplus
> > > > > > > > > > > config for
> > > > > > > > > > > that
> > > > > > > item.
> > > > > > > > > > > For example, if your file has:
> > > > > > > > > > >
> > > > > > > > > > > *level_category = [];*
> > > > > > > > > > >
> > > > > > > > > > > and the wrapped config file has:
> > > > > > > > > > >
> > > > > > > > > > > *level_category = [0, 1, 4, 5, 6];*
> > > > > > > > > > >
> > > > > > > > > > > then you don't need to do anything in the
METplus
> > > > > > > > > > > config.
> > > > > > > > > > > Your
> > > > > > > value
> > > > > > > > > > > matches the new default and will be used. If
your
> > > > > > > > > > > version
> > > > > > > > > > > had
> > > > > > > > something
> > > > > > > > > > > like:
> > > > > > > > > > >
> > > > > > > > > > > * level_category = [2, 3]; *
> > > > > > > > > > >
> > > > > > > > > > > then in your METplus .conf file you would need
to
> > > > > > > > > > > set:
> > > > > > > > > > >
> > > > > > > > > > > PB2NC_LEVEL_CATEGORY = 2, 3
> > > > > > > > > > >
> > > > > > > > > > > 1c. Info about the METplus conf variables that
are
> > > > > > > > > > > available for
> > > > > > > each
> > > > > > > > > > > wrapper can be found here:
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > >
> > >
> >
https://metplus.readthedocs.io/en/latest/Users_Guide/wrappers.html#pb2nc-
> > > > > > met-conf
> > > > > > > > > > >
> > > > > > > > > > > If there is a conf variable that corresponds to
the
> > > > > > > > > > > value
> > > > > > > > > > > you
> > > > > > need
> > > > > > > to
> > > > > > > > > > > override in the MET config file, you can use
that
> > instead.
> > > > > > > > > > > If
> > > > > > > support
> > > > > > > > > > for a
> > > > > > > > > > > variable in the MET config is not listed, then
you
> > > > > > > > > > > can
> > > > > > > > > > > override
> > > > > > the
> > > > > > > > > > values
> > > > > > > > > > > using PB2NC_MET_CONFIG_OVERRIDES (see
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > >
> > > >
> > >
> >
https://metplus.readthedocs.io/en/latest/Users_Guide/systemconfiguration.html#overriding-
> > > > > > unsupported-met-configuration-variables
> > > > > > > > > > > ).
> > > > > > > > > > >
> > > > > > > > > > > 2. In your METplus .conf file, you will need to
set
> > > > > > > PB2NC_CONFIG_FILE
> > > > > > > > > and
> > > > > > > > > > > POINT_STAT_CONFIG_FILE to point to the wrapped
> > > > > > > > > > > version
> > that
> > > > > > > > > > > is in
> > > > > > > the
> > > > > > > > > > parm
> > > > > > > > > > > directory.
> > > > > > > > > > >
> > > > > > > > > > > *PB2NC_CONFIG_FILE =
> > > > > > > > > > > {PARM_BASE}/met_config/PB2NCConfig_wrapped*
> > > > > > > > > > >
> > > > > > > > > > > *POINT_STAT_CONFIG_FILE
> > > > > > > > > ={PARM_BASE}/met_config/PointStatConfig_wrapped*
> > > > > > > > > > >
> > > > > > > > > > > You will never need to change these values going
> > > > > > > > > > > forward,
> > > > > > > > > > > as any
> > > > > > > > > > > unsupported MET variables overrides can be done
> > > > > > > > > > > directly
> > in
> > > > > > > > > > > the
> > > > > > > > METplus
> > > > > > > > > > > .conf file.
> > > > > > > > > > >
> > > > > > > > > > > Again, I know this process can be confusing, so
I
> > > > > > > > > > > am
> > happy
> > > > > > > > > > > to
> > > > > > make
> > > > > > > > the
> > > > > > > > > > > updates for you if you send me or point me to
your
> > > > > > > > > > > files.
> > > > > > > > > > >
> > > > > > > > > > > Thanks,
> > > > > > > > > > > George
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > On Mon, Jun 7, 2021 at 9:51 AM George McCabe
> > > > > > > > > > > <mccabe at ucar.edu>
> > > > > > > > wrote:
> > > > > > > > > > >
> > > > > > > > > > > > Hi Perry,
> > > > > > > > > > > >
> > > > > > > > > > > > Are these paths on WCOSS? If so, could you
send
> > > > > > > > > > > > me the
> > > > > > > > > > > > config
> > > > > > > > files?
> > > > > > > > > > > >
> > > > > > > > > > > > With the new approach, you will no longer have
to
> > create
> > > > > > > > > > > > your
> > > > > > own
> > > > > > > > > > wrapped
> > > > > > > > > > > > config files. You will always use the versions
in
> > > > > > > > > > > > the
> > > > > > > > > > > > METplus
> > > > > > > > > > repository
> > > > > > > > > > > > (parm/met_config). Many of the settings that
you
> > > > > > > > > > > > would
> > > > > > > > > > > > change
> > > > > > are
> > > > > > > > now
> > > > > > > > > > > > supported via the METplus config files and any
> > > > > > > > > > > > that are
> > > > > > > > > > > > not can
> > > > > > > be
> > > > > > > > > set
> > > > > > > > > > in
> > > > > > > > > > > > the METplus config file as well. Your _cam
config
> > > > > > > > > > > > files
> > > > > > > > > > > > should
> > > > > > > > still
> > > > > > > > > > work
> > > > > > > > > > > > the same as they did before, but it would be a
> > > > > > > > > > > > good
> > idea
> > > > > > > > > > > > to
> > > > > > > update
> > > > > > > > > your
> > > > > > > > > > > > METplus configs to avoid using them.
> > > > > > > > > > > >
> > > > > > > > > > > > I will write up some suggestions to update
your
> > > > > > > > > > > > config
> > > > > > > > > > > > files to
> > > > > > > use
> > > > > > > > > the
> > > > > > > > > > > > new approach and reply here with the steps. If
> > > > > > > > > > > > you'd
> > > > > > > > > > > > prefer, we
> > > > > > > > could
> > > > > > > > > > set
> > > > > > > > > > > > up a working session to go through them.
> > > > > > > > > > > >
> > > > > > > > > > > > Thanks,
> > > > > > > > > > > > George
> > > > > > > > > > > >
> > > > > > > > > > > > On Fri, Jun 4, 2021 at 9:26 AM
> > > > > > > > > > > > perry.shafran at noaa.gov
> > > via
> > > > > > > > > > > > RT <
> > > > > > > > > > > > met_help at ucar.edu> wrote:
> > > > > > > > > > > >
> > > > > > > > > > > >>
> > > > > > > > > > > >> Fri Jun 04 09:18:47 2021: Request 100108 was
> > > > > > > > > > > >> acted
> > upon.
> > > > > > > > > > > >> Transaction: Ticket created by
> > > > > > > > > > > >> perry.shafran at noaa.gov
> > > > > > > > > > > >> Queue: met_help
> > > > > > > > > > > >> Subject: config file changes for MET
10.0.0
> > > > > > > > > > > >> Owner: Nobody
> > > > > > > > > > > >> Requestors: perry.shafran at noaa.gov
> > > > > > > > > > > >> Status: new
> > > > > > > > > > > >> Ticket <URL:
> > > > > > > > > >
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=100108
> > > > > > > > > > > >
> > > > > > > > > > > >>
> > > > > > > > > > > >>
> > > > > > > > > > > >> Hi, all,
> > > > > > > > > > > >>
> > > > > > > > > > > >> I'm trying to convert to MET 10.0.0, and it
> > > > > > > > > > > >> looks like
> > > > > > > > > > > >> things
> > > > > > > have
> > > > > > > > > > > changed
> > > > > > > > > > > >> for the MET config files. Can you take a
look
> > > > > > > > > > > >> at my
> > > > > > > > > > > >> config
> > > > > > > files
> > > > > > > > > and
> > > > > > > > > > > >> explain what would need to be changed? I
think
> > > > > > > > > > > >> you
> > had
> > > > > > > discussed
> > > > > > > > > this
> > > > > > > > > > > >> before in a prior METplus user's meeting, but
> > > > > > > > > > > >> that was
> > > > > > > > > > > >> so long
> > > > > > > ago
> > > > > > > > > > that
> > > > > > > > > > > I
> > > > > > > > > > > >> don't quite remember.
> > > > > > > > > > > >>
> > > > > > > > > > > >> The files to examine are both in the
directory:
> > > > > > > > > > > >>
> > > > > > > > > > > >>
> > > > > > > > > > > >>
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > /gpfs/dell2/emc/verification/save/Perry.Shafran/METplus-
> > > > > > 4.0.0/parm/met_config
> > > > > > > > > > > >>
> > > > > > > > > > > >> and would be PB2NCConfig_cam and
> > > > > > > > > > > >> PointStatConfig_cam.
> > > > > > > > > > > >>
> > > > > > > > > > > >> What would be the best resource to compare
the
> > > > > > > > > > > >> old
> > with
> > > > > > > > > > > >> the
> > > > > > new?
> > > > > > > > > Can
> > > > > > > > > > > you
> > > > > > > > > > > >> find that in the User's Guide?
> > > > > > > > > > > >>
> > > > > > > > > > > >> Thanks!
> > > > > > > > > > > >>
> > > > > > > > > > > >> Perry
> > > > > > > > > > > >>
> > > > > > > > > > > >> --
> > > > > > > > > > > >> Perry C. Shafran
> > > > > > > > > > > >> Verification/MEG Group Leader for IMSG
> > > > > > > > > > > >> VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > > > > > > >> Office: 301-683-3765
> > > > > > > > > > > >> Cell: 301-717-6454
> > > > > > > > > > > >> (he/him/his)
> > > > > > > > > > > >> perry.shafran at noaa.gov
> > > > > > > > > > > >>
> > > > > > > > > > > >>
> > > > > > > > > > > >
> > > > > > > > > > > > --
> > > > > > > > > > > > George McCabe - Software Engineer III
> > > > > > > > > > > > National Center for Atmospheric Research
> > > > > > > > > > > > Research Applications Laboratory
> > > > > > > > > > > > 303-497-2768
> > > > > > > > > > > > ---
> > > > > > > > > > > > My working day may not be your working day.
> > > > > > > > > > > > Please do
> > not
> > > > > > > > > > > > feel
> > > > > > > > > obliged
> > > > > > > > > > to
> > > > > > > > > > > > reply to this email outside of your normal
> > > > > > > > > > > > working
> > hours.
> > > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > > > --
> > > > > > > > > > > George McCabe - Software Engineer III
> > > > > > > > > > > National Center for Atmospheric Research
> > > > > > > > > > > Research Applications Laboratory
> > > > > > > > > > > 303-497-2768
> > > > > > > > > > > ---
> > > > > > > > > > > My working day may not be your working day.
Please
> > > > > > > > > > > do not
> > > > > > > > > > > feel
> > > > > > > > obliged
> > > > > > > > > to
> > > > > > > > > > > reply to this email outside of your normal
working
> > > > > > > > > > > hours.
> > > > > > > > > > >
> > > > > > > > > > >
> > > > > > > > > >
> > > > > > > > > > --
> > > > > > > > > > Perry C. Shafran
> > > > > > > > > > Verification/MEG Group Leader for IMSG
> > > > > > > > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > > > > > Office: 301-683-3765
> > > > > > > > > > Cell: 301-717-6454
> > > > > > > > > > (he/him/his)
> > > > > > > > > > perry.shafran at noaa.gov
> > > > > > > > > >
> > > > > > > > > >
> > > > > > > > >
> > > > > > > > > --
> > > > > > > > > George McCabe - Software Engineer III
> > > > > > > > > National Center for Atmospheric Research
> > > > > > > > > Research Applications Laboratory
> > > > > > > > > 303-497-2768
> > > > > > > > > ---
> > > > > > > > > My working day may not be your working day. Please
do
> > > > > > > > > not
> > feel
> > > > > > obliged
> > > > > > > to
> > > > > > > > > reply to this email outside of your normal working
> > > > > > > > > hours.
> > > > > > > > >
> > > > > > > > >
> > > > > > > >
> > > > > > > > --
> > > > > > > > Perry C. Shafran
> > > > > > > > Verification/MEG Group Leader for IMSG
> > > > > > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > > > Office: 301-683-3765
> > > > > > > > Cell: 301-717-6454
> > > > > > > > (he/him/his)
> > > > > > > > perry.shafran at noaa.gov
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > > --
> > > > > > > George McCabe - Software Engineer III
> > > > > > > National Center for Atmospheric Research
> > > > > > > Research Applications Laboratory
> > > > > > > 303-497-2768
> > > > > > > ---
> > > > > > > My working day may not be your working day. Please do
not
> > > > > > > feel
> > > > > > > obliged to
> > > > > > > reply to this email outside of your normal working
hours.
> > > > > > >
> > > > > > >
> > > > > >
> > > > > > --
> > > > > > Perry C. Shafran
> > > > > > Verification/MEG Group Leader for IMSG
> > > > > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > > > > Office: 301-683-3765
> > > > > > Cell: 301-717-6454
> > > > > > (he/him/his)
> > > > > > perry.shafran at noaa.gov
> > > > > >
> > > > > >
> > > >
> > > >
> > > >
> > > >
> > >
> > > --
> > > Perry C. Shafran
> > > Verification/MEG Group Leader for IMSG
> > > VPPPG Branch of EMC/NCEP/NOAA/NWS
> > > Office: 301-683-3765
> > > Cell: 301-717-6454
> > > (he/him/his)
> > > perry.shafran at noaa.gov
> > >
> > >
> >
> > --
> > George McCabe - Software Engineer III
> > National Center for Atmospheric Research
> > Research Applications Laboratory
> > 303-497-2768
> > ---
> > My working day may not be your working day. Please do not feel
> > obliged to
> > reply to this email outside of your normal working hours.
> >
> >
------------------------------------------------
More information about the Met_help
mailing list