[Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-26 Thread Václav Šmilauer
*** This bug is a duplicate of bug 569169 *** https://bugs.launchpad.net/bugs/569169 Oh, if it is duplicate, it takes status from the master bug. OK then. -- New container causes different results between r2091 and r2092 https://bugs.launchpad.net/bugs/563894 You received this bug notificati

[Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-26 Thread Anton Gladky
*** This bug is a duplicate of bug 569169 *** https://bugs.launchpad.net/bugs/569169 I cannot change the status of this big. The button does not work for me. -- New container causes different results between r2091 and r2092 https://bugs.launchpad.net/bugs/563894 You received this bug notific

[Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-26 Thread Anton Gladky
*** This bug is a duplicate of bug 569169 *** https://bugs.launchpad.net/bugs/569169 Thank you very much Vaclav! It works now as should work. -- New container causes different results between r2091 and r2092 https://bugs.launchpad.net/bugs/563894 You received this bug notification because yo

Re: [Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-26 Thread Bruno Chareyre
I get it. So, it would be a good idea perhaps to reduce damping effects on DOF "i" if vel[i] is close to 0 (perhaps using some sort of non-dimensional proportionality factor)? It also suggests applying damping separately on each DOF (not like in Hentz) is better, regarding this "feature", since

[Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-26 Thread Václav Šmilauer
*** This bug is a duplicate of bug 569169 *** https://bugs.launchpad.net/bugs/569169 I think if you ran without damping, the difference wouldn't be as noticeable. Cundall's damping is not Lorentz-like function that amplifies small causes into big effect. It is function that is _discontinuous_

Re: [Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-26 Thread Chareyre
*** This bug is a duplicate of bug 569169 *** https://bugs.launchpad.net/bugs/569169 You are right, the difference comes only when j=2 apparently (I didn't notice it was the default!). I reviewed the discussion about this : I'm still surprised roudings can make such significant difference in

[Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-26 Thread Václav Šmilauer
*** This bug is a duplicate of bug 569169 *** https://bugs.launchpad.net/bugs/569169 OK, open a new bugreport then. Anton's case is fixed. BTW the fact that multi-threaded simulations are not deterministic has been discussed here multiple times. That is not a bug. -- New container causes di

[Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-26 Thread Chareyre
*** This bug is a duplicate of bug 569169 *** https://bugs.launchpad.net/bugs/569169 I wrote "iterations"? Sorry, I meant "interactions". Unfortunately, the other fix in container doesn't seem to solve this problem (it was not a duplicated bug). In r2181, generate a TriaxialTest.xml and run

[Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-25 Thread Václav Šmilauer
*** This bug is a duplicate of bug 569169 *** https://bugs.launchpad.net/bugs/569169 OK, it seems it was due of bug #569169 after all. Please check by redefining def cohesiveContacts(): coh=[(i.id1,i.id2) for i in O.interactions if i.phys.isCohesive] print len(coh),len(set(co

[Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-25 Thread Václav Šmilauer
It was a clean instal what I did... -- New container causes different results between r2091 and r2092 https://bugs.launchpad.net/bugs/563894 You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. Status in Yet Another Dynamic Engine: New Bug

Re: [Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-25 Thread Anton Gladky
Hi, Vaclav, please, try to make a clean r2092 install and you should get the difference. For one time I also got r2092 normal results, but after clean install I have got again the problem. Thank you __ Anton Gladkyy 2010/4/25 Václav Šmilauer > Anton, I am not able

[Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-25 Thread Václav Šmilauer
Anton, I am not able to reproduce the bug with your script. I have 17716 with both r2091 and r2092, and 19872 with current (which is due to regularHexa changes). Bruno, can you be more precise? Different number of iterations could be fine (finite precision, periodic engines bound to computation ti

Re: [Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-25 Thread Chareyre
I confirmed this bug with FrictPhys contacts. Scene generated with TT preprocessor : different runs give different numbers of iterations. In addition : different numbers in load/saved scenes, as in https://bugs.launchpad.net/yade/+bug/569169. -- New container causes different results between r

[Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-25 Thread Václav Šmilauer
** Changed in: yade Milestone: None => 0.5 -- New container causes different results between r2091 and r2092 https://bugs.launchpad.net/bugs/563894 You received this bug notification because you are a member of Yade developers, which is subscribed to Yade. Status in Yet Another Dynamic Engin

[Yade-dev] [Bug 563894] Re: New container causes different results between r2091 and r2092

2010-04-15 Thread Anton Gladky
** Attachment added: "test.py" http://launchpadlibrarian.net/44275029/test.py -- New container causes different results between r2091 and r2092 https://bugs.launchpad.net/bugs/563894 You received this bug notification because you are a member of Yade developers, which is subscribed to Yade.