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
