<div dir="ltr"><div>Yes, I did indeed interpret the question wrong and Ken probably gave you a proper answer.<br><br></div>To finish off my question, the Process ID Scalars filter should only be shown in the GUI if you're running the ParaView server (pvserver) in parallel. Otherwise it's a very boring filter that just wastes compute cycles and memory.<br></div><div class="gmail_extra"><br><div class="gmail_quote">On Fri, Feb 5, 2016 at 2:56 PM, Moreland, Kenneth <span dir="ltr"><<a href="mailto:kmorel@sandia.gov" target="_blank">kmorel@sandia.gov</a>></span> wrote:<br><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div style="word-wrap:break-word;color:rgb(0,0,0);font-size:14px;font-family:Calibri,sans-serif">
<div>
<div>
<div>Rao,</div>
</div>
</div>
<div><br>
</div>
<div>I think you were asking how to get the file ID representing the processor holding the piece in the simulation whereas Andy's instructions tell you the process ID that the parts got loaded into the visualization.</div>
<div><br>
</div>
<div>To get the file ID, go to the properties panel for the Exodus reader and find the property labeled "Generate File Id Array." (The easiest way to find it is to type "generate" in the search bar at the top of the properties panel.) Turn on that checkbox
and ParaView will generate a field named "FileId". Just color by that field and you are good to go.</div>
<div><br>
</div>
<div>-Ken</div>
<div><br>
</div>
<span>
<div style="font-family:Calibri;font-size:11pt;text-align:left;color:black;BORDER-BOTTOM:medium none;BORDER-LEFT:medium none;PADDING-BOTTOM:0in;PADDING-LEFT:0in;PADDING-RIGHT:0in;BORDER-TOP:#b5c4df 1pt solid;BORDER-RIGHT:medium none;PADDING-TOP:3pt">
<span style="font-weight:bold">From: </span>ParaView <<a href="mailto:paraview-bounces@paraview.org" target="_blank">paraview-bounces@paraview.org</a>> on behalf of Andy Bauer <<a href="mailto:andy.bauer@kitware.com" target="_blank">andy.bauer@kitware.com</a>><br>
<span style="font-weight:bold">Date: </span>Friday, February 5, 2016 at 12:27 PM<br>
<span style="font-weight:bold">To: </span>"Garimella, Rao Veerabhadra (LANL)" <<a href="mailto:rao@lanl.gov" target="_blank">rao@lanl.gov</a>><br>
<span style="font-weight:bold">Cc: </span>"<a href="mailto:paraview@paraview.org" target="_blank">paraview@paraview.org</a>" <<a href="mailto:paraview@paraview.org" target="_blank">paraview@paraview.org</a>><br>
<span style="font-weight:bold">Subject: </span>[EXTERNAL] Re: [Paraview] Coloring parallel Exodus II meshes by file/Processor ID<br>
</div><span class="">
<div><br>
</div>
<div>
<div>
<div dir="ltr">
<div>
<div>
<div>HI Rao,<br>
<br>
</div>
The Process Id Scalars creates a field that shows the current partitioning of the grid for pvserver. That may be what you're looking for. If you're looking for the grid partitioning that was used for the simulation, this information would need to be communicated
in the ExodusII file itself. Depending on how things are written out, there should be a block ID available though that you give you this information for certain simulation outputs.<br>
<br>
</div>
<div>Please let me know if this isn't what you're looking for and we can try and see how to get it.<br>
</div>
<div><br>
</div>
Best,<br>
</div>
Andy<br>
</div>
<div class="gmail_extra"><br>
<div class="gmail_quote">On Fri, Feb 5, 2016 at 12:33 PM, Rao Garimella <span dir="ltr">
<<a href="mailto:rao@lanl.gov" target="_blank">rao@lanl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Hi<br>
<br>
I tried looking for this in the archives but did not find anything relevant.<br>
<br>
After importing a distributed mesh from the Exodus II/Nemesis I format<br>
into paraview, how can I ask it to color the elements based on the<br>
file/processor ID that they were read in from?<br>
<br>
Thanks<br>
Rao<br>
_______________________________________________<br>
Powered by <a href="http://www.kitware.com" rel="noreferrer" target="_blank">www.kitware.com</a><br>
<br>
Visit other Kitware open-source projects at <a href="http://www.kitware.com/opensource/opensource.html" rel="noreferrer" target="_blank">
http://www.kitware.com/opensource/opensource.html</a><br>
<br>
Please keep messages on-topic and check the ParaView Wiki at: <a href="http://paraview.org/Wiki/ParaView" rel="noreferrer" target="_blank">
http://paraview.org/Wiki/ParaView</a><br>
<br>
Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" rel="noreferrer" target="_blank">
http://markmail.org/search/?q=ParaView</a><br>
<br>
Follow this link to subscribe/unsubscribe:<br>
<a href="http://public.kitware.com/mailman/listinfo/paraview" rel="noreferrer" target="_blank">http://public.kitware.com/mailman/listinfo/paraview</a><br>
</blockquote>
</div>
<br>
</div>
</div>
</div>
</span></span>
</div>
</blockquote></div><br></div>