[Paraview] Fwd: PV 2.0.0 - problem w/ scalar range of contour filter?

[Amy Squillacote]

Hi Randy,

Thank you for reporting this bug.  It seems that when you try to apply a 
second contour filter to the data, only the second scalars array 
(StagnationEnergy) is available.  It's range (0.0 to 0.0) is correct, but 
the other array (Density) should also be available.  This problem occurs in 
ParaView 2.0 as well as in the current development version.  I will add it 
to ParaView's bug tracker (http://www.paraview.org/Bug/) and look into it 
shortly.

- Amy

At 10:17 AM 4/29/2005, Randy Hudson wrote:
>At 4/29/2005 07:44 AM, Amy Squillacote wrote:
> >Hi Randy,
> >
> >Can you provide any more information about the steps you took that put 
> ParaView into the state you described?  I tried to reproduce the problem 
> using the vox8_bin.vtk data set included in the ParaView release, but I 
> had no problems with the scalar range for the contour.
> >
> >- Amy
>
>
>I used multicomb_0.vts data, which comes w/ paraview.
>
>After reading the data, I clicked on its entry in the Selection Window and 
>then clicked on the icon at the top of the GUI for isolines and 
>isosurfaces -- the one with image of the concentric hemispheres.  I moved 
>the "Add value" slider of the contour filter's "Parameters" tab and 
>clicked "Add".  Then I clicked "Accept".  An isosurface appeared.
>
>For the 2nd isosurface, I clicked on the dataset's entry in the Selection 
>Window and then clicked on the icon at the top of the GUI for isolines and 
>isosurfaces again. At this point, the "Scalars" menu and the data range 
>widget were already invalid..
>
>
> >At 01:33 PM 4/28/2005, Randy Hudson wrote:
> >
> >
> >>Ignore my 2nd mail.  I HAD meant to describe using multiple contour 
> filters of the dataset for the SAME scalar.
> >>
> >>Also, I tested the downloaded executable of pv1.8.3 against that of 
> pv2.0.0, and pv1.8.3 does not have the problem.  I tested it on the 
> multicomb_0.vts data that comes w/ paraview.  I created 3 contour filters 
> of the Density scalar, and in 1.8.3, the "Parameters" tab of each filter 
> shows the same value range, whereas in 2.0.0, only that of the 1st 
> contour shows that range.
> >>
> >>
> >>>Date: Thu, 28 Apr 2005 09:33:54 -0500
> >>>To: paraview at paraview.org
> >>>From: Randy Hudson <hudson at mcs.anl.gov>
> >>>
> >>>
> >>>I forgot to make clear that I was talking about isosurfaces of 
> multiple scalar variables, and not multiple surfaces of the same variable....
> >>>
> >>>
> >>>>Date: Wed, 27 Apr 2005 10:14:52 -0500
> >>>>To: paraview at paraview.org
> >>>>From: Randy Hudson <hudson at mcs.anl.gov>
> >>>>
> >>>>
> >>>>(This email describes (with one exception) results of running the 
> paraview 2.0.0 executable I downloaded from the paraview web page, but 
> I'm having similar problems with the paraview 2.0.0 source I'm changing 
> with and building....)
> >>>>
> >>>>There seems to be a problem with (at least) the "Scalar Range:" and 
> "Scalars" widgets of the "Parameters" page of the contour filter.
> >>>>
> >>>>All seems fine for the first isosurface I create of some 
> data.  Assume the isovalue I've chosen is "ISO_ONE".
> >>>>
> >>>>But, if I then select the data in the Selection Window and try to 
> create a second isosurface of it, the "Scalars" menu contains "None", 
> instead of the name of the 1st scalar, and the scalar range is "Invalid 
> Data Range".  (In the paraview whose source I'm working with, the range 
> is "<ISO_ONE> to <ISO_ONE>".
> >>>>
> >>>>If I "Accept" the second isovalue, paraview crashes and the call 
> stack in Visual Studio lists "VTKPATENTED" a couple times.
> >>>>
> >>>>If this can be fixed by a simple source change, please tell me what 
> that is so I can fix the source I'm working with, rather than downloading 
> a new release.
> >>>>
> >>>>Thanks.
> >>
> >>
> >>Randy.
> >>630 252 8690.
> >>
> >>_______________________________________________
> >>ParaView mailing list
> >>ParaView at paraview.org
> >>http://www.paraview.org/mailman/listinfo/paraview
>
>
>Randy.
>
>"I awaken each day in a mood not of happiness or confidence, but in one of 
>barely-concealed irritation and foreboding at what foolishness, knavery 
>and hokum I'm about to see in the world about me.
>
>I'm seldom disappointed."
>
>                                                             Kim du Toit.