20050224: IDV - isosurface bug or feature?

>From: Dave Santek <address@hidden>
>Organization: SSEC
>Keywords: 200502242017.j1OKH3v2023191  IDV formulas

Hi Dave-

>My workaround is fine for now....thanks for the explanation.

Okay.

>But, now I have another issue. I went through and set the isosurface 
>values for pairs of time steps. I did levels something like: 5, 10, 15, 
>20, 45. [I don't recall exactly what they were]. I did a File->Save As 
>so I could bring it back later. But, when I open this xidv file, things 
>are different! The isosurface values are now set to: 117, 141, 139, 149, 
>and 45. And, instead of having different isosurface values on different 
>frames [this probably isn't the correct term], it looks like all the 
>different levels are on every frame.

The problem is that the time subselections are not getting 
saved, so it was going through all of the timesteps for each
isosurface display.  Thanks for finding this bug.  The fix
will be in the next release (mid-March).  Unfortunately, you
would have to make a new bundle for this fix to take effect.
The current bundle didn't save the time subsetting.

Because of this bug, the range of the values for each isosurface
display is the now difference along the entire time sequence 
rather than just the subsets before.  You should see that
the range in the sliders is the same in each display now.
We had a bug that someone else at SSEC uncovered where the
value for the isosurface was not getting set correctly when
the range was small.  We were using a percentage of the
slider range, but this was recently fixed.  In your case,
now that the range is larger, the percentage gives higher
values.  This should be fixed in the next release.

>Also, when I restored the xidv, I got these errors:
>=========================================================
>java.lang.Exception: Stack trace
>         at java.lang.Thread.dumpStack(Unknown Source)
>         at javax.swing.SwingGraphics.createSwingGraphics(Unknown Source)
>         at javax.swing.JComponent._paintImmediately(Unknown Source)
<snip>
>In paintImmediately null graphics

This is a harmless error.  It's something in Java 3D and we have
not been able to track down the exact cause (and therefore no
solution).

>============================================================
>
>I didn't see these errors when I generated the loop in the first place. 
>Also, I generated the loop on my laptop without an external monitor. Now 
>I'm viewing it attached to a monitor.

That shouldn't matter in this case.  If you have different screen 
resolutions, you can run into problems because the bundle saves off 
the window positions.

Don
NOTE: All email exchanges with Unidata User Support are recorded in the
Unidata inquiry tracking system and then made publicly available
through the web.  If you do not want to have your interactions made
available in this way, you must let us know in each email you send to us.