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

You are not logged in.

#1 Re: Salome-Meca installation » Salome_Meca V2019.0.3_Ubuntu 18.04 Installation Issues » 2020-02-11 07:33:50

Hi, I had the same problem with Salome meca 2019.0.3 as kathi in the start of this thread "SIGSEGV error as soon as I activate the mesh module".

From "code-aster.org/forum2/viewtopic.php?id=24678" installing with "sudo" seem to remove this issue:

tar xzf salome_meca-2019.0.3-1-universal.tgz && sudo ./salome_meca-2019.0.3-1-universal.run



BR/Micke

#3 Salome-Meca usage » Number of labels in colorbar [SOLVED] » 2019-12-07 12:54:14

mihe
Replies: 3

Hi,
In Salome mecca 2017 it was possible to control the number of label in the color bar. By setting discrete number of colors to for example 10 and then max  number of lables to 11 one could then achieve a color bar with tickmarks and lables between all colors. See attached picture.

-In Salome mecca 2019 I can not find out how to control this. Is it possible?

BR/Micke

#4 Re: Code_Aster usage » [SOLVED] COQUE + CONTACT + MATRICE='ELASTIQUE' => Erreur » 2018-10-15 12:48:49

I guess I should open a new post. But I do not have example files yet:
I have found a similar issue, possible ralated bug: ELAS_ORTH + Contact + MATRICE='ELASTIQUE' -does not work either.
BR/Micke

#5 Code_Aster usage » Impose displacement as a function of displacments of another node » 2018-09-24 08:05:38

mihe
Replies: 2

Hi, is it possible to define a non-linear function of  (XF^2+YF^2)^0.5 of node N1 and use it to impose a displacement on degree of freedom DX of node N2? The relation should be imposed within a STAT_NON_LINE solution(not sequential between different load steps).
I think e.g. FORMULE() only works to create a nodal function based on variables of the same node.
BR/Micke

#6 Re: Code_Aster usage » Non-linear spring between two beam elements » 2018-09-24 07:53:30

I have attached an example of a non-linear spring. You should be able to adapt it to your problem.
BR/Micke

#7 Re: Code_Aster usage » Centrifugal load with account to displacement of the center of mass » 2018-09-20 11:35:20

I have found one solution to this problem.  It is to use AFFE_CHAR_MECA_F with a load as function of XF.

For centrifugal load:
e1=0.6*1.0; rpm1=150.0; w1=rpm1/60.0*2.0*pi; m1=152.75;
a1=1e6;   #dummy hex8 face area
x1=-500.0 #dummy hex8 face mesh x coordinate
FROT=DEFI_FONCTION(NOM_PARA='XF',PROL_DROITE='LINEAIRE', PROL_GAUCHE='LINEAIRE', INTERPOL='LIN', 
                 VALE=(x1,     (m1*e1*w1**2 + m1*0*w1**2)/a1,   
                       x1+1.0, (m1*e1*w1**2 + m1*1*w1**2)/a1
                       ))

Then apply the load by:
_F(CHARGE = LCROT, TYPE_CHARGE = 'SUIV' ),

TYPE_CHARGE = 'SUIV' only work with a few types of load. Therefore I needed to include a dummy hex8 element and apply the load as pressure on one face of the dummy element.

Is there a better way to solve " Centrifugal load with account to displacement of the center of mass"?
BR/Micke

#8 Code_Aster usage » Centrifugal load with account to displacement of the center of mass » 2018-09-19 15:18:55

mihe
Replies: 1

I am trying to run a STAT_NON_LINE simulation with a ROTATION load (centrifugal load)
w=150/60*2*pi
LCROT=AFFE_CHAR_MECA(MODELE=MOD1, ROTATION=_F(VITESSE=w, AXE=(0.0,0.0,-1.0), CENTRE=(0.0,0.0,0.0), GROUP_MA='ROTM',),);

As the displacements moves the element ROTM center of mass out from the axis of rotation I would like the load to increase.  ROTM is a unbalance mass initially at a distance e away from the axis of rotation. The centrifugal force is F=M*e*w^2.  With deformation u the load should increase to  F=M*(e+u)*w^2.

