<div dir="ltr">Well then let me explain I'm hoping to achieve. Maybe there is a better to achieve what I'm trying to do.<div><br></div><div>I am trying to visualize the parallel partitioning in my application (not paraview) by moving separate partitions to different locations. Initially I was doing this by creating threshold filters on the pvtu file that was pointing to individual vtu files. For some reason PV runs out of memory when doing that even though I'm doing this on a large number of processors (100M unstructured grid partitioned among 256 processors and visualized using paraview on 128 processors).</div>
<div><br></div><div>Anyway since that did not work, I though I would avoid the thresholds altogether and load individual vtu files manually to have control over individual pieces. It seems that if I use pvd instead of pvtu I can also have access over individual parts using ExtractBlock filter but I'm not sure if that would be any different than using the threshold filter ... which did not work.</div>
<div><br></div><div>Is there any better way of achieving what I'm trying to do here?</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Wed, Apr 16, 2014 at 11:42 AM, Utkarsh Ayachit <span dir="ltr"><<a href="mailto:utkarsh.ayachit@kitware.com" target="_blank">utkarsh.ayachit@kitware.com</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">It's unclear if the readers are being deleted and their memory<br>
released based on what you say and hence not sure what could be<br>
causing the problem. Another thing to try maybe the following:<br>
<br>
+ Create a .vtm file that refers all of the vtu files. Attached file<br>
shows the format. just add <DataSet /> elements for each of the files<br>
with correct index. Note the file paths are relative to the vtm file.<br>
+ Now open this and contour it. In parallel, ParaView will read each<br>
vtu file separately on each of the processes.<br>
<span class="HOEnZb"><font color="#888888"><br>
Utkarsh<br>
</font></span><div class="HOEnZb"><div class="h5"><br>
On Wed, Apr 16, 2014 at 1:00 PM, Mohammad Mirzadeh <<a href="mailto:mirzadeh@gmail.com">mirzadeh@gmail.com</a>> wrote:<br>
> When does the distribution happen?<br>
><br>
> I have a loop in which I load individual vtu files, then create a contour<br>
> and then go to next vtu file. After all the files are load3d and the<br>
> contours created I issue a render and that when PV crashes.<br>
><br>
> Also if I run pvbatch with --symmetric option, can I directly load vtu files<br>
> on each process and work with the contours in parallel?<br>
><br>
> On Apr 16, 2014 6:51 AM, "Utkarsh Ayachit" <<a href="mailto:utkarsh.ayachit@kitware.com">utkarsh.ayachit@kitware.com</a>><br>
> wrote:<br>
>><br>
>> For *.vtu files, ParaView reads the data on the 0th node and then<br>
>> partitions and redistributes it to all ranks.<br>
>><br>
>> On Tue, Apr 15, 2014 at 7:00 PM, Mohammad Mirzadeh <<a href="mailto:mirzadeh@gmail.com">mirzadeh@gmail.com</a>><br>
>> wrote:<br>
>> > just asking this question in a different way. What happens if I load a<br>
>> > vtu<br>
>> > file in parallel? Can paraview handle that automatically (i.e.<br>
>> > partitioning<br>
>> > it and sending it to different processors) or is every processor going<br>
>> > to<br>
>> > load the same exact file?<br>
>> ><br>
>> ><br>
>> > On Thu, Apr 10, 2014 at 6:10 PM, Mohammad Mirzadeh <<a href="mailto:mirzadeh@gmail.com">mirzadeh@gmail.com</a>><br>
>> > wrote:<br>
>> >><br>
>> >> Hi,<br>
>> >><br>
>> >> I have a modest size problem, 100M unstructured, and I can easily load<br>
>> >> into paraview with 64 processors / 128G ram when I load the pvtu file.<br>
>> >><br>
>> >> I can also work on the file, meaning creating contours, etc. However,<br>
>> >> when<br>
>> >> I load all vtu files separately and create contours on each file<br>
>> >> separately<br>
>> >> it seems that PV runs out of memory and my process gets terminated.<br>
>> >><br>
>> >> Is this normal?<br>
>> >><br>
>> ><br>
>> ><br>
>> > _______________________________________________<br>
>> > Powered by <a href="http://www.kitware.com" target="_blank">www.kitware.com</a><br>
>> ><br>
>> > Visit other Kitware open-source projects at<br>
>> > <a href="http://www.kitware.com/opensource/opensource.html" target="_blank">http://www.kitware.com/opensource/opensource.html</a><br>
>> ><br>
>> > Please keep messages on-topic and check the ParaView Wiki at:<br>
>> > <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/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/mailman/listinfo/paraview</a><br>
>> ><br>
</div></div></blockquote></div><br></div>