[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

[IDV #HRF-958294]: Fwd: 3-D traj in idv



> Here is a link.
> 
> https://rda.ucar.edu/thredds/catalog/files/g/ds608.0/3HRLY/2017/catalog.html
> >

So the naming of these datasets is not standardized. What you can do here is: 
1) first load it 
2) in the 3D grid > Fields, select u-component...., right click and add to U 
Component of wind, and the same for v, and w.
3) right click the data source name and reload the dataset

Now you can do the Grid 3D trajectory.

> 
> Also not sure what using ncml means to fix it.  Is that this:  If so I do I
> enter this into idv?
> 
I will send you a ncml file later.

Yuan

> float omega(time=111043, lev=42, lat=361, lon=576);
> :_CoordinateAxes = "time lev lat lon ";
> :_FillValue = 9.9999999E14f; // float
> :missing_value = 9.9999999E14f; // float
> :long_name = "vertical pressure velocity pa s-1 ";
> 
> Thanks,
> 
> Dave
> 
> David Reynolds
> Senior Research Meteorologist
> Cooperative Institute for Research in the  Environmental Sciences
> Univ. of Colorado
> Monterey, CA 93940
> 831-521-9262 cell
> 
> address@hidden> wrote:
> 
> > > Hi Yuan,
> > >
> > > I was trying to produce some 3-d traj from MERRA 2 data.  It has vertical
> > > pressure units in millibars not hpa.  Get an error message that units
> > have
> > > to be hpa.   Maybe another fix you could make?  Thanks.
> > >
> > > NARR data doesn't have 3-d traj in grib file so not able to find a data
> > set
> > > from Dec 2016 or Jan 2017 that works for 3-D traj.   Are you aware of a
> > > data set that I could load two consecutive days of 3 or 6-hr data that
> > has
> > > 3-d traj?  Thanks.
> > >
> > >
> > > Dave
> >
> > Hi Dave,
> >
> > There is no unit in the MERRA2 omega field, you can use ncml to fixed it.
> > If the NARR dataset has u, v, and w, we can
> > use the alias table to make it work. Can you send me a link of NARR
> > dataset?
> >
> > Yuan
> >
> >  float omega(time=111043, lev=42, lat=361, lon=576);
> >       :_CoordinateAxes = "time lev lat lon ";
> >       :_FillValue = 9.9999999E14f; // float
> >       :missing_value = 9.9999999E14f; // float
> >       :long_name = "vertical pressure velocity pa s-1 ";
> > >
> > > David Reynolds
> > > Senior Research Meteorologist
> > > Cooperative Institute for Research in the  Environmental Sciences
> > > Univ. of Colorado
> > > Monterey, CA 93940
> > > 831-521-9262 cell
> > >
> > > address@hidden> wrote:
> > >
> > > > > Hi Yuan,
> > > > >
> > > > > I installed the new version but a few issues.  One I can't seem to
> > run
> > > > any
> > > > > 2-D traj with the new version.  It seems to force 3-D traj.  Also I
> > keep
> > > > > getting heap space errors. Anyway to address these memory errors?
> > > > Thanks.
> > > > >
> > > > > Dave
> > > > >
> > > > > David Reynolds
> > > > > Senior Research Meteorologist
> > > > > Cooperative Institute for Research in the  Environmental Sciences
> > > > > Univ. of Colorado
> > > > > Monterey, CA 93940
> > > > > 831-521-9262 cell
> > > > >
> > > >
> > > > Hi Dave,
> > > >
> > > > I removed the 2-D trajectory from the derived. It is no longer working
> > in
> > > > the new VisAD. We are moving to replace the original trajectory with
> > the
> > > > new VisAD enhancement.
> > > >  I am still working on the 3-D,  I may go back to add the 2D in the
> > near
> > > > future.
> > > >
> > > > For the memory issue, you can open the datasource property window and
> > > > subset the region and setting the skip for x/y. I really like to have
> > some
> > > > feedback.
> > > >
> > > > For the 3D, the backward is working, the new POINT trajectory type is
> > very
> > > > interesting, and you can do colored by another parameter.
> > > >
> > > > Yuan
> > > >
> > > > > address@hidden> wrote:
> > > > >
> > > > > > > Hi Yuan,
> > > > > > >
> > > > > > > Don Murray suggested I send this to you.  Any ideas why I am
> > getting
> > > > this
> > > > > > > error message?  Hopefully all the attachments are included.
> > Thanks.
> > > > > > >
> > > > > > > Dave
> > > > > > > David Reynolds
> > > > > > > Senior Research Meteorologist
> > > > > > > Cooperative Institute for Research in the  Environmental Sciences
> > > > > > > Univ. of Colorado
> > > > > > > Monterey, CA 93940
> > > > > > > 831-521-9262 cell
> > > > > > >
> > > > > >
> > > > > > Hi Dave,
> > > > > >
> > > > > > I have been working on redo the 3D trajectory feature, it will be
> > done
> > > > in
> > > > > > a couple week. If you download the nightly
> > > > > > release, the forward trajectory should be ready, but the backward
> > still
> > > > > > under development.
> > > > > >
> > > > > > Let me know if you see any problem in the nightly release.
> > > > > >
> > > > > >
> > > > > > Yuan
> > > > > > > ---------- Forwarded message ----------
> > > > > > > From: David Reynolds - NOAA Affiliate <address@hidden>
> > > > > > > Date: Tue, May 2, 2017 at 7:44 AM
> > > > > > > Subject: 3-D traj in idv
> > > > > > > To: Donald Murray - NOAA Affiliate <address@hidden>
> > > > > > >
> > > > > > >
> > > > > > > Hi Don,
> > > > > > >
> > > > > > > I am trying to generate a 3-d display of traj using MERRA 2
> > data.  I
> > > > am
> > > > > > > following the video of Dr. Mapes using isobaric temperature to
> > color
> > > > the
> > > > > > > traj lines.  I keep getting an error.
> > > > > > >
> > > > > > > Also attached is the Field Selector window I used.  I am sure I
> > am
> > > > doing
> > > > > > > something stupid.  Any ideas based on error message.  I had to
> > use
> > > > the
> > > > > > NARR
> > > > > > > data for isobaric Temps since MERRA2 did not have this field.
> > > > > > >
> > > > > > > Thanks,
> > > > > > >
> > > > > > > Dave
> > > > > > > David Reynolds
> > > > > > > Senior Research Meteorologist
> > > > > > > Cooperative Institute for Research in the  Environmental Sciences
> > > > > > > Univ. of Colorado
> > > > > > > Monterey, CA 93940
> > > > > > > 831-521-9262 <(831)%20521-9262> cell
> > > > > > >
> > > > > > >
> > > > > >
> > > > > >
> > > > > > Ticket Details
> > > > > > ===================
> > > > > > Ticket ID: HRF-958294
> > > > > > Department: Support IDV
> > > > > > Priority: Normal
> > > > > > Status: Open
> > > > > > ===================
> > > > > > NOTE: All email exchanges with Unidata User Support are recorded
> > in the
> > > > > > Unidata inquiry tracking system and then made publicly available
> > > > through
> > > > > > the web.  If you do not want to have your interactions made
> > available
> > > > in
> > > > > > this way, you must let us know in each email you send to us.
> > > > > >
> > > > > >
> > > > > >
> > > > >
> > > > >
> > > >
> > > >
> > > > Ticket Details
> > > > ===================
> > > > Ticket ID: HRF-958294
> > > > Department: Support IDV
> > > > Priority: Normal
> > > > Status: Open
> > > > ===================
> > > > NOTE: All email exchanges with Unidata User Support are recorded in the
> > > > Unidata inquiry tracking system and then made publicly available
> > through
> > > > the web.  If you do not want to have your interactions made available
> > in
> > > > this way, you must let us know in each email you send to us.
> > > >
> > > >
> > > >
> > >
> > >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: HRF-958294
> > Department: Support IDV
> > Priority: Normal
> > Status: Closed
> > ===================
> > NOTE: All email exchanges with Unidata User Support are recorded in the
> > Unidata inquiry tracking system and then made publicly available through
> > the web.  If you do not want to have your interactions made available in
> > this way, you must let us know in each email you send to us.
> >
> >
> >
> 
> 


Ticket Details
===================
Ticket ID: HRF-958294
Department: Support IDV
Priority: Normal
Status: Open
===================
NOTE: All email exchanges with Unidata User Support are recorded in the Unidata 
inquiry tracking system and then made publicly available through the web.  If 
you do not want to have your interactions made available in this way, you must 
let us know in each email you send to us.



NOTE: All email exchanges with Unidata User Support are recorded in the Unidata inquiry tracking system and then made publicly available through the web. If you do not want to have your interactions made available in this way, you must let us know in each email you send to us.