[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

20050526: IDV - Batch processing

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.

  • Subject: 20050526: IDV - Batch processing
  • Date: Fri, 27 May 2005 14:13:50 -0600
I've narrowed this down a bit more, and made my example easier to understand. I have 2 grib files: 
chop.pgbanl.fnl.2004081012
chop.pgbanl.fnl.2004081600


Dave,
Thanks for the files and the narrowing down. This is a side effect of a small, yet dumb, design decision on our part. The isosurface value is saved in the bundle as a percent. This percent is applied to the min-max range of the data to find the actual isosurface value. Unfortunately I cannot think of a work around. We will get this fixed in the next release which is occuring in 
early June.
Thanks again for the files and example bundles. They really helped tracking this down. 

-Jeff