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.
Hi Randy- > yes...the memory indicator at bottom left shows just > under 3GB. that was the only memory trace we saw. Okay. I'm guessing that it's some point in the rendering where this is happening. I don't have a solution other than to decimate the data taking every other point. > Have you heard of Vapor visualization tool. Also > developed at ucar. We loaded the file into it and it > rendered in about 3 seconds with hardly any memory > usage. However, it was not geolocated. This is why we > want to use IDV. The only thing I know about Vapor is that it wouldn't install on my windows box. I think it only handles grids so you would not be able to compare it with satellite and observational data. Did you have to convert the file into their format before loading? That's interesting about the lack of geolocation. It certainly simplifies the rendering if you don't have to worry about geographic transforms. > any suggestions? would 64bit java correct things? The only other suggestion I have it so turn on Fast Rendering in the User Preferences (under Main View tab). That will avoid some extra memory use. Don Ticket Details =================== Ticket ID: HHW-968552 Department: Support IDV Priority: Normal Status: Open