[Paraview] particletracer, vectors menu?
Berk Geveci
berk.geveci at kitware.com
Thu Feb 14 12:09:17 EST 2008
Awesome! I feel the same way about (7) but I don't think
vtkTemporalStreamTracer will make sense to users. What about
vtkTemporalParticleTracer?
-berk
On 2/14/08, John Biddiscombe <biddisco at cscs.ch> wrote:
> Berk / Charl
>
> I had a quick play this morning and then got involved with other work so
> didn't fix it. I shall attend to this problem very soon, once I've
> finished off data preparation, I need to use the code right away and I'm
> also planning
> 1) Optimizing the FindCell stuff to use spatial locators for
> unstructured data
> 2) Improve and clean up the Cell Cache stuff for static/dynamic meshes
> 3) Multi-threading the main particle trace so I can use all 4 cpus on
> these quad core processors
> 4) Doing particle going backwards in time from seed points at the (time)
> end of the data
> 5) Adding interpolation methods for using particle data as the vector
> field. No cells to do findcell on.
> 6) Other stuff I can't remember
> 7) Tidy up and rename class to vtkParticleTracer (even though I prefer
> all the temporal stuff to be vtkTemporalSomething)
>
>
> JB
>
>
> > This is actually simple to fix. In the filters xml
> > (Servers/ServerManager/Resources/filters.xml), ParticleTracer says it
> > is expecting a vtkTemporalDataSet input. However, in some cases, the
> > input may look like a vtkUnstructuredGrid, for example. The input type
> > for ParticleTracer should be set to vtkDataObject to fix this. I am
> > attaching a patch. I am not sure this is the best way to fix this in
> > the main repository so I am not committing it yet.
> >
> > -berk
> >
> >
> > On 2/13/08, John Biddiscombe <biddisco at cscs.ch> wrote:
> >
> >> I'll play with it first thing tomorrow and find out what's going wrong.
> >>
> >> JB
> >>
> >>
> >>
> >> Hi there John!!
> >>
> >> On Feb 13, 2008 5:50 PM, John Biddiscombe <biddisco at cscs.ch> wrote:
> >>
> >>
> >> TemporalStremTracer actually expects a vtkTemporalDataSet as input, but
> >> the LEA test data is a series of vti files and the generic reader in
> >> PraaView does not export TIME_RANGE so the executive won't allow it to
> >> be used as a temporal dataset.
> >>
> >> I've made a PVD file (see attached) for the LEA VTI files. That seems
> >> to assign a timestep to each frame, is that not sufficient?
> >>
> >> Thanks for having a look,
> >> Charl
> >>
> >>
> >>
> >> --
> >> John Biddiscombe, email:biddisco @ cscs.ch
> >> http://www.cscs.ch/about/BJohn.php
> >> CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07
> >> Via Cantonale, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82
> >>
> >> _______________________________________________
> >> ParaView mailing list
> >> ParaView at paraview.org
> >> http://www.paraview.org/mailman/listinfo/paraview
> >>
> >>
> >>
>
>
>
> --
>
> John Biddiscombe, email:biddisco @ cscs.ch
> http://www.cscs.ch/about/BJohn.php
> CSCS, Swiss National Supercomputing Centre | Tel: +41 (91) 610.82.07
> Via Cantonale, 6928 Manno, Switzerland | Fax: +41 (91) 610.82.82
>
>
>
More information about the ParaView
mailing list