The model is with beam elements(I have tried POU_D_T and POU_D_T_GD) but I have also tried to use  a HEXA8 element as ROTM.
I have tried different DEFORMATION='PETIT',  DEFORMATION='PETIT_REAC',  DEFORMATION='GROT_GDEP' .
I have tried to specify TYPE_CHARGE = 'SUIV'  at the definition of the load (EXCIT=). But that gives error "Le TYPE_ELEMENT MECA_POU_D_T  ne sait pas encore calculer l'option:  RIGI_MECA_RO."

So far the load does not increase with the displacement of the center of mass.
-How do I take the displacement of the center of mass  into account for the centrifugal load?
-Or can I define a load with AFFE_CHAR_MECA_F as function of DX?
-Is there an example?

BR/Micke

#9 Re: Code_Aster usage » [SOLVED] COQUE + CONTACT + MATRICE='ELASTIQUE' => Erreur » 2018-08-28 08:08:24

Thank you for the answer!
I had a look at bitbucket.org but I do not know what to do there. Is there some guide on how to open a ticket? Or else hopefully someone else can get this bug report into the right place.
BR/Micke

#10 Code_Aster usage » [SOLVED] COQUE + CONTACT + MATRICE='ELASTIQUE' => Erreur » 2018-08-27 12:12:26

mihe
Replies: 5

Hi,
For more robust converges I usually prefer   NEWTON=(_F(MATRICE='ELASTIQUE',REAC_ITER=1,),), in contact analysis(FORMULATION='CONTINUE').

But in this case the analysis fails when COQUE_3D elements TRIA6_7 are included in the model. See error message below. The COQUE_3D elements are not part of the contact. With NEWTON=(_F(MATRICE='TANGENTE',REAC_ITER=1,),), it works.
What is the reason for this behaviour? See  attached files.
BR/Micke



!-------------------------------------------------------------------------------------------------------------!
   ! <EXCEPTION> <CALCUL_16>                                                                                     !
   !                                                                                                             !
   !  le paramètre: PCACOQU  n'est pas un paramètre de l'option: FULL_MECA_ELAS  pour le type_élément:  MEC3TR7H !
   !-------------------------------------------------------------------------------------------------------------!
   
   Maille concernée : M1
   Option de calcul : FULL_MECA_ELAS
   Commentaire:
     Paramètre d'entrée : PCACOQU
      Commentaire:
<<  PCACOQU : CARACTERISTIQUE DE COQUE  >>
     Grandeur associée au champ : CACOQU
      Commentaire:
<<  CACOQU  Type:R  Caracteristiques des coques
EP      : epaisseur de la coque
SECT_L  : somme des sections d'armatures dans la direction L
ALPHA   : 1er angle de l'axe de reference dans le plan transverse
BETA    : 2eme angle de l'axe de reference dans le plan transverse
Ces deux angles definissent par rapport au repere de reference
le vecteur a projeter sur le plan tangent de l'element afin
d'y definir le repere (T,N,L).
La direction L est perpendiculaire au plan tangent.
KAPPA   : coefficient de cisaillement transverse
C_METR  : coefficient de modification metrique pour l'element coque
DIST_N  : excentrement de la nappe d'armatures vs la maille support
CTOR    : constante multiplicative de la rigidite en rotation associee a
la direction perpendiculaire au plan tangent de l'element
EXCENT  : excentrement du feuillet moyen
INERTIE : prise en compte de l'inertie de rotation
>>
   
   !-------------------------------------------------------!
   ! <EXCEPTION> <DVP_1>                                   !
   !                                                       !
   ! Erreur de programmation.                              !
   !                                                       !
   ! Condition non respectée:                              !
   !     .false.                                           !
   ! Fichier contex.F90, ligne 145                         !
   !                                                       !
   !                                                       !
   !                                                       !
   ! Il y a probablement une erreur dans la programmation. !
   ! Veuillez contacter votre assistance technique.        !
   !-------------------------------------------------------!

#11 Re: Code_Aster usage » COQUE display stress on deformed shape » 2018-08-27 09:55:41

Thank you for the info. I have not used Gmsh before, maybe I should.
Since paravis is included in Salome meca I expect it to be able to handle this. I hope I am not the first one that wants to plot shell stress on deformed shape in paravis.
/Micke

#12 Code_Aster usage » COQUE display stress on deformed shape » 2018-08-27 08:37:06

mihe
Replies: 4

Hi,
For an analysis with shell elements -how do I plot stress(_NOEU) on the deformed shape i paravis?

I understand that I first have to use POST_CHAMP with option EXTR_COQUE to choose surface for the stress results. E.g.:

R1S=POST_CHAMP(RESULTAT=R1,  EXTR_COQUE=_F(NOM_CHAM=('SIGM_ELNO',), NUME_COUCHE=1, NIVE_COUCHE='SUP',),);
R1I=POST_CHAMP(RESULTAT=R1,  EXTR_COQUE=_F(NOM_CHAM=('SIGM_ELNO',), NUME_COUCHE=1, NIVE_COUCHE='INF',),);

Then  calculate _NOEU results:
R1S=CALC_CHAMP(reuse =R1S, RESULTAT=R1S, GROUP_MA='ALLSHELL', CRITERES='SIEQ_NOEU', CONTRAINTE='SIGM_NOEU',);
R1I=CALC_CHAMP(reuse =R1I, RESULTAT=R1I, GROUP_MA='ALLSHELL', CRITERES='SIEQ_NOEU', CONTRAINTE='SIGM_NOEU',);

The creatye a "display modell" with TRIA6 elements:
MODP1=AFFE_MODELE(MAILLAGE=MAIL900, AFFE=(_F(GROUP_MA=('ALLSHELL' ), PHENOMENE='MECANIQUE',MODELISATION = ('3D'),),
                                         _F(GROUP_MA=('ALLV' ), PHENOMENE='MECANIQUE',MODELISATION = ('3D_SI', '3D'),),
                                         _F(GROUP_MA=('SH_M'),PHENOMENE='MECANIQUE',MODELISATION='DIS_TR',),
                                         #_F(GROUP_MA=('SLSP1','SLSP2', 'PISP1','PISP2'),PHENOMENE='MECANIQUE',MODELISATION='DIS_T',),
                                          ),);

Then project the results on a TRIA6 elements:
P1=PROJ_CHAMP(RESULTAT=R1_with_combination_of_R1_and_R1S_results???, 
                    NOM_CHAM=('DEPL', 'SIEQ_NOEU???'),
                    CAS_FIGURE='3D',
                    MODELE_1=MOD1,
                    MODELE_2=MODP1,
                    VIS_A_VIS= ( _F (GROUP_MA_1='ALLSHELL' , GROUP_MA_2=('ALLSHELL'),),
                                 #???_F (GROUP_MA_1='ALLV' , GROUP_MA_2=('ALLV'),),
                                 ),
                    INFO=1);

To be able to plot SIGM_NOEU on deformed shape I then, somewhere in between these operations, need to create a results which includes DEPL and SIGM(and preferable also the SIGM results for the volume elements too). Possible with CREA_CHAMP and option 'EXTR' , 'AFFE' or 'ASSE'. But how? Please post an example!

BR/Micke

#14 Code_Aster usage » MODI_REPERE with COQUE_UTIL_CYL » 2018-08-23 12:12:36

mihe
Replies: 1

Hi,
I try to use MODI_REPERE with COQUE_UTIL_CYL to transform shell element stresses defined in a element local coordinate system to a global cylindrical coordinate system but after transformation all stresses are zero. See attached files.

Please help if you understand what is wrong
BR/Micke

#15 Re: Code_Aster usage » Visualise COQUE_3D results with thickness? » 2018-05-04 08:52:55

To be able to visualize the shell thickness with results both on the SUP and INF layers is helpful when evaluating results. In addition to the macro procedure described above one could also transform the stress results defined in the shell local coordinate system to the global coordinate system. In this way direction of results would also be easier to evaluate.
But to simplify one could start vid only the scalar value of the stress invariants von Mises and principal stresses.
My skills with python is however probably not enough for this task. My code usually get too slow. It would be highly appreciated if this functionality could be implemented in CA.
BR/Micke

#17 Code_Aster usage » Discrete contact (DIS_CHOC, DIS_CONTACT) » 2018-03-19 12:29:03

mihe
Replies: 1

I am trying to define a discrete contact. The final goal is to achieve a non linear spring as indicated in the post "Ressorts non linéaires/Non-linear spring"

However when I play around with JEU=xxx or DIST_1=xxx I do not get the expected result.
See attached files.
I use 2 discrete elements DIS_T. Both with stiffness 1000. One of them uses DIS_CONTACT with  define a clearance e.g 0.5mm.
If I then apply a load of 1000 then I expect to get a deformation of that fulfil U*1000+ (U-0.5)*1000=1000  => U= 1500/(2*1000) = 0.75mm.
But the result becomes 1.0 as if the contact never is closed.

-Can someone help explain why?
-What is the difference between JEU and DIST_1?

BR/Micke

#18 Re: Salome-Meca usage » Why does Paravis split the result up in different sub folders? » 2017-07-21 13:11:45

In a different case, where I had problems with DEPL in one separate folder,  I managed to fool Aster by duplicating the result with:

R1=CALC_CHAMP(reuse =R1, RESULTAT=R1, GROUP_MA='ALLV',
             FORCE='REAC_NODA',
             CONTRAINTE='SIEF_NOEU',CRITERES='SIEQ_NOEU', ); #NOEUD_CMP='VMIS'

#Dummy/duplicate  result with displacements:
R1DEPL=MODI_REPERE(RESULTAT=R1, #NUME_ORDRE=1,
                  MODI_CHAM=(_F(NOM_CHAM='DEPL', NOM_CMP=('DX', 'DY', 'DZ'), TYPE_CHAM='VECT_3D',),),
                  REPERE='UTILISATEUR',AFFE=_F(ANGL_NAUT = (0.,0.,0.,),),
                  );

Then write to med file:
IMPR_RESU(FORMAT='MED', RESU=(
  _F(RESULTAT=R1, GROUP_MA='ALL3D', NOM_CHAM=('SIEF_NOEU'), NOM_CHAM_MED= ('SIEF_NOEU'), ),
  _F(RESULTAT=R1DEPL, GROUP_MA='ALL3D', NOM_CHAM=('DEPL'),      NOM_CHAM_MED= ('DEPL'),     NOM_CMP=('DX', 'DY', 'DZ',),  ),
  _F(RESULTAT=R1, GROUP_MA='ALL3D', NOM_CHAM=('DEPL'),      NOM_CHAM_MED= ('LAGS_C'),     ),
  _F(RESULTAT=R1, GROUP_MA='ALL3D', NOM_CHAM=('VALE_CONT'), NOM_CHAM_MED= ('VALE_CONT'), NOM_CMP=( 'JEU',), ),
  _F(RESULTAT=R1, GROUP_MA='ALL3D', NOM_CHAM=('REAC_NODA'),  ),

  _F(RESULTAT=R1CYL, GROUP_MA='ALL3D', NOM_CHAM=('SIEF_NOEU'),  NOM_CHAM_MED= ('SIEQ_NOEU_CYL')   ),
  _F(RESULTAT=R1CYL, GROUP_MA='ALL3D', NOM_CHAM=('DEPL'),       NOM_CHAM_MED= ('DEPL_CYL')   ),

                            ),);

Some improvement but still VALE_CONT is written to separate ComSup/sub folder.
/Micke

#19 Re: Salome-Meca usage » Why does Paravis split the result up in different sub folders? » 2017-07-18 08:48:26

Thank you for this input!.

-I tried it. It worked fore the 2D case. -> SOLVED
MAIL999=DEFI_GROUP(reuse =MAIL999, MAILLAGE=MAIL999, CREA_GROUP_MA=_F(NOM='ALL2D', TOUT='OUI',TYPE_MAILLE='2D',),);

IMPR_RESU(FORMAT='MED',UNITE=80, RESU=(
     _F(RESULTAT=R1, GROUP_MA='ALL2D', NOM_CHAM=('DEPL','SIEQ_NOEU'),),
       ),) 


