[Met_help] [rt.rap.ucar.edu #60368] History for plot_data_plane
John Halley Gotway via RT
met_help at ucar.edu
Fri Feb 22 08:28:44 MST 2013
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
I used to plot gridded WRF output using the following command with METV3.1:
plot_data_plane WRFPRS_d01.00 WRFPRS_d01_GE297K TMP/Z2 -plot_range 297 298.397 -title 2mTempGE297
Now with METV4.0 I can't get it to work.
It flags the "/" in the config_string for TMP/Z2
The usage info doesn't go into any detail and I couldn't find any description in the V4.0.1 User's Guide.
Can you give some more detail on how the variable and level are supposed to be formatted? (I'm assuming that this is the problem)
Thanks.
R/
John
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #60368] plot_data_plane
From: John Halley Gotway
Time: Thu Feb 21 14:06:02 2013
John,
Ah, yes. We really need to do a better job documenting and providing
examples for the plot_data_plane utility. The way of specifying the
field
to be plotted changed from METv3.1 to METv4.0 as a result of the
generalization of the config file language.
Please try running the following instead:
plot_data_plane \
WRFPRS_d01.00 \
WRFPRS_d01_GE297K \
'name="TMP"; level="Z2";' \
-plot_range 297 298.397 \
-title 2mTempGE297
The change is in the specification of the field to be plotted.
Instead of
using (what we've been calling a magic string) "TMP/Z2", you now use a
mini-configuration string:
'name="TMP"; level="Z2";'
Any configuration entries that go in the fcst.field and obs.field
settings
in the other MET configuration files can be supplied within that
string.
That gives us very general control over what field to plot.
Sorry about the confusion. Give that a try and let me know if you
continue to experience problems.
Thanks,
John
>
> Thu Feb 21 13:40:11 2013: Request 60368 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
> Queue: met_help
> Subject: plot_data_plane
> Owner: Nobody
> Requestors: john.w.raby2.civ at mail.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60368 >
>
>
> I used to plot gridded WRF output using the following command with
> METV3.1:
>
> plot_data_plane WRFPRS_d01.00 WRFPRS_d01_GE297K TMP/Z2 -plot_range
297
> 298.397 -title 2mTempGE297
>
> Now with METV4.0 I can't get it to work.
>
> It flags the "/" in the config_string for TMP/Z2
>
> The usage info doesn't go into any detail and I couldn't find any
> description in the V4.0.1 User's Guide.
>
> Can you give some more detail on how the variable and level are
supposed
> to be formatted? (I'm assuming that this is the problem)
>
> Thanks.
>
> R/
> John
>
>
------------------------------------------------
Subject: plot_data_plane
From: Raby, John W USA CIV
Time: Thu Feb 21 15:46:00 2013
John -
Thanks for your quick response and the info on that utility. I
literally cut and pasted the command from your email into my terminal
and ran it. Worked perfect with no errors.
See the attached plot.
The only problem is the data in the forecast contained no temperatures
which met the criterion I had used, but otherwise it looks like I will
be able to use the utility now with your example.
R/
John
________________________________________
From: John Halley Gotway via RT [met_help at ucar.edu]
Sent: Thursday, February 21, 2013 2:06 PM
To: Raby, John W CIV (US)
Cc: Vaucher, Gail T CIV (US); Passner, Jeffrey E CIV (US)
Subject: Re: [rt.rap.ucar.edu #60368] plot_data_plane
John,
Ah, yes. We really need to do a better job documenting and providing
examples for the plot_data_plane utility. The way of specifying the
field
to be plotted changed from METv3.1 to METv4.0 as a result of the
generalization of the config file language.
Please try running the following instead:
plot_data_plane \
WRFPRS_d01.00 \
WRFPRS_d01_GE297K \
'name="TMP"; level="Z2";' \
-plot_range 297 298.397 \
-title 2mTempGE297
The change is in the specification of the field to be plotted.
Instead of
using (what we've been calling a magic string) "TMP/Z2", you now use a
mini-configuration string:
'name="TMP"; level="Z2";'
Any configuration entries that go in the fcst.field and obs.field
settings
in the other MET configuration files can be supplied within that
string.
That gives us very general control over what field to plot.
Sorry about the confusion. Give that a try and let me know if you
continue to experience problems.
Thanks,
John
>
> Thu Feb 21 13:40:11 2013: Request 60368 was acted upon.
> Transaction: Ticket created by john.w.raby2.civ at mail.mil
> Queue: met_help
> Subject: plot_data_plane
> Owner: Nobody
> Requestors: john.w.raby2.civ at mail.mil
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60368 >
>
>
> I used to plot gridded WRF output using the following command with
> METV3.1:
>
> plot_data_plane WRFPRS_d01.00 WRFPRS_d01_GE297K TMP/Z2 -plot_range
297
> 298.397 -title 2mTempGE297
>
> Now with METV4.0 I can't get it to work.
>
> It flags the "/" in the config_string for TMP/Z2
>
> The usage info doesn't go into any detail and I couldn't find any
> description in the V4.0.1 User's Guide.
>
> Can you give some more detail on how the variable and level are
supposed
> to be formatted? (I'm assuming that this is the problem)
>
> Thanks.
>
> R/
> John
>
>
------------------------------------------------
Subject: Re: [rt.rap.ucar.edu #60368] plot_data_plane
From: John Halley Gotway
Time: Fri Feb 22 08:15:38 2013
John,
Great, glad that worked. Please be aware that if you do NOT specify
the "-plot_range" argument, by default, it will set the plotting range
to the minimum and maximum values in the field.
Thanks,
John
On 02/21/2013 03:46 PM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60368 >
>
> John -
>
> Thanks for your quick response and the info on that utility. I
literally cut and pasted the command from your email into my terminal
and ran it. Worked perfect with no errors.
>
> See the attached plot.
>
> The only problem is the data in the forecast contained no
temperatures which met the criterion I had used, but otherwise it
looks like I will be able to use the utility now with your example.
>
> R/
> John
>
> ________________________________________
> From: John Halley Gotway via RT [met_help at ucar.edu]
> Sent: Thursday, February 21, 2013 2:06 PM
> To: Raby, John W CIV (US)
> Cc: Vaucher, Gail T CIV (US); Passner, Jeffrey E CIV (US)
> Subject: Re: [rt.rap.ucar.edu #60368] plot_data_plane
>
> John,
>
> Ah, yes. We really need to do a better job documenting and
providing
> examples for the plot_data_plane utility. The way of specifying the
field
> to be plotted changed from METv3.1 to METv4.0 as a result of the
> generalization of the config file language.
>
> Please try running the following instead:
> plot_data_plane \
> WRFPRS_d01.00 \
> WRFPRS_d01_GE297K \
> 'name="TMP"; level="Z2";' \
> -plot_range 297 298.397 \
> -title 2mTempGE297
>
> The change is in the specification of the field to be plotted.
Instead of
> using (what we've been calling a magic string) "TMP/Z2", you now use
a
> mini-configuration string:
> 'name="TMP"; level="Z2";'
>
> Any configuration entries that go in the fcst.field and obs.field
settings
> in the other MET configuration files can be supplied within that
string.
> That gives us very general control over what field to plot.
>
> Sorry about the confusion. Give that a try and let me know if you
> continue to experience problems.
>
> Thanks,
> John
>
>>
>> Thu Feb 21 13:40:11 2013: Request 60368 was acted upon.
>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>> Queue: met_help
>> Subject: plot_data_plane
>> Owner: Nobody
>> Requestors: john.w.raby2.civ at mail.mil
>> Status: new
>> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60368 >
>>
>>
>> I used to plot gridded WRF output using the following command with
>> METV3.1:
>>
>> plot_data_plane WRFPRS_d01.00 WRFPRS_d01_GE297K TMP/Z2 -plot_range
297
>> 298.397 -title 2mTempGE297
>>
>> Now with METV4.0 I can't get it to work.
>>
>> It flags the "/" in the config_string for TMP/Z2
>>
>> The usage info doesn't go into any detail and I couldn't find any
>> description in the V4.0.1 User's Guide.
>>
>> Can you give some more detail on how the variable and level are
supposed
>> to be formatted? (I'm assuming that this is the problem)
>>
>> Thanks.
>>
>> R/
>> John
>>
>>
>
>
>
>
------------------------------------------------
Subject: plot_data_plane
From: Raby, John W USA CIV
Time: Fri Feb 22 08:18:34 2013
Classification: UNCLASSIFIED
Caveats: NONE
John -
This is good info. Thanks.
R/
John
-----Original Message-----
From: John Halley Gotway via RT [mailto:met_help at ucar.edu]
Sent: Friday, February 22, 2013 8:16 AM
To: Raby, John W CIV (US)
Cc: Vaucher, Gail T CIV (US); Passner, Jeffrey E CIV (US)
Subject: Re: [rt.rap.ucar.edu #60368] plot_data_plane
John,
Great, glad that worked. Please be aware that if you do NOT specify
the
"-plot_range" argument, by default, it will set the plotting range to
the
minimum and maximum values in the field.
Thanks,
John
On 02/21/2013 03:46 PM, Raby, John W USA CIV via RT wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60368 >
>
> John -
>
> Thanks for your quick response and the info on that utility. I
literally cut
> and pasted the command from your email into my terminal and ran it.
Worked
> perfect with no errors.
>
> See the attached plot.
>
> The only problem is the data in the forecast contained no
temperatures which
> met the criterion I had used, but otherwise it looks like I will be
able to
> use the utility now with your example.
>
> R/
> John
>
> ________________________________________
> From: John Halley Gotway via RT [met_help at ucar.edu]
> Sent: Thursday, February 21, 2013 2:06 PM
> To: Raby, John W CIV (US)
> Cc: Vaucher, Gail T CIV (US); Passner, Jeffrey E CIV (US)
> Subject: Re: [rt.rap.ucar.edu #60368] plot_data_plane
>
> John,
>
> Ah, yes. We really need to do a better job documenting and
providing
> examples for the plot_data_plane utility. The way of specifying the
> field to be plotted changed from METv3.1 to METv4.0 as a result of
the
> generalization of the config file language.
>
> Please try running the following instead:
> plot_data_plane \
> WRFPRS_d01.00 \
> WRFPRS_d01_GE297K \
> 'name="TMP"; level="Z2";' \
> -plot_range 297 298.397 \
> -title 2mTempGE297
>
> The change is in the specification of the field to be plotted.
> Instead of using (what we've been calling a magic string) "TMP/Z2",
> you now use a mini-configuration string:
> 'name="TMP"; level="Z2";'
>
> Any configuration entries that go in the fcst.field and obs.field
> settings in the other MET configuration files can be supplied within
that
> string.
> That gives us very general control over what field to plot.
>
> Sorry about the confusion. Give that a try and let me know if you
> continue to experience problems.
>
> Thanks,
> John
>
>>
>> Thu Feb 21 13:40:11 2013: Request 60368 was acted upon.
>> Transaction: Ticket created by john.w.raby2.civ at mail.mil
>> Queue: met_help
>> Subject: plot_data_plane
>> Owner: Nobody
>> Requestors: john.w.raby2.civ at mail.mil
>> Status: new
>> Ticket <URL:
>> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=60368 >
>>
>>
>> I used to plot gridded WRF output using the following command with
>> METV3.1:
>>
>> plot_data_plane WRFPRS_d01.00 WRFPRS_d01_GE297K TMP/Z2 -plot_range
>> 297
>> 298.397 -title 2mTempGE297
>>
>> Now with METV4.0 I can't get it to work.
>>
>> It flags the "/" in the config_string for TMP/Z2
>>
>> The usage info doesn't go into any detail and I couldn't find any
>> description in the V4.0.1 User's Guide.
>>
>> Can you give some more detail on how the variable and level are
>> supposed to be formatted? (I'm assuming that this is the problem)
>>
>> Thanks.
>>
>> R/
>> John
>>
>>
>
>
>
>
Classification: UNCLASSIFIED
Caveats: NONE
------------------------------------------------
More information about the Met_help
mailing list