Hi, The XML readers and writers don't properly support time so currently the best way would be to create a pvd file which would contain the time and time step information. I don't know of anything in VTK or ParaView that writes out pvd files (I only see a vtkPVDReader in ParaView) but the format is meant to be simple. I would suggest doing it directly in the Catalyst Python script through some Python library as the best workaround for now.
On Thu, Sep 28, 2017 at 3:08 PM, Hermano Lustosa <hllust...@gmail.com> wrote: > Ohh I see... > > Just another quick question. Currently, I am creating a series of VTU and > VTI files whose names follow the pattern mysimulation-t%d. With %d being > replaced by an integer index identifying the time step. I am about to code > a simple PVD writer to consolidate the output and also to assign the real > time step value in seconds instead of maintaining this integer index. > > It doesn't seem to be very hard to create this PVD file by hand, but I was > just wondering if there is something in the VTK library that could > automatically create these files for me. I still could not understand how I > can assign the real time step in seconds to a file, don't know if its even > possible with VT? files. If this is possible, some directions that could > help me implement that would be very nice! > > Thanks once again! > > > > > > On Thu, Sep 28, 2017 at 3:50 PM, Andy Bauer <andy.ba...@kitware.com> > wrote: > >> Hi, >> >> The TemporalStatistics filter (or any other filter that iterates through >> time steps) doesn't currently work with Catalyst. We hope to change this in >> the future but because of the way that the ParaView pipeline works it makes >> it a non-trivial change. >> >> Andy >> >> On Thu, Sep 28, 2017 at 2:40 PM, Hermano Lustosa <hllust...@gmail.com> >> wrote: >> >>> I have doubt about using paraview catalyst from my simulation code. >>> Suppose I created a simple Paraview pipeline containing the >>> TemporalStatistics filter only. >>> >>> Initially, it is not clear for which "dummy" source is adequate for the >>> script. I used a simple programmable source or even a unstructured cell >>> types source to create the python script. Then, I call the script from >>> catalyst in my code like this: >>> >>> for each time step >>> update grid; >>> create data description; >>> call coprocessing method; >>> >>> The problem is that I expect the TemporalStatistics filter to create a >>> single file containing the statistics for all the time steps. However, this >>> approach creates a file for every time step. What I should do in the >>> catalyst (or during the script creation) to have a single output for this >>> filter. >>> >>> Thanks in advance. >>> >>> >>> >>> >>> >>> _______________________________________________ >>> 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