yade-users team mailing list archive

[Bruno Chareyre <question659557@xxxxxxxxxxxxxxxxxxxxx>]

Question #659557 on Yade changed:
https://answers.launchpad.net/yade/+question/659557

    Status: Open => Answered

Bruno Chareyre proposed the following answer:
> for the boundaryUseMaxMin=[1,1,1,1,1,1] . I misunderstood the doc.

Or the doc is not clear... feel free to improve when you spot missing
pieces of information.

> For the calibration of the coordination number, yes, we could do that
with a dedicated python script but I must say that I am not a big fan of
the randomDensePack() function

I never thought about using randomDensePack.

> Regarding the problem with the solver, I guess I'll need to figure it
out by myself... Not an easy task...

I can't reproduce your problem, sorry.

> Regarding the walls appended after the packing, no error message shows
up really (even with debug=1). It is just that the computation is wrong
(Qin and Qout are not equal)

Your script reads:
Qin = flow.getBoundaryFlux(0)
Qout = flow.getBoundaryFlux(1)
and you get:
Qin= -1.62684535981e-16  Qout= 1.17717250878e-16

Yade [1]: flow.getBoundaryFlux?
Docstring:
getBoundaryFlux( (FlowEngineT)arg1, (int)boundary) -> float :
    Get total flux through boundary defined by its body id.

Are bodies 0 and 1 the walls when you append the walls after the sĥeres?

> and that the VTK file cannot be open with paraview (error reading
ascii cell data). Could this be related to the tesselation?

It could be that someone assumed wall ids 0,...,5 for some vtk export.
You could check that in the code. It should not interfere in the actual
resolution (but it is still annoying).

Bruno

-- 
You received this question notification because your team yade-users is
an answer contact for Yade.