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

[IDV #ANC-313982]: related to 3d grid datasources

This archive contains answers to questions sent to Unidata support through mid-2025. Note that the archive is no longer being updated. We provide the archive for reference; many of the answers presented here remain technically correct, even if somewhat outdated. For the most up-to-date information on the use of NSF Unidata software and data services, please consult the Software Documentation first.

  • Subject: [IDV #ANC-313982]: related to 3d grid datasources
  • Date: Tue, 22 Oct 2013 09:38:42 -0600
> Just a teaser.. How the tickets are closed? For example the current one
> ;-)....
> 
> ghansham
> 

We are expecting you providing the fix promptly. I can let it open if you 
prefer this way. :)


Yuan
> 
> address@hidden> wrote:
> 
> > > Actually the same issues also apply for times tab too.I will try to
> > handle
> > > those issues may be first by writing a plugin for insat3d sounder profile
> > > output then will try to see how this can be used in core idv code.
> > > I hope you understand. I am really caught up in lots of other work.
> > > Meanwhile another query can we run idv in imageserver mode as a service
> > on
> > > linux in /etc/init.d which starts at system startup.
> > > Ghansham
> >
> > Ghansham,
> >      I think the RAMADDA server does something similar to this.
> >
> >
> > Yuan
> > >
> > > address@hidden> wrote:
> > > > Ghansham,
> > > >
> > > > We confirm the problems you describe. We will have to put it on the to
> > do
> > > list, unless you would like to provide us a fix. :-)
> > > >
> > > > Best Wishes,
> > > >
> > > > Unidata IDV Support
> > > >
> > > >> R/sir
> > > >>
> > > >> I think this is more of a design issue or I am ignorant. Can we
> > select a
> > > >> set of pressure levels that aren't contiguous from data selector
> > > component.
> > > >> I tried pressing control key to select non contiguous levels. I am
> > using
> > > >> 4.1u1. Another one is that inside geogrid code, the flatfield is made
> > > >> corresponding to all pressure levels when any one pressure level is
> > > >> selected to allow user to cycle through levels but I feel this is
> > > >> inefficient and wastage of memory for a sample test case like this.
> > > >> Lets suppose if a user wants to load grids for 4 different pressure
> > > levels
> > > >> in a 4 pane display he shall be creating four flatfields using all
> > > pressure
> > > >> levels. Even if user wants to load all pressure levels, he can do by
> > > >> choosing "All Levels" from levels data selection component. Am I able
> > > >> communicate clearly?
> > > >> Regards
> > > >> Ghansham
> > > >>
> > > >>
> > > >
> > > >
> > > > Ticket Details
> > > > ===================
> > > > Ticket ID: ANC-313982
> > > > Department: Support IDV
> > > > Priority: Normal
> > > > Status: Open
> > > >
> > > >
> > >
> > >
> >
> >
> > Ticket Details
> > ===================
> > Ticket ID: ANC-313982
> > Department: Support IDV
> > Priority: Normal
> > Status: Closed
> >
> >
> 
> 


Ticket Details
===================
Ticket ID: ANC-313982
Department: Support IDV
Priority: Normal
Status: Open