[Paraview] General Catalyst questions

[Christopher Neal]

Thank you Andy.

 

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.

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;


def RequestDataDescription(datadescription):

    "Callback to populate the request for current timestep"

    global coprocessor

    if datadescription.GetForceOutput() == True:

        # We are just going to request all fields and meshes from the simulation

        # code/adaptor.

        for i in range(datadescription.GetNumberOfInputDescriptions()):

            datadescription.GetInputDescription(i).AllFieldsOn()

            datadescription.GetInputDescription(i).GenerateMeshOn()

        return

 

    # setup requests for all inputs based on the requirements of the

    # pipeline.

    coprocessor.LoadRequestedData(datadescription)



>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”?



Thank you,

Chris Neal


 

From: Andy Bauer <andy.bauer at kitware.com>
Date: Wednesday, August 24, 2016 at 3:41 PM
To: Christopher Neal <chrisneal at snumerics.com>
Cc: Benson Muite via ParaView <paraview at paraview.org>
Subject: Re: [Paraview] General Catalyst questions

 

Look at the discussion at http://markmail.org/search/?q=paraview+luigi+calori#query:paraview%20luigi%20calori+page:1+mid:i5dxviq6va7simyi+state:results for the current state of the art for not exporting all variables from the adaptor.

Catalyst can output data extracts. It's in the Writers menu once you load the Catalyst Script Generator plugin.

 

On Wed, Aug 24, 2016 at 2:29 PM, Christopher Neal <chrisneal at snumerics.com> wrote:

Hi Catalyst developers,


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.

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?

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.


Thank you,
Chris Neal


_______________________________________________
Powered by www.kitware.com

Visit other Kitware open-source projects at http://www.kitware.com/opensource/opensource.html

Please keep messages on-topic and check the ParaView Wiki at: http://paraview.org/Wiki/ParaView

Search the list archives at: http://markmail.org/search/?q=ParaView

Follow this link to subscribe/unsubscribe:
http://public.kitware.com/mailman/listinfo/paraview

 

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://public.kitware.com/pipermail/paraview/attachments/20160824/12e4d3ff/attachment.html>