[Support #DTV-598228]: RE: Model Data and DMAC tasks

Hi Nickitas,


> Tech notes of caution (lessons learned.):
> 
> IDV does not seem to want to capture legends in movie mode without
> obstructing the view. Or it does, and I just don't know how to.
I assume you mean the side legend on the right?
In the movie capture dialog you can select "Full Window" under "What to capture"



> 
> Also, in order to make 2 days of 10-min averages render (this is the new
> NYHOPS temporal resolution), even for the much smaller subdomain displayed,
> we had to increase the Java VM memory that IDV sees to its highest allowed
> for 32bit Windows (1.6MB, set by editing the runIDV.bat file). Hopefully,
> 64bit will work better, esp. with Windows 7 (no commission from MS yet.)
> 

There are a number of things you can do to improve performance:
http://www.unidata.ucar.edu/software/IDV/docs/userguide/misc/PerformanceTuning.html

These mostly revolve around accessing fewer times or less data (e.g., 
subsetting).
However, you can also configure a data source to cache its data, per time step, 
to disk.
The above help page does not describe that (yet) but below is the new writeup:

>For grids and images you can specify that the data for each time step is 
>cached to disk. From the data source >properties dialog select "Always 
>cache to disk". Using this there will be some processing overhead because 
>>the IDV, after reading a grid or image timestep, will write the data to disk. 
>However, the advantage is that only >one time step's worth of data will be 
>held in memory at a time.
>The "Delay" field allows you to specify a delay before the data is 
>removed from memory. For example, if >you are doing an interactive data probe 
>then every time you move the probe the IDV needs to access the data in 
>>memory. If there was no delay then the IDV would have to read the data from 
>disk at every probe movement.


-Jeff



Ticket Details
===================
Ticket ID: DTV-598228
Department: Support IDV
Priority: High
Status: Closed