← Back to team overview

yade-dev team mailing list archive

Re: [Branch ~yade-pkg/yade/git-trunk] Rev 3541: Many changes towards a more consistent sign convention throughout the code for stresses and strai...

 

On 19/11/14 17:58, Jerome Duriez wrote:
> But I did consider examples/triax-tutorial/script-session2.py. I did
> not modify it because it was, in the current state, already broken
> because of an attribute definition that does not exist anymore...
Ah, I see... Well, if you can first fix broken scripts, then change the
sign, it is awesome. But this is high demanding.
If all signs are reverted at least in not-broken scripts it is good enough.

Luc (in hidden cc.), if you have recent scripts for incremental loadings
you probably know already how to fix the script-session2.py.
Could you please have a look?

Bruno





> Now that another day has started I can completely fix this one too.
>
>
> ------------------------------------------------------------------------
> *From:* Yade-dev
> [yade-dev-bounces+jerome.duriez=ucalgary.ca@xxxxxxxxxxxxxxxxxxx] on
> behalf of Bruno Chareyre [bruno.chareyre@xxxxxxxxxxxxxxx]
> *Sent:* November 19, 2014 4:45 AM
> *To:* yade-dev@xxxxxxxxxxxxxxxxxxx
> *Subject:* Re: [Yade-dev] [Branch ~yade-pkg/yade/git-trunk] Rev 3541:
> Many changes towards a more consistent sign convention throughout the
> code for stresses and strai...
>
> This is great! Thank you Jérôme.
> Yet, it seems to me that you missed some updates in examples.
> For instance, examples/triax-tutorial/script-session2.py is not in
> your list.
> Did you make a global search to find where the attributes are used?
>
> Bruno
>
>
> On 19/11/14 01:18, noreply@xxxxxxxxxxxxx wrote:
>> ------------------------------------------------------------
>> revno: 3541
>> committer: jduriez <jerome.duriez@xxxxxxxxxxx>
>> timestamp: Tue 2014-11-18 12:46:27 -0700
>> message:
>>   Many changes towards a more consistent sign convention throughout the code for stresses and strains. Should fix e.g. https://bugs.launchpad.net/yade/+bug/1381282. The goal is to know directly the meaning of a strain or stress value each time one is encountered. Relying on the classical Continuum Mechanics convention (editorial choice...). A global announcement is planned in a couple of days, in case some errors appear in the meantime.
>> modified:
>>   examples/FluidCouplingPFV/oedometer.py
>>   examples/clumps/triax-basic-with-clumps.py
>>   examples/test/triax-basic.py
>>   examples/test/triax-cohesive.py
>>   examples/triax-tutorial/script-session1.py
>>   pkg/dem/CapillaryTriaxialTest.hpp
>>   pkg/dem/CohesiveTriaxialTest.hpp
>>   pkg/dem/TriaxialCompressionEngine.cpp
>>   pkg/dem/TriaxialCompressionEngine.hpp
>>   pkg/dem/TriaxialStressController.cpp
>>   pkg/dem/TriaxialStressController.hpp
>>   pkg/dem/TriaxialTest.hpp
>>   py/pack/pack.py
>>   scripts/checks-and-tests/checks/DEM-PFV-check.py
>>   scripts/checks-and-tests/checks/checkTestTriax.py
>>
>>
>> --
>> lp:yade
>> https://code.launchpad.net/~yade-pkg/yade/git-trunk
>>
>> Your team Yade developers is subscribed to branch lp:yade.
>> To unsubscribe from this branch go to https://code.launchpad.net/~yade-pkg/yade/git-trunk/+edit-subscription
>>
>>
>> _______________________________________________
>> Mailing list: https://launchpad.net/~yade-dev
>> Post to     : yade-dev@xxxxxxxxxxxxxxxxxxx
>> Unsubscribe : https://launchpad.net/~yade-dev
>> More help   : https://help.launchpad.net/ListHelp
>
>
> -- 
> _______________
> Bruno Chareyre
> Associate Professor
> ENSE³ - Grenoble INP
> Lab. 3SR
> BP 53
> 38041 Grenoble cedex 9
> Tél : +33 4 56 52 86 21
> Fax : +33 4 76 82 70 43
> ________________
>
>
> _______________________________________________
> Mailing list: https://launchpad.net/~yade-dev
> Post to     : yade-dev@xxxxxxxxxxxxxxxxxxx
> Unsubscribe : https://launchpad.net/~yade-dev
> More help   : https://help.launchpad.net/ListHelp


-- 
_______________
Bruno Chareyre
Associate Professor
ENSE³ - Grenoble INP
Lab. 3SR
BP 53
38041 Grenoble cedex 9
Tél : +33 4 56 52 86 21
Fax : +33 4 76 82 70 43
________________


Follow ups

References