<div dir="ltr">Hi Brian,<div><br></div><div>It is actually relatively easy to achieve what you are after. You need two parallel pipelines:</div><div><br></div><div>- Surface -> Clip</div><div>- Slice</div><div><br></div>
<div>You need to link the plane widget of the Clip and Slice filters such that they are identical.</div><div><br></div><div>Note that although this is visually identical to clipping with a plane, under the covers the outputs are significantly different. This approach produces only the outer shell and is memory efficient. Whereas the clip filter extracts all the cells inside the clip domain and is useful for further process (calculating volume for example).</div>
<div><br></div><div>It is possible to make Clip for structured data more memory efficient by converting only a minimal subset of the output to unstructured data and keeping the rest structured. However, it is decent amount of work to write such a filter and the above solution should be sufficient for most people.</div>
<div><br></div><div>Does this make sense?</div><div><br></div><div>-berk</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Jun 11, 2014 at 12:05 PM, Brian Corrie <span dir="ltr"><<a href="mailto:bcorrie@sfu.ca" target="_blank">bcorrie@sfu.ca</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">Hi David,<br>
<br>
I guess I am a bit surprised at the significant jump in memory, although I suppose I shouldn't be in thinking about it in more detail. Thanks for doing the math 8-)<br>
<br>
Given the above, it isn't really practical to use the clip filter on volume data set sizes of significant size unless you have a mondo big memory computer. At the same time, clipping is a very powerful technique for exploration. It is one of my favorite filters to use when looking at a new dataset.<br>
<br>
Utkarsh suggests using "Extract Subset" or "Slice" but both are somewhat limited compared to an arbitrary clip plane. Extract subset results in clipping only along the data set axes and slice doesn't show internal structure around the slice plane.<br>
<br>
Are there any other alternatives to getting an arbitrary clip plane on a large volume data set without blowing out the memory? Has anyone come up with any clever tricks?<br>
<br>
For me this is mostly curiosity driven, as I am no longer working on the project that sparked my Dec 2012 email, but clearly there are some people that are struggling with this issue still (e.g. Robert).<br>
<br>
Brian<div class=""><br>
<br>
<br>
On 6/10/2014 11:03 AM, David E DeMarle wrote:<br>
</div><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="">
On Tue, Jun 10, 2014 at 12:41 PM, Brian Corrie <<a href="mailto:bcorrie@sfu.ca" target="_blank">bcorrie@sfu.ca</a><br></div><div class="">
<mailto:<a href="mailto:bcorrie@sfu.ca" target="_blank">bcorrie@sfu.ca</a>>> wrote:<br>
<br>
Hi All,<br>
<br>
I have one question regarding this conversation, as I have run into<br>
this issue before. It intrigues me as to why one can't clip a<br>
structured data set efficiently.<br>
<br></div>
<a href="http://www.paraview.org/__pipermail/paraview/2012-__December/026976.html" target="_blank">http://www.paraview.org/__<u></u>pipermail/paraview/2012-__<u></u>December/026976.html</a><div><div class="h5"><br>
<<a href="http://www.paraview.org/pipermail/paraview/2012-December/026976.html" target="_blank">http://www.paraview.org/<u></u>pipermail/paraview/2012-<u></u>December/026976.html</a>><br>
<br>
The question I have is - does clip REALLY require all that memory -<br>
in my case it was a structured grid of 698x693x665 growing to in<br>
excess of 20 GB (see the question on the list above). That seems<br>
pretty excessive given the original size of the data set... I<br>
haven't done the math on the data set size of an unstructured data<br>
set, but 320MB to 20GB is a pretty big step.<br>
<br>
<br>
Very likely.<br>
<br>
imagedata<br>
origin + extent + spacing ~= 36 bytes #(x,y,z + ni,nj,nk + sx,sy,sz) *<br>
4bytes per word<br>
(700^3 * 4)/(1024^3) = 1.27 GB #to store one scalar value on each point<br>
<br>
unstructured grid<br>
points array = (700^3 * 3 * 4)/(1024^3) = 3.8 GB #3=x,y,z, 4=4bytes per word<br>
cellarray = (699^3 * 9 * 4)/*(1024^3) = 11.45GB, #1 numverts + 8 vertex<br>
index<br>
celltype = (699^3 * 4)/(1024^3) = 1.27GB<br>
celllink = (700^3*9*4)/(1024^3) = 11.5GB #1 numcells + 8 using cells per<br>
vert<br>
(700^3 * 4)/(1024^3) = 1.27 GB #to store one scalar value on each point<br>
(Someone check me on all of that please).<br>
</div></div></blockquote><div class="HOEnZb"><div class="h5">
<br>
T<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
But yes, a clip like widget to something like Extract Subset that is<br>
easy to use AND preserves the data type would be a really nice thing to<br>
have in ParaView.<br>
<br>
</blockquote></div></div><div class="HOEnZb"><div class="h5">
______________________________<u></u>_________________<br>
Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/<u></u>opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/<u></u>ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://www.paraview.org/mailman/listinfo/paraview" target="_blank">http://www.paraview.org/<u></u>mailman/listinfo/paraview</a><br>
</div></div></blockquote></div><br></div>