Question #659557 on Yade changed:
https://answers.launchpad.net/yade/+question/659557
Status: Open => Answered
Bruno Chareyre proposed the following answer:
> boundaryUseMaxMin=[1,1,1,1,1,1]
It means that instead of walls positions it will use static positions
defined by max/min (the static positions can change with time but in
terms of boundary condition it is always as if the wall was immobile).
It does not mean "no wall", at some point some fluid forces on the walls
are calculated and they need to be assigned to a body (that's at leas
the current code). So, you still need the corresponding bodies (not
necessarily of the Box class).
For wallIds, yes please show a script.
>How did these stories end?
They did not end unfortunately, but for the moment I am not able to tell if it
is a problem on yade side or on user's side.
Too vague statements/crash reports to know if it is wrong timestep, wrong
allocation of ressources on a cluster, or really unexpected behavior by the
fluid solver.
I understand the reason for the reloading exemple, ok.
The need to predetermine interaction range does not make reloading a packing
mandatory (imagine you insert the python script doing this calibration inside
the script doing the actual simulation?), but that's another story. We can
discuss it separately if you like.
Cheers
Bruno
--
You received this question notification because your team yade-users is
an answer contact for Yade.
_______________________________________________
Mailing list: https://launchpad.net/~yade-users
Post to : [email protected]
Unsubscribe : https://launchpad.net/~yade-users
More help : https://help.launchpad.net/ListHelp
