yade-users team mailing list archive

[Ken Mendoza <ken_mendoza@xxxxxxxxxxxxxxxxxx>]

Hi,

Sorry for the brief hiatus from yade this past few weeks.

I've rerun the simulation, & the yade primary view clearly shows the particles behaving as expected, being transported by the archimedes screws within the casing to the paddle section. However, playing the *.vtk files in paraview still shows the same problem of particles "drifting" out of the geometry.

I'm thinking its an issue with the visualisation in paraview rather than what the *.vtk files capture. The reason being that if the *.vtk files truly captured the wrong data, the drift should be consistent in a specific direction regardless of viewpoint, something clearly not the case where I observe the particles drifting off in random directions based on viewpoint in paraview.

Thanks & Rgds,
Ken

________________________________________
From: yade-users-bounces+ken_mendoza=ices.a-star.edu.sg@xxxxxxxxxxxxxxxxxxx [yade-users-bounces+ken_mendoza=ices.a-star.edu.sg@xxxxxxxxxxxxxxxxxxx] on behalf of Vaclav Smilauer [eudoxos@xxxxxxxx]
Sent: 15 September 2010 18:11
To: yade-users@xxxxxxxxxxxxxxxxxxx
Subject: Re: [Yade-users] Visualisation problem: particles "drifting off" while maintaining container volume

> try to use glyphes, as here described
> https://www.yade-dem.org/sphinx/user.html?highlight=glyph#loading-data-into-paraview

Anton, I don't think that would help. The squares are rendered at the
center of spheres; so if they are out of the extruder themselves, so
will be the glyphs.

Ken, I added the 'ascii' option to VTKRecorder in the last commit, so
you can check "manually" whether the positions match. I tried something
like this (past to the yade command-line)

TriaxialTest().load(); O.run(200,True); VTKRecorder(fileName='aaa-',ascii=True)()

which creates file with name aaa-spheres.200.vtu and in there you can
check the coordinates (the position array has no name, it appears under
<Points><DataArray type="float32" Name="Array 0x25a0980"...>. The first
sphere is body #6, so the first 3 numbers in the file should  match
O.bodies[6].state.pos.

You can try the same with your data, although any discrepancy would
surprise me, since VTKRecorder directly uses positions in Body::state.

Let us know what you find.

Cheers, v.



_______________________________________________
Mailing list: https://launchpad.net/~yade-users
Post to     : yade-users@xxxxxxxxxxxxxxxxxxx
Unsubscribe : https://launchpad.net/~yade-users
More help   : https://help.launchpad.net/ListHelp

This email is confidential and may be privileged. If you are not the intended recipient, please delete it and notify us immediately. 
Please do not copy it or use it for any purpose, or disclose its contents to any other person. Thank you.