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.
Dave, A second experiment you can try is simply restart RAMADDA when you see this problem. If this (temporarily) fixes the issue, then according to Don Murray, a more permanent solution for this problem is in the latest version of RAMADDA, so upgrade if possible. Please keep us up-to-date on your progress. Best Wishes, Unidata IDV Support > Dave, > > First off, nice bundle. It would be nice to showcase this work possibly in a > screencast. > > This issue is similar to the issue (note the similar stack traces) you > reported earlier so I am hoping to kill a few birds with one stone. > > I am having some difficulty reproducing the issue today (though I did see it > yesterday, and in a different client (toolsui) so I have some reason to > believe that it may be a RAMADDA stale metadata caching problem -- though > that is just a tentative theory at this point.) > > I would like you to do an experiment for me to help isolate the root cause of > this problem. Would it be possible to do exactly the steps you reported > earlier but with the WRF data file local (on your local disk drive) instead > of obtaining it from RAMADDA? In other words, download the file locally, and > view your data in the IDV as normal. Now save your bundle with only the > displays and not the data. Now clear the IDV of all displays and data > (restart if you want), and load your renamed local file WRF datasource. Now > open up your displays only bundle and reattach it to the data just as you > were describing. Do you see the problem you described earlier? > > If no, this *might* indicate a server (RAMADDA) problem. > > We have a skeleton crew at Unidata this week on account of the Thanksgiving > holiday. We will try to get this resolved as quickly as possible. > > Best Wishes, > > Unidata IDV Support > > > > > On Nov 25, 2013, at 6:21 PM, Unidata IDV Support <address@hidden> wrote: > > > > > > > > address@hidden, > > > > > > Your Ticket has been received, and a Unidata staff member will review it > > > and reply accordingly. Listed below are details of this new Ticket. > > > Please make sure the Ticket ID remains in the Subject: line on all > > > correspondence related to this Ticket. > > > > > > Ticket ID: KET-549746 > > > Subject: IDV v.4.1u1: Bundle saved with "No Data" fails to load data > > > from original (but renamed) data source > > > Department: Support IDV > > > Priority: Normal > > > Status: Open > > > > > > > IDV support, > > > > An update on the request for support above: > > > > The IDV bundled saved with “No Data”, and loaded with the original (but > > renamed) data source, succeeded in plotting terrain elevation data (color > > filled and line contours and a vertical profile), but failed to plot all of > > the other (meteorological) fields. Most of the errors were of the sort > > included in the original support request, followed promptly by an “Unable > > to load field: …. “ message; some others were of the “Initializing after > > unpersistence” variety. > > > > — Dave > > > Ticket Details =================== Ticket ID: KET-549746 Department: Support IDV Priority: Normal Status: Open