[MARS-UD-100] StateVariable change issue

Multiphysics Modeling - Thermal, Aging, ASR, Creep and more.

[MARS-UD-100] StateVariable change issue

Postby madura » Thu Apr 07, 2016 1:07 am

By checking the statevariable: "CompressiveYieldingStress", we saw that the value was -1.

If in the input file, we use LDPM-X for the material properties, then the change of the STV name (CompressiveYieldingStress) in mRCConcreteXUD does not matter because only mRCConcreteX is read. That explains that why the aging module cannot find the state variable index according to the name you modified in mtRCConcreteXUD class.

If we use LDPM-XUD (the userdefined version), at the moment where I use LdpmModules in my input file (where I use the Aging part), LdpmModules is not reading mRCConcreteXUD but mRCConcreteX. The issue is maybe because LdpmModules cannot recognize the UD version of the material model.
Attachments
diffMat.mrs
(3.26 KiB) Downloaded 576 times
Cylinder.mrs
(717.9 KiB) Downloaded 573 times
runA.mrs
(9.36 KiB) Downloaded 562 times
madura
 
Posts: 11
Joined: Wed Feb 24, 2016 2:10 am

Re: StateVariable change issue

Postby zhouxinwei » Thu Apr 07, 2016 3:43 am

If you start the input with Material, you are using the material model in the production version, not the one you are developing now.

To use the user defined version of LPDM material in MARS-UD-100 repository, you need to use
Code: Select all
UserDefinedObject Concrete LDPM-XUD {

instead of

Code: Select all
Material Concrete LDPM-X {


Advice: change LDPM-XUD to M-LDPMUD, as we are changing X-LDPM/LDPM-X to M-LDPM.

Edit: in MARS-UD-100 file src/xldpm/mtRCConcreteXUD.h, change

Code: Select all
string getLabel() const { return "RCConcrete model X UD"; }

to

Code: Select all
string getLabel() const { return "RCConcrete model X"; }
zhouxinwei
 
Posts: 208
Joined: Thu Jul 09, 2015 7:12 pm

Re: StateVariable change issue

Postby giacusatis » Wed Apr 13, 2016 5:33 pm

Xinwei, it would be good to make sure that all the M-LDPM code under development be in the UD files. With the label renaming issue we incurred in the situation that although all the coding was correct in the UD files, still it was not compatible with what coded in the library.
giacusatis
 
Posts: 4
Joined: Fri Jul 10, 2015 2:57 pm

Re: StateVariable change issue

Postby zhouxinwei » Wed Apr 13, 2016 6:17 pm

giacusatis wrote:Xinwei, it would be good to make sure that all the M-LDPM code under development be in the UD files. With the label renaming issue we incurred in the situation that although all the coding was correct in the UD files, still it was not compatible with what coded in the library.


MARS-UD-100 and MARS library has been recently updated to reflect this request. Since MARS library version 2016.2.02, the UD repository is independent of the library. More details can be found here: viewtopic.php?f=2&t=64.
zhouxinwei
 
Posts: 208
Joined: Thu Jul 09, 2015 7:12 pm


Return to Multiphysics LDPM (M-LDPM)

Who is online

Users browsing this forum: No registered users and 1 guest

cron