wow, thanks a lot for this! I am on a report deadline at the moment but will
try it afterwards. I guess the easiest way is just to write integers (1, 2, 3
...) as the timesteps to the cgns file which should make the mapping work
without problems. In any case, I will fiddle around a bit with
OK try this. Apply a Programmable Filter to the csv file. Turn on advanced
properties on that panel and use the following scripts:
Script:
oi = self.GetOutputInformation(0)
ut = oi.Get(vtk.vtkStreamingDemandDrivenPipeline.UPDATE_TIME_STEP())
t = inputs[0].RowData['t']
Hi Tom-Robin,
ParaView does not support having a time series of particles within a single
csv file. You can have a file series of csv files as described here:
http://www.paraview.org/Wiki/ParaView/Users_Guide/Loading_Data
Unfortunately, you will not be able to specify a time value in this case.
Hi,
I am doing particle tracking at the moment and I am visualise my results with
paraview. I have a 3D Navier Stokes solver from which I get a CGNS file with
the flow solution (for example velocity and vorticity in x, y and z) and I also
get csv file where I store position of particles,
Marcelo,
Is this using OSMesa for offscreen rendering? There was a memory leak
in 3.10.0 that has been subsequently fixed when saving animations with
OS Mesa and offscreen rendering enabled.
Utkarsh
On Mon, Feb 20, 2012 at 6:23 AM, Marcelo Emmel marc...@emmel.eng.br wrote:
Jean Favre jfavre at
Hi, Utkarsh,
sorry I forgot to replay to the list. I wrote Marcelo yesterday
"Dear Marcelo,
try Edit-Settings-Render View and disable "Use
Offscreenrendering for Screenshots".
The animation will take more time, but the memory ussage is constant
Jean Favre jfavre at cscs.ch writes:
Berk Geveci wrote:
To animate particles in a
steady-state flow field, I'd think that you would generate streamlines
and then somehow animate particles along those.
this is exactly the technique I use. Generate streamlines. Then
iso-contour the
I am wondering what the state of this is? I am very interested in this
feature. Up to new I used Johns workaround but iso-clipping the
streamlines makes my Paraview 3.6.1 crash without any further comment.
Regards
BastiL
I don't think this answers Pei's question. To my knowledge the
temporal
Hi Berk, Jean,
Is this something more than a few users would want?
Yes I would b e very interested, Jeans workaround only works for
streamlines calculated either forwards or backwards but not both
Jean, how do you exactly do please?
-Then iso-contour the streamline object with the scalar
That's great! I've been wondering how to animate streamlines.
Regards,
Paul
2009/2/12 Jean Favre jfa...@cscs.ch
Berk Geveci wrote:
To animate particles in a
steady-state flow field, I'd think that you would generate streamlines
and then somehow animate particles along those.
this is
Berk
Oops. I didn't notice that it was a "steady state" flow field. The
TemporalStremTRacer expects unsteady flows, however it would be quite
simple to modify it to use a single step. (I think easier than taking
streamlines and animating particles along them - though thinking about
it, the
Berk Geveci wrote:
To animate particles in a
steady-state flow field, I'd think that you would generate streamlines
and then somehow animate particles along those.
this is exactly the technique I use. Generate streamlines. Then
iso-contour the streamline object with the scalar field
Interesting. I guess the biggest challenge of doing this in our
pipeline would be finding the time range. Ideally, the integration
should continue until all particles leave the domain or get stuck in a
stagnant region. That would require integrating them first and then
looking at the largest
That's a really cool solution. Bravo Jean.
-Ken
On 2/12/09 6:58 AM, Jean Favre jfa...@cscs.ch wrote:
Berk Geveci wrote:
To animate particles in a
steady-state flow field, I'd think that you would generate streamlines
and then somehow animate particles along those.
this is exactly the
This conversation has basically become academic, but it would also be pretty
easy to create a filter that reported a bunch of time steps and just passed the
same data every time. The particle tracer would thing it was a time varying
data even though it was not.
Jean's solution is still easier
Hi Pei-Ying,
You may want to try ParaView Meshless
(https://twiki.cscs.ch/twiki/bin/view/ParaViewMeshless). It is a
version of ParaView with the cutting edge of John Biddiscombe's
particle tracking work in it. Some of those features will be/have been
integrated into the main paraview code, but I
16 matches
Mail list logo
