yade-dev team mailing list archive

[Václav Šmilauer <eu@xxxxxxxx>]

> Don't hesitate to tell if you'd prefer to see commits to separate versions for some classes.
I had no intention of suggesting that. Of course it is everybody's 
choice though.
> Maybe you think homothetic resize is "not consistent"? I'm wondering now.
Homothetic resize is very good, that one was constructive, I agree.
> I should perhaps not interfeer when you think relSpin=spin2-spin1 is inconsistent,
Oh come on, I asked about that --... and I thought it was consistent 
with beam bending (which is true), but then I realized contact of 2 
spheres cannot be geometrically modeled as beam, or at least does not 
have to. Good that you told me that, I am grateful.
> plastic dissipation is wrong, loading rate control is comparing apples and oranges, etc. I'd just ask you to not claim such things to loud on the list (except if it concerns your own code ofc) as it can mislead others.
There you go with personal reactions I talked about. Facts: plastic 
dissipation is not always giving correct results (e.g. dynamic 
simulations); loading control does not always work, depending on how you 
tune the "mass" parameter. For me, when you commit some code to trunk 
(and it is not something clearly experimental, in development etc), you 
also implicitly agree to public scrutiny of that code, when it becomes 
used. If you don't want to hear that, create a moderated 
yade-pr@xxxxxxxxxxxxxxxxxxx where only messages praising qualities of 
your code will be allowed; I am dead serious about that.
> This is quite depreciating. Even if Yade is a very nice toolkit, it is _also_ really a complete DEM solution.
It can be a "complete solution", though that depends how you put the 
pieces together. I don't see a reason to not develop another piece; 
there is no obligation to pick it for anyone, nor does it break existing 
code.
>   Out of the box, it offers more than PFC (GUI, scripting, variety of validated contact laws and boundary conditions, set of predefined simulations).
I know, I've seen some of that code actually.

Best, v.