[Paraview] trouble with Append Attributes

[Andy Bauer]

I think this is the proper behavior. The contour filter isn't scaling
values but only keeps the values for the geometry that gets
isosurfaced/contoured. For example, if the contour result was a point then
the array range would be the field values at that point. If this isn't
clear, I suggest using the calculator filter to create a point data array
based on coordinates. After you contour that you'll see that the range of
the calculator filter result is the same as the domain bounds. You could
also check the value of the array at each point to make sure it still
matches the local coordinate.

Andy

On Wed, Jun 27, 2012 at 11:30 PM, Tom Schoenemann <toms at indiana.edu> wrote:

> I've narrowed it down a bit further. It appears that Contour inexplicably
> rescales ALL the data arrays, even though only one is used to create the
> surface.  When I change the Isosurfaces data range (before applying the
> Contour) to different values (adding different values, adding ranges,
> etc.), this changes the range of the other data array after I "apply".  I
> don't want this other array touched.  I'm not sure why this would be the
> default so I'm suspecting a bug?? Perhaps I'm missing something?
>
> In any case, is there actually a way to have Contour create a surface from
> one data array, but not fuss with the other data array (so that when I have
> the surface colored with this other array, the data don't get completely
> changed from real data to something else)?
>
> -Tom
>
> On Jun 27, 2012, at 10:50 PM, Tom Schoenemann wrote:
>
> Sorry - scratch that. The Append Attributes item DOES claim to have the
> right values.  According to the Information tab, there are 2 data arrays:
> One with scalars representing the stat data, and the other called "surface"
> which ranges from 0 to 1 and was created by the calculator step (see my
> last note).  However, when I make a Contour out of this item, telling it to
> use "surface" to do this, it does indeed make a surface, but it
> inexplicably changes the stat data scalars to a completely new range
> of [127.863, 128.063].  Note that the Append Attributes item claims to have
> this same array with [0, 128.619].
>
> Any ideas? As far as I can tell, Contour inexplicably changes the stat
> data scalar values to a new range.  ???  Is this a bug, or am I doing
> something wrong?
>
> -Tom
>
> On Jun 27, 2012, at 10:36 PM, Tom Schoenemann wrote:
>
> Hi all,
>
> I'm trying to display statistical values in color on a surface.  The stat
> values are in voxels, originally, but are translated from a NIFTI format
> file to a .vtk format.  I've got a binary version of the object (1's where
> the object is, 0's everywhere else). Through comments on this list, I've
> figured out that if I use the calculator to create a copy of the binary
> scalar values (and rename them as something else, e.g., "surface"), and
> then use Append Attributes to combine the stat data scalars with the
> surface scalars (from the binary image), I can then use Contour to make the
> surface (using the "surface" scalars) and then color this surface with the
> stat data scalars.  So far so good.
>
> Here is my problem: When I do Append Attributes, the stat data scalars all
> get changed to a range of 0 to 1, even though the stat data file that was
> used in Append Attributes claims to have values of: [0, 128.619].  So, what
> is going on?  Why is Append Attributes not appending attributes without
> changing their values??
>
> Any ideas?
>
> -Tom
>
>
> _________________________________________________
> P. Thomas Schoenemann
>
> Associate Professor
> Department of Anthropology
> Indiana University
> Bloomington, IN  47405
> Phone: 812-855-8800
> E-mail: toms at indiana.edu
>
> Open Research Scan Archive (ORSA) Co-Director
> Consulting Scholar
> Museum of Archaeology and Anthropology
> University of Pennsylvania
>
> Homepage: http://mypage.iu.edu/~toms/
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
> _________________________________________________
> P. Thomas Schoenemann
>
> Associate Professor
> Department of Anthropology
> Indiana University
> Bloomington, IN  47405
> Phone: 812-855-8800
> E-mail: toms at indiana.edu
>
> Open Research Scan Archive (ORSA) Co-Director
> Consulting Scholar
> Museum of Archaeology and Anthropology
> University of Pennsylvania
>
> Homepage: http://mypage.iu.edu/~toms/
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
> _________________________________________________
> P. Thomas Schoenemann
>
> Associate Professor
> Department of Anthropology
> Indiana University
> Bloomington, IN  47405
> Phone: 812-855-8800
> E-mail: toms at indiana.edu
>
> Open Research Scan Archive (ORSA) Co-Director
> Consulting Scholar
> Museum of Archaeology and Anthropology
> University of Pennsylvania
>
> Homepage: http://mypage.iu.edu/~toms/
>
>
>
>
>
>
>
>
>
>
> _______________________________________________
> Powered by www.kitware.com
>
> Visit other Kitware open-source projects at
> http://www.kitware.com/opensource/opensource.html
>
> Please keep messages on-topic and check the ParaView Wiki at:
> http://paraview.org/Wiki/ParaView
>
> Follow this link to subscribe/unsubscribe:
> http://www.paraview.org/mailman/listinfo/paraview
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://www.paraview.org/pipermail/paraview/attachments/20120628/1298c388/attachment-0001.htm>