> The information is present in one data source. > The source is chosen in Data Choosers (Catalog -> Unidata model data -> > NCEP -> Rapid Refresh (RAP) -> Choose any scale or run. > All of this goes smoothly, and all of the information is present in the > same source. The problem is that the IDV, for whatever reason, loads the > temperature information into one Sounding field, and the dewpoint into > another. > Field Selector: 3d grid -> Temperature -> Derived -- And that's where the > problem is. There's two separate choices for Sounding Data (with True > Winds). > > Hope this is clearer! > > Tim Tim, I see the problem. Those derived parameters are based on variable alias table. Since there are three Temperature fields in the 3D, and two of them are recognized as Temperature in this table, the IDV would automatically construct two different sounding variables. One is good, the other will generate error message and you should ignore it. Sorry for the confusion, but I don't have better solution at this moment. Yuan > > > address@hidden> wrote: > > > > Full Name: Tim Carr > > > Email Address: address@hidden > > > Organization: university of missouri > > > Package Version: 4.u1 > > > Operating System: windows 8.1 > > > Hardware: > > > Description of problem: > > > > > > For some reason, all iterations of the RAP model on my machine is > > > separating the Soundings (with true winds) into two files. This is off > > > the NCEP catalog, and it affects all runs on all scales. > > > > > > When you run the two sources, the first (top most) resource will load > > > just temperature while the bottom most will load just dewpoint. > > > > > > > I think the only option left is to use the formula to calculate the > > sounding. > > It is impossible for the IDV to create the derived parameter if this > > derived > > parameter depends on variables from two different data sources. > > > > > > Yuan > > > > > > > > > Ticket Details > > =================== > > Ticket ID: MRU-948171 > > Department: Support IDV > > Priority: Normal > > Status: Closed > > > > > > Ticket Details =================== Ticket ID: MRU-948171 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.