<div dir="ltr"><div><div>Hi,<br><br></div>The points and point data are considered separate for each grid in the multiblock. Although the points can be shared it is assumed that they aren't. Also, the Programmable filter makes a deep copy (VTK parlance for a full memory copy) of all of its input to make it easier not to modify a filter's input (a no-no in VTK) so at this point it means that even if the input multiblock was sharing the point locations array as well as point data arrays, the output will definitely not be sharing this information.<br>
<br></div>Regards,<br>Andy<br></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Fri, Oct 18, 2013 at 7:58 AM, <span dir="ltr"><<a href="mailto:dennis_conklin@goodyear.com" target="_blank">dennis_conklin@goodyear.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><font face="sans-serif">Andy,</font>
<br>
<br><font face="sans-serif">A typical rookie mistake. I was
combining composite data set examples and non-composite examples from the
wiki, and I got my output and my block intermixed. It's very obvious
now that you pointed it out.</font>
<br>
<br><font face="sans-serif">Thanks very much, that works fine now.
</font>
<br>
<br><font face="sans-serif">One question if I may: since Nodes
(or points) are common to multiple blocks at block boundaries I'm surprised
that something strange didn't happen when I assigned PointData to some
points multiple times - once for each block they are contained in. It
also seems strange that there isn't some master POINTS array of all points
in the composite data set that I could have operated on, especially as
I did nothing to the cells and it seems the blocks are mostly a cell thing.
Am I missing something there? How are points common to different
blocks handled?</font>
<br>
<br><font face="sans-serif">Thanks again</font>
<br><div class="im">
<br><font size="1" color="#002060" face="Verdana"><b>Dennis Conklin</b><i><br>
<b>RDE & Q Senior Engineer </b></i></font>
<br><font size="1" color="#002060" face="Verdana"><b><i>Engineering Mechanics</i></b><i><br>
</i>The Goodyear Tire & Rubber Company</font>
<br><font size="1" color="#002060" face="Verdana">200 Innovation Way, Akron,
OH 44316<br>
phone.<a href="tel:330-796-5701" value="+13307965701" target="_blank">330-796-5701</a><br>
<a href="mailto:dennis_conklin@goodyear.com" target="_blank">dennis_conklin@goodyear.com</a></font>
<br>
<br><img src="cid:_2_076E4A88076E481C0041D0FD85257C08">
<br>
<br>
<br>
<br></div><font size="1" color="#5f5f5f" face="sans-serif">From:
</font><font size="1" face="sans-serif">Andy Bauer <<a href="mailto:andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a>></font>
<br><font size="1" color="#5f5f5f" face="sans-serif">To:
</font><font size="1" face="sans-serif"><a href="mailto:dennis_conklin@goodyear.com" target="_blank">dennis_conklin@goodyear.com</a></font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Cc:
</font><font size="1" face="sans-serif">"<a href="mailto:paraview@paraview.org" target="_blank">paraview@paraview.org</a>"
<<a href="mailto:paraview@paraview.org" target="_blank">paraview@paraview.org</a>></font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Date:
</font><font size="1" face="sans-serif">10/17/2013 01:19 PM</font>
<br><font size="1" color="#5f5f5f" face="sans-serif">Subject:
</font><font size="1" face="sans-serif">Re: [Paraview]
Programmable Filter Help, Part 2</font>
<br>
<hr noshade><div class="HOEnZb"><div class="h5">
<br>
<br>
<br><font size="3">Hi,<br>
</font>
<br><font size="3">Where did you get the example from? <br>
</font>
<br><font size="3">I think your confusion is from the difference between
multiblock data sets and regular data sets. The regular data set has points
and the Programmable Filter gives a shortcut to access those points by
using inputs[0].Points and output.Points but there is no concept of a group
of points in a multiblock data set, only in the regular data set blocks
of the multiblock data set. So for the process_block() method you'll want
to do a block.GetPoints() to get the points. To make it more efficient
you can use numpy. An example is at </font><a href="http://www.paraview.org/Wiki/Python_Programmable_Filter#Center_Data_using_numpy" target="_blank"><font size="3" color="blue"><u>http://www.paraview.org/Wiki/Python_Programmable_Filter#Center_Data_using_numpy</u></font></a><font size="3">.
<br>
</font>
<br><font size="3">You can add print statements in the script but they'll
be outputted to the output window (Tools->Output Window).</font>
<br>
<br><font size="3">Regards,<br>
Andy </font>
<br><font size="3"><br>
</font>
<br><font size="3">On Thu, Oct 17, 2013 at 10:35 AM, <</font><a href="mailto:dennis_conklin@goodyear.com" target="_blank"><font size="3" color="blue"><u>dennis_conklin@goodyear.com</u></font></a><font size="3">>
wrote:</font>
<br><font size="3" face="sans-serif">My original post was truncated into
oblivion, so here is my Second attempt.</font><font size="3"> <br>
</font><font size="3" face="sans-serif"><br>
I'm trying to put together a Programmable filter that will add arrays of
deformed and undeformed coordinates and undeformed angles to my PointData
in 4.0.1</font><font size="3"> <br>
</font><font size="3" face="sans-serif"><br>