Atom topic feed | site map | contact | login | Protection des données personnelles | Powered by FluxBB | réalisation artaban
You are not logged in.
YOU MAY DOWNLOAD THE WORKING MODEL AT THE END OF THIS POST.
Hello I am posting an example of a Reinforced Concrete beam modeled as POU_D_TGM that is almost working. just one exception on the last command.
I modeled the Steel bars with ELAS and ECRO_LINE for the concrete I did the same thing, although I was thinking of modeling it with CABLE and give it a very low Young's Modulus for tension Et and the normal Youngs for compression. Is this the correct way?
Neverthless I am posting the mesh, command and the salome files If someone could help me get it right I would really appreciate it.
Humberto H.
Last edited by Humberto (2013-02-28 00:15:41)
Offline
hello
i would not be so optimistic with the result as you are,
according the 'Message.mess' file
your calculation fails very early in the AFFE_CARA_ELEM command
AFFE_MODELE looks like being no set ok
for POU_D_TGM, AFFE_SECT and AFFE_FIBRE should be used according to U4.42.01
jean pierre aubry
consider reading my book
freely available here https://framabook.org/beginning-with-code_aster/
Offline
Thanks so much Jeanpierreaubry, interestingly the keywords AFFE_SECT and AFFE_FIBRE do not exist inside U.4.42.01
do I have to have one mesh (1D) for the beam (concrete) and another for the steel? or is it all taken care with DEFI_GEOM_FIBRE?
Thank you so much for pointing me in the right direction.
Humberto
Offline
interestingly the keywords AFFE_SECT and AFFE_FIBRE do not exist inside U.4.42.01
humm! you are right i was looking a very old doc (year 2007)
and the syntax seems to have changed quite a lot since
do I have to have one mesh (1D) for the beam (concrete) and another for the steel? or is it all taken care with DEFI_GEOM_FIBRE?
i guess so
but i cannot help any further as i did not use this element recently
by making a search with POU_D_TGM in this forum you should find some examples
consider reading my book
freely available here https://framabook.org/beginning-with-code_aster/
Offline
there is no reason not to succeed
instructions may be found here
www.code-aster.org/V2/doc/default/en/man_u/u3/u3.11.04.pdf
and a test case is V6.02.022
consider reading my book
freely available here https://framabook.org/beginning-with-code_aster/
Offline
Ok it is almost working, The model goes into the first iteration of time, and gives me an error that honestly I dont understand:
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
! <S> Exception utilisateur levee mais pas interceptee. !
! Les bases sont fermees. !
! Type de l'exception : error !
! !
! Actuellement, on ne sait dériver que les 'POU_D_E'. !
!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!!
Interestingly I am not using any POU_D_E, My modellization is POU_D_TGM
This time my google translator did not help.
Any help will be greatly appreciated.
Humberto.
I am posting the case again. This time it runs on all the instructions without raising any warnings or errors.
Last edited by Humberto (2013-02-12 20:06:52)
Offline
Hello Humbert,
Interestingly I am not using any POU_D_E, My modellization is POU_D_TGM
I think you missunderstood the error message.
!-----------------------------------------------------!
! <EXCEPTION> <SENSIBILITE_52> !
! !
! Actuellement, on ne sait dériver que les 'POU_D_E'. !
!-----------------------------------------------------!
It states that aster only knows how to derive POU_D_E elements.
It is a bit strange that you get an error concerning sensitivity analysis as I can't see you have it activated in your STAT_NON_LINE.
Perhaps it's a bug or some problem with your installation.
Best regards,
Richard
Last edited by RichardS (2013-02-12 23:00:10)
Richard Szoeke-Schuller
Product Management
www.simscale.com
We are hiring! https://www.simscale.com/jobs/
Offline
Hello Humbert,
It is a bit strange that you get an error concerning sensitivity analysis as I can't see you have it activated in your STAT_NON_LINE.
Perhaps it's a bug or some problem with your installation.Best regards,
Richard
Richard, thanks for your response. Could you please run this problem on your computer in order to rule out a defective installation on my side?
I would be very grateful.
Humberto
Offline
hello
a run on my machine raises the same error
replacing 'POU_D_TGM', by 'POU_D_EM',and it runs ok
one remark: is ever using 'G' beam, with warping, you have to a set a GRX in the DDL_IMPO to restrain the warping otherwise it is not necessary to use this type of beam
finally the error seems to be a limitation of Aster in the present day
jean pierre aubry
consider reading my book
freely available here https://framabook.org/beginning-with-code_aster/
Offline
hello
a run on my machine raises the same error
replacing 'POU_D_TGM', by 'POU_D_EM',and it runs okone remark: is ever using 'G' beam, with warping, you have to a set a GRX in the DDL_IMPO to restrain the warping otherwise it is not necessary to use this type of beam
finally the error seems to be a limitation of Aster in the present day
jean pierre aubry
Indeed the POU_D_TGM model in Code_Aster does not support multiple materials for the moment. That is on one element there must be only one type of material contrary to the POU_D_EM model that does support different materials on each fiber.
An improvement is already underway to extend this feature to all multi-fiber models.
The error message that is being raised is completely out of scope but should be clearer in version 11.
TdS
Offline