Visualise pathlines in PV12

Claudio Wolfer's picture
Submitted by Claudio Wolfer on Mon, 01/30/2012 - 09:01

Hi

In PV12 I'm trying to visualize the pathlines from three particles (s. attachment). The problem is, that PV draws lines from a particle path to another particle path (left lower corner). This is not the path from the particle. Each particle should have a continuous smooth pathline.

How can I visualize pathlines in PV without these interrupts?

Cheers
Claudio

AttachmentSize
Image icon pathlines.png5.73 KB
Nucleophobe's picture

Nucleophobe | Mon, 04/27/2015 - 12:52

Just bumping Claudio's question from a few years ago.

Does anyone know how to visualize particle pathlines from VTK output (e.g., the output from LPP)? The 'particle path' and 'particle trace' filters in ParaView are intended for extracting paths from Eulerian velocity fields. I do not see a filter intended for Lagrangian particles like we have in LIGGGHTS, but I imagine someone has figured out a way to do this.

Thanks!
-Nuc

Nucleophobe's picture

Nucleophobe | Wed, 04/29/2015 - 05:20

Thanks richti83 for the response.

I tried the suggested filter (Temporal particles to pathlines), but instead of drawing pathlines, the filter produces a set of lines connecting the particle positions at each time step.

Are you able to use this filter successfully with your data? I am loading VTK files output from my dump files via LPP.

Thanks again,
-Nuc

Nucleophobe's picture

Nucleophobe | Wed, 04/29/2015 - 05:48

^ I just tried again and was able to get "Temporal particles to pathlines" to work. I didn't realize I had to push "Play" to generate the streamline.

I was trying to visualize results from multiple simulations at once using the "Group datasets" filter before though to save time, and it appears that doing so breaks the "Temporal particles to pathlines" filter. I think the problem is related to this thread:
http://public.kitware.com/pipermail/paraview/2010-October/019025.html

Anyway, I think I can figure something out now. Thanks again, Richti83!

hunger's picture

hunger | Sat, 01/02/2016 - 11:46

Hi all!

I would like to track the path of a certain particle in my simulation to visualize its way through the domain. The "Temporal particles to pathlines" filter works in general fine for me, but I was not able to somehow select a certain particle.

My idea was to track a particle through its ID, but there are 2 problems:
1) the IDs are continously reassigned in LIGGGHTS. According to the doc this is due to speed up of the simulation.
2) I did not find a possibility to track a certain ID of a praticle through the direct input of a number.

Any suggestions how to handle this in a better way (maybe groups, new particle type, etc.)?
Thanks for your help in advance!

Best regards
Harald

richti83's picture

richti83 | Sat, 01/02/2016 - 14:07


1) the IDs are continously reassigned in LIGGGHTS. According to the doc this is due to speed up of the simulation.

Is this true ? I've never seen this, for me the ID's of particle insertion are strictly increasing.
2) I did not find a possibility to track a certain ID of a praticle through the direct input of a number.

You can attach a threshold filter, by Scalars ID, select ID or range you want as upper/lower limit and attach the temporal particles filter to the threshold

I'm not an associate of DCS GmbH and not a core developer of LIGGGHTS®
ResearchGate | Contact

hunger's picture

hunger | Sat, 01/02/2016 - 17:04

Thx for the fast reply!

ad 2)
The threshold filter works fine for my problem!

ad 1)
In my case the particle IDs are reassigned, I have double checked the vtk files and I have also used the threshold filter to visualize the issue. I think this is connected with the decomposition of my computational domain, since the ID visualization is matching the processor pattern I have chosen in my input script.

I am also using the dump/VTK command, but I think this is not causing the reassignment of the particles.

Before I was referring to the atom_modify command in the doc, especially to the sort keyword. If I understand correctly, the default setting for Nfreq is causing the reassignment. I will run a test to check if it works if I set Nfreq=0.

Maybe I have unintentionally set another switch in the simulation that is causing the reassignemt ...

Best regards
Harald

hunger's picture

hunger | Mon, 01/04/2016 - 08:50

I was able to locate the problem and solve it.

I am using the delete_atoms command in combination with the run every command to continously remove atoms from my computational domain.
For the delete_atoms command, the default setting for the compress value is YES, which is causing a re-assignment of the particle ID every time particles are removed from the domain.
Setting compress to NO solves the problem.

Best regards
Harald