Thanks Andy, I was not aware of the examples. Best, Lokman ================================
----- Mail original ----- > De: "Andy Bauer" <[email protected]> > À: "Matthieu Dorier" <[email protected]> > Cc: "ParaView Mailing List [[email protected]]" <[email protected]> > Envoyé: Mercredi 21 Septembre 2016 16:25:36 > Objet: Re: [Paraview] Catalyst: dump everything in C++ > Hi Matthieu, > You can indeed use Catalyst without Python. There are two examples in the > Examples/Catalyst subdirectory of the source tree to do that. They are > CxxVTKPipelineExample and CxxPVSMPipelineExample. I wouldn't recommend this > method as the Python route is much simpler. Several people have thought > about avoiding the Python interface and generally come around to its > flexibility (both ease in creating new Catalyst output as well as making > changes without having to recompile code). > In my opinion, if you're not doing image output the C++ route is manageable > without too much difficulty. For image output there's a lot of things which > need to be set in order to get all the lookup tables, data ranges, camera > angle, etc. that can get quite complex. If you look at a GUI generated > Catalyst script for data extract output and compare it to image output > you'll easily see the difference in the complexity. Also, Cinema output is > Python driven so that wouldn't be available through a C++ pipeline. > Now that I've gone through all of this, is there a specific reason why you're > looking to avoid Python? > Best, > Andy > On Wed, Sep 21, 2016 at 9:27 AM, Dorier, Matthieu < [email protected] > wrote: > > Hi, > > > In general the way we create python scripts for a Catalyst-enabled > > simulation > > is by first running the simulation with a Python script that writes the > > data > > into files, then do offline analysis on those files and export a python > > script representing the analysis tasks to be done in situ. > > > I was wondering if, instead of using a Python script for writing all the > > data > > into file, an equivalent C++ code was available, and how such a code would > > be integrated into a Catalyst-enabled simulation? Or maybe just with VTK > > once the adaptors are written for the simulation's data? > > > Thanks, > > > Matthieu > > > _______________________________________________ > > > 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 > > _______________________________________________ > 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
_______________________________________________ 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
