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 CJ, The head of the IDV went to NOAA, Climate Services PSD. address@hidden Have you changed your memory allocation in the IDV?It is set at a 512 MB default, and it can be bumped higher if the machine has the RAM. 32 bit machines will only offer 1.5 GB of space for the stack heap, but 64 bit machines can go much higher :)
We have run the IDV with 12 GB of RAM and had great improvement. You would also need to make sure you have the latest (2.9) version installed. Memory inprovements in the underlying Vis5D package have ben incorporated into that build.
Changing units ~should get rid of the 273 Kelvin offset... Let us know how else we can help! Cheers, Jeff --------------------------------------------------------------------- Jeff Weber address@hidden : Unidata Program Center PH:303-497-8676 : University Corp for Atmospheric Research 3300 Mitchell Ln : http://www.unidata.ucar.edu/staff/jweber Boulder,Co 80307-3000 : --------------------------------------------------------------------- On Wed, 2 Jun 2010, CJ Beegle-Krause wrote:
Hi John, IDV questions.Do you know where the IDV programmers that left, um, went to? It's not uncommon for us to bring people back (our contract) for incident specific programming for their application specific knowledge.We're breaking IDV with 100 to 200 particles. It that something that can be changed? This is a long incident....Fixing that low temps get 273 added to them automatically may not be an issue for the Gulf of Mexico, but should would be nice for us oceanographers...Will be sending on a few more standard test files as they are coming in. Best regards, CJ