[Met_help] [rt.rap.ucar.edu #81265] History for MODE NetCDF Attributes
Julie Prestopnik via RT
met_help at ucar.edu
Mon Aug 7 14:44:25 MDT 2017
----------------------------------------------------------------
Initial Request
----------------------------------------------------------------
Hello,
I've just started using MODE and succeeded with the sample data, but it's
unable to read my own NetCDF files. I believe this is because of inadequate
attribute data - could you tell me what attributes need to be defined for
MODE to read a NetCDF?
Thank you!
Jacob Radford
----------------------------------------------------------------
Complete Ticket History
----------------------------------------------------------------
Subject: MODE NetCDF Attributes
From: Julie Prestopnik
Time: Wed Jul 19 12:43:15 2017
Hi Jacob. I see that you are encountering a problem with MODE reading
your
NetCDF files.
MET supports a few flavors of NetCDF...
- Gridded NetCDF files following the CF-convention
- Gridded NetCDF output of the WRF pinterp utility
- Internal MET formatted NetCDF file
When you pass MET a NetCDF file, it inspects the file to determine
it's
type. If it's not CF-compliant or a pinterp file, it assumes it's
the 3rd
type. The 3rd type is basically just the output of pcp_combine tool.
I have attached a sample input file that is the output of pcp_combine,
so
that you can take a look.
I hope this is helpful. Please let us know if you have any other
questions.
Julie
On Tue, Jul 18, 2017 at 6:56 PM, Jacob Radford via RT
<met_help at ucar.edu>
wrote:
>
> Tue Jul 18 18:56:20 2017: Request 81265 was acted upon.
> Transaction: Ticket created by jtradfor at ncsu.edu
> Queue: met_help
> Subject: MODE NetCDF Attributes
> Owner: Nobody
> Requestors: jtradfor at ncsu.edu
> Status: new
> Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
>
>
> Hello,
>
> I've just started using MODE and succeeded with the sample data, but
it's
> unable to read my own NetCDF files. I believe this is because of
inadequate
> attribute data - could you tell me what attributes need to be
defined for
> MODE to read a NetCDF?
>
> Thank you!
> Jacob Radford
>
>
------------------------------------------------
Subject: MODE NetCDF Attributes
From: Jacob Radford
Time: Thu Jul 20 11:38:49 2017
Hi Julie,
Thank you for the information. Let me explain a little bit about what
I'm
trying to do:
I originally had a geotiff that I converted to a NetCDF using a Python
package. It's basically just a base reflectivity field with a
corresponding
LatLon grid. I'd like to be able to have this outputted NetCDF read by
MODE. Originally, without setting any attributes, I received an error
stating that MODE was unable to read the NetCDF. I then found this
link
specifying the global grid attributes that are produced by pcp_combine
for
a LatLon grid:
http://mailman.ucar.edu/pipermail/met_help/2014-February/002090.html
I attempted to configure these attributes for my own file so that my
own
global attributes look like so:
:Projection = "LatLon" ;
:lat_ll = "23.000000 degrees_north" ;
:lon_ll = "126.000000 degrees_west" ;
:delta_lat = "0.005000 degrees" ;
:delta_lon = "0.005000 degrees" ;
:Nlat = "5400 grid_points" ;
:Nlon = "12200 grid_points" ;
I had some success with this as I no longer received the "unreadable"
error, but instead it gets to the step stating "Identifying objects in
the forecast and observation fields..." after which the job is killed
without any further details. I attached a screenshot of this.
I can attach the NetCDF file I've produced if it would help, but
refrained from doing so as it's quite large due to the large grid
size.
Any advice you could provide would be greatly appreciated!
Best,
Jacob Radford
On Wed, Jul 19, 2017 at 2:43 PM, Julie Prestopnik via RT
<met_help at ucar.edu>
wrote:
> Hi Jacob. I see that you are encountering a problem with MODE
reading your
> NetCDF files.
>
> MET supports a few flavors of NetCDF...
> - Gridded NetCDF files following the CF-convention
> - Gridded NetCDF output of the WRF pinterp utility
> - Internal MET formatted NetCDF file
>
> When you pass MET a NetCDF file, it inspects the file to determine
it's
> type. If it's not CF-compliant or a pinterp file, it assumes it's
the 3rd
> type. The 3rd type is basically just the output of pcp_combine
tool.
>
> I have attached a sample input file that is the output of
pcp_combine, so
> that you can take a look.
>
> I hope this is helpful. Please let us know if you have any other
> questions.
>
> Julie
>
>
> On Tue, Jul 18, 2017 at 6:56 PM, Jacob Radford via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > Tue Jul 18 18:56:20 2017: Request 81265 was acted upon.
> > Transaction: Ticket created by jtradfor at ncsu.edu
> > Queue: met_help
> > Subject: MODE NetCDF Attributes
> > Owner: Nobody
> > Requestors: jtradfor at ncsu.edu
> > Status: new
> > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> >
> >
> > Hello,
> >
> > I've just started using MODE and succeeded with the sample data,
but it's
> > unable to read my own NetCDF files. I believe this is because of
> inadequate
> > attribute data - could you tell me what attributes need to be
defined for
> > MODE to read a NetCDF?
> >
> > Thank you!
> > Jacob Radford
> >
> >
>
>
------------------------------------------------
Subject: MODE NetCDF Attributes
From: Julie Prestopnik
Time: Thu Jul 20 11:52:31 2017
Hi Jacob. Thank you for providing more information. To get more
information about what is going on you could try running MODE with a
higher
verbosity level (e.g. -v 9). Also, please feel free to upload your
file on
our anonymous ftp site:
http://www.dtcenter.org/met/users/support/met_help.php#ftp
so that we can also take a look. If you do upload data, please upload
all
the files used and send me the command you are using to run the code,
so
that I can try to reproduce the behavior.
Also, what version of MET are you using?
Thanks,
Julie
On Thu, Jul 20, 2017 at 11:38 AM, Jacob Radford via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
>
> Hi Julie,
>
> Thank you for the information. Let me explain a little bit about
what I'm
> trying to do:
>
> I originally had a geotiff that I converted to a NetCDF using a
Python
> package. It's basically just a base reflectivity field with a
corresponding
> LatLon grid. I'd like to be able to have this outputted NetCDF read
by
> MODE. Originally, without setting any attributes, I received an
error
> stating that MODE was unable to read the NetCDF. I then found this
link
> specifying the global grid attributes that are produced by
pcp_combine for
> a LatLon grid:
>
> http://mailman.ucar.edu/pipermail/met_help/2014-February/002090.html
>
> I attempted to configure these attributes for my own file so that my
own
> global attributes look like so:
>
> :Projection = "LatLon" ;
> :lat_ll = "23.000000 degrees_north" ;
> :lon_ll = "126.000000 degrees_west" ;
> :delta_lat = "0.005000 degrees" ;
> :delta_lon = "0.005000 degrees" ;
> :Nlat = "5400 grid_points" ;
> :Nlon = "12200 grid_points" ;
>
> I had some success with this as I no longer received the
"unreadable"
> error, but instead it gets to the step stating "Identifying objects
in
> the forecast and observation fields..." after which the job is
killed
> without any further details. I attached a screenshot of this.
>
> I can attach the NetCDF file I've produced if it would help, but
> refrained from doing so as it's quite large due to the large grid
> size.
>
> Any advice you could provide would be greatly appreciated!
>
> Best,
> Jacob Radford
>
>
> On Wed, Jul 19, 2017 at 2:43 PM, Julie Prestopnik via RT <
> met_help at ucar.edu>
> wrote:
>
> > Hi Jacob. I see that you are encountering a problem with MODE
reading
> your
> > NetCDF files.
> >
> > MET supports a few flavors of NetCDF...
> > - Gridded NetCDF files following the CF-convention
> > - Gridded NetCDF output of the WRF pinterp utility
> > - Internal MET formatted NetCDF file
> >
> > When you pass MET a NetCDF file, it inspects the file to determine
it's
> > type. If it's not CF-compliant or a pinterp file, it assumes
it's the
> 3rd
> > type. The 3rd type is basically just the output of pcp_combine
tool.
> >
> > I have attached a sample input file that is the output of
pcp_combine, so
> > that you can take a look.
> >
> > I hope this is helpful. Please let us know if you have any other
> > questions.
> >
> > Julie
> >
> >
> > On Tue, Jul 18, 2017 at 6:56 PM, Jacob Radford via RT
<met_help at ucar.edu
> >
> > wrote:
> >
> > >
> > > Tue Jul 18 18:56:20 2017: Request 81265 was acted upon.
> > > Transaction: Ticket created by jtradfor at ncsu.edu
> > > Queue: met_help
> > > Subject: MODE NetCDF Attributes
> > > Owner: Nobody
> > > Requestors: jtradfor at ncsu.edu
> > > Status: new
> > > Ticket <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265
> >
> > >
> > >
> > > Hello,
> > >
> > > I've just started using MODE and succeeded with the sample data,
but
> it's
> > > unable to read my own NetCDF files. I believe this is because of
> > inadequate
> > > attribute data - could you tell me what attributes need to be
defined
> for
> > > MODE to read a NetCDF?
> > >
> > > Thank you!
> > > Jacob Radford
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: MODE NetCDF Attributes
From: Jacob Radford
Time: Thu Jul 20 23:33:30 2017
Hi Julie,
I increased the verbosity as you suggested and it looks like the
problem is
occurring at the convolution step. I uploaded my NetCDF
(reflectivity.nc)
and my MODE configuration file (MODEConfig_tutorial) following the
conventions in the FTP instructions (under Radford_data). I tried to
change
as little as possible from the tutorial configuration, so I mostly
just
edited the forecast/observation field to read the information from my
own
file. I'm also using the same file for the forecast and observations
initially because I'm just getting familiar with MET and trying to get
it
to read my data at this point.
I'm running METv6.0 in Docker and the command I'm using is:
> mode \
> tutorial/out/pcp_combine/reflectivity.nc \
> tutorial/out/pcp_combine/reflectivity.nc \
> tutorial/config/MODEConfig_tutorial \
> -outdir tutorial/out/mode \
> -v 9
Let me know if there's any other information or files that you need
from me
to look into this.
Best,
Jacob
On Thu, Jul 20, 2017 at 1:52 PM, Julie Prestopnik via RT
<met_help at ucar.edu>
wrote:
> Hi Jacob. Thank you for providing more information. To get more
> information about what is going on you could try running MODE with a
higher
> verbosity level (e.g. -v 9). Also, please feel free to upload your
file on
> our anonymous ftp site:
>
> http://www.dtcenter.org/met/users/support/met_help.php#ftp
>
> so that we can also take a look. If you do upload data, please
upload all
> the files used and send me the command you are using to run the
code, so
> that I can try to reproduce the behavior.
>
> Also, what version of MET are you using?
>
> Thanks,
> Julie
>
> On Thu, Jul 20, 2017 at 11:38 AM, Jacob Radford via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> >
> > Hi Julie,
> >
> > Thank you for the information. Let me explain a little bit about
what I'm
> > trying to do:
> >
> > I originally had a geotiff that I converted to a NetCDF using a
Python
> > package. It's basically just a base reflectivity field with a
> corresponding
> > LatLon grid. I'd like to be able to have this outputted NetCDF
read by
> > MODE. Originally, without setting any attributes, I received an
error
> > stating that MODE was unable to read the NetCDF. I then found this
link
> > specifying the global grid attributes that are produced by
pcp_combine
> for
> > a LatLon grid:
> >
> > http://mailman.ucar.edu/pipermail/met_help/2014-
February/002090.html
> >
> > I attempted to configure these attributes for my own file so that
my own
> > global attributes look like so:
> >
> > :Projection = "LatLon" ;
> > :lat_ll = "23.000000 degrees_north" ;
> > :lon_ll = "126.000000 degrees_west" ;
> > :delta_lat = "0.005000 degrees" ;
> > :delta_lon = "0.005000 degrees" ;
> > :Nlat = "5400 grid_points" ;
> > :Nlon = "12200 grid_points" ;
> >
> > I had some success with this as I no longer received the
"unreadable"
> > error, but instead it gets to the step stating "Identifying
objects in
> > the forecast and observation fields..." after which the job is
killed
> > without any further details. I attached a screenshot of this.
> >
> > I can attach the NetCDF file I've produced if it would help, but
> > refrained from doing so as it's quite large due to the large grid
> > size.
> >
> > Any advice you could provide would be greatly appreciated!
> >
> > Best,
> > Jacob Radford
> >
> >
> > On Wed, Jul 19, 2017 at 2:43 PM, Julie Prestopnik via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Hi Jacob. I see that you are encountering a problem with MODE
reading
> > your
> > > NetCDF files.
> > >
> > > MET supports a few flavors of NetCDF...
> > > - Gridded NetCDF files following the CF-convention
> > > - Gridded NetCDF output of the WRF pinterp utility
> > > - Internal MET formatted NetCDF file
> > >
> > > When you pass MET a NetCDF file, it inspects the file to
determine it's
> > > type. If it's not CF-compliant or a pinterp file, it assumes
it's the
> > 3rd
> > > type. The 3rd type is basically just the output of pcp_combine
tool.
> > >
> > > I have attached a sample input file that is the output of
pcp_combine,
> so
> > > that you can take a look.
> > >
> > > I hope this is helpful. Please let us know if you have any
other
> > > questions.
> > >
> > > Julie
> > >
> > >
> > > On Tue, Jul 18, 2017 at 6:56 PM, Jacob Radford via RT <
> met_help at ucar.edu
> > >
> > > wrote:
> > >
> > > >
> > > > Tue Jul 18 18:56:20 2017: Request 81265 was acted upon.
> > > > Transaction: Ticket created by jtradfor at ncsu.edu
> > > > Queue: met_help
> > > > Subject: MODE NetCDF Attributes
> > > > Owner: Nobody
> > > > Requestors: jtradfor at ncsu.edu
> > > > Status: new
> > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=81265
> > >
> > > >
> > > >
> > > > Hello,
> > > >
> > > > I've just started using MODE and succeeded with the sample
data, but
> > it's
> > > > unable to read my own NetCDF files. I believe this is because
of
> > > inadequate
> > > > attribute data - could you tell me what attributes need to be
defined
> > for
> > > > MODE to read a NetCDF?
> > > >
> > > > Thank you!
> > > > Jacob Radford
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: MODE NetCDF Attributes
From: Julie Prestopnik
Time: Fri Jul 21 11:05:42 2017
Hi Jacob. Thank you for sending me the data and the command line you
are
using. We can see that MET is working on your data, but unfortunately
it
is not realistic to have MET run on such a dense grid. MODE was
running
extremely slowly due to the grid density.
We regridded your data using the following command to a .1 degree
grid:
regrid_data_plane reflectivity.nc 'latlon 610 270 23 126 0.1 0.1'
reflectivity_REGRID.nc -field 'name="Reflectivity"; level="(*,*)";'
-name
Reflectivity -method BILIN -width 2
We also played around with your configuration file a bit and made some
changes. Using the new file, reflectivity_REGRID.nc with the new
configuration file (attached), we were able to create reasonable
looking
objects.
Please take a look and let us know if you have any questions.
Thanks,
Julie
On Thu, Jul 20, 2017 at 11:33 PM, Jacob Radford via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
>
> Hi Julie,
>
> I increased the verbosity as you suggested and it looks like the
problem is
> occurring at the convolution step. I uploaded my NetCDF
(reflectivity.nc)
> and my MODE configuration file (MODEConfig_tutorial) following the
> conventions in the FTP instructions (under Radford_data). I tried to
change
> as little as possible from the tutorial configuration, so I mostly
just
> edited the forecast/observation field to read the information from
my own
> file. I'm also using the same file for the forecast and observations
> initially because I'm just getting familiar with MET and trying to
get it
> to read my data at this point.
>
> I'm running METv6.0 in Docker and the command I'm using is:
>
> > mode \
> > tutorial/out/pcp_combine/reflectivity.nc \
> > tutorial/out/pcp_combine/reflectivity.nc \
> > tutorial/config/MODEConfig_tutorial \
> > -outdir tutorial/out/mode \
> > -v 9
>
> Let me know if there's any other information or files that you need
from me
> to look into this.
>
> Best,
> Jacob
>
> On Thu, Jul 20, 2017 at 1:52 PM, Julie Prestopnik via RT <
> met_help at ucar.edu>
> wrote:
>
> > Hi Jacob. Thank you for providing more information. To get more
> > information about what is going on you could try running MODE with
a
> higher
> > verbosity level (e.g. -v 9). Also, please feel free to upload
your file
> on
> > our anonymous ftp site:
> >
> > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >
> > so that we can also take a look. If you do upload data, please
upload
> all
> > the files used and send me the command you are using to run the
code, so
> > that I can try to reproduce the behavior.
> >
> > Also, what version of MET are you using?
> >
> > Thanks,
> > Julie
> >
> > On Thu, Jul 20, 2017 at 11:38 AM, Jacob Radford via RT <
> met_help at ucar.edu>
> > wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> > >
> > > Hi Julie,
> > >
> > > Thank you for the information. Let me explain a little bit about
what
> I'm
> > > trying to do:
> > >
> > > I originally had a geotiff that I converted to a NetCDF using a
Python
> > > package. It's basically just a base reflectivity field with a
> > corresponding
> > > LatLon grid. I'd like to be able to have this outputted NetCDF
read by
> > > MODE. Originally, without setting any attributes, I received an
error
> > > stating that MODE was unable to read the NetCDF. I then found
this link
> > > specifying the global grid attributes that are produced by
pcp_combine
> > for
> > > a LatLon grid:
> > >
> > > http://mailman.ucar.edu/pipermail/met_help/2014-
February/002090.html
> > >
> > > I attempted to configure these attributes for my own file so
that my
> own
> > > global attributes look like so:
> > >
> > > :Projection = "LatLon" ;
> > > :lat_ll = "23.000000 degrees_north" ;
> > > :lon_ll = "126.000000 degrees_west" ;
> > > :delta_lat = "0.005000 degrees" ;
> > > :delta_lon = "0.005000 degrees" ;
> > > :Nlat = "5400 grid_points" ;
> > > :Nlon = "12200 grid_points" ;
> > >
> > > I had some success with this as I no longer received the
"unreadable"
> > > error, but instead it gets to the step stating "Identifying
objects in
> > > the forecast and observation fields..." after which the job is
killed
> > > without any further details. I attached a screenshot of this.
> > >
> > > I can attach the NetCDF file I've produced if it would help, but
> > > refrained from doing so as it's quite large due to the large
grid
> > > size.
> > >
> > > Any advice you could provide would be greatly appreciated!
> > >
> > > Best,
> > > Jacob Radford
> > >
> > >
> > > On Wed, Jul 19, 2017 at 2:43 PM, Julie Prestopnik via RT <
> > > met_help at ucar.edu>
> > > wrote:
> > >
> > > > Hi Jacob. I see that you are encountering a problem with MODE
> reading
> > > your
> > > > NetCDF files.
> > > >
> > > > MET supports a few flavors of NetCDF...
> > > > - Gridded NetCDF files following the CF-convention
> > > > - Gridded NetCDF output of the WRF pinterp utility
> > > > - Internal MET formatted NetCDF file
> > > >
> > > > When you pass MET a NetCDF file, it inspects the file to
determine
> it's
> > > > type. If it's not CF-compliant or a pinterp file, it assumes
it's
> the
> > > 3rd
> > > > type. The 3rd type is basically just the output of
pcp_combine tool.
> > > >
> > > > I have attached a sample input file that is the output of
> pcp_combine,
> > so
> > > > that you can take a look.
> > > >
> > > > I hope this is helpful. Please let us know if you have any
other
> > > > questions.
> > > >
> > > > Julie
> > > >
> > > >
> > > > On Tue, Jul 18, 2017 at 6:56 PM, Jacob Radford via RT <
> > met_help at ucar.edu
> > > >
> > > > wrote:
> > > >
> > > > >
> > > > > Tue Jul 18 18:56:20 2017: Request 81265 was acted upon.
> > > > > Transaction: Ticket created by jtradfor at ncsu.edu
> > > > > Queue: met_help
> > > > > Subject: MODE NetCDF Attributes
> > > > > Owner: Nobody
> > > > > Requestors: jtradfor at ncsu.edu
> > > > > Status: new
> > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > Ticket/Display.html?id=81265
> > > >
> > > > >
> > > > >
> > > > > Hello,
> > > > >
> > > > > I've just started using MODE and succeeded with the sample
data,
> but
> > > it's
> > > > > unable to read my own NetCDF files. I believe this is
because of
> > > > inadequate
> > > > > attribute data - could you tell me what attributes need to
be
> defined
> > > for
> > > > > MODE to read a NetCDF?
> > > > >
> > > > > Thank you!
> > > > > Jacob Radford
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: MODE NetCDF Attributes
From: Jacob Radford
Time: Fri Jul 21 11:44:21 2017
Hi Julie,
Thank you for all your help! I thought the grid density might be an
issue.
Interpolating to a coarser grid was ultimately the plan anyway.
Best,
Jacob
On Fri, Jul 21, 2017 at 1:05 PM, Julie Prestopnik via RT
<met_help at ucar.edu>
wrote:
> Hi Jacob. Thank you for sending me the data and the command line
you are
> using. We can see that MET is working on your data, but
unfortunately it
> is not realistic to have MET run on such a dense grid. MODE was
running
> extremely slowly due to the grid density.
>
> We regridded your data using the following command to a .1 degree
grid:
>
> regrid_data_plane reflectivity.nc 'latlon 610 270 23 126 0.1 0.1'
> reflectivity_REGRID.nc -field 'name="Reflectivity"; level="(*,*)";'
-name
> Reflectivity -method BILIN -width 2
>
> We also played around with your configuration file a bit and made
some
> changes. Using the new file, reflectivity_REGRID.nc with the new
> configuration file (attached), we were able to create reasonable
looking
> objects.
>
> Please take a look and let us know if you have any questions.
>
> Thanks,
> Julie
>
> On Thu, Jul 20, 2017 at 11:33 PM, Jacob Radford via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> >
> > Hi Julie,
> >
> > I increased the verbosity as you suggested and it looks like the
problem
> is
> > occurring at the convolution step. I uploaded my NetCDF
(reflectivity.nc
> )
> > and my MODE configuration file (MODEConfig_tutorial) following the
> > conventions in the FTP instructions (under Radford_data). I tried
to
> change
> > as little as possible from the tutorial configuration, so I mostly
just
> > edited the forecast/observation field to read the information from
my own
> > file. I'm also using the same file for the forecast and
observations
> > initially because I'm just getting familiar with MET and trying to
get it
> > to read my data at this point.
> >
> > I'm running METv6.0 in Docker and the command I'm using is:
> >
> > > mode \
> > > tutorial/out/pcp_combine/reflectivity.nc \
> > > tutorial/out/pcp_combine/reflectivity.nc \
> > > tutorial/config/MODEConfig_tutorial \
> > > -outdir tutorial/out/mode \
> > > -v 9
> >
> > Let me know if there's any other information or files that you
need from
> me
> > to look into this.
> >
> > Best,
> > Jacob
> >
> > On Thu, Jul 20, 2017 at 1:52 PM, Julie Prestopnik via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Hi Jacob. Thank you for providing more information. To get
more
> > > information about what is going on you could try running MODE
with a
> > higher
> > > verbosity level (e.g. -v 9). Also, please feel free to upload
your
> file
> > on
> > > our anonymous ftp site:
> > >
> > > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> > >
> > > so that we can also take a look. If you do upload data, please
upload
> > all
> > > the files used and send me the command you are using to run the
code,
> so
> > > that I can try to reproduce the behavior.
> > >
> > > Also, what version of MET are you using?
> > >
> > > Thanks,
> > > Julie
> > >
> > > On Thu, Jul 20, 2017 at 11:38 AM, Jacob Radford via RT <
> > met_help at ucar.edu>
> > > wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265
>
> > > >
> > > > Hi Julie,
> > > >
> > > > Thank you for the information. Let me explain a little bit
about what
> > I'm
> > > > trying to do:
> > > >
> > > > I originally had a geotiff that I converted to a NetCDF using
a
> Python
> > > > package. It's basically just a base reflectivity field with a
> > > corresponding
> > > > LatLon grid. I'd like to be able to have this outputted NetCDF
read
> by
> > > > MODE. Originally, without setting any attributes, I received
an error
> > > > stating that MODE was unable to read the NetCDF. I then found
this
> link
> > > > specifying the global grid attributes that are produced by
> pcp_combine
> > > for
> > > > a LatLon grid:
> > > >
> > > > http://mailman.ucar.edu/pipermail/met_help/2014-
February/002090.html
> > > >
> > > > I attempted to configure these attributes for my own file so
that my
> > own
> > > > global attributes look like so:
> > > >
> > > > :Projection = "LatLon" ;
> > > > :lat_ll = "23.000000 degrees_north" ;
> > > > :lon_ll = "126.000000 degrees_west" ;
> > > > :delta_lat = "0.005000 degrees" ;
> > > > :delta_lon = "0.005000 degrees" ;
> > > > :Nlat = "5400 grid_points" ;
> > > > :Nlon = "12200 grid_points" ;
> > > >
> > > > I had some success with this as I no longer received the
"unreadable"
> > > > error, but instead it gets to the step stating "Identifying
objects
> in
> > > > the forecast and observation fields..." after which the job is
killed
> > > > without any further details. I attached a screenshot of this.
> > > >
> > > > I can attach the NetCDF file I've produced if it would help,
but
> > > > refrained from doing so as it's quite large due to the large
grid
> > > > size.
> > > >
> > > > Any advice you could provide would be greatly appreciated!
> > > >
> > > > Best,
> > > > Jacob Radford
> > > >
> > > >
> > > > On Wed, Jul 19, 2017 at 2:43 PM, Julie Prestopnik via RT <
> > > > met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > > Hi Jacob. I see that you are encountering a problem with
MODE
> > reading
> > > > your
> > > > > NetCDF files.
> > > > >
> > > > > MET supports a few flavors of NetCDF...
> > > > > - Gridded NetCDF files following the CF-convention
> > > > > - Gridded NetCDF output of the WRF pinterp utility
> > > > > - Internal MET formatted NetCDF file
> > > > >
> > > > > When you pass MET a NetCDF file, it inspects the file to
determine
> > it's
> > > > > type. If it's not CF-compliant or a pinterp file, it
assumes it's
> > the
> > > > 3rd
> > > > > type. The 3rd type is basically just the output of
pcp_combine
> tool.
> > > > >
> > > > > I have attached a sample input file that is the output of
> > pcp_combine,
> > > so
> > > > > that you can take a look.
> > > > >
> > > > > I hope this is helpful. Please let us know if you have any
other
> > > > > questions.
> > > > >
> > > > > Julie
> > > > >
> > > > >
> > > > > On Tue, Jul 18, 2017 at 6:56 PM, Jacob Radford via RT <
> > > met_help at ucar.edu
> > > > >
> > > > > wrote:
> > > > >
> > > > > >
> > > > > > Tue Jul 18 18:56:20 2017: Request 81265 was acted upon.
> > > > > > Transaction: Ticket created by jtradfor at ncsu.edu
> > > > > > Queue: met_help
> > > > > > Subject: MODE NetCDF Attributes
> > > > > > Owner: Nobody
> > > > > > Requestors: jtradfor at ncsu.edu
> > > > > > Status: new
> > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > > Ticket/Display.html?id=81265
> > > > >
> > > > > >
> > > > > >
> > > > > > Hello,
> > > > > >
> > > > > > I've just started using MODE and succeeded with the sample
data,
> > but
> > > > it's
> > > > > > unable to read my own NetCDF files. I believe this is
because of
> > > > > inadequate
> > > > > > attribute data - could you tell me what attributes need to
be
> > defined
> > > > for
> > > > > > MODE to read a NetCDF?
> > > > > >
> > > > > > Thank you!
> > > > > > Jacob Radford
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: MODE NetCDF Attributes
From: John Halley Gotway
Time: Fri Jul 21 12:43:49 2017
Jacob,
This is John and I work with Julie on providing MET support. Julie
sent
you an example of using the regrid_data_plane tool in MET to regrid
your
data before processing it in MODE.
You also have a second regridding option. Instead of calling
regrid_data_plane first, you could pass your original data file to
MODE and
use the "regrid" option in the MODE config file. That tells MODE to
do the
regridding on the fly without writing an intermediate file.
Either method will work and should result in identical output. It's
up to
you to decide whether you want to write an intermediate regridded
NetCDF
file.
Here's the regrid setting you could try in the MODE config file:
regrid = {
to_grid = "latlon 610 270 23 126 0.1 0.1";
method = BILIN;
width = 2;
vld_thresh = 0.5;
}
Hope that helps.
Thanks,
John
On Fri, Jul 21, 2017 at 11:44 AM, Jacob Radford via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
>
> Hi Julie,
>
> Thank you for all your help! I thought the grid density might be an
issue.
> Interpolating to a coarser grid was ultimately the plan anyway.
>
> Best,
> Jacob
>
> On Fri, Jul 21, 2017 at 1:05 PM, Julie Prestopnik via RT <
> met_help at ucar.edu>
> wrote:
>
> > Hi Jacob. Thank you for sending me the data and the command line
you are
> > using. We can see that MET is working on your data, but
unfortunately it
> > is not realistic to have MET run on such a dense grid. MODE was
running
> > extremely slowly due to the grid density.
> >
> > We regridded your data using the following command to a .1 degree
grid:
> >
> > regrid_data_plane reflectivity.nc 'latlon 610 270 23 126 0.1 0.1'
> > reflectivity_REGRID.nc -field 'name="Reflectivity";
level="(*,*)";' -name
> > Reflectivity -method BILIN -width 2
> >
> > We also played around with your configuration file a bit and made
some
> > changes. Using the new file, reflectivity_REGRID.nc with the new
> > configuration file (attached), we were able to create reasonable
looking
> > objects.
> >
> > Please take a look and let us know if you have any questions.
> >
> > Thanks,
> > Julie
> >
> > On Thu, Jul 20, 2017 at 11:33 PM, Jacob Radford via RT <
> met_help at ucar.edu>
> > wrote:
> >
> > >
> > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> > >
> > > Hi Julie,
> > >
> > > I increased the verbosity as you suggested and it looks like the
> problem
> > is
> > > occurring at the convolution step. I uploaded my NetCDF (
> reflectivity.nc
> > )
> > > and my MODE configuration file (MODEConfig_tutorial) following
the
> > > conventions in the FTP instructions (under Radford_data). I
tried to
> > change
> > > as little as possible from the tutorial configuration, so I
mostly just
> > > edited the forecast/observation field to read the information
from my
> own
> > > file. I'm also using the same file for the forecast and
observations
> > > initially because I'm just getting familiar with MET and trying
to get
> it
> > > to read my data at this point.
> > >
> > > I'm running METv6.0 in Docker and the command I'm using is:
> > >
> > > > mode \
> > > > tutorial/out/pcp_combine/reflectivity.nc \
> > > > tutorial/out/pcp_combine/reflectivity.nc \
> > > > tutorial/config/MODEConfig_tutorial \
> > > > -outdir tutorial/out/mode \
> > > > -v 9
> > >
> > > Let me know if there's any other information or files that you
need
> from
> > me
> > > to look into this.
> > >
> > > Best,
> > > Jacob
> > >
> > > On Thu, Jul 20, 2017 at 1:52 PM, Julie Prestopnik via RT <
> > > met_help at ucar.edu>
> > > wrote:
> > >
> > > > Hi Jacob. Thank you for providing more information. To get
more
> > > > information about what is going on you could try running MODE
with a
> > > higher
> > > > verbosity level (e.g. -v 9). Also, please feel free to upload
your
> > file
> > > on
> > > > our anonymous ftp site:
> > > >
> > > > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> > > >
> > > > so that we can also take a look. If you do upload data,
please
> upload
> > > all
> > > > the files used and send me the command you are using to run
the code,
> > so
> > > > that I can try to reproduce the behavior.
> > > >
> > > > Also, what version of MET are you using?
> > > >
> > > > Thanks,
> > > > Julie
> > > >
> > > > On Thu, Jul 20, 2017 at 11:38 AM, Jacob Radford via RT <
> > > met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > >
> > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> > > > >
> > > > > Hi Julie,
> > > > >
> > > > > Thank you for the information. Let me explain a little bit
about
> what
> > > I'm
> > > > > trying to do:
> > > > >
> > > > > I originally had a geotiff that I converted to a NetCDF
using a
> > Python
> > > > > package. It's basically just a base reflectivity field with
a
> > > > corresponding
> > > > > LatLon grid. I'd like to be able to have this outputted
NetCDF read
> > by
> > > > > MODE. Originally, without setting any attributes, I received
an
> error
> > > > > stating that MODE was unable to read the NetCDF. I then
found this
> > link
> > > > > specifying the global grid attributes that are produced by
> > pcp_combine
> > > > for
> > > > > a LatLon grid:
> > > > >
> > > > > http://mailman.ucar.edu/pipermail/met_help/2014-
> February/002090.html
> > > > >
> > > > > I attempted to configure these attributes for my own file so
that
> my
> > > own
> > > > > global attributes look like so:
> > > > >
> > > > > :Projection = "LatLon" ;
> > > > > :lat_ll = "23.000000 degrees_north" ;
> > > > > :lon_ll = "126.000000 degrees_west" ;
> > > > > :delta_lat = "0.005000 degrees" ;
> > > > > :delta_lon = "0.005000 degrees" ;
> > > > > :Nlat = "5400 grid_points" ;
> > > > > :Nlon = "12200 grid_points" ;
> > > > >
> > > > > I had some success with this as I no longer received the
> "unreadable"
> > > > > error, but instead it gets to the step stating "Identifying
objects
> > in
> > > > > the forecast and observation fields..." after which the job
is
> killed
> > > > > without any further details. I attached a screenshot of
this.
> > > > >
> > > > > I can attach the NetCDF file I've produced if it would help,
but
> > > > > refrained from doing so as it's quite large due to the large
grid
> > > > > size.
> > > > >
> > > > > Any advice you could provide would be greatly appreciated!
> > > > >
> > > > > Best,
> > > > > Jacob Radford
> > > > >
> > > > >
> > > > > On Wed, Jul 19, 2017 at 2:43 PM, Julie Prestopnik via RT <
> > > > > met_help at ucar.edu>
> > > > > wrote:
> > > > >
> > > > > > Hi Jacob. I see that you are encountering a problem with
MODE
> > > reading
> > > > > your
> > > > > > NetCDF files.
> > > > > >
> > > > > > MET supports a few flavors of NetCDF...
> > > > > > - Gridded NetCDF files following the CF-convention
> > > > > > - Gridded NetCDF output of the WRF pinterp utility
> > > > > > - Internal MET formatted NetCDF file
> > > > > >
> > > > > > When you pass MET a NetCDF file, it inspects the file to
> determine
> > > it's
> > > > > > type. If it's not CF-compliant or a pinterp file, it
assumes
> it's
> > > the
> > > > > 3rd
> > > > > > type. The 3rd type is basically just the output of
pcp_combine
> > tool.
> > > > > >
> > > > > > I have attached a sample input file that is the output of
> > > pcp_combine,
> > > > so
> > > > > > that you can take a look.
> > > > > >
> > > > > > I hope this is helpful. Please let us know if you have
any other
> > > > > > questions.
> > > > > >
> > > > > > Julie
> > > > > >
> > > > > >
> > > > > > On Tue, Jul 18, 2017 at 6:56 PM, Jacob Radford via RT <
> > > > met_help at ucar.edu
> > > > > >
> > > > > > wrote:
> > > > > >
> > > > > > >
> > > > > > > Tue Jul 18 18:56:20 2017: Request 81265 was acted upon.
> > > > > > > Transaction: Ticket created by jtradfor at ncsu.edu
> > > > > > > Queue: met_help
> > > > > > > Subject: MODE NetCDF Attributes
> > > > > > > Owner: Nobody
> > > > > > > Requestors: jtradfor at ncsu.edu
> > > > > > > Status: new
> > > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > > > Ticket/Display.html?id=81265
> > > > > >
> > > > > > >
> > > > > > >
> > > > > > > Hello,
> > > > > > >
> > > > > > > I've just started using MODE and succeeded with the
sample
> data,
> > > but
> > > > > it's
> > > > > > > unable to read my own NetCDF files. I believe this is
because
> of
> > > > > > inadequate
> > > > > > > attribute data - could you tell me what attributes need
to be
> > > defined
> > > > > for
> > > > > > > MODE to read a NetCDF?
> > > > > > >
> > > > > > > Thank you!
> > > > > > > Jacob Radford
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: MODE NetCDF Attributes
From: Jacob Radford
Time: Tue Jul 25 11:56:53 2017
Hi Julie/John,
Thanks again for all your help. I thought of another quick question:
In the tutorial sample nc file for MODE these global attributes are
defined
scale_lat_1 = '25.000000'
scale_lat_2 = '25.000000'
lat_pin = '12.190000'
lon_pin = '-133.459000'
x_pin = '0.000000'
y_pin = '0.000000'
lon_orient = '-95.000000'
d_km = '40.635000'
r_km = '6371.200000'
nx = '185'
ny = '129 grid_points'
On Fri, Jul 21, 2017 at 2:43 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Jacob,
>
> This is John and I work with Julie on providing MET support. Julie
sent
> you an example of using the regrid_data_plane tool in MET to regrid
your
> data before processing it in MODE.
>
> You also have a second regridding option. Instead of calling
> regrid_data_plane first, you could pass your original data file to
MODE and
> use the "regrid" option in the MODE config file. That tells MODE to
do the
> regridding on the fly without writing an intermediate file.
>
> Either method will work and should result in identical output. It's
up to
> you to decide whether you want to write an intermediate regridded
NetCDF
> file.
>
> Here's the regrid setting you could try in the MODE config file:
>
> regrid = {
> to_grid = "latlon 610 270 23 126 0.1 0.1";
> method = BILIN;
> width = 2;
> vld_thresh = 0.5;
> }
>
> Hope that helps.
>
> Thanks,
> John
>
> On Fri, Jul 21, 2017 at 11:44 AM, Jacob Radford via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> >
> > Hi Julie,
> >
> > Thank you for all your help! I thought the grid density might be
an
> issue.
> > Interpolating to a coarser grid was ultimately the plan anyway.
> >
> > Best,
> > Jacob
> >
> > On Fri, Jul 21, 2017 at 1:05 PM, Julie Prestopnik via RT <
> > met_help at ucar.edu>
> > wrote:
> >
> > > Hi Jacob. Thank you for sending me the data and the command
line you
> are
> > > using. We can see that MET is working on your data, but
unfortunately
> it
> > > is not realistic to have MET run on such a dense grid. MODE was
> running
> > > extremely slowly due to the grid density.
> > >
> > > We regridded your data using the following command to a .1
degree grid:
> > >
> > > regrid_data_plane reflectivity.nc 'latlon 610 270 23 126 0.1
0.1'
> > > reflectivity_REGRID.nc -field 'name="Reflectivity";
level="(*,*)";'
> -name
> > > Reflectivity -method BILIN -width 2
> > >
> > > We also played around with your configuration file a bit and
made some
> > > changes. Using the new file, reflectivity_REGRID.nc with the new
> > > configuration file (attached), we were able to create reasonable
> looking
> > > objects.
> > >
> > > Please take a look and let us know if you have any questions.
> > >
> > > Thanks,
> > > Julie
> > >
> > > On Thu, Jul 20, 2017 at 11:33 PM, Jacob Radford via RT <
> > met_help at ucar.edu>
> > > wrote:
> > >
> > > >
> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265
>
> > > >
> > > > Hi Julie,
> > > >
> > > > I increased the verbosity as you suggested and it looks like
the
> > problem
> > > is
> > > > occurring at the convolution step. I uploaded my NetCDF (
> > reflectivity.nc
> > > )
> > > > and my MODE configuration file (MODEConfig_tutorial) following
the
> > > > conventions in the FTP instructions (under Radford_data). I
tried to
> > > change
> > > > as little as possible from the tutorial configuration, so I
mostly
> just
> > > > edited the forecast/observation field to read the information
from my
> > own
> > > > file. I'm also using the same file for the forecast and
observations
> > > > initially because I'm just getting familiar with MET and
trying to
> get
> > it
> > > > to read my data at this point.
> > > >
> > > > I'm running METv6.0 in Docker and the command I'm using is:
> > > >
> > > > > mode \
> > > > > tutorial/out/pcp_combine/reflectivity.nc \
> > > > > tutorial/out/pcp_combine/reflectivity.nc \
> > > > > tutorial/config/MODEConfig_tutorial \
> > > > > -outdir tutorial/out/mode \
> > > > > -v 9
> > > >
> > > > Let me know if there's any other information or files that you
need
> > from
> > > me
> > > > to look into this.
> > > >
> > > > Best,
> > > > Jacob
> > > >
> > > > On Thu, Jul 20, 2017 at 1:52 PM, Julie Prestopnik via RT <
> > > > met_help at ucar.edu>
> > > > wrote:
> > > >
> > > > > Hi Jacob. Thank you for providing more information. To get
more
> > > > > information about what is going on you could try running
MODE with
> a
> > > > higher
> > > > > verbosity level (e.g. -v 9). Also, please feel free to
upload your
> > > file
> > > > on
> > > > > our anonymous ftp site:
> > > > >
> > > > > http://www.dtcenter.org/met/users/support/met_help.php#ftp
> > > > >
> > > > > so that we can also take a look. If you do upload data,
please
> > upload
> > > > all
> > > > > the files used and send me the command you are using to run
the
> code,
> > > so
> > > > > that I can try to reproduce the behavior.
> > > > >
> > > > > Also, what version of MET are you using?
> > > > >
> > > > > Thanks,
> > > > > Julie
> > > > >
> > > > > On Thu, Jul 20, 2017 at 11:38 AM, Jacob Radford via RT <
> > > > met_help at ucar.edu>
> > > > > wrote:
> > > > >
> > > > > >
> > > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> > > > > >
> > > > > > Hi Julie,
> > > > > >
> > > > > > Thank you for the information. Let me explain a little bit
about
> > what
> > > > I'm
> > > > > > trying to do:
> > > > > >
> > > > > > I originally had a geotiff that I converted to a NetCDF
using a
> > > Python
> > > > > > package. It's basically just a base reflectivity field
with a
> > > > > corresponding
> > > > > > LatLon grid. I'd like to be able to have this outputted
NetCDF
> read
> > > by
> > > > > > MODE. Originally, without setting any attributes, I
received an
> > error
> > > > > > stating that MODE was unable to read the NetCDF. I then
found
> this
> > > link
> > > > > > specifying the global grid attributes that are produced by
> > > pcp_combine
> > > > > for
> > > > > > a LatLon grid:
> > > > > >
> > > > > > http://mailman.ucar.edu/pipermail/met_help/2014-
> > February/002090.html
> > > > > >
> > > > > > I attempted to configure these attributes for my own file
so that
> > my
> > > > own
> > > > > > global attributes look like so:
> > > > > >
> > > > > > :Projection = "LatLon" ;
> > > > > > :lat_ll = "23.000000 degrees_north" ;
> > > > > > :lon_ll = "126.000000 degrees_west" ;
> > > > > > :delta_lat = "0.005000 degrees" ;
> > > > > > :delta_lon = "0.005000 degrees" ;
> > > > > > :Nlat = "5400 grid_points" ;
> > > > > > :Nlon = "12200 grid_points" ;
> > > > > >
> > > > > > I had some success with this as I no longer received the
> > "unreadable"
> > > > > > error, but instead it gets to the step stating
"Identifying
> objects
> > > in
> > > > > > the forecast and observation fields..." after which the
job is
> > killed
> > > > > > without any further details. I attached a screenshot of
this.
> > > > > >
> > > > > > I can attach the NetCDF file I've produced if it would
help, but
> > > > > > refrained from doing so as it's quite large due to the
large grid
> > > > > > size.
> > > > > >
> > > > > > Any advice you could provide would be greatly appreciated!
> > > > > >
> > > > > > Best,
> > > > > > Jacob Radford
> > > > > >
> > > > > >
> > > > > > On Wed, Jul 19, 2017 at 2:43 PM, Julie Prestopnik via RT <
> > > > > > met_help at ucar.edu>
> > > > > > wrote:
> > > > > >
> > > > > > > Hi Jacob. I see that you are encountering a problem
with MODE
> > > > reading
> > > > > > your
> > > > > > > NetCDF files.
> > > > > > >
> > > > > > > MET supports a few flavors of NetCDF...
> > > > > > > - Gridded NetCDF files following the CF-convention
> > > > > > > - Gridded NetCDF output of the WRF pinterp utility
> > > > > > > - Internal MET formatted NetCDF file
> > > > > > >
> > > > > > > When you pass MET a NetCDF file, it inspects the file to
> > determine
> > > > it's
> > > > > > > type. If it's not CF-compliant or a pinterp file, it
assumes
> > it's
> > > > the
> > > > > > 3rd
> > > > > > > type. The 3rd type is basically just the output of
pcp_combine
> > > tool.
> > > > > > >
> > > > > > > I have attached a sample input file that is the output
of
> > > > pcp_combine,
> > > > > so
> > > > > > > that you can take a look.
> > > > > > >
> > > > > > > I hope this is helpful. Please let us know if you have
any
> other
> > > > > > > questions.
> > > > > > >
> > > > > > > Julie
> > > > > > >
> > > > > > >
> > > > > > > On Tue, Jul 18, 2017 at 6:56 PM, Jacob Radford via RT <
> > > > > met_help at ucar.edu
> > > > > > >
> > > > > > > wrote:
> > > > > > >
> > > > > > > >
> > > > > > > > Tue Jul 18 18:56:20 2017: Request 81265 was acted
upon.
> > > > > > > > Transaction: Ticket created by jtradfor at ncsu.edu
> > > > > > > > Queue: met_help
> > > > > > > > Subject: MODE NetCDF Attributes
> > > > > > > > Owner: Nobody
> > > > > > > > Requestors: jtradfor at ncsu.edu
> > > > > > > > Status: new
> > > > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > > > > Ticket/Display.html?id=81265
> > > > > > >
> > > > > > > >
> > > > > > > >
> > > > > > > > Hello,
> > > > > > > >
> > > > > > > > I've just started using MODE and succeeded with the
sample
> > data,
> > > > but
> > > > > > it's
> > > > > > > > unable to read my own NetCDF files. I believe this is
because
> > of
> > > > > > > inadequate
> > > > > > > > attribute data - could you tell me what attributes
need to be
> > > > defined
> > > > > > for
> > > > > > > > MODE to read a NetCDF?
> > > > > > > >
> > > > > > > > Thank you!
> > > > > > > > Jacob Radford
> > > > > > > >
> > > > > > > >
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > >
> > >
> >
> >
>
>
------------------------------------------------
Subject: MODE NetCDF Attributes
From: Jacob Radford
Time: Tue Jul 25 11:58:09 2017
Oops, sent that on accident without finishing the email - but what I
was
wondering is what the scale_lat_1, scale_lat_2 and lon_orient
attributes
mean.
Best,
Jacob
On Tue, Jul 25, 2017 at 1:56 PM, Jacob Radford <jtradfor at ncsu.edu>
wrote:
> Hi Julie/John,
>
> Thanks again for all your help. I thought of another quick question:
>
> In the tutorial sample nc file for MODE these global attributes are
defined
>
> scale_lat_1 = '25.000000'
> scale_lat_2 = '25.000000'
> lat_pin = '12.190000'
> lon_pin = '-133.459000'
> x_pin = '0.000000'
> y_pin = '0.000000'
> lon_orient = '-95.000000'
> d_km = '40.635000'
> r_km = '6371.200000'
> nx = '185'
> ny = '129 grid_points'
>
> On Fri, Jul 21, 2017 at 2:43 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Jacob,
>>
>> This is John and I work with Julie on providing MET support. Julie
sent
>> you an example of using the regrid_data_plane tool in MET to regrid
your
>> data before processing it in MODE.
>>
>> You also have a second regridding option. Instead of calling
>> regrid_data_plane first, you could pass your original data file to
MODE
>> and
>> use the "regrid" option in the MODE config file. That tells MODE
to do
>> the
>> regridding on the fly without writing an intermediate file.
>>
>> Either method will work and should result in identical output.
It's up to
>> you to decide whether you want to write an intermediate regridded
NetCDF
>> file.
>>
>> Here's the regrid setting you could try in the MODE config file:
>>
>> regrid = {
>> to_grid = "latlon 610 270 23 126 0.1 0.1";
>> method = BILIN;
>> width = 2;
>> vld_thresh = 0.5;
>> }
>>
>> Hope that helps.
>>
>> Thanks,
>> John
>>
>> On Fri, Jul 21, 2017 at 11:44 AM, Jacob Radford via RT
<met_help at ucar.edu
>> >
>> wrote:
>>
>> >
>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
>> >
>> > Hi Julie,
>> >
>> > Thank you for all your help! I thought the grid density might be
an
>> issue.
>> > Interpolating to a coarser grid was ultimately the plan anyway.
>> >
>> > Best,
>> > Jacob
>> >
>> > On Fri, Jul 21, 2017 at 1:05 PM, Julie Prestopnik via RT <
>> > met_help at ucar.edu>
>> > wrote:
>> >
>> > > Hi Jacob. Thank you for sending me the data and the command
line you
>> are
>> > > using. We can see that MET is working on your data, but
>> unfortunately it
>> > > is not realistic to have MET run on such a dense grid. MODE
was
>> running
>> > > extremely slowly due to the grid density.
>> > >
>> > > We regridded your data using the following command to a .1
degree
>> grid:
>> > >
>> > > regrid_data_plane reflectivity.nc 'latlon 610 270 23 126 0.1
0.1'
>> > > reflectivity_REGRID.nc -field 'name="Reflectivity";
level="(*,*)";'
>> -name
>> > > Reflectivity -method BILIN -width 2
>> > >
>> > > We also played around with your configuration file a bit and
made some
>> > > changes. Using the new file, reflectivity_REGRID.nc with the
new
>> > > configuration file (attached), we were able to create
reasonable
>> looking
>> > > objects.
>> > >
>> > > Please take a look and let us know if you have any questions.
>> > >
>> > > Thanks,
>> > > Julie
>> > >
>> > > On Thu, Jul 20, 2017 at 11:33 PM, Jacob Radford via RT <
>> > met_help at ucar.edu>
>> > > wrote:
>> > >
>> > > >
>> > > > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265
>
>> > > >
>> > > > Hi Julie,
>> > > >
>> > > > I increased the verbosity as you suggested and it looks like
the
>> > problem
>> > > is
>> > > > occurring at the convolution step. I uploaded my NetCDF (
>> > reflectivity.nc
>> > > )
>> > > > and my MODE configuration file (MODEConfig_tutorial)
following the
>> > > > conventions in the FTP instructions (under Radford_data). I
tried to
>> > > change
>> > > > as little as possible from the tutorial configuration, so I
mostly
>> just
>> > > > edited the forecast/observation field to read the information
from
>> my
>> > own
>> > > > file. I'm also using the same file for the forecast and
observations
>> > > > initially because I'm just getting familiar with MET and
trying to
>> get
>> > it
>> > > > to read my data at this point.
>> > > >
>> > > > I'm running METv6.0 in Docker and the command I'm using is:
>> > > >
>> > > > > mode \
>> > > > > tutorial/out/pcp_combine/reflectivity.nc \
>> > > > > tutorial/out/pcp_combine/reflectivity.nc \
>> > > > > tutorial/config/MODEConfig_tutorial \
>> > > > > -outdir tutorial/out/mode \
>> > > > > -v 9
>> > > >
>> > > > Let me know if there's any other information or files that
you need
>> > from
>> > > me
>> > > > to look into this.
>> > > >
>> > > > Best,
>> > > > Jacob
>> > > >
>> > > > On Thu, Jul 20, 2017 at 1:52 PM, Julie Prestopnik via RT <
>> > > > met_help at ucar.edu>
>> > > > wrote:
>> > > >
>> > > > > Hi Jacob. Thank you for providing more information. To
get more
>> > > > > information about what is going on you could try running
MODE
>> with a
>> > > > higher
>> > > > > verbosity level (e.g. -v 9). Also, please feel free to
upload
>> your
>> > > file
>> > > > on
>> > > > > our anonymous ftp site:
>> > > > >
>> > > > > http://www.dtcenter.org/met/users/support/met_help.php#ftp
>> > > > >
>> > > > > so that we can also take a look. If you do upload data,
please
>> > upload
>> > > > all
>> > > > > the files used and send me the command you are using to run
the
>> code,
>> > > so
>> > > > > that I can try to reproduce the behavior.
>> > > > >
>> > > > > Also, what version of MET are you using?
>> > > > >
>> > > > > Thanks,
>> > > > > Julie
>> > > > >
>> > > > > On Thu, Jul 20, 2017 at 11:38 AM, Jacob Radford via RT <
>> > > > met_help at ucar.edu>
>> > > > > wrote:
>> > > > >
>> > > > > >
>> > > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
>> > > > > >
>> > > > > > Hi Julie,
>> > > > > >
>> > > > > > Thank you for the information. Let me explain a little
bit about
>> > what
>> > > > I'm
>> > > > > > trying to do:
>> > > > > >
>> > > > > > I originally had a geotiff that I converted to a NetCDF
using a
>> > > Python
>> > > > > > package. It's basically just a base reflectivity field
with a
>> > > > > corresponding
>> > > > > > LatLon grid. I'd like to be able to have this outputted
NetCDF
>> read
>> > > by
>> > > > > > MODE. Originally, without setting any attributes, I
received an
>> > error
>> > > > > > stating that MODE was unable to read the NetCDF. I then
found
>> this
>> > > link
>> > > > > > specifying the global grid attributes that are produced
by
>> > > pcp_combine
>> > > > > for
>> > > > > > a LatLon grid:
>> > > > > >
>> > > > > > http://mailman.ucar.edu/pipermail/met_help/2014-
>> > February/002090.html
>> > > > > >
>> > > > > > I attempted to configure these attributes for my own file
so
>> that
>> > my
>> > > > own
>> > > > > > global attributes look like so:
>> > > > > >
>> > > > > > :Projection = "LatLon" ;
>> > > > > > :lat_ll = "23.000000 degrees_north" ;
>> > > > > > :lon_ll = "126.000000 degrees_west" ;
>> > > > > > :delta_lat = "0.005000 degrees" ;
>> > > > > > :delta_lon = "0.005000 degrees" ;
>> > > > > > :Nlat = "5400 grid_points" ;
>> > > > > > :Nlon = "12200 grid_points" ;
>> > > > > >
>> > > > > > I had some success with this as I no longer received the
>> > "unreadable"
>> > > > > > error, but instead it gets to the step stating
"Identifying
>> objects
>> > > in
>> > > > > > the forecast and observation fields..." after which the
job is
>> > killed
>> > > > > > without any further details. I attached a screenshot of
this.
>> > > > > >
>> > > > > > I can attach the NetCDF file I've produced if it would
help, but
>> > > > > > refrained from doing so as it's quite large due to the
large
>> grid
>> > > > > > size.
>> > > > > >
>> > > > > > Any advice you could provide would be greatly
appreciated!
>> > > > > >
>> > > > > > Best,
>> > > > > > Jacob Radford
>> > > > > >
>> > > > > >
>> > > > > > On Wed, Jul 19, 2017 at 2:43 PM, Julie Prestopnik via RT
<
>> > > > > > met_help at ucar.edu>
>> > > > > > wrote:
>> > > > > >
>> > > > > > > Hi Jacob. I see that you are encountering a problem
with MODE
>> > > > reading
>> > > > > > your
>> > > > > > > NetCDF files.
>> > > > > > >
>> > > > > > > MET supports a few flavors of NetCDF...
>> > > > > > > - Gridded NetCDF files following the CF-convention
>> > > > > > > - Gridded NetCDF output of the WRF pinterp utility
>> > > > > > > - Internal MET formatted NetCDF file
>> > > > > > >
>> > > > > > > When you pass MET a NetCDF file, it inspects the file
to
>> > determine
>> > > > it's
>> > > > > > > type. If it's not CF-compliant or a pinterp file, it
assumes
>> > it's
>> > > > the
>> > > > > > 3rd
>> > > > > > > type. The 3rd type is basically just the output of
>> pcp_combine
>> > > tool.
>> > > > > > >
>> > > > > > > I have attached a sample input file that is the output
of
>> > > > pcp_combine,
>> > > > > so
>> > > > > > > that you can take a look.
>> > > > > > >
>> > > > > > > I hope this is helpful. Please let us know if you have
any
>> other
>> > > > > > > questions.
>> > > > > > >
>> > > > > > > Julie
>> > > > > > >
>> > > > > > >
>> > > > > > > On Tue, Jul 18, 2017 at 6:56 PM, Jacob Radford via RT <
>> > > > > met_help at ucar.edu
>> > > > > > >
>> > > > > > > wrote:
>> > > > > > >
>> > > > > > > >
>> > > > > > > > Tue Jul 18 18:56:20 2017: Request 81265 was acted
upon.
>> > > > > > > > Transaction: Ticket created by jtradfor at ncsu.edu
>> > > > > > > > Queue: met_help
>> > > > > > > > Subject: MODE NetCDF Attributes
>> > > > > > > > Owner: Nobody
>> > > > > > > > Requestors: jtradfor at ncsu.edu
>> > > > > > > > Status: new
>> > > > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
>> > > > > Ticket/Display.html?id=81265
>> > > > > > >
>> > > > > > > >
>> > > > > > > >
>> > > > > > > > Hello,
>> > > > > > > >
>> > > > > > > > I've just started using MODE and succeeded with the
sample
>> > data,
>> > > > but
>> > > > > > it's
>> > > > > > > > unable to read my own NetCDF files. I believe this is
>> because
>> > of
>> > > > > > > inadequate
>> > > > > > > > attribute data - could you tell me what attributes
need to
>> be
>> > > > defined
>> > > > > > for
>> > > > > > > > MODE to read a NetCDF?
>> > > > > > > >
>> > > > > > > > Thank you!
>> > > > > > > > Jacob Radford
>> > > > > > > >
>> > > > > > > >
>> > > > > > >
>> > > > > > >
>> > > > > >
>> > > > > >
>> > > > >
>> > > > >
>> > > >
>> > > >
>> > >
>> > >
>> >
>> >
>>
>>
>
------------------------------------------------
Subject: MODE NetCDF Attributes
From: John Halley Gotway
Time: Tue Jul 25 12:40:03 2017
Jacob,
These are attributes used when defining a lambert conformal
projection.
The lon_orient is also sometime called the center longitude. The two
scale
latitudes are often set to the same value but not have to be.
I don't know enough about grid projections to give you a complete
explanation, but suffice it to say, that MET parses these values when
instantiating the grid.
John
On Tue, Jul 25, 2017 at 11:58 AM, Jacob Radford via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
>
> Oops, sent that on accident without finishing the email - but what I
was
> wondering is what the scale_lat_1, scale_lat_2 and lon_orient
attributes
> mean.
>
> Best,
> Jacob
>
> On Tue, Jul 25, 2017 at 1:56 PM, Jacob Radford <jtradfor at ncsu.edu>
wrote:
>
> > Hi Julie/John,
> >
> > Thanks again for all your help. I thought of another quick
question:
> >
> > In the tutorial sample nc file for MODE these global attributes
are
> defined
> >
> > scale_lat_1 = '25.000000'
> > scale_lat_2 = '25.000000'
> > lat_pin = '12.190000'
> > lon_pin = '-133.459000'
> > x_pin = '0.000000'
> > y_pin = '0.000000'
> > lon_orient = '-95.000000'
> > d_km = '40.635000'
> > r_km = '6371.200000'
> > nx = '185'
> > ny = '129 grid_points'
> >
> > On Fri, Jul 21, 2017 at 2:43 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Jacob,
> >>
> >> This is John and I work with Julie on providing MET support.
Julie sent
> >> you an example of using the regrid_data_plane tool in MET to
regrid your
> >> data before processing it in MODE.
> >>
> >> You also have a second regridding option. Instead of calling
> >> regrid_data_plane first, you could pass your original data file
to MODE
> >> and
> >> use the "regrid" option in the MODE config file. That tells MODE
to do
> >> the
> >> regridding on the fly without writing an intermediate file.
> >>
> >> Either method will work and should result in identical output.
It's up
> to
> >> you to decide whether you want to write an intermediate regridded
NetCDF
> >> file.
> >>
> >> Here's the regrid setting you could try in the MODE config file:
> >>
> >> regrid = {
> >> to_grid = "latlon 610 270 23 126 0.1 0.1";
> >> method = BILIN;
> >> width = 2;
> >> vld_thresh = 0.5;
> >> }
> >>
> >> Hope that helps.
> >>
> >> Thanks,
> >> John
> >>
> >> On Fri, Jul 21, 2017 at 11:44 AM, Jacob Radford via RT <
> met_help at ucar.edu
> >> >
> >> wrote:
> >>
> >> >
> >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> >> >
> >> > Hi Julie,
> >> >
> >> > Thank you for all your help! I thought the grid density might
be an
> >> issue.
> >> > Interpolating to a coarser grid was ultimately the plan anyway.
> >> >
> >> > Best,
> >> > Jacob
> >> >
> >> > On Fri, Jul 21, 2017 at 1:05 PM, Julie Prestopnik via RT <
> >> > met_help at ucar.edu>
> >> > wrote:
> >> >
> >> > > Hi Jacob. Thank you for sending me the data and the command
line
> you
> >> are
> >> > > using. We can see that MET is working on your data, but
> >> unfortunately it
> >> > > is not realistic to have MET run on such a dense grid. MODE
was
> >> running
> >> > > extremely slowly due to the grid density.
> >> > >
> >> > > We regridded your data using the following command to a .1
degree
> >> grid:
> >> > >
> >> > > regrid_data_plane reflectivity.nc 'latlon 610 270 23 126 0.1
0.1'
> >> > > reflectivity_REGRID.nc -field 'name="Reflectivity";
level="(*,*)";'
> >> -name
> >> > > Reflectivity -method BILIN -width 2
> >> > >
> >> > > We also played around with your configuration file a bit and
made
> some
> >> > > changes. Using the new file, reflectivity_REGRID.nc with the
new
> >> > > configuration file (attached), we were able to create
reasonable
> >> looking
> >> > > objects.
> >> > >
> >> > > Please take a look and let us know if you have any questions.
> >> > >
> >> > > Thanks,
> >> > > Julie
> >> > >
> >> > > On Thu, Jul 20, 2017 at 11:33 PM, Jacob Radford via RT <
> >> > met_help at ucar.edu>
> >> > > wrote:
> >> > >
> >> > > >
> >> > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> >> > > >
> >> > > > Hi Julie,
> >> > > >
> >> > > > I increased the verbosity as you suggested and it looks
like the
> >> > problem
> >> > > is
> >> > > > occurring at the convolution step. I uploaded my NetCDF (
> >> > reflectivity.nc
> >> > > )
> >> > > > and my MODE configuration file (MODEConfig_tutorial)
following the
> >> > > > conventions in the FTP instructions (under Radford_data). I
tried
> to
> >> > > change
> >> > > > as little as possible from the tutorial configuration, so I
mostly
> >> just
> >> > > > edited the forecast/observation field to read the
information from
> >> my
> >> > own
> >> > > > file. I'm also using the same file for the forecast and
> observations
> >> > > > initially because I'm just getting familiar with MET and
trying to
> >> get
> >> > it
> >> > > > to read my data at this point.
> >> > > >
> >> > > > I'm running METv6.0 in Docker and the command I'm using is:
> >> > > >
> >> > > > > mode \
> >> > > > > tutorial/out/pcp_combine/reflectivity.nc \
> >> > > > > tutorial/out/pcp_combine/reflectivity.nc \
> >> > > > > tutorial/config/MODEConfig_tutorial \
> >> > > > > -outdir tutorial/out/mode \
> >> > > > > -v 9
> >> > > >
> >> > > > Let me know if there's any other information or files that
you
> need
> >> > from
> >> > > me
> >> > > > to look into this.
> >> > > >
> >> > > > Best,
> >> > > > Jacob
> >> > > >
> >> > > > On Thu, Jul 20, 2017 at 1:52 PM, Julie Prestopnik via RT <
> >> > > > met_help at ucar.edu>
> >> > > > wrote:
> >> > > >
> >> > > > > Hi Jacob. Thank you for providing more information. To
get
> more
> >> > > > > information about what is going on you could try running
MODE
> >> with a
> >> > > > higher
> >> > > > > verbosity level (e.g. -v 9). Also, please feel free to
upload
> >> your
> >> > > file
> >> > > > on
> >> > > > > our anonymous ftp site:
> >> > > > >
> >> > > > >
http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >> > > > >
> >> > > > > so that we can also take a look. If you do upload data,
please
> >> > upload
> >> > > > all
> >> > > > > the files used and send me the command you are using to
run the
> >> code,
> >> > > so
> >> > > > > that I can try to reproduce the behavior.
> >> > > > >
> >> > > > > Also, what version of MET are you using?
> >> > > > >
> >> > > > > Thanks,
> >> > > > > Julie
> >> > > > >
> >> > > > > On Thu, Jul 20, 2017 at 11:38 AM, Jacob Radford via RT <
> >> > > > met_help at ucar.edu>
> >> > > > > wrote:
> >> > > > >
> >> > > > > >
> >> > > > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265
> >
> >> > > > > >
> >> > > > > > Hi Julie,
> >> > > > > >
> >> > > > > > Thank you for the information. Let me explain a little
bit
> about
> >> > what
> >> > > > I'm
> >> > > > > > trying to do:
> >> > > > > >
> >> > > > > > I originally had a geotiff that I converted to a NetCDF
using
> a
> >> > > Python
> >> > > > > > package. It's basically just a base reflectivity field
with a
> >> > > > > corresponding
> >> > > > > > LatLon grid. I'd like to be able to have this outputted
NetCDF
> >> read
> >> > > by
> >> > > > > > MODE. Originally, without setting any attributes, I
received
> an
> >> > error
> >> > > > > > stating that MODE was unable to read the NetCDF. I then
found
> >> this
> >> > > link
> >> > > > > > specifying the global grid attributes that are produced
by
> >> > > pcp_combine
> >> > > > > for
> >> > > > > > a LatLon grid:
> >> > > > > >
> >> > > > > > http://mailman.ucar.edu/pipermail/met_help/2014-
> >> > February/002090.html
> >> > > > > >
> >> > > > > > I attempted to configure these attributes for my own
file so
> >> that
> >> > my
> >> > > > own
> >> > > > > > global attributes look like so:
> >> > > > > >
> >> > > > > > :Projection = "LatLon" ;
> >> > > > > > :lat_ll = "23.000000 degrees_north" ;
> >> > > > > > :lon_ll = "126.000000 degrees_west" ;
> >> > > > > > :delta_lat = "0.005000 degrees" ;
> >> > > > > > :delta_lon = "0.005000 degrees" ;
> >> > > > > > :Nlat = "5400 grid_points" ;
> >> > > > > > :Nlon = "12200 grid_points" ;
> >> > > > > >
> >> > > > > > I had some success with this as I no longer received
the
> >> > "unreadable"
> >> > > > > > error, but instead it gets to the step stating
"Identifying
> >> objects
> >> > > in
> >> > > > > > the forecast and observation fields..." after which the
job is
> >> > killed
> >> > > > > > without any further details. I attached a screenshot of
this.
> >> > > > > >
> >> > > > > > I can attach the NetCDF file I've produced if it would
help,
> but
> >> > > > > > refrained from doing so as it's quite large due to the
large
> >> grid
> >> > > > > > size.
> >> > > > > >
> >> > > > > > Any advice you could provide would be greatly
appreciated!
> >> > > > > >
> >> > > > > > Best,
> >> > > > > > Jacob Radford
> >> > > > > >
> >> > > > > >
> >> > > > > > On Wed, Jul 19, 2017 at 2:43 PM, Julie Prestopnik via
RT <
> >> > > > > > met_help at ucar.edu>
> >> > > > > > wrote:
> >> > > > > >
> >> > > > > > > Hi Jacob. I see that you are encountering a problem
with
> MODE
> >> > > > reading
> >> > > > > > your
> >> > > > > > > NetCDF files.
> >> > > > > > >
> >> > > > > > > MET supports a few flavors of NetCDF...
> >> > > > > > > - Gridded NetCDF files following the CF-convention
> >> > > > > > > - Gridded NetCDF output of the WRF pinterp utility
> >> > > > > > > - Internal MET formatted NetCDF file
> >> > > > > > >
> >> > > > > > > When you pass MET a NetCDF file, it inspects the file
to
> >> > determine
> >> > > > it's
> >> > > > > > > type. If it's not CF-compliant or a pinterp file, it
> assumes
> >> > it's
> >> > > > the
> >> > > > > > 3rd
> >> > > > > > > type. The 3rd type is basically just the output of
> >> pcp_combine
> >> > > tool.
> >> > > > > > >
> >> > > > > > > I have attached a sample input file that is the
output of
> >> > > > pcp_combine,
> >> > > > > so
> >> > > > > > > that you can take a look.
> >> > > > > > >
> >> > > > > > > I hope this is helpful. Please let us know if you
have any
> >> other
> >> > > > > > > questions.
> >> > > > > > >
> >> > > > > > > Julie
> >> > > > > > >
> >> > > > > > >
> >> > > > > > > On Tue, Jul 18, 2017 at 6:56 PM, Jacob Radford via RT
<
> >> > > > > met_help at ucar.edu
> >> > > > > > >
> >> > > > > > > wrote:
> >> > > > > > >
> >> > > > > > > >
> >> > > > > > > > Tue Jul 18 18:56:20 2017: Request 81265 was acted
upon.
> >> > > > > > > > Transaction: Ticket created by jtradfor at ncsu.edu
> >> > > > > > > > Queue: met_help
> >> > > > > > > > Subject: MODE NetCDF Attributes
> >> > > > > > > > Owner: Nobody
> >> > > > > > > > Requestors: jtradfor at ncsu.edu
> >> > > > > > > > Status: new
> >> > > > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> >> > > > > Ticket/Display.html?id=81265
> >> > > > > > >
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > > > Hello,
> >> > > > > > > >
> >> > > > > > > > I've just started using MODE and succeeded with the
sample
> >> > data,
> >> > > > but
> >> > > > > > it's
> >> > > > > > > > unable to read my own NetCDF files. I believe this
is
> >> because
> >> > of
> >> > > > > > > inadequate
> >> > > > > > > > attribute data - could you tell me what attributes
need to
> >> be
> >> > > > defined
> >> > > > > > for
> >> > > > > > > > MODE to read a NetCDF?
> >> > > > > > > >
> >> > > > > > > > Thank you!
> >> > > > > > > > Jacob Radford
> >> > > > > > > >
> >> > > > > > > >
> >> > > > > > >
> >> > > > > > >
> >> > > > > >
> >> > > > > >
> >> > > > >
> >> > > > >
> >> > > >
> >> > > >
> >> > >
> >> > >
> >> >
> >> >
> >>
> >>
> >
>
>
------------------------------------------------
Subject: MODE NetCDF Attributes
From: Jacob Radford
Time: Mon Jul 31 12:17:50 2017
Thanks, John.
I have one more question (for now...):
I'm trying to use MODE for a new file I created but am getting an
error
stating "MetNcFile::data(NcVar *, const LongArray &, DataPlane &)
const -> star
found in bad slot"
The command I'm using is:
> mode \
> tutorial/out/pcp_combine/201703141300.nc \
> tutorial/out/pcp_combine/201703141300.nc \
> tutorial/config/MODEConfig_tutorial \
> -outdir tutorial/out/mode \
> -v 2
What does this mean? I uploaded the netcdf file and my config file to
the
FTP site (named "201703141300.nc" under directory /Radford) if you
want to
try it yourself.
Thank you!
Jacob Radford
On Tue, Jul 25, 2017 at 2:40 PM, John Halley Gotway via RT <
met_help at ucar.edu> wrote:
> Jacob,
>
> These are attributes used when defining a lambert conformal
projection.
> The lon_orient is also sometime called the center longitude. The
two scale
> latitudes are often set to the same value but not have to be.
>
> I don't know enough about grid projections to give you a complete
> explanation, but suffice it to say, that MET parses these values
when
> instantiating the grid.
>
> John
>
> On Tue, Jul 25, 2017 at 11:58 AM, Jacob Radford via RT
<met_help at ucar.edu>
> wrote:
>
> >
> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> >
> > Oops, sent that on accident without finishing the email - but what
I was
> > wondering is what the scale_lat_1, scale_lat_2 and lon_orient
attributes
> > mean.
> >
> > Best,
> > Jacob
> >
> > On Tue, Jul 25, 2017 at 1:56 PM, Jacob Radford <jtradfor at ncsu.edu>
> wrote:
> >
> > > Hi Julie/John,
> > >
> > > Thanks again for all your help. I thought of another quick
question:
> > >
> > > In the tutorial sample nc file for MODE these global attributes
are
> > defined
> > >
> > > scale_lat_1 = '25.000000'
> > > scale_lat_2 = '25.000000'
> > > lat_pin = '12.190000'
> > > lon_pin = '-133.459000'
> > > x_pin = '0.000000'
> > > y_pin = '0.000000'
> > > lon_orient = '-95.000000'
> > > d_km = '40.635000'
> > > r_km = '6371.200000'
> > > nx = '185'
> > > ny = '129 grid_points'
> > >
> > > On Fri, Jul 21, 2017 at 2:43 PM, John Halley Gotway via RT <
> > > met_help at ucar.edu> wrote:
> > >
> > >> Jacob,
> > >>
> > >> This is John and I work with Julie on providing MET support.
Julie
> sent
> > >> you an example of using the regrid_data_plane tool in MET to
regrid
> your
> > >> data before processing it in MODE.
> > >>
> > >> You also have a second regridding option. Instead of calling
> > >> regrid_data_plane first, you could pass your original data file
to
> MODE
> > >> and
> > >> use the "regrid" option in the MODE config file. That tells
MODE to
> do
> > >> the
> > >> regridding on the fly without writing an intermediate file.
> > >>
> > >> Either method will work and should result in identical output.
It's
> up
> > to
> > >> you to decide whether you want to write an intermediate
regridded
> NetCDF
> > >> file.
> > >>
> > >> Here's the regrid setting you could try in the MODE config
file:
> > >>
> > >> regrid = {
> > >> to_grid = "latlon 610 270 23 126 0.1 0.1";
> > >> method = BILIN;
> > >> width = 2;
> > >> vld_thresh = 0.5;
> > >> }
> > >>
> > >> Hope that helps.
> > >>
> > >> Thanks,
> > >> John
> > >>
> > >> On Fri, Jul 21, 2017 at 11:44 AM, Jacob Radford via RT <
> > met_help at ucar.edu
> > >> >
> > >> wrote:
> > >>
> > >> >
> > >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265
>
> > >> >
> > >> > Hi Julie,
> > >> >
> > >> > Thank you for all your help! I thought the grid density might
be an
> > >> issue.
> > >> > Interpolating to a coarser grid was ultimately the plan
anyway.
> > >> >
> > >> > Best,
> > >> > Jacob
> > >> >
> > >> > On Fri, Jul 21, 2017 at 1:05 PM, Julie Prestopnik via RT <
> > >> > met_help at ucar.edu>
> > >> > wrote:
> > >> >
> > >> > > Hi Jacob. Thank you for sending me the data and the
command line
> > you
> > >> are
> > >> > > using. We can see that MET is working on your data, but
> > >> unfortunately it
> > >> > > is not realistic to have MET run on such a dense grid.
MODE was
> > >> running
> > >> > > extremely slowly due to the grid density.
> > >> > >
> > >> > > We regridded your data using the following command to a .1
degree
> > >> grid:
> > >> > >
> > >> > > regrid_data_plane reflectivity.nc 'latlon 610 270 23 126
0.1 0.1'
> > >> > > reflectivity_REGRID.nc -field 'name="Reflectivity";
> level="(*,*)";'
> > >> -name
> > >> > > Reflectivity -method BILIN -width 2
> > >> > >
> > >> > > We also played around with your configuration file a bit
and made
> > some
> > >> > > changes. Using the new file, reflectivity_REGRID.nc with
the new
> > >> > > configuration file (attached), we were able to create
reasonable
> > >> looking
> > >> > > objects.
> > >> > >
> > >> > > Please take a look and let us know if you have any
questions.
> > >> > >
> > >> > > Thanks,
> > >> > > Julie
> > >> > >
> > >> > > On Thu, Jul 20, 2017 at 11:33 PM, Jacob Radford via RT <
> > >> > met_help at ucar.edu>
> > >> > > wrote:
> > >> > >
> > >> > > >
> > >> > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> > >> > > >
> > >> > > > Hi Julie,
> > >> > > >
> > >> > > > I increased the verbosity as you suggested and it looks
like the
> > >> > problem
> > >> > > is
> > >> > > > occurring at the convolution step. I uploaded my NetCDF (
> > >> > reflectivity.nc
> > >> > > )
> > >> > > > and my MODE configuration file (MODEConfig_tutorial)
following
> the
> > >> > > > conventions in the FTP instructions (under Radford_data).
I
> tried
> > to
> > >> > > change
> > >> > > > as little as possible from the tutorial configuration, so
I
> mostly
> > >> just
> > >> > > > edited the forecast/observation field to read the
information
> from
> > >> my
> > >> > own
> > >> > > > file. I'm also using the same file for the forecast and
> > observations
> > >> > > > initially because I'm just getting familiar with MET and
trying
> to
> > >> get
> > >> > it
> > >> > > > to read my data at this point.
> > >> > > >
> > >> > > > I'm running METv6.0 in Docker and the command I'm using
is:
> > >> > > >
> > >> > > > > mode \
> > >> > > > > tutorial/out/pcp_combine/reflectivity.nc \
> > >> > > > > tutorial/out/pcp_combine/reflectivity.nc \
> > >> > > > > tutorial/config/MODEConfig_tutorial \
> > >> > > > > -outdir tutorial/out/mode \
> > >> > > > > -v 9
> > >> > > >
> > >> > > > Let me know if there's any other information or files
that you
> > need
> > >> > from
> > >> > > me
> > >> > > > to look into this.
> > >> > > >
> > >> > > > Best,
> > >> > > > Jacob
> > >> > > >
> > >> > > > On Thu, Jul 20, 2017 at 1:52 PM, Julie Prestopnik via RT
<
> > >> > > > met_help at ucar.edu>
> > >> > > > wrote:
> > >> > > >
> > >> > > > > Hi Jacob. Thank you for providing more information.
To get
> > more
> > >> > > > > information about what is going on you could try
running MODE
> > >> with a
> > >> > > > higher
> > >> > > > > verbosity level (e.g. -v 9). Also, please feel free to
upload
> > >> your
> > >> > > file
> > >> > > > on
> > >> > > > > our anonymous ftp site:
> > >> > > > >
> > >> > > > >
http://www.dtcenter.org/met/users/support/met_help.php#ftp
> > >> > > > >
> > >> > > > > so that we can also take a look. If you do upload
data,
> please
> > >> > upload
> > >> > > > all
> > >> > > > > the files used and send me the command you are using to
run
> the
> > >> code,
> > >> > > so
> > >> > > > > that I can try to reproduce the behavior.
> > >> > > > >
> > >> > > > > Also, what version of MET are you using?
> > >> > > > >
> > >> > > > > Thanks,
> > >> > > > > Julie
> > >> > > > >
> > >> > > > > On Thu, Jul 20, 2017 at 11:38 AM, Jacob Radford via RT
<
> > >> > > > met_help at ucar.edu>
> > >> > > > > wrote:
> > >> > > > >
> > >> > > > > >
> > >> > > > > > <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=81265
> > >
> > >> > > > > >
> > >> > > > > > Hi Julie,
> > >> > > > > >
> > >> > > > > > Thank you for the information. Let me explain a
little bit
> > about
> > >> > what
> > >> > > > I'm
> > >> > > > > > trying to do:
> > >> > > > > >
> > >> > > > > > I originally had a geotiff that I converted to a
NetCDF
> using
> > a
> > >> > > Python
> > >> > > > > > package. It's basically just a base reflectivity
field with
> a
> > >> > > > > corresponding
> > >> > > > > > LatLon grid. I'd like to be able to have this
outputted
> NetCDF
> > >> read
> > >> > > by
> > >> > > > > > MODE. Originally, without setting any attributes, I
received
> > an
> > >> > error
> > >> > > > > > stating that MODE was unable to read the NetCDF. I
then
> found
> > >> this
> > >> > > link
> > >> > > > > > specifying the global grid attributes that are
produced by
> > >> > > pcp_combine
> > >> > > > > for
> > >> > > > > > a LatLon grid:
> > >> > > > > >
> > >> > > > > > http://mailman.ucar.edu/pipermail/met_help/2014-
> > >> > February/002090.html
> > >> > > > > >
> > >> > > > > > I attempted to configure these attributes for my own
file so
> > >> that
> > >> > my
> > >> > > > own
> > >> > > > > > global attributes look like so:
> > >> > > > > >
> > >> > > > > > :Projection = "LatLon" ;
> > >> > > > > > :lat_ll = "23.000000 degrees_north"
;
> > >> > > > > > :lon_ll = "126.000000 degrees_west"
;
> > >> > > > > > :delta_lat = "0.005000 degrees" ;
> > >> > > > > > :delta_lon = "0.005000 degrees" ;
> > >> > > > > > :Nlat = "5400 grid_points" ;
> > >> > > > > > :Nlon = "12200 grid_points" ;
> > >> > > > > >
> > >> > > > > > I had some success with this as I no longer received
the
> > >> > "unreadable"
> > >> > > > > > error, but instead it gets to the step stating
"Identifying
> > >> objects
> > >> > > in
> > >> > > > > > the forecast and observation fields..." after which
the job
> is
> > >> > killed
> > >> > > > > > without any further details. I attached a screenshot
of
> this.
> > >> > > > > >
> > >> > > > > > I can attach the NetCDF file I've produced if it
would help,
> > but
> > >> > > > > > refrained from doing so as it's quite large due to
the large
> > >> grid
> > >> > > > > > size.
> > >> > > > > >
> > >> > > > > > Any advice you could provide would be greatly
appreciated!
> > >> > > > > >
> > >> > > > > > Best,
> > >> > > > > > Jacob Radford
> > >> > > > > >
> > >> > > > > >
> > >> > > > > > On Wed, Jul 19, 2017 at 2:43 PM, Julie Prestopnik via
RT <
> > >> > > > > > met_help at ucar.edu>
> > >> > > > > > wrote:
> > >> > > > > >
> > >> > > > > > > Hi Jacob. I see that you are encountering a
problem with
> > MODE
> > >> > > > reading
> > >> > > > > > your
> > >> > > > > > > NetCDF files.
> > >> > > > > > >
> > >> > > > > > > MET supports a few flavors of NetCDF...
> > >> > > > > > > - Gridded NetCDF files following the CF-convention
> > >> > > > > > > - Gridded NetCDF output of the WRF pinterp utility
> > >> > > > > > > - Internal MET formatted NetCDF file
> > >> > > > > > >
> > >> > > > > > > When you pass MET a NetCDF file, it inspects the
file to
> > >> > determine
> > >> > > > it's
> > >> > > > > > > type. If it's not CF-compliant or a pinterp file,
it
> > assumes
> > >> > it's
> > >> > > > the
> > >> > > > > > 3rd
> > >> > > > > > > type. The 3rd type is basically just the output of
> > >> pcp_combine
> > >> > > tool.
> > >> > > > > > >
> > >> > > > > > > I have attached a sample input file that is the
output of
> > >> > > > pcp_combine,
> > >> > > > > so
> > >> > > > > > > that you can take a look.
> > >> > > > > > >
> > >> > > > > > > I hope this is helpful. Please let us know if you
have
> any
> > >> other
> > >> > > > > > > questions.
> > >> > > > > > >
> > >> > > > > > > Julie
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > > > On Tue, Jul 18, 2017 at 6:56 PM, Jacob Radford via
RT <
> > >> > > > > met_help at ucar.edu
> > >> > > > > > >
> > >> > > > > > > wrote:
> > >> > > > > > >
> > >> > > > > > > >
> > >> > > > > > > > Tue Jul 18 18:56:20 2017: Request 81265 was acted
upon.
> > >> > > > > > > > Transaction: Ticket created by jtradfor at ncsu.edu
> > >> > > > > > > > Queue: met_help
> > >> > > > > > > > Subject: MODE NetCDF Attributes
> > >> > > > > > > > Owner: Nobody
> > >> > > > > > > > Requestors: jtradfor at ncsu.edu
> > >> > > > > > > > Status: new
> > >> > > > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> > >> > > > > Ticket/Display.html?id=81265
> > >> > > > > > >
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > > > > > > Hello,
> > >> > > > > > > >
> > >> > > > > > > > I've just started using MODE and succeeded with
the
> sample
> > >> > data,
> > >> > > > but
> > >> > > > > > it's
> > >> > > > > > > > unable to read my own NetCDF files. I believe
this is
> > >> because
> > >> > of
> > >> > > > > > > inadequate
> > >> > > > > > > > attribute data - could you tell me what
attributes need
> to
> > >> be
> > >> > > > defined
> > >> > > > > > for
> > >> > > > > > > > MODE to read a NetCDF?
> > >> > > > > > > >
> > >> > > > > > > > Thank you!
> > >> > > > > > > > Jacob Radford
> > >> > > > > > > >
> > >> > > > > > > >
> > >> > > > > > >
> > >> > > > > > >
> > >> > > > > >
> > >> > > > > >
> > >> > > > >
> > >> > > > >
> > >> > > >
> > >> > > >
> > >> > >
> > >> > >
> > >> >
> > >> >
> > >>
> > >>
> > >
> >
> >
>
>
------------------------------------------------
Subject: MODE NetCDF Attributes
From: Jacob Radford
Time: Mon Jul 31 13:02:56 2017
Problem solved - It looks like I incorrectly defined my NetCDF
dimensions.
Sorry about that!
On Mon, Jul 31, 2017 at 2:17 PM, Jacob Radford <jtradfor at ncsu.edu>
wrote:
> Thanks, John.
>
> I have one more question (for now...):
>
> I'm trying to use MODE for a new file I created but am getting an
error
> stating "MetNcFile::data(NcVar *, const LongArray &, DataPlane &)
const ->
> star found in bad slot"
>
> The command I'm using is:
>
> > mode \
> > tutorial/out/pcp_combine/201703141300.nc \
> > tutorial/out/pcp_combine/201703141300.nc \
> > tutorial/config/MODEConfig_tutorial \
> > -outdir tutorial/out/mode \
> > -v 2
>
> What does this mean? I uploaded the netcdf file and my config file
to the
> FTP site (named "201703141300.nc" under directory /Radford) if you
want
> to try it yourself.
>
> Thank you!
> Jacob Radford
>
> On Tue, Jul 25, 2017 at 2:40 PM, John Halley Gotway via RT <
> met_help at ucar.edu> wrote:
>
>> Jacob,
>>
>> These are attributes used when defining a lambert conformal
projection.
>> The lon_orient is also sometime called the center longitude. The
two
>> scale
>> latitudes are often set to the same value but not have to be.
>>
>> I don't know enough about grid projections to give you a complete
>> explanation, but suffice it to say, that MET parses these values
when
>> instantiating the grid.
>>
>> John
>>
>> On Tue, Jul 25, 2017 at 11:58 AM, Jacob Radford via RT
<met_help at ucar.edu
>> >
>> wrote:
>>
>> >
>> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
>> >
>> > Oops, sent that on accident without finishing the email - but
what I was
>> > wondering is what the scale_lat_1, scale_lat_2 and lon_orient
attributes
>> > mean.
>> >
>> > Best,
>> > Jacob
>> >
>> > On Tue, Jul 25, 2017 at 1:56 PM, Jacob Radford
<jtradfor at ncsu.edu>
>> wrote:
>> >
>> > > Hi Julie/John,
>> > >
>> > > Thanks again for all your help. I thought of another quick
question:
>> > >
>> > > In the tutorial sample nc file for MODE these global attributes
are
>> > defined
>> > >
>> > > scale_lat_1 = '25.000000'
>> > > scale_lat_2 = '25.000000'
>> > > lat_pin = '12.190000'
>> > > lon_pin = '-133.459000'
>> > > x_pin = '0.000000'
>> > > y_pin = '0.000000'
>> > > lon_orient = '-95.000000'
>> > > d_km = '40.635000'
>> > > r_km = '6371.200000'
>> > > nx = '185'
>> > > ny = '129 grid_points'
>> > >
>> > > On Fri, Jul 21, 2017 at 2:43 PM, John Halley Gotway via RT <
>> > > met_help at ucar.edu> wrote:
>> > >
>> > >> Jacob,
>> > >>
>> > >> This is John and I work with Julie on providing MET support.
Julie
>> sent
>> > >> you an example of using the regrid_data_plane tool in MET to
regrid
>> your
>> > >> data before processing it in MODE.
>> > >>
>> > >> You also have a second regridding option. Instead of calling
>> > >> regrid_data_plane first, you could pass your original data
file to
>> MODE
>> > >> and
>> > >> use the "regrid" option in the MODE config file. That tells
MODE to
>> do
>> > >> the
>> > >> regridding on the fly without writing an intermediate file.
>> > >>
>> > >> Either method will work and should result in identical output.
It's
>> up
>> > to
>> > >> you to decide whether you want to write an intermediate
regridded
>> NetCDF
>> > >> file.
>> > >>
>> > >> Here's the regrid setting you could try in the MODE config
file:
>> > >>
>> > >> regrid = {
>> > >> to_grid = "latlon 610 270 23 126 0.1 0.1";
>> > >> method = BILIN;
>> > >> width = 2;
>> > >> vld_thresh = 0.5;
>> > >> }
>> > >>
>> > >> Hope that helps.
>> > >>
>> > >> Thanks,
>> > >> John
>> > >>
>> > >> On Fri, Jul 21, 2017 at 11:44 AM, Jacob Radford via RT <
>> > met_help at ucar.edu
>> > >> >
>> > >> wrote:
>> > >>
>> > >> >
>> > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
>> > >> >
>> > >> > Hi Julie,
>> > >> >
>> > >> > Thank you for all your help! I thought the grid density
might be an
>> > >> issue.
>> > >> > Interpolating to a coarser grid was ultimately the plan
anyway.
>> > >> >
>> > >> > Best,
>> > >> > Jacob
>> > >> >
>> > >> > On Fri, Jul 21, 2017 at 1:05 PM, Julie Prestopnik via RT <
>> > >> > met_help at ucar.edu>
>> > >> > wrote:
>> > >> >
>> > >> > > Hi Jacob. Thank you for sending me the data and the
command line
>> > you
>> > >> are
>> > >> > > using. We can see that MET is working on your data, but
>> > >> unfortunately it
>> > >> > > is not realistic to have MET run on such a dense grid.
MODE was
>> > >> running
>> > >> > > extremely slowly due to the grid density.
>> > >> > >
>> > >> > > We regridded your data using the following command to a .1
degree
>> > >> grid:
>> > >> > >
>> > >> > > regrid_data_plane reflectivity.nc 'latlon 610 270 23 126
0.1
>> 0.1'
>> > >> > > reflectivity_REGRID.nc -field 'name="Reflectivity";
>> level="(*,*)";'
>> > >> -name
>> > >> > > Reflectivity -method BILIN -width 2
>> > >> > >
>> > >> > > We also played around with your configuration file a bit
and made
>> > some
>> > >> > > changes. Using the new file, reflectivity_REGRID.nc with
the new
>> > >> > > configuration file (attached), we were able to create
reasonable
>> > >> looking
>> > >> > > objects.
>> > >> > >
>> > >> > > Please take a look and let us know if you have any
questions.
>> > >> > >
>> > >> > > Thanks,
>> > >> > > Julie
>> > >> > >
>> > >> > > On Thu, Jul 20, 2017 at 11:33 PM, Jacob Radford via RT <
>> > >> > met_help at ucar.edu>
>> > >> > > wrote:
>> > >> > >
>> > >> > > >
>> > >> > > > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265
>> >
>> > >> > > >
>> > >> > > > Hi Julie,
>> > >> > > >
>> > >> > > > I increased the verbosity as you suggested and it looks
like
>> the
>> > >> > problem
>> > >> > > is
>> > >> > > > occurring at the convolution step. I uploaded my NetCDF
(
>> > >> > reflectivity.nc
>> > >> > > )
>> > >> > > > and my MODE configuration file (MODEConfig_tutorial)
following
>> the
>> > >> > > > conventions in the FTP instructions (under
Radford_data). I
>> tried
>> > to
>> > >> > > change
>> > >> > > > as little as possible from the tutorial configuration,
so I
>> mostly
>> > >> just
>> > >> > > > edited the forecast/observation field to read the
information
>> from
>> > >> my
>> > >> > own
>> > >> > > > file. I'm also using the same file for the forecast and
>> > observations
>> > >> > > > initially because I'm just getting familiar with MET and
>> trying to
>> > >> get
>> > >> > it
>> > >> > > > to read my data at this point.
>> > >> > > >
>> > >> > > > I'm running METv6.0 in Docker and the command I'm using
is:
>> > >> > > >
>> > >> > > > > mode \
>> > >> > > > > tutorial/out/pcp_combine/reflectivity.nc \
>> > >> > > > > tutorial/out/pcp_combine/reflectivity.nc \
>> > >> > > > > tutorial/config/MODEConfig_tutorial \
>> > >> > > > > -outdir tutorial/out/mode \
>> > >> > > > > -v 9
>> > >> > > >
>> > >> > > > Let me know if there's any other information or files
that you
>> > need
>> > >> > from
>> > >> > > me
>> > >> > > > to look into this.
>> > >> > > >
>> > >> > > > Best,
>> > >> > > > Jacob
>> > >> > > >
>> > >> > > > On Thu, Jul 20, 2017 at 1:52 PM, Julie Prestopnik via RT
<
>> > >> > > > met_help at ucar.edu>
>> > >> > > > wrote:
>> > >> > > >
>> > >> > > > > Hi Jacob. Thank you for providing more information.
To get
>> > more
>> > >> > > > > information about what is going on you could try
running MODE
>> > >> with a
>> > >> > > > higher
>> > >> > > > > verbosity level (e.g. -v 9). Also, please feel free
to
>> upload
>> > >> your
>> > >> > > file
>> > >> > > > on
>> > >> > > > > our anonymous ftp site:
>> > >> > > > >
>> > >> > > > >
http://www.dtcenter.org/met/users/support/met_help.php#ftp
>> > >> > > > >
>> > >> > > > > so that we can also take a look. If you do upload
data,
>> please
>> > >> > upload
>> > >> > > > all
>> > >> > > > > the files used and send me the command you are using
to run
>> the
>> > >> code,
>> > >> > > so
>> > >> > > > > that I can try to reproduce the behavior.
>> > >> > > > >
>> > >> > > > > Also, what version of MET are you using?
>> > >> > > > >
>> > >> > > > > Thanks,
>> > >> > > > > Julie
>> > >> > > > >
>> > >> > > > > On Thu, Jul 20, 2017 at 11:38 AM, Jacob Radford via RT
<
>> > >> > > > met_help at ucar.edu>
>> > >> > > > > wrote:
>> > >> > > > >
>> > >> > > > > >
>> > >> > > > > > <URL: https://rt.rap.ucar.edu/rt/Tic
>> ket/Display.html?id=81265
>> > >
>> > >> > > > > >
>> > >> > > > > > Hi Julie,
>> > >> > > > > >
>> > >> > > > > > Thank you for the information. Let me explain a
little bit
>> > about
>> > >> > what
>> > >> > > > I'm
>> > >> > > > > > trying to do:
>> > >> > > > > >
>> > >> > > > > > I originally had a geotiff that I converted to a
NetCDF
>> using
>> > a
>> > >> > > Python
>> > >> > > > > > package. It's basically just a base reflectivity
field
>> with a
>> > >> > > > > corresponding
>> > >> > > > > > LatLon grid. I'd like to be able to have this
outputted
>> NetCDF
>> > >> read
>> > >> > > by
>> > >> > > > > > MODE. Originally, without setting any attributes, I
>> received
>> > an
>> > >> > error
>> > >> > > > > > stating that MODE was unable to read the NetCDF. I
then
>> found
>> > >> this
>> > >> > > link
>> > >> > > > > > specifying the global grid attributes that are
produced by
>> > >> > > pcp_combine
>> > >> > > > > for
>> > >> > > > > > a LatLon grid:
>> > >> > > > > >
>> > >> > > > > > http://mailman.ucar.edu/pipermail/met_help/2014-
>> > >> > February/002090.html
>> > >> > > > > >
>> > >> > > > > > I attempted to configure these attributes for my own
file
>> so
>> > >> that
>> > >> > my
>> > >> > > > own
>> > >> > > > > > global attributes look like so:
>> > >> > > > > >
>> > >> > > > > > :Projection = "LatLon" ;
>> > >> > > > > > :lat_ll = "23.000000 degrees_north"
;
>> > >> > > > > > :lon_ll = "126.000000 degrees_west"
;
>> > >> > > > > > :delta_lat = "0.005000 degrees" ;
>> > >> > > > > > :delta_lon = "0.005000 degrees" ;
>> > >> > > > > > :Nlat = "5400 grid_points" ;
>> > >> > > > > > :Nlon = "12200 grid_points" ;
>> > >> > > > > >
>> > >> > > > > > I had some success with this as I no longer received
the
>> > >> > "unreadable"
>> > >> > > > > > error, but instead it gets to the step stating
"Identifying
>> > >> objects
>> > >> > > in
>> > >> > > > > > the forecast and observation fields..." after which
the
>> job is
>> > >> > killed
>> > >> > > > > > without any further details. I attached a screenshot
of
>> this.
>> > >> > > > > >
>> > >> > > > > > I can attach the NetCDF file I've produced if it
would
>> help,
>> > but
>> > >> > > > > > refrained from doing so as it's quite large due to
the
>> large
>> > >> grid
>> > >> > > > > > size.
>> > >> > > > > >
>> > >> > > > > > Any advice you could provide would be greatly
appreciated!
>> > >> > > > > >
>> > >> > > > > > Best,
>> > >> > > > > > Jacob Radford
>> > >> > > > > >
>> > >> > > > > >
>> > >> > > > > > On Wed, Jul 19, 2017 at 2:43 PM, Julie Prestopnik
via RT <
>> > >> > > > > > met_help at ucar.edu>
>> > >> > > > > > wrote:
>> > >> > > > > >
>> > >> > > > > > > Hi Jacob. I see that you are encountering a
problem with
>> > MODE
>> > >> > > > reading
>> > >> > > > > > your
>> > >> > > > > > > NetCDF files.
>> > >> > > > > > >
>> > >> > > > > > > MET supports a few flavors of NetCDF...
>> > >> > > > > > > - Gridded NetCDF files following the CF-
convention
>> > >> > > > > > > - Gridded NetCDF output of the WRF pinterp
utility
>> > >> > > > > > > - Internal MET formatted NetCDF file
>> > >> > > > > > >
>> > >> > > > > > > When you pass MET a NetCDF file, it inspects the
file to
>> > >> > determine
>> > >> > > > it's
>> > >> > > > > > > type. If it's not CF-compliant or a pinterp file,
it
>> > assumes
>> > >> > it's
>> > >> > > > the
>> > >> > > > > > 3rd
>> > >> > > > > > > type. The 3rd type is basically just the output
of
>> > >> pcp_combine
>> > >> > > tool.
>> > >> > > > > > >
>> > >> > > > > > > I have attached a sample input file that is the
output of
>> > >> > > > pcp_combine,
>> > >> > > > > so
>> > >> > > > > > > that you can take a look.
>> > >> > > > > > >
>> > >> > > > > > > I hope this is helpful. Please let us know if you
have
>> any
>> > >> other
>> > >> > > > > > > questions.
>> > >> > > > > > >
>> > >> > > > > > > Julie
>> > >> > > > > > >
>> > >> > > > > > >
>> > >> > > > > > > On Tue, Jul 18, 2017 at 6:56 PM, Jacob Radford via
RT <
>> > >> > > > > met_help at ucar.edu
>> > >> > > > > > >
>> > >> > > > > > > wrote:
>> > >> > > > > > >
>> > >> > > > > > > >
>> > >> > > > > > > > Tue Jul 18 18:56:20 2017: Request 81265 was
acted upon.
>> > >> > > > > > > > Transaction: Ticket created by jtradfor at ncsu.edu
>> > >> > > > > > > > Queue: met_help
>> > >> > > > > > > > Subject: MODE NetCDF Attributes
>> > >> > > > > > > > Owner: Nobody
>> > >> > > > > > > > Requestors: jtradfor at ncsu.edu
>> > >> > > > > > > > Status: new
>> > >> > > > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
>> > >> > > > > Ticket/Display.html?id=81265
>> > >> > > > > > >
>> > >> > > > > > > >
>> > >> > > > > > > >
>> > >> > > > > > > > Hello,
>> > >> > > > > > > >
>> > >> > > > > > > > I've just started using MODE and succeeded with
the
>> sample
>> > >> > data,
>> > >> > > > but
>> > >> > > > > > it's
>> > >> > > > > > > > unable to read my own NetCDF files. I believe
this is
>> > >> because
>> > >> > of
>> > >> > > > > > > inadequate
>> > >> > > > > > > > attribute data - could you tell me what
attributes
>> need to
>> > >> be
>> > >> > > > defined
>> > >> > > > > > for
>> > >> > > > > > > > MODE to read a NetCDF?
>> > >> > > > > > > >
>> > >> > > > > > > > Thank you!
>> > >> > > > > > > > Jacob Radford
>> > >> > > > > > > >
>> > >> > > > > > > >
>> > >> > > > > > >
>> > >> > > > > > >
>> > >> > > > > >
>> > >> > > > > >
>> > >> > > > >
>> > >> > > > >
>> > >> > > >
>> > >> > > >
>> > >> > >
>> > >> > >
>> > >> >
>> > >> >
>> > >>
>> > >>
>> > >
>> >
>> >
>>
>>
>
------------------------------------------------
Subject: MODE NetCDF Attributes
From: John Halley Gotway
Time: Mon Jul 31 14:29:15 2017
Jacob,
No worries. Glad you figured it out.
Thanks,
John
On Mon, Jul 31, 2017 at 1:02 PM, Jacob Radford via RT
<met_help at ucar.edu>
wrote:
>
> <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
>
> Problem solved - It looks like I incorrectly defined my NetCDF
dimensions.
> Sorry about that!
>
> On Mon, Jul 31, 2017 at 2:17 PM, Jacob Radford <jtradfor at ncsu.edu>
wrote:
>
> > Thanks, John.
> >
> > I have one more question (for now...):
> >
> > I'm trying to use MODE for a new file I created but am getting an
error
> > stating "MetNcFile::data(NcVar *, const LongArray &, DataPlane &)
const
> ->
> > star found in bad slot"
> >
> > The command I'm using is:
> >
> > > mode \
> > > tutorial/out/pcp_combine/201703141300.nc \
> > > tutorial/out/pcp_combine/201703141300.nc \
> > > tutorial/config/MODEConfig_tutorial \
> > > -outdir tutorial/out/mode \
> > > -v 2
> >
> > What does this mean? I uploaded the netcdf file and my config file
to the
> > FTP site (named "201703141300.nc" under directory /Radford) if you
want
> > to try it yourself.
> >
> > Thank you!
> > Jacob Radford
> >
> > On Tue, Jul 25, 2017 at 2:40 PM, John Halley Gotway via RT <
> > met_help at ucar.edu> wrote:
> >
> >> Jacob,
> >>
> >> These are attributes used when defining a lambert conformal
projection.
> >> The lon_orient is also sometime called the center longitude. The
two
> >> scale
> >> latitudes are often set to the same value but not have to be.
> >>
> >> I don't know enough about grid projections to give you a complete
> >> explanation, but suffice it to say, that MET parses these values
when
> >> instantiating the grid.
> >>
> >> John
> >>
> >> On Tue, Jul 25, 2017 at 11:58 AM, Jacob Radford via RT <
> met_help at ucar.edu
> >> >
> >> wrote:
> >>
> >> >
> >> > <URL: https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> >> >
> >> > Oops, sent that on accident without finishing the email - but
what I
> was
> >> > wondering is what the scale_lat_1, scale_lat_2 and lon_orient
> attributes
> >> > mean.
> >> >
> >> > Best,
> >> > Jacob
> >> >
> >> > On Tue, Jul 25, 2017 at 1:56 PM, Jacob Radford
<jtradfor at ncsu.edu>
> >> wrote:
> >> >
> >> > > Hi Julie/John,
> >> > >
> >> > > Thanks again for all your help. I thought of another quick
question:
> >> > >
> >> > > In the tutorial sample nc file for MODE these global
attributes are
> >> > defined
> >> > >
> >> > > scale_lat_1 = '25.000000'
> >> > > scale_lat_2 = '25.000000'
> >> > > lat_pin = '12.190000'
> >> > > lon_pin = '-133.459000'
> >> > > x_pin = '0.000000'
> >> > > y_pin = '0.000000'
> >> > > lon_orient = '-95.000000'
> >> > > d_km = '40.635000'
> >> > > r_km = '6371.200000'
> >> > > nx = '185'
> >> > > ny = '129 grid_points'
> >> > >
> >> > > On Fri, Jul 21, 2017 at 2:43 PM, John Halley Gotway via RT <
> >> > > met_help at ucar.edu> wrote:
> >> > >
> >> > >> Jacob,
> >> > >>
> >> > >> This is John and I work with Julie on providing MET support.
Julie
> >> sent
> >> > >> you an example of using the regrid_data_plane tool in MET to
regrid
> >> your
> >> > >> data before processing it in MODE.
> >> > >>
> >> > >> You also have a second regridding option. Instead of
calling
> >> > >> regrid_data_plane first, you could pass your original data
file to
> >> MODE
> >> > >> and
> >> > >> use the "regrid" option in the MODE config file. That tells
MODE
> to
> >> do
> >> > >> the
> >> > >> regridding on the fly without writing an intermediate file.
> >> > >>
> >> > >> Either method will work and should result in identical
output.
> It's
> >> up
> >> > to
> >> > >> you to decide whether you want to write an intermediate
regridded
> >> NetCDF
> >> > >> file.
> >> > >>
> >> > >> Here's the regrid setting you could try in the MODE config
file:
> >> > >>
> >> > >> regrid = {
> >> > >> to_grid = "latlon 610 270 23 126 0.1 0.1";
> >> > >> method = BILIN;
> >> > >> width = 2;
> >> > >> vld_thresh = 0.5;
> >> > >> }
> >> > >>
> >> > >> Hope that helps.
> >> > >>
> >> > >> Thanks,
> >> > >> John
> >> > >>
> >> > >> On Fri, Jul 21, 2017 at 11:44 AM, Jacob Radford via RT <
> >> > met_help at ucar.edu
> >> > >> >
> >> > >> wrote:
> >> > >>
> >> > >> >
> >> > >> > <URL:
https://rt.rap.ucar.edu/rt/Ticket/Display.html?id=81265 >
> >> > >> >
> >> > >> > Hi Julie,
> >> > >> >
> >> > >> > Thank you for all your help! I thought the grid density
might be
> an
> >> > >> issue.
> >> > >> > Interpolating to a coarser grid was ultimately the plan
anyway.
> >> > >> >
> >> > >> > Best,
> >> > >> > Jacob
> >> > >> >
> >> > >> > On Fri, Jul 21, 2017 at 1:05 PM, Julie Prestopnik via RT <
> >> > >> > met_help at ucar.edu>
> >> > >> > wrote:
> >> > >> >
> >> > >> > > Hi Jacob. Thank you for sending me the data and the
command
> line
> >> > you
> >> > >> are
> >> > >> > > using. We can see that MET is working on your data, but
> >> > >> unfortunately it
> >> > >> > > is not realistic to have MET run on such a dense grid.
MODE
> was
> >> > >> running
> >> > >> > > extremely slowly due to the grid density.
> >> > >> > >
> >> > >> > > We regridded your data using the following command to a
.1
> degree
> >> > >> grid:
> >> > >> > >
> >> > >> > > regrid_data_plane reflectivity.nc 'latlon 610 270 23 126
0.1
> >> 0.1'
> >> > >> > > reflectivity_REGRID.nc -field 'name="Reflectivity";
> >> level="(*,*)";'
> >> > >> -name
> >> > >> > > Reflectivity -method BILIN -width 2
> >> > >> > >
> >> > >> > > We also played around with your configuration file a bit
and
> made
> >> > some
> >> > >> > > changes. Using the new file, reflectivity_REGRID.nc with
the
> new
> >> > >> > > configuration file (attached), we were able to create
> reasonable
> >> > >> looking
> >> > >> > > objects.
> >> > >> > >
> >> > >> > > Please take a look and let us know if you have any
questions.
> >> > >> > >
> >> > >> > > Thanks,
> >> > >> > > Julie
> >> > >> > >
> >> > >> > > On Thu, Jul 20, 2017 at 11:33 PM, Jacob Radford via RT <
> >> > >> > met_help at ucar.edu>
> >> > >> > > wrote:
> >> > >> > >
> >> > >> > > >
> >> > >> > > > <URL: https://rt.rap.ucar.edu/rt/
> Ticket/Display.html?id=81265
> >> >
> >> > >> > > >
> >> > >> > > > Hi Julie,
> >> > >> > > >
> >> > >> > > > I increased the verbosity as you suggested and it
looks like
> >> the
> >> > >> > problem
> >> > >> > > is
> >> > >> > > > occurring at the convolution step. I uploaded my
NetCDF (
> >> > >> > reflectivity.nc
> >> > >> > > )
> >> > >> > > > and my MODE configuration file (MODEConfig_tutorial)
> following
> >> the
> >> > >> > > > conventions in the FTP instructions (under
Radford_data). I
> >> tried
> >> > to
> >> > >> > > change
> >> > >> > > > as little as possible from the tutorial configuration,
so I
> >> mostly
> >> > >> just
> >> > >> > > > edited the forecast/observation field to read the
information
> >> from
> >> > >> my
> >> > >> > own
> >> > >> > > > file. I'm also using the same file for the forecast
and
> >> > observations
> >> > >> > > > initially because I'm just getting familiar with MET
and
> >> trying to
> >> > >> get
> >> > >> > it
> >> > >> > > > to read my data at this point.
> >> > >> > > >
> >> > >> > > > I'm running METv6.0 in Docker and the command I'm
using is:
> >> > >> > > >
> >> > >> > > > > mode \
> >> > >> > > > > tutorial/out/pcp_combine/reflectivity.nc \
> >> > >> > > > > tutorial/out/pcp_combine/reflectivity.nc \
> >> > >> > > > > tutorial/config/MODEConfig_tutorial \
> >> > >> > > > > -outdir tutorial/out/mode \
> >> > >> > > > > -v 9
> >> > >> > > >
> >> > >> > > > Let me know if there's any other information or files
that
> you
> >> > need
> >> > >> > from
> >> > >> > > me
> >> > >> > > > to look into this.
> >> > >> > > >
> >> > >> > > > Best,
> >> > >> > > > Jacob
> >> > >> > > >
> >> > >> > > > On Thu, Jul 20, 2017 at 1:52 PM, Julie Prestopnik via
RT <
> >> > >> > > > met_help at ucar.edu>
> >> > >> > > > wrote:
> >> > >> > > >
> >> > >> > > > > Hi Jacob. Thank you for providing more information.
To
> get
> >> > more
> >> > >> > > > > information about what is going on you could try
running
> MODE
> >> > >> with a
> >> > >> > > > higher
> >> > >> > > > > verbosity level (e.g. -v 9). Also, please feel free
to
> >> upload
> >> > >> your
> >> > >> > > file
> >> > >> > > > on
> >> > >> > > > > our anonymous ftp site:
> >> > >> > > > >
> >> > >> > > > >
http://www.dtcenter.org/met/users/support/met_help.php#ftp
> >> > >> > > > >
> >> > >> > > > > so that we can also take a look. If you do upload
data,
> >> please
> >> > >> > upload
> >> > >> > > > all
> >> > >> > > > > the files used and send me the command you are using
to run
> >> the
> >> > >> code,
> >> > >> > > so
> >> > >> > > > > that I can try to reproduce the behavior.
> >> > >> > > > >
> >> > >> > > > > Also, what version of MET are you using?
> >> > >> > > > >
> >> > >> > > > > Thanks,
> >> > >> > > > > Julie
> >> > >> > > > >
> >> > >> > > > > On Thu, Jul 20, 2017 at 11:38 AM, Jacob Radford via
RT <
> >> > >> > > > met_help at ucar.edu>
> >> > >> > > > > wrote:
> >> > >> > > > >
> >> > >> > > > > >
> >> > >> > > > > > <URL: https://rt.rap.ucar.edu/rt/Tic
> >> ket/Display.html?id=81265
> >> > >
> >> > >> > > > > >
> >> > >> > > > > > Hi Julie,
> >> > >> > > > > >
> >> > >> > > > > > Thank you for the information. Let me explain a
little
> bit
> >> > about
> >> > >> > what
> >> > >> > > > I'm
> >> > >> > > > > > trying to do:
> >> > >> > > > > >
> >> > >> > > > > > I originally had a geotiff that I converted to a
NetCDF
> >> using
> >> > a
> >> > >> > > Python
> >> > >> > > > > > package. It's basically just a base reflectivity
field
> >> with a
> >> > >> > > > > corresponding
> >> > >> > > > > > LatLon grid. I'd like to be able to have this
outputted
> >> NetCDF
> >> > >> read
> >> > >> > > by
> >> > >> > > > > > MODE. Originally, without setting any attributes,
I
> >> received
> >> > an
> >> > >> > error
> >> > >> > > > > > stating that MODE was unable to read the NetCDF. I
then
> >> found
> >> > >> this
> >> > >> > > link
> >> > >> > > > > > specifying the global grid attributes that are
produced
> by
> >> > >> > > pcp_combine
> >> > >> > > > > for
> >> > >> > > > > > a LatLon grid:
> >> > >> > > > > >
> >> > >> > > > > > http://mailman.ucar.edu/pipermail/met_help/2014-
> >> > >> > February/002090.html
> >> > >> > > > > >
> >> > >> > > > > > I attempted to configure these attributes for my
own file
> >> so
> >> > >> that
> >> > >> > my
> >> > >> > > > own
> >> > >> > > > > > global attributes look like so:
> >> > >> > > > > >
> >> > >> > > > > > :Projection = "LatLon" ;
> >> > >> > > > > > :lat_ll = "23.000000
degrees_north" ;
> >> > >> > > > > > :lon_ll = "126.000000
degrees_west" ;
> >> > >> > > > > > :delta_lat = "0.005000 degrees" ;
> >> > >> > > > > > :delta_lon = "0.005000 degrees" ;
> >> > >> > > > > > :Nlat = "5400 grid_points" ;
> >> > >> > > > > > :Nlon = "12200 grid_points" ;
> >> > >> > > > > >
> >> > >> > > > > > I had some success with this as I no longer
received the
> >> > >> > "unreadable"
> >> > >> > > > > > error, but instead it gets to the step stating
> "Identifying
> >> > >> objects
> >> > >> > > in
> >> > >> > > > > > the forecast and observation fields..." after
which the
> >> job is
> >> > >> > killed
> >> > >> > > > > > without any further details. I attached a
screenshot of
> >> this.
> >> > >> > > > > >
> >> > >> > > > > > I can attach the NetCDF file I've produced if it
would
> >> help,
> >> > but
> >> > >> > > > > > refrained from doing so as it's quite large due to
the
> >> large
> >> > >> grid
> >> > >> > > > > > size.
> >> > >> > > > > >
> >> > >> > > > > > Any advice you could provide would be greatly
> appreciated!
> >> > >> > > > > >
> >> > >> > > > > > Best,
> >> > >> > > > > > Jacob Radford
> >> > >> > > > > >
> >> > >> > > > > >
> >> > >> > > > > > On Wed, Jul 19, 2017 at 2:43 PM, Julie Prestopnik
via RT
> <
> >> > >> > > > > > met_help at ucar.edu>
> >> > >> > > > > > wrote:
> >> > >> > > > > >
> >> > >> > > > > > > Hi Jacob. I see that you are encountering a
problem
> with
> >> > MODE
> >> > >> > > > reading
> >> > >> > > > > > your
> >> > >> > > > > > > NetCDF files.
> >> > >> > > > > > >
> >> > >> > > > > > > MET supports a few flavors of NetCDF...
> >> > >> > > > > > > - Gridded NetCDF files following the CF-
convention
> >> > >> > > > > > > - Gridded NetCDF output of the WRF pinterp
utility
> >> > >> > > > > > > - Internal MET formatted NetCDF file
> >> > >> > > > > > >
> >> > >> > > > > > > When you pass MET a NetCDF file, it inspects the
file
> to
> >> > >> > determine
> >> > >> > > > it's
> >> > >> > > > > > > type. If it's not CF-compliant or a pinterp
file, it
> >> > assumes
> >> > >> > it's
> >> > >> > > > the
> >> > >> > > > > > 3rd
> >> > >> > > > > > > type. The 3rd type is basically just the output
of
> >> > >> pcp_combine
> >> > >> > > tool.
> >> > >> > > > > > >
> >> > >> > > > > > > I have attached a sample input file that is the
output
> of
> >> > >> > > > pcp_combine,
> >> > >> > > > > so
> >> > >> > > > > > > that you can take a look.
> >> > >> > > > > > >
> >> > >> > > > > > > I hope this is helpful. Please let us know if
you have
> >> any
> >> > >> other
> >> > >> > > > > > > questions.
> >> > >> > > > > > >
> >> > >> > > > > > > Julie
> >> > >> > > > > > >
> >> > >> > > > > > >
> >> > >> > > > > > > On Tue, Jul 18, 2017 at 6:56 PM, Jacob Radford
via RT <
> >> > >> > > > > met_help at ucar.edu
> >> > >> > > > > > >
> >> > >> > > > > > > wrote:
> >> > >> > > > > > >
> >> > >> > > > > > > >
> >> > >> > > > > > > > Tue Jul 18 18:56:20 2017: Request 81265 was
acted
> upon.
> >> > >> > > > > > > > Transaction: Ticket created by
jtradfor at ncsu.edu
> >> > >> > > > > > > > Queue: met_help
> >> > >> > > > > > > > Subject: MODE NetCDF Attributes
> >> > >> > > > > > > > Owner: Nobody
> >> > >> > > > > > > > Requestors: jtradfor at ncsu.edu
> >> > >> > > > > > > > Status: new
> >> > >> > > > > > > > Ticket <URL: https://rt.rap.ucar.edu/rt/
> >> > >> > > > > Ticket/Display.html?id=81265
> >> > >> > > > > > >
> >> > >> > > > > > > >
> >> > >> > > > > > > >
> >> > >> > > > > > > > Hello,
> >> > >> > > > > > > >
> >> > >> > > > > > > > I've just started using MODE and succeeded
with the
> >> sample
> >> > >> > data,
> >> > >> > > > but
> >> > >> > > > > > it's
> >> > >> > > > > > > > unable to read my own NetCDF files. I believe
this is
> >> > >> because
> >> > >> > of
> >> > >> > > > > > > inadequate
> >> > >> > > > > > > > attribute data - could you tell me what
attributes
> >> need to
> >> > >> be
> >> > >> > > > defined
> >> > >> > > > > > for
> >> > >> > > > > > > > MODE to read a NetCDF?
> >> > >> > > > > > > >
> >> > >> > > > > > > > Thank you!
> >> > >> > > > > > > > Jacob Radford
> >> > >> > > > > > > >
> >> > >> > > > > > > >
> >> > >> > > > > > >
> >> > >> > > > > > >
> >> > >> > > > > >
> >> > >> > > > > >
> >> > >> > > > >
> >> > >> > > > >
> >> > >> > > >
> >> > >> > > >
> >> > >> > >
> >> > >> > >
> >> > >> >
> >> > >> >
> >> > >>
> >> > >>
> >> > >
> >> >
> >> >
> >>
> >>
> >
>
>
------------------------------------------------
More information about the Met_help
mailing list