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.
> > > I also created a bundle with the test data I have been using that is > > almost as similar as to what the user is displaying, if this will help: > > ftp://ftp.ssec.wisc.edu/pub/incoming/time-animation.zidv > > Jessica, The problem stems from the lightning data. There are 277000 observations and the user is using the time accumulation in the point data display to show 1 minutes worth of lightning at each animation step. The way this is implemented is that at every animation step we go and figure out what needs to be shown. This is also using alot of memory which may be causing the garbage collector to run. The odd thing about the point data is that we can't read it as a point netcdf dataset but rather your user (as a work around) is reading it in as a trajectory. If we could read it in as point data then the data could be binned, thus removing the need to do the above work when animating. We're looking into why the data can't be read as point data. -Jeff Ticket Details =================== Ticket ID: YPH-121185 Department: Support IDV Priority: Normal Status: Open