NOTICE: This version of the NSF Unidata web site (archive.unidata.ucar.edu) is no longer being updated.
Current content can be found at unidata.ucar.edu.
To learn about what's going on, see About the Archive Site.
Gilbert, Thanks for your help. I'm supporting several field campaigns right now so I'll have to wait to upgrade to a new version. I may be able to install the new version on a vm that I can use for everything else once my field campaigns are over. I haven't run ldm on a vm so I don't know if that is problematic or not but it is a possibility. Thanks again for your help! Greg On Wed, Apr 19, 2017 at 9:42 PM, Gilbert Sebenste <gilbert@xxxxxxx> wrote: > Hi Greg, > > OK. For CIDD, the second step should not be necessary if you can already > visualize the data just fine, minus the issue here. > > I can tell you that problem was fixed in the LDM 6.13 series. I wanted to > rule out to make sure that there was nothing else causing a complication > first. Is there any chance you could do an upgrade to 6.13.6, and fail back > over to the old version if things go haywire? > > Also, If it installs fine, I believe your load average should be > noticeably smaller as well. > > Gilbert > > On Apr 19, 2017, at 10:03 PM, Greg Stossmeister <gstoss@xxxxxxxx> wrote: > > Gilbert, > We are still using LDM 6.11.2 - a ways behind I know. I'm not sure > what you mean by coding software - how we are looking at the data? We are > using an NCAR package called CIDD for visualizing the data. I think the > problem may be I'm not saving these files in a two-step process as > described here: https://www.unidata.ucar.edu/data/radar.html I'm only > using the first pattern. > > Thanks, > Greg > > On Wed, Apr 19, 2017 at 8:56 PM, Gilbert Sebenste < > gilbert@xxxxxxxxxxxxxxxx> wrote: > >> Hi Greg, >> >> I haven't noticed it. What version of LDM and the coding software are you >> using? Just curious. >> >> Gilbert >> >> >> On Apr 19, 2017, at 9:14 PM, Greg Stossmeister <gstoss@xxxxxxxx> wrote: >> >> We've recently discovered that we are missing roughly a third of the >> beams from the highest elevation scan in the level 2 data we are receiving. >> We've seen this with every NEXRAD we've randomly checked. This also seems >> to have been going on for quite some time - > months. We are trying to >> figure out the cause. Has anyone else noticed this in the level 2 data? >> >> Thanks, >> Greg >> >> Greg Stossmeister >> Interim Facility Manager >> Data Management & Services Facility >> NCAR/Earth Observing Laboratory >> 303.497.8692 <(303)%20497-8692> >> gstoss@xxxxxxxx >> >> >> _______________________________________________ >> NOTE: All exchanges posted to Unidata maintained email lists are >> recorded in the Unidata inquiry tracking system and made publicly >> available through the web. Users who post to any of the lists we >> maintain are reminded to remove any personal information that they >> do not want to be made public. >> >> >> ldm-users mailing list >> ldm-users@xxxxxxxxxxxxxxxx >> For list information or to unsubscribe, visit: >> http://www.unidata.ucar.edu/mailing_lists/ >> >> > _______________________________________________ > NOTE: All exchanges posted to Unidata maintained email lists are > recorded in the Unidata inquiry tracking system and made publicly > available through the web. Users who post to any of the lists we > maintain are reminded to remove any personal information that they > do not want to be made public. > > > ldm-users mailing list > ldm-users@xxxxxxxxxxxxxxxx > For list information or to unsubscribe, visit: > http://www.unidata.ucar.edu/mailing_lists/ > >
ldm-users
archives: