Welcome to the forums. Please post in English or French.

You are not logged in.

#1 Re: Salome-Meca usage » Units used in Salome-Meca? metres or millimetres? » 2020-05-12 17:51:28

hello

sameer21101970 wrote:

tonne/mm3
is not acceptable

what do you mean by not acceptable!!!!

i have been using this for well over 30 years on many finite element codes including code_aster

jean pierre aubry

#2 Code_Aster usage » numpy inside a FORMULE troubles » 2020-04-26 09:16:29

jeanpierreaubry
Replies: 1

hello

its seems that using numpy inside a FORMULE called from CALC_CHAMP with CHAM_UTIL is impossible

the following sequence

import numpy as np

fsig = FORMULE(
	NOM_PARA=('SN','SMFY','SMFZ',),
	VALE="""np.sign(SN)*(abs(SN)+abs(SMFY)+abs(SMFZ))""",
);

stat=CALC_CHAMP(
	reuse =stat,RESULTAT=stat, 
	GROUP_MA=('pot','chexp',),
	CHAM_UTIL=_F(NOM_CHAM='SIPO_ELNO',FORMULE=(fsig,),NUME_CHAM_RESU=2,),
	INFO=2,
);

produces the following output

ERREUR LORS DE L'ÉVALUATION DE LA FORMULE 'fsig' :
>> name 'np' is not defined

  
   !------------------------------------------------------------------------------------!
   ! <A> <FONCT0_9>                                                                     !
   !                                                                                    !
   ! Erreur lors de l'interpolation de la fonction 'fsig'.                              !
   !                                                                                    !
   ! Erreur lors de l'évaluation de la formule.                                         !
   ! La remontée d'erreur suivante peut aider à comprendre où se situe l'erreur :       !
   ! Traceback (most recent call last):                                                 !
   !   File "/opt/aster142/14.2/lib64/aster/Build/B_ETAPE.py", line 565, in fiintf      !
   !     res = objet_sd(**dval)                                                         !
   !   File "/opt/aster142/14.2/lib64/aster/Noyau/N_FONCTION.py", line 84, in __call__  !
   !     res = eval(self.code, self._initial_context, context)                          !
   !   File "np.sign(SN)*(abs(SN)+abs(SMFY)+abs(SMFZ))", line 1, in <module>            !
   ! NameError: name 'np' is not defined                                                !
   !                                                                                    !
   ! Conseils :                                                                         !
   !   Si le problème reporté ci-dessus ressemble à 'NameError: 'XXX'...',              !
   !   vérifiez que le paramètre 'XXX' fait bien partie des paramètres de définition de !
   !   la formule (mot clé FORMULE / NOM_PARA).                                         !
   !                                                                                    !
   !                                                                                    !
   ! Ceci est une alarme. Si vous ne comprenez pas le sens de cette                     !
   ! alarme, vous pouvez obtenir des résultats inattendus !                             !
   !------------------------------------------------------------------------------------!

my remarks
numpy is correctly imported and the use of np.sign in a FORMULE outside a CALC_CHAM with CHAM_UTIL does not raise any error

its seems that using numpy inside a FORMULE called from CALC_CHAM with CHAM_UTIL is impossible

it should not be!!

is there any work around?

please do not tell me that sign(SN)=SN/abs(SN) without numpy, i know it!!

jean pierre aubry

#3 Re: Code_Aster usage » Error in using MASSIF_COQUE » 2020-04-26 08:05:54

hello

but it is clearly stated in the message

Le TYPE_RACCORD='MASSIF_COQUE' n'est pas utilisable avec des COQUE_3D. !

COQUE_3D are not allowed in this case you have to use either DKT or DST

jean pierre aubry

#4 Re: Code_Aster usage » [Solved] ANGL_REP ou VECTEUR. error ? » 2020-04-22 07:44:47

lskrinjar wrote:

can a VECTEUR has values (1, 1, 1) for all elements? - This would be logical for me.

of course i can
but be carefull this may not be the solution il ALL cases

#5 Re: Code_Aster usage » [Solved] ANGL_REP ou VECTEUR. error ? » 2020-04-21 09:57:27

please read carefully the do U4.42.01  AFFE_CARA_ELEM
you will clearly see that VECTEUR cannot be normal to the element
i your case it is for all 'vertical' group
VECTEUR must not be mixed with the normal to the element as stated earlier in this thread

#7 Re: Code_Aster usage » [Solved] ANGL_REP ou VECTEUR. error ? » 2020-04-20 18:05:49

hello

i cannot give you a better advice than what is said in the .mess file
the vector you define is normal to some element

which ones i cannot tell without the mesh

jean pierre aubry

#8 Re: Code_Aster usage » What's wrong with "Saturated file"? » 2020-04-20 13:39:52

how are you running the calculation astk or as_run?
how much memory did you allocate?

#9 Re: Code_Aster usage » What's wrong with "Saturated file"? » 2020-04-20 10:59:10

hello

may be a search on the forum would help
one among many answers
......./viewtopic.php?id=23337

jean pierre aubry

#10 Re: Code_Aster usage » (SOLVED) Force Nodale in DKT and COQUE_3D » 2020-04-15 14:28:46

hello

you are applying 41 times the load as there are 41 nodes in group LOAD
so if the defection is 41 times too high everything is ok

besides that there are some oddities in the .comm file please read the message file

another point in the .comm the thickness is 200 mm and not 2

also consider the advice in signature of this post

jean pierre aubry

#11 Re: Code_Aster usage » Non linear analysis - DIS BILI ELAS » 2020-04-12 10:42:58

hello DanieleD

matmol = DEFI_MATERIAU(MATER=mater,
                         DIS_BILI_ELAS=_F(KDEB_DZ=KDEB_DZ,
                                          FPRE_DZ=20.0,
                                          KFIN_DZ=KFIN_DZ,),
                         INFO=1,)

what means KDEB_DZ=KDEB_DZ,in the above code abstract
here is the error depicted in the .mess file
but once solved i am afraid you are finished with it!!

please read careffully the relevant sections in
U4.43.01, R5.03.17, V6.08.103 and the test case SSND103


jean pierre aubry

#12 Re: Code_Aster usage » Non linear analysis - DIS BILI ELAS » 2020-04-12 08:26:11

hello

sameer21101970 wrote:

error msg is self explanatory,

CONVERGENCE=_F(ITER_GLOB_MAXI=300,
                                          ARRET='OUI',
                                          ITER_GLOB_ELAS=25,),

increase iter glob maxi ---to 300 or 3000...

if u can share .comm. med files,

reading the message file i doubt the problem is there
the calculation does not even start the first iteration

jean pierre aubry

#13 Re: Code_Aster usage » Contraintes dans le repère matériau » 2020-04-10 14:38:36

en fait c'est assez simple
le calcul de CRITERES=('SIEQ_NOEU',),donne accès a tout ces résultats aux noeuds

  - CHAMP SIEQ_NOEU        :
       * VMIS    
       * TRESCA  
       * PRIN_1  
       * PRIN_2  
       * PRIN_3  
       * VMIS_SG 
       * VECT_1_X
       * VECT_1_Y
       * VECT_1_Z
       * VECT_2_X
       * VECT_2_Y
       * VECT_2_Z
       * VECT_3_X
       * VECT_3_Y
       * VECT_3_Z
       * TRSIG   
       * TRIAX   

attention il s'agit de moyenne au noeuds à interpréter avec précaution surtout  à  l'interface avec les couches
SIEQ_ELGA, au point de Gauss serait plus juste
ensuite en créant des champs utilisateurs avec PRIN_* qui est la contrainte principale et VECT_*_X , Y, Z qui est l'orientation de ce vecteur
on peut faire des choses et visualiser en post traitement les vecteurs de contraintes

La même chose s'applique avec des éléments coques qui une fois de plus sont la meilleure réponse au problème (la plus juste probablement)
avec DEFI_COMPOSITE

#14 Re: Code_Aster usage » Contraintes dans le repère matériau » 2020-04-10 10:12:36

je crois me rappeler que l'on peut obtenir en résultats les composantes du vecteur local de l'élément (je ne me souviens plus comment)


après cela avec un peu de python on pourrait générer les contraintes dans le repère local

cependant

je serais curieux de savoir quel est le cas de calcul qui ferait préférer les éléments 3D aux éléments 2D multicouches composites

en effet j'ai derrière moi une petite dizaines d'années (il y a bien longtemps) de conception et calcul de composites multicouches dans les  domaines aéronautique, militaire et autre et c'est la première fois que je vois quelqu'un employer des éléments 3D à la place des éléments 2D dédiés

je suis très dubitatif sur la pertinence d'un modélisation en 3D sur des peaux fines

le logiciel utilisé à l'époque était SAMCEF

#15 Re: Code_Aster usage » Contraintes dans le repère matériau » 2020-04-08 14:21:34

bonjour

avec des éléments 3D cela  sera toujours dans le repère global (par définition de l'élément) et je crois quelque soit le code
pour voir dans l'épaisseur il suffit de mettre plusieurs couches, voir la doc
quoiqu'il en soit il est bien préférable d'utilser des coques pour une modélisation composite multicouches

toutes les autres tentatives de mots clés que vous avez faites me semble être au petit bonheur la chance sans lire la doc ?

jean pierre aubry

#17 Re: Code_Aster usage » DOF associated with node N3 and the component DRX » 2020-03-24 11:48:09

Thank you Jean Pierre,
Having developed a while back linear dynamics operators in code_aster, I agree and it is true that beam elements formulations are exact in MECA_STATIQUE and DYNA_VIBRA, but not in STAT_NON_LINE (even if ELAS behavior is chosen). So you're right, convergence check will and should not change the results *at the beam's boundary nodes".

you are absolutely right
i was just pointing out that the mesh convergence test was of no help in this case
as the problem is rather different

@Iskrinjar
once blocking sup_B in DZ
i get sensible results see attached image (made with Gmsh)
i think you are completely misusing the plot
if i look at depl_problem picture i can see 'Mode 1:0 hz' in the upper right corner
are you trying to view a mode shape ?

#18 Re: Code_Aster usage » Modal analysis of an orthotropic tube » 2020-03-23 17:24:43

hello

for a beginning you better make the 2D mesh at the neutral fiber before tackling the more complicated bit of the offset  plate element relative to the mesh plane

for a 3D problem AFFE_CARA_ELEM should not be used at all

jean pierre aubry

#19 Re: Code_Aster usage » DOF associated with node N3 and the component DRX » 2020-03-23 17:08:15

what i want is the mesh not the comm file which i already have from a previous post

if you have length in mm and force in N then you need to set mass density in t/mm3
this is written in all good textbooks or in my book in chapter 6.1
or i can be checked with a very simple dimensional calculation
this was just an educational remark as this parameter is not used in your case

as the element formulation is exact a convergence mesh check is a waste of time
but if you want to do it

#20 Re: Code_Aster installation » Failed Installation of code_aster » 2020-03-23 15:45:51

hello

why trying to install such an old and deprecated version?

now for the trouble
one should never install code_aster as root (with sudo) this is calling for later trouble (maybe on the whole system)

you should as root
create the folder /opt/aster
give it read write access for namhung user

then do python setup.py install –prefix=/opt/aster as namhung user

this is valid whatever the version of code_aster

jean pierre aubry

#21 Re: Salome-Meca usage » FeaForAll Plate Tutorial error message » 2020-03-23 15:31:02

hello

EXECUTION_CODE_ASTER_EXIT_929=0.
is not an error code
it means that study 929 finsihed OK which is the meaning of  =0   

jean pierre aubry

#22 Re: Code_Aster usage » DOF associated with node N3 and the component DRX » 2020-03-23 15:01:29

hello

regarding the boundary condition the mesh would help to find out, please post it
but if i assume the dimension to be mm the RHO value is a thousand time too high to be steel

for hberro
in a static analysis the number of beam elements in a given section  can be anything, minimum 1, as the formulation of the element is exact

jean pierre aubry

#23 Re: Code_Aster usage » Incomplete mesh assignment for MODEL = AFFE_MODELE » 2019-11-21 15:11:09

hello

i am no specialist in thermal
but the difference is 508
equal to the number of SEG2
also equal to the number in right, left and bottom

isnt the trouble lying in the mesh

cannot say more without the included files

jean pierre aubry

#24 Re: Code_Aster usage » Nonlinear Simulation of Shell Structure » 2019-11-15 17:53:23

hello

are you sure you run the same problem
in code_aster it fails on the first step of the calculation

i think your problem is ill defined
do you understand all the commands in the .comm file

also the mesh is unduly fine

jean pierre aubry

#25 Re: Code_Aster usage » Mass point » 2019-11-07 08:00:14

the run looks like ok
the error is somewhere else
we need the mesh to understand and the values calculated by ansys