[Met_help] [rt.rap.ucar.edu #94767] History for plot_data_plane and ncview show different orientations
John Halley Gotway via RT
met_help at ucar.edu
Fri Apr 3 13:07:41 MDT 2020
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
I'm creating a netcdf file from a grib2 file using a python script. I had
originally filled in the values starting from the ul corner (90, 0). Ncview
and plot_data_plane showed two different orientations of the data. I had
worked with Randy on this issue and he said he believed that
plot_data_plane was correct and that I needed to fill the values from the
ll corner (-90, 0), which would show the same results in both ncview and
plot data plane. After doing so, I'm still getting two different
projections and I don't know which one is right. Please help!
Best,
Lindsay
--
Lindsay R. Blank
Associate Scientist
Joint Numerical Testbed Program
National Center for Atmospheric Research
+1 (303)-497-2772
*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.*
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: plot_data_plane and ncview show different orientations
From: John Halley Gotway
Time: Mon Mar 30 12:36:25 2020
Hi Linday,
When this sort of issue has come up in the past, we've fixed it by
reversing the order in the met_data python array using a -1 in one or
both
dimensions. Please try that yourself first to see if that orients the
data
correctly.
By way of example, please see take a look at this script:
https://dtcenter.org/sites/default/files/community-code/met/python-
scripts/read_NRL_binary.py.txt
And then at these lines:
# Read and re-orient the data
met_data = data[::-1].reshape(181, 360)[:,::-1].copy()
If you're still stuck, please point me to your python script and GRIB2
file? Also, please share the plot_data_plane command you're running
and,
if possible, an image showing how it should be oriented.
Thanks,
John
On Mon, Mar 30, 2020 at 11:59 AM Lindsay Blank via RT
<met_help at ucar.edu>
wrote:
>
> Mon Mar 30 11:59:19 2020: Request 94767 was acted upon.
> Transaction: Ticket created by lblank at ucar.edu
> Queue: met_help
> Subject: plot_data_plane and ncview show different orientations
> Owner: Nobody
> Requestors: lblank at ucar.edu
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=94767 >
>
>
> Hello,
>
> I'm creating a netcdf file from a grib2 file using a python script.
I had
> originally filled in the values starting from the ul corner (90, 0).
Ncview
> and plot_data_plane showed two different orientations of the data. I
had
> worked with Randy on this issue and he said he believed that
> plot_data_plane was correct and that I needed to fill the values
from the
> ll corner (-90, 0), which would show the same results in both ncview
and
> plot data plane. After doing so, I'm still getting two different
> projections and I don't know which one is right. Please help!
>
> Best,
> Lindsay
> --
> Lindsay R. Blank
> Associate Scientist
> Joint Numerical Testbed Program
> National Center for Atmospheric Research
> +1 (303)-497-2772
>
> *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: plot_data_plane and ncview show different orientations
From: Lindsay Blank
Time: Mon Mar 30 14:37:48 2020
Hi John,
Thanks for this. The main problem is I don't know which way the data
should
be oriented so I don't know if MET is plotting the data correctly and
ncview incorrectly or vice versa. I think the problem is how I'm
filling in
the netcdf file, but I'm not sure.
My python script is on dakota: /d2/lblank/wind_dir_thresh.py. I've
been
running this on my personal laptop.
The grib2 file I'm using in the script is here:
dakota:/d2/lblank/multivariate_mode/data/gfs.t00z.pgrb2.0p25.f120
There are two netcdf files that are
output: dakota:/d2/lblank/multivariate_mode/data/dryline_test_4.nc
which is the original output before I reversed the range over which to
loop
(line 68 in my script) and the results of the reversed loop:
dakota:/d2/lblank/multivariate_mode/data/dryline_test_reversed.nc
The plot_data_plane command I've been running
is: /d3/projects/MET/MET_releases/met-9.0/bin/plot_data_plane
dryline_test_reversed.nc dryline_test_reversed.ps
'name="delta_u_direction"; level="(*,*)";'
Thank you!
Best,
Lindsay
On Mon, Mar 30, 2020 at 12:46 PM John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Hi Linday,
>
> When this sort of issue has come up in the past, we've fixed it by
> reversing the order in the met_data python array using a -1 in one
or both
> dimensions. Please try that yourself first to see if that orients
the data
> correctly.
>
> By way of example, please see take a look at this script:
>
> https://dtcenter.org/sites/default/files/community-code/met/python-
scripts/read_NRL_binary.py.txt
>
> And then at these lines:
>
> # Read and re-orient the data
> met_data = data[::-1].reshape(181, 360)[:,::-1].copy()
>
> If you're still stuck, please point me to your python script and
GRIB2
> file? Also, please share the plot_data_plane command you're running
and,
> if possible, an image showing how it should be oriented.
>
> Thanks,
> John
>
>
>
>
>
> On Mon, Mar 30, 2020 at 11:59 AM Lindsay Blank via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > Mon Mar 30 11:59:19 2020: Request 94767 was acted upon.
> > Transaction: Ticket created by lblank at ucar.edu
> > Queue: met_help
> > Subject: plot_data_plane and ncview show different
orientations
> > Owner: Nobody
> > Requestors: lblank at ucar.edu
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=94767 >
> >
> >
> > Hello,
> >
> > I'm creating a netcdf file from a grib2 file using a python
script. I had
> > originally filled in the values starting from the ul corner (90,
0).
> Ncview
> > and plot_data_plane showed two different orientations of the data.
I had
> > worked with Randy on this issue and he said he believed that
> > plot_data_plane was correct and that I needed to fill the values
from the
> > ll corner (-90, 0), which would show the same results in both
ncview and
> > plot data plane. After doing so, I'm still getting two different
> > projections and I don't know which one is right. Please help!
> >
> > Best,
> > Lindsay
> > --
> > Lindsay R. Blank
> > Associate Scientist
> > Joint Numerical Testbed Program
> > National Center for Atmospheric Research
> > +1 (303)-497-2772
> >
> > *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.*
> >
> >
>
>
--
Lindsay R. Blank
Associate Scientist
Joint Numerical Testbed Program
National Center for Atmospheric Research
+1 (303)-497-2772
*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: plot_data_plane and ncview show different orientations
From: John Halley Gotway
Time: Mon Mar 30 18:12:59 2020
Lindsay,
Thanks for sending along some details. I checked for the files you
listed,
but those NetCDF files do not exist:
ls /d2/lblank/multivariate_mode/data/dryline_test_4.nc
ls: cannot access
'/d2/lblank/multivariate_mode/data/dryline_test_4.nc': No
such file or directory
I copied over your input file and python script into:
dakota:/d3/projects/MET/MET_Help/blank_data_20200330
After modifying your script to read from the current directory, I
tried
running it:
/usr/local/python3/bin/python3 wind_dir_thresh.py
But python3 results in this error:
TypeError: find_intersections takes 4 parameters, but 3 units were
passed
Is this for python2 or python3?
It seems to me that the real question is how should your data be
oriented?
And you really don't have a standard to compare against. Here's one
way
you could approach this problem. Wherever you're able to get this
script
to run, modify it to simply write the U-component of wind instead of
the
derived value. Plot the resulting NetCDF file using plot_data_plane.
Also, run plot_data_plane to plot the U-component of wind from the
input
GRIB file. Tweak the looping order logic of your script until the
resulting images match.
Once they do, swap back in your derivation logic. That way you'll be
pretty confident that the data is oriented correctly.
John
On Mon, Mar 30, 2020 at 2:46 PM Lindsay Blank via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=94767 >
>
> Hi John,
>
> Thanks for this. The main problem is I don't know which way the data
should
> be oriented so I don't know if MET is plotting the data correctly
and
> ncview incorrectly or vice versa. I think the problem is how I'm
filling in
> the netcdf file, but I'm not sure.
>
> My python script is on dakota: /d2/lblank/wind_dir_thresh.py. I've
been
> running this on my personal laptop.
>
> The grib2 file I'm using in the script is here:
> dakota:/d2/lblank/multivariate_mode/data/gfs.t00z.pgrb2.0p25.f120
>
> There are two netcdf files that are
> output: dakota:/d2/lblank/multivariate_mode/data/dryline_test_4.nc
>
> which is the original output before I reversed the range over which
to loop
> (line 68 in my script) and the results of the reversed loop:
> dakota:/d2/lblank/multivariate_mode/data/dryline_test_reversed.nc
>
> The plot_data_plane command I've been running
> is: /d3/projects/MET/MET_releases/met-9.0/bin/plot_data_plane
> dryline_test_reversed.nc dryline_test_reversed.ps
> 'name="delta_u_direction"; level="(*,*)";'
>
> Thank you!
>
> Best,
> Lindsay
>
> On Mon, Mar 30, 2020 at 12:46 PM John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
> > Hi Linday,
> >
> > When this sort of issue has come up in the past, we've fixed it by
> > reversing the order in the met_data python array using a -1 in one
or
> both
> > dimensions. Please try that yourself first to see if that orients
the
> data
> > correctly.
> >
> > By way of example, please see take a look at this script:
> >
> >
> https://dtcenter.org/sites/default/files/community-code/met/python-
scripts/read_NRL_binary.py.txt
> >
> > And then at these lines:
> >
> > # Read and re-orient the data
> > met_data = data[::-1].reshape(181, 360)[:,::-1].copy()
> >
> > If you're still stuck, please point me to your python script and
GRIB2
> > file? Also, please share the plot_data_plane command you're
running and,
> > if possible, an image showing how it should be oriented.
> >
> > Thanks,
> > John
> >
> >
> >
> >
> >
> > On Mon, Mar 30, 2020 at 11:59 AM Lindsay Blank via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> > >
> > > Mon Mar 30 11:59:19 2020: Request 94767 was acted upon.
> > > Transaction: Ticket created by lblank at ucar.edu
> > > Queue: met_help
> > > Subject: plot_data_plane and ncview show different
orientations
> > > Owner: Nobody
> > > Requestors: lblank at ucar.edu
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=94767
> >
> > >
> > >
> > > Hello,
> > >
> > > I'm creating a netcdf file from a grib2 file using a python
script. I
> had
> > > originally filled in the values starting from the ul corner (90,
0).
> > Ncview
> > > and plot_data_plane showed two different orientations of the
data. I
> had
> > > worked with Randy on this issue and he said he believed that
> > > plot_data_plane was correct and that I needed to fill the values
from
> the
> > > ll corner (-90, 0), which would show the same results in both
ncview
> and
> > > plot data plane. After doing so, I'm still getting two different
> > > projections and I don't know which one is right. Please help!
> > >
> > > Best,
> > > Lindsay
> > > --
> > > Lindsay R. Blank
> > > Associate Scientist
> > > Joint Numerical Testbed Program
> > > National Center for Atmospheric Research
> > > +1 (303)-497-2772
> > >
> > > *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.*
> > >
> > >
> >
> >
>
> --
> Lindsay R. Blank
> Associate Scientist
> Joint Numerical Testbed Program
> National Center for Atmospheric Research
> +1 (303)-497-2772
>
> *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: plot_data_plane and ncview show different orientations
From: Lindsay Blank
Time: Thu Apr 02 16:32:51 2020
Hi John,
Thanks for looking into this. I'm afraid I gave you the wrong path for
those netcdf files, they're located here: dakota:/d2/lblank
This is for python3. I'm running a conda environment on my personal
machine
with python 3.6.
I did the debugging method you suggested and I was able to figure out
the
proper orientation. Ncview was showing the right orientation. I was
able to
get my netcdf file to produce the same data as the model grib2 file by
reversing the values of the uwind variable I read in from the sa,e
grib2
file. It doesn't seem to make any sense to me, but it works and shows
the
correct orientation. I ran pcp_combine -subtract on the original model
data
and the resulting netcdf file from my script and the result was 0s
everywhere. While I'm not sure why it's working that way, I'll take
it.
Thank you very much again for your help!
Best,
Lindsay
On Mon, Mar 30, 2020 at 6:13 PM John Halley Gotway via RT
<met_help at ucar.edu>
wrote:
> Lindsay,
>
> Thanks for sending along some details. I checked for the files you
listed,
> but those NetCDF files do not exist:
>
> ls /d2/lblank/multivariate_mode/data/dryline_test_4.nc
> ls: cannot access
'/d2/lblank/multivariate_mode/data/dryline_test_4.nc':
> No
> such file or directory
>
> I copied over your input file and python script into:
> dakota:/d3/projects/MET/MET_Help/blank_data_20200330
>
> After modifying your script to read from the current directory, I
tried
> running it:
> /usr/local/python3/bin/python3 wind_dir_thresh.py
>
> But python3 results in this error:
> TypeError: find_intersections takes 4 parameters, but 3 units were
passed
>
> Is this for python2 or python3?
>
> It seems to me that the real question is how should your data be
oriented?
> And you really don't have a standard to compare against. Here's one
way
> you could approach this problem. Wherever you're able to get this
script
> to run, modify it to simply write the U-component of wind instead of
the
> derived value. Plot the resulting NetCDF file using
plot_data_plane.
> Also, run plot_data_plane to plot the U-component of wind from the
input
> GRIB file. Tweak the looping order logic of your script until the
> resulting images match.
>
> Once they do, swap back in your derivation logic. That way you'll
be
> pretty confident that the data is oriented correctly.
>
> John
>
>
>
> On Mon, Mar 30, 2020 at 2:46 PM Lindsay Blank via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=94767 >
> >
> > Hi John,
> >
> > Thanks for this. The main problem is I don't know which way the
data
> should
> > be oriented so I don't know if MET is plotting the data correctly
and
> > ncview incorrectly or vice versa. I think the problem is how I'm
filling
> in
> > the netcdf file, but I'm not sure.
> >
> > My python script is on dakota: /d2/lblank/wind_dir_thresh.py. I've
been
> > running this on my personal laptop.
> >
> > The grib2 file I'm using in the script is here:
> > dakota:/d2/lblank/multivariate_mode/data/gfs.t00z.pgrb2.0p25.f120
> >
> > There are two netcdf files that are
> > output: dakota:/d2/lblank/multivariate_mode/data/dryline_test_4.nc
> >
> > which is the original output before I reversed the range over
which to
> loop
> > (line 68 in my script) and the results of the reversed loop:
> > dakota:/d2/lblank/multivariate_mode/data/dryline_test_reversed.nc
> >
> > The plot_data_plane command I've been running
> > is: /d3/projects/MET/MET_releases/met-9.0/bin/plot_data_plane
> > dryline_test_reversed.nc dryline_test_reversed.ps
> > 'name="delta_u_direction"; level="(*,*)";'
> >
> > Thank you!
> >
> > Best,
> > Lindsay
> >
> > On Mon, Mar 30, 2020 at 12:46 PM John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> > > Hi Linday,
> > >
> > > When this sort of issue has come up in the past, we've fixed it
by
> > > reversing the order in the met_data python array using a -1 in
one or
> > both
> > > dimensions. Please try that yourself first to see if that
orients the
> > data
> > > correctly.
> > >
> > > By way of example, please see take a look at this script:
> > >
> > >
> >
> https://dtcenter.org/sites/default/files/community-code/met/python-
scripts/read_NRL_binary.py.txt
> > >
> > > And then at these lines:
> > >
> > > # Read and re-orient the data
> > > met_data = data[::-1].reshape(181, 360)[:,::-1].copy()
> > >
> > > If you're still stuck, please point me to your python script and
GRIB2
> > > file? Also, please share the plot_data_plane command you're
running
> and,
> > > if possible, an image showing how it should be oriented.
> > >
> > > Thanks,
> > > John
> > >
> > >
> > >
> > >
> > >
> > > On Mon, Mar 30, 2020 at 11:59 AM Lindsay Blank via RT <
> met_help at ucar.edu
> > >
> > > wrote:
> > >
> > > >
> > > > Mon Mar 30 11:59:19 2020: Request 94767 was acted upon.
> > > > Transaction: Ticket created by lblank at ucar.edu
> > > > Queue: met_help
> > > > Subject: plot_data_plane and ncview show different
orientations
> > > > Owner: Nobody
> > > > Requestors: lblank at ucar.edu
> > > > Status: new
> > > > Ticket <URL:
> https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=94767
> > >
> > > >
> > > >
> > > > Hello,
> > > >
> > > > I'm creating a netcdf file from a grib2 file using a python
script. I
> > had
> > > > originally filled in the values starting from the ul corner
(90, 0).
> > > Ncview
> > > > and plot_data_plane showed two different orientations of the
data. I
> > had
> > > > worked with Randy on this issue and he said he believed that
> > > > plot_data_plane was correct and that I needed to fill the
values from
> > the
> > > > ll corner (-90, 0), which would show the same results in both
ncview
> > and
> > > > plot data plane. After doing so, I'm still getting two
different
> > > > projections and I don't know which one is right. Please help!
> > > >
> > > > Best,
> > > > Lindsay
> > > > --
> > > > Lindsay R. Blank
> > > > Associate Scientist
> > > > Joint Numerical Testbed Program
> > > > National Center for Atmospheric Research
> > > > +1 (303)-497-2772
> > > >
> > > > *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.*
> > > >
> > > >
> > >
> > >
> >
> > --
> > Lindsay R. Blank
> > Associate Scientist
> > Joint Numerical Testbed Program
> > National Center for Atmospheric Research
> > +1 (303)-497-2772
> >
> > *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.*
> >
> >
>
>
--
Lindsay R. Blank
Associate Scientist
Joint Numerical Testbed Program
National Center for Atmospheric Research
+1 (303)-497-2772
*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: plot_data_plane and ncview show different orientations
From: John Halley Gotway
Time: Thu Apr 02 21:07:26 2020
Lindsay,
Oh great. Glad you were able to figure it out.
Thanks for letting me know.
John
On Thu, Apr 2, 2020 at 4:33 PM Lindsay Blank via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=94767 >
>
> Hi John,
>
> Thanks for looking into this. I'm afraid I gave you the wrong path
for
> those netcdf files, they're located here: dakota:/d2/lblank
>
> This is for python3. I'm running a conda environment on my personal
machine
> with python 3.6.
>
> I did the debugging method you suggested and I was able to figure
out the
> proper orientation. Ncview was showing the right orientation. I was
able to
> get my netcdf file to produce the same data as the model grib2 file
by
> reversing the values of the uwind variable I read in from the sa,e
grib2
> file. It doesn't seem to make any sense to me, but it works and
shows the
> correct orientation. I ran pcp_combine -subtract on the original
model data
> and the resulting netcdf file from my script and the result was 0s
> everywhere. While I'm not sure why it's working that way, I'll take
it.
>
> Thank you very much again for your help!
>
> Best,
> Lindsay
>
> On Mon, Mar 30, 2020 at 6:13 PM John Halley Gotway via RT <
> met_help at ucar.edu>
> wrote:
>
> > Lindsay,
> >
> > Thanks for sending along some details. I checked for the files
you
> listed,
> > but those NetCDF files do not exist:
> >
> > ls /d2/lblank/multivariate_mode/data/dryline_test_4.nc
> > ls: cannot access
'/d2/lblank/multivariate_mode/data/dryline_test_4.nc':
> > No
> > such file or directory
> >
> > I copied over your input file and python script into:
> > dakota:/d3/projects/MET/MET_Help/blank_data_20200330
> >
> > After modifying your script to read from the current directory, I
tried
> > running it:
> > /usr/local/python3/bin/python3 wind_dir_thresh.py
> >
> > But python3 results in this error:
> > TypeError: find_intersections takes 4 parameters, but 3 units were
passed
> >
> > Is this for python2 or python3?
> >
> > It seems to me that the real question is how should your data be
> oriented?
> > And you really don't have a standard to compare against. Here's
one way
> > you could approach this problem. Wherever you're able to get this
script
> > to run, modify it to simply write the U-component of wind instead
of the
> > derived value. Plot the resulting NetCDF file using
plot_data_plane.
> > Also, run plot_data_plane to plot the U-component of wind from the
input
> > GRIB file. Tweak the looping order logic of your script until the
> > resulting images match.
> >
> > Once they do, swap back in your derivation logic. That way you'll
be
> > pretty confident that the data is oriented correctly.
> >
> > John
> >
> >
> >
> > On Mon, Mar 30, 2020 at 2:46 PM Lindsay Blank via RT
<met_help at ucar.edu>
> > wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=94767 >
> > >
> > > Hi John,
> > >
> > > Thanks for this. The main problem is I don't know which way the
data
> > should
> > > be oriented so I don't know if MET is plotting the data
correctly and
> > > ncview incorrectly or vice versa. I think the problem is how I'm
> filling
> > in
> > > the netcdf file, but I'm not sure.
> > >
> > > My python script is on dakota: /d2/lblank/wind_dir_thresh.py.
I've been
> > > running this on my personal laptop.
> > >
> > > The grib2 file I'm using in the script is here:
> > >
dakota:/d2/lblank/multivariate_mode/data/gfs.t00z.pgrb2.0p25.f120
> > >
> > > There are two netcdf files that are
> > > output:
dakota:/d2/lblank/multivariate_mode/data/dryline_test_4.nc
> > >
> > > which is the original output before I reversed the range over
which to
> > loop
> > > (line 68 in my script) and the results of the reversed loop:
> > >
dakota:/d2/lblank/multivariate_mode/data/dryline_test_reversed.nc
> > >
> > > The plot_data_plane command I've been running
> > > is: /d3/projects/MET/MET_releases/met-9.0/bin/plot_data_plane
> > > dryline_test_reversed.nc dryline_test_reversed.ps
> > > 'name="delta_u_direction"; level="(*,*)";'
> > >
> > > Thank you!
> > >
> > > Best,
> > > Lindsay
> > >
> > > On Mon, Mar 30, 2020 at 12:46 PM John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > > > Hi Linday,
> > > >
> > > > When this sort of issue has come up in the past, we've fixed
it by
> > > > reversing the order in the met_data python array using a -1 in
one or
> > > both
> > > > dimensions. Please try that yourself first to see if that
orients
> the
> > > data
> > > > correctly.
> > > >
> > > > By way of example, please see take a look at this script:
> > > >
> > > >
> > >
> >
> https://dtcenter.org/sites/default/files/community-code/met/python-
scripts/read_NRL_binary.py.txt
> > > >
> > > > And then at these lines:
> > > >
> > > > # Read and re-orient the data
> > > > met_data = data[::-1].reshape(181, 360)[:,::-1].copy()
> > > >
> > > > If you're still stuck, please point me to your python script
and
> GRIB2
> > > > file? Also, please share the plot_data_plane command you're
running
> > and,
> > > > if possible, an image showing how it should be oriented.
> > > >
> > > > Thanks,
> > > > John
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > On Mon, Mar 30, 2020 at 11:59 AM Lindsay Blank via RT <
> > met_help at ucar.edu
> > > >
> > > > wrote:
> > > >
> > > > >
> > > > > Mon Mar 30 11:59:19 2020: Request 94767 was acted upon.
> > > > > Transaction: Ticket created by lblank at ucar.edu
> > > > > Queue: met_help
> > > > > Subject: plot_data_plane and ncview show different
> orientations
> > > > > Owner: Nobody
> > > > > Requestors: lblank at ucar.edu
> > > > > Status: new
> > > > > Ticket <URL:
> > https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=94767
> > > >
> > > > >
> > > > >
> > > > > Hello,
> > > > >
> > > > > I'm creating a netcdf file from a grib2 file using a python
> script. I
> > > had
> > > > > originally filled in the values starting from the ul corner
(90,
> 0).
> > > > Ncview
> > > > > and plot_data_plane showed two different orientations of the
data.
> I
> > > had
> > > > > worked with Randy on this issue and he said he believed that
> > > > > plot_data_plane was correct and that I needed to fill the
values
> from
> > > the
> > > > > ll corner (-90, 0), which would show the same results in
both
> ncview
> > > and
> > > > > plot data plane. After doing so, I'm still getting two
different
> > > > > projections and I don't know which one is right. Please
help!
> > > > >
> > > > > Best,
> > > > > Lindsay
> > > > > --
> > > > > Lindsay R. Blank
> > > > > Associate Scientist
> > > > > Joint Numerical Testbed Program
> > > > > National Center for Atmospheric Research
> > > > > +1 (303)-497-2772
> > > > >
> > > > > *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.*
> > > > >
> > > > >
> > > >
> > > >
> > >
> > > --
> > > Lindsay R. Blank
> > > Associate Scientist
> > > Joint Numerical Testbed Program
> > > National Center for Atmospheric Research
> > > +1 (303)-497-2772
> > >
> > > *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.*
> > >
> > >
> >
> >
>
> --
> Lindsay R. Blank
> Associate Scientist
> Joint Numerical Testbed Program
> National Center for Atmospheric Research
> +1 (303)-497-2772
>
> *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