-It did not work for the 3D case.  DEPL and VALE_CONT  still are divided up in different sub folders.
MAIL999=DEFI_GROUP(reuse =MAIL999, MAILLAGE=MAIL999, CREA_GROUP_MA=_F(NOM='ALL3D', TOUT='OUI',TYPE_MAILLE='3D',),);
IMPR_RESU(FORMAT='MED', RESU=(
  _F(RESULTAT=R1, GROUP_MA='ALL3D', NOM_CHAM=('DEPL', 'VALE_CONT'),),
  ),);

BR/Micke

#20 Re: Salome-Meca usage » Paravis, is it possible to reload a results file? » 2017-07-18 08:17:53

Thank you for this macro!
I also found a refresh button in Paravis. See attached picture.
BR/Micke

#21 Re: Salome-Meca usage » Why does Paravis split the result up in different sub folders? » 2017-07-18 08:09:52

Hi,
I was wrong about contact pressure, at least for 3D analyses. Contact pressure result LAGS_C is located in the DEPL array and is therefore in the same ComSup as displacements in Paravis. However other contact results as for example JEU is put in  VALE_CONT array. And VALE_CONT is placed in a separate ComSup. As a result it is not possible to combine contact clearance(JEU)-displacement plots (e.g. display JEU  on deformed shape).

I have added a picture of how it looks in paravis. The upper part of the picture is from a 3D analysis. The result med-file was created by:
IMPR_RESU(FORMAT='MED', RESU=(
  _F(RESULTAT=R1, NOM_CHAM=('DEPL', 'VALE_CONT'),),
  ),);
-Why are DEPL and VALE_CONT  divided up in different sub folders(ComSup0 and ComSup1)?
-Can this be controlled/Avoided?

The lower part of the picture is from a 2D analysis (C_PLAN). The result med-file was created by:
IMPR_RESU(FORMAT='MED',UNITE=80, RESU=(
     _F(RESULTAT=R1, NOM_CHAM=('DEPL','SIEQ_NOEU'),),
       ),) 
The stress result are put in ComSup1 and the displacements in ComSup0.  As a result it is not possible to display stress  on deformed shape.
-Can this be controlled/Avoided? -How?

BR/Micke

#22 Salome-Meca usage » Why does Paravis split the result up in different sub folders? » 2017-07-05 20:33:45

mihe
Replies: 5

I find it anoying that Paravis split up results (eg DEPL, SIGM_, LAGS_C..,) in in different sub foders (ComSup?) in paravis. For example contct pressure is usually put in a separate foder. And I reasently did a 2D stress analysis. Paravis then put the displacements in a separate subfolder. As a result it is not possible to combine contact pressure/stress-displacement plots (e.g. display contact pressure  on deformed shape, or for 2D display stress on deformed shape).   
-Why are results are divided up in different sub folders? Can this be controlled/Avoided?
BR/Micke

#23 Re: Code_Aster usage » Post processing a model with different elements type in Paraview » 2017-06-02 13:50:26

I have a similar problem. Why are results are divided up in different "ComSup"? Can this be controlled?
Another issue -How do one omit writing the instant zero to the med file? (without having to set INST=1, INST=2... for all instances with results)
/MIcke

#24 Re: Code_Aster usage » Calculate principal stress from combination of results » 2017-03-14 15:44:40

I still have not figured out how to do this.
Using  CREA_CHAMP + COMB I think I can only create nodal results. How to get from there to a principal stress or von mises stress I do not know. There is a "formula" method but I think one should be able to use Aster already implemented algorithms to calculate equivalent stresses.

Maybe I should use CREA_CHAMP + ASSE. But I have not succeed yet. It would have been nice with an example for this relatively useful/simple task but I have not found one....

BR/Micke

#25 Salome-Meca usage » Paravis, is it possible to reload a results file? » 2017-01-27 14:38:03

mihe
Replies: 2

Hi, is it possible to reload a med file in paravis?

Say that I have a med file xxx.med loaded into paravis.
I then modify the calculation xxx and re-calculate it to get a new xx.med result file. -Is it then possible to reload the file in Paravis instead of deleting the old one and opening the new one?

/Micke