<html xmlns:o="urn:schemas-microsoft-com:office:office" xmlns:w="urn:schemas-microsoft-com:office:word" xmlns:m="http://schemas.microsoft.com/office/2004/12/omml" xmlns="http://www.w3.org/TR/REC-html40"><head><meta name=Title content=""><meta name=Keywords content=""><meta http-equiv=Content-Type content="text/html; charset=utf-8"><meta name=Generator content="Microsoft Word 15 (filtered medium)"><style><!--
/* Font Definitions */
@font-face
{font-family:"Cambria Math";
panose-1:2 4 5 3 5 4 6 3 2 4;}
@font-face
{font-family:Calibri;
panose-1:2 15 5 2 2 2 4 3 2 4;}
@font-face
{font-family:MingLiU;
panose-1:2 2 5 9 0 0 0 0 0 0;}
/* Style Definitions */
p.MsoNormal, li.MsoNormal, div.MsoNormal
{margin:0in;
margin-bottom:.0001pt;
font-size:12.0pt;
font-family:"Times New Roman";}
a:link, span.MsoHyperlink
{mso-style-priority:99;
color:blue;
text-decoration:underline;}
a:visited, span.MsoHyperlinkFollowed
{mso-style-priority:99;
color:purple;
text-decoration:underline;}
span.EmailStyle17
{mso-style-type:personal-reply;
font-family:Calibri;
color:windowtext;}
span.msoIns
{mso-style-type:export-only;
mso-style-name:"";
text-decoration:underline;
color:teal;}
.MsoChpDefault
{mso-style-type:export-only;
font-size:10.0pt;}
@page WordSection1
{size:8.5in 11.0in;
margin:1.0in 1.0in 1.0in 1.0in;}
div.WordSection1
{page:WordSection1;}
--></style></head><body bgcolor=white lang=EN-US link=blue vlink=purple><div class=WordSection1><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'>Thank you Andy.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'>We have a unique situation where we would need to know ahead of time what variables are in play with the python scripts. This is due to the way that the simulation code operates (it throws out rules that accumulate all of the attributes that would not be needed before the first iteration is taken). If we can’t tell it which to toss before it starts, then all the variables would be kept.<br><br>With that in mind, I read the discussion. I do see the section that you are referring to in the python script. For example in the CxxFullExample case the script feslicescript.py has;<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'><br>def RequestDataDescription(datadescription):<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> "Callback to populate the request for current timestep"<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> global coprocessor<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> if datadescription.GetForceOutput() == True:<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> # We are just going to request all fields and meshes from the simulation<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> # code/adaptor.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> for i in range(datadescription.GetNumberOfInputDescriptions()):<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> datadescription.GetInputDescription(i).AllFieldsOn()<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> datadescription.GetInputDescription(i).GenerateMeshOn()<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> return<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'><o:p> </o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> # setup requests for all inputs based on the requirements of the<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> # pipeline.<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'> coprocessor.LoadRequestedData(datadescription)<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'><br><br>From my understanding if I just have a single grid, then datadescription.GetNumberOfInputDescriptions() should return 1. So if this example required only “pressure” and “velocity”, how would I change this function to tell say that the fields that are required are “pressure” and “velocity”?<br><br><br><br>Thank you,<o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'>Chris Neal<br><br><o:p></o:p></span></p><p class=MsoNormal><span style='font-size:11.0pt;font-family:Calibri'><o:p> </o:p></span></p><div style='border:none;border-top:solid #B5C4DF 1.0pt;padding:3.0pt 0in 0in 0in'><p class=MsoNormal><b><span style='font-family:Calibri;color:black'>From: </span></b><span style='font-family:Calibri;color:black'>Andy Bauer <andy.bauer@kitware.com><br><b>Date: </b>Wednesday, August 24, 2016 at 3:41 PM<br><b>To: </b>Christopher Neal <chrisneal@snumerics.com><br><b>Cc: </b>Benson Muite via ParaView <paraview@paraview.org><br><b>Subject: </b>Re: [Paraview] General Catalyst questions<o:p></o:p></span></p></div><div><p class=MsoNormal><o:p> </o:p></p></div><div><div><p class=MsoNormal style='margin-bottom:12.0pt'>Look at the discussion at <a href="http://markmail.org/search/?q=paraview+luigi+calori#query:paraview%20luigi%20calori+page:1+mid:i5dxviq6va7simyi+state:results">http://markmail.org/search/?q=paraview+luigi+calori#query:paraview%20luigi%20calori+page:1+mid:i5dxviq6va7simyi+state:results</a> for the current state of the art for not exporting all variables from the adaptor.<o:p></o:p></p></div><p class=MsoNormal>Catalyst can output data extracts. It's in the Writers menu once you load the Catalyst Script Generator plugin.<o:p></o:p></p></div><div><p class=MsoNormal><o:p> </o:p></p><div><p class=MsoNormal>On Wed, Aug 24, 2016 at 2:29 PM, Christopher Neal <<a href="mailto:chrisneal@snumerics.com" target="_blank">chrisneal@snumerics.com</a>> wrote:<o:p></o:p></p><blockquote style='border:none;border-left:solid #CCCCCC 1.0pt;padding:0in 0in 0in 6.0pt;margin-left:4.8pt;margin-right:0in'><div><div><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt'>Hi Catalyst developers,</span><o:p></o:p></p><p class=MsoNormal style='mso-margin-top-alt:auto;mso-margin-bottom-alt:auto'><span style='font-size:11.0pt'><br>Our team has recently succeeded in integrating Catalyst into our code (which would not have been possible without all of your help). Now that the details of getting our data into the VTK format via the adaptor are settled, we are running into new questions about how to effectively utilize Catalyst within our code.<br><br>One question that I have about Catalyst is: Say my code supports 100 optional variables, and I don’t really want to load every single one of those variables into memory if the user is just asking for contours of pressure and velocity. Is there a way to know what variables are in play within the Catalyst Python scripts that were passed to the code? In other words, is there a way to query what variables will be requested by a set of Catalyst scripts before we take our first timestep so that we can set up some rules for loading only the requested variables into the VTK format?<br><br>I also noticed that the Catalyst export state option in ParaView 5.1 appears to be somewhat limited in that it requires me to export either 1.) A live image, 2.) An animation, or 3.) A static screenshot of the current display. What if I created a pipeline that has a final result of a histogram? Is exporting that histogram data not supported currently in the Catalyst export state option? What about just saving the data to *vtu format without exporting any images? I could put a script together to do this, but I’m thinking about what a user would do if they weren’t well versed in the ParaView python scripting language.</span><span style='font-size:11.0pt;font-family:MingLiU'><br><br><br></span><span style='font-size:11.0pt'>Thank you,</span><span style='font-size:11.0pt;font-family:MingLiU'><br></span><span style='font-size:11.0pt'>Chris Neal</span><o:p></o:p></p></div></div><p class=MsoNormal style='margin-bottom:12.0pt'><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 <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: <a href="http://paraview.org/Wiki/ParaView" target="_blank">http://paraview.org/Wiki/ParaView</a><br><br>Search the list archives at: <a href="http://markmail.org/search/?q=ParaView" 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" target="_blank">http://public.kitware.com/mailman/listinfo/paraview</a><o:p></o:p></p></blockquote></div><p class=MsoNormal><o:p> </o:p></p></div></div></body></html>