I added the particle writing as a "stub" so that the user can define his own writing class. simply create a writer sub-classed from vtkAbstractParticleWriter http://www.vtk.org/doc/nightly/html/classvtkAbstractParticleWriter.html override the WriteData function, and add it to your build, then set it manually in the constructor of the temporal stream tracer (or other suitable place using SetParticleWriter)
JB > -----Original Message----- > From: paraview-boun...@paraview.org [mailto:paraview-boun...@paraview.org] > On Behalf Of Florian Rathgeber > Sent: 07 June 2010 14:54 > To: Andy Bauer > Cc: paraview@paraview.org > Subject: Re: [Paraview] Particle tracer: output particle coordinates for > every time step to file? > > Hi, > > Thank you, that works, but gives me lots of data I don't actually need. > I would rather have something more concise. > > Is anybody more familiar with the particle tracer and can tell what this > particle writing is supposed to do and how to get it to work? > > Florian > > On 04.06.2010 23:03, Andy Bauer wrote: > > Hi, > > > > I'm not sure how the enable particle writing works in that filter. I > > would just use either the VTK legacy writer or VTK Polydata file writer > > and check "Write all timesteps as file-series.". You'll get a series of > > files from that. > > > > Andy > > > > On Fri, Jun 4, 2010 at 10:19 AM, Florian Rathgeber <f...@kth.se > > <mailto:f...@kth.se>> wrote: > > > > Hi! > > > > I am looking for a way to output the 3D particle coordinates computed > by > > the particle tracer to a file for every time step. > > > > The particle tracer has this option "Enable Particle Writing", but > > giving a filename and checking the box gave no result. I thought this > > might be the feature I am looking for, but I couldn't find any > > documentation (apart from the interface). > > > > Does it do what I want? And if so, how? And if not, is there another > way > > to get the coordinates (potentially using the python interface?) > > > > I am grateful for any hints and tips, > > Florian > > _______________________________________________ > > Powered by www.kitware.com <http://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 > > > > Follow this link to subscribe/unsubscribe: > > http://www.paraview.org/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 > > Follow this link to subscribe/unsubscribe: > http://www.paraview.org/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 Follow this link to subscribe/unsubscribe: http://www.paraview.org/mailman/listinfo/paraview