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

You are not logged in.

#1 Re: Code_Aster installation » error during Aster compilation » 2018-07-27 16:18:30

Hi Thomas,
Really grateful for your input on this, thank you very much.
My compilers are pretty old indeed, I'm using Intel compilers 2013. It looks like they're affected from the same issue.

Nick

#3 Code_Aster installation » error during Aster compilation » 2018-07-06 15:23:10

laconick
Replies: 3

Hi,
I'm trying to install version 13.4, but the installation fails due to an error during the compiling process:

...
[2613/7926] Compiling bibfor/cataelem/ibcatc.F90
Waf: Leaving directory `/tmp/install_aster.2012/aster-13.4.0/build/release'
EXIT_COMMAND_2012_00000152=1

 *** Exception raised : error during compilation

That using Intel compilers, but the result isn't much different with the GNU compilers:

...
[7912/7926] Linking build/release/bibc/aster
Waf: Leaving directory `/tmp/install_aster.5623/aster-13.4.0/build/release'
EXIT_COMMAND_5623_00000109=1

 *** Exception raised : error during compilation

Anybody have any suggestions on how to deal with these frustrations?
Attached are the log files related to the first attempt (Intel compilers).
Thanks for helping

#4 Re: Code_Aster usage » [Solved] CALC_CHAMP Erreur lors de la fabrication d'un champ ... » 2017-07-12 17:22:07

Not completely clear, but modifying the comm file as follows solves the issue

EQ_Sup_B=CALC_CHAMP(RESULTAT=Ch_Sup_B,
                    GROUP_MA='shell',
                    CRITERES='SIEQ_NOEU',);

essentially you must add the keyword GROUP_MA also to CALC_CHAMP

#5 Re: Code_Aster usage » [Solved] CALC_CHAMP Erreur lors de la fabrication d'un champ ... » 2017-07-12 16:26:27

One more info: I've just noticed that the element M206614 is a Tetra, the model contains solid elements, but the field Ch_Sup_B shouldn't, since it's calculated only on the group "shell".

#6 Code_Aster usage » [Solved] CALC_CHAMP Erreur lors de la fabrication d'un champ ... » 2017-07-12 16:04:12

laconick
Replies: 2

Hi all,
I’m post-processing a shell structure with the “usual” procedure (at least, I’ve used it many times, I think it should be ok):

  result = CALC_CHAMP(reuse=result,
                      FORCE=('REAC_NODA', ),
                      RESULTAT=result,
                      PRECISION=1.E-06,
                      CONTRAINTE=('SIGM_ELNO', 'SIGM_ELGA'),
                      INFO=1,
                      CRITERE='RELATIF',)

Ch_Sup_B = POST_CHAMP(GROUP_MA=('shell', ),
                        RESULTAT=result,
                        EXTR_COQUE=_F(NUME_COUCHE=1,
                                      NIVE_COUCHE='SUP',
                                      NOM_CHAM=('SIGM_ELNO', 'SIGM_ELGA'),),
                        )

  EQ_Sup_B = CALC_CHAMP(RESULTAT=Ch_Sup_B,
                        PRECISION=1.E-06,
                        CRITERES=('SIEQ_NOEU', ),
                        INFO=1,
                        CRITERE='RELATIF',)

but today I’m getting the following error and cannot figure out what’s happened:

   !----------------------------------------------------------------------------!
   ! <EXCEPTION> <CALCULEL_58>                                                  !
   !                                                                            !
   ! Erreur lors de la fabrication d'un champ par éléments :                    !
   !  Il manque la composante : SIXX  sur la maille : M206614                   !
   !  Champ : &&CALCUL.CHML.1                                                   !
   !                                                                            !
   ! Risques et conseils :                                                      !
   !  Si cette erreur se produit lors de l'exécution de la commande PROJ_CHAMP, !
   !  il est possible de poursuivre le calcul en choisissant PROL_ZERO='OUI'    !
   !----------------------------------------------------------------------------!

Could someone give me a clue?
Thanks

Nick

#7 Re: Code_Aster usage » [SOLVED] XFEM results » 2017-03-04 16:33:44

Many thanks for having posted that solution, which helped me to solve an old issue. I don't understand why, but it works. Even in structural analysis in order to put calculated fields on the nodes in the same group of DEPL, and so allowing a nice postprocessing with ParaVIS.

#9 Re: Code_Aster usage » [Discussion] How to model a hinge bc allowing large rotations » 2014-01-14 10:51:38

Thanks Richard, interesting script. However, I wonder whether it is worthwhile to use spiders. The method proposed by Lagrange to make the connection seems good, however you do not get reliable indications on the stress on the hole. So why not use LIASON_SOLIDE, instead of spiders?

#10 Re: Code_Aster usage » [Discussion] How to model a hinge bc allowing large rotations » 2014-01-14 08:24:01

lagrange wrote:

The first node of each SEG2 element should be BOLT_HINGE1 and the second node should be one node at the sliding surface of BOLT

Let me get this: you must first build two "spiders" from the central node to the surface of the hole. Right?
Not bad, but maybe this modeling is a bit slow if there are a several pins. Is there a way to automate the construction of the spiders?

#11 Re: Code_Aster usage » CHAM_UTIL: les paramètres de la formule n'ont pas été fournis? » 2013-12-23 15:15:33

Here the new .comm, but the med file is 20 Mb compressed: I do not know how to send it ... by email?

#12 Re: Code_Aster usage » CHAM_UTIL: les paramètres de la formule n'ont pas été fournis? » 2013-12-23 12:52:49

This is quite funny indeed, my problem now runs even replacing SIEF_ELNO to EFGE_ELNO.
I remove the SOLVED tag from the first post, there is still something to look into.

Nick

#13 Re: Code_Aster usage » CHAM_UTIL: les paramètres de la formule n'ont pas été fournis? » 2013-12-23 10:30:18

jeanpierreaubry wrote:

try to write 2 different CALC_CHAMP with group restriction according to the formula

That was the issue!
I thought that the non-existent components for a part of the model were set to zero. I was wrong.
Thank you!

#14 Re: Code_Aster usage » CHAM_UTIL: les paramètres de la formule n'ont pas été fournis? » 2013-12-23 09:18:16

Of course. I enclose solution and post-processing .comm and .mess files.
Thanks

#15 Re: Code_Aster usage » publication of my book "Beginning with Code_Aster" » 2013-12-20 17:47:02

Great job! I took a look at the pdf: not just for beginners I'd say. I'm going to order the hard copy to keep on my desk.

#16 Code_Aster usage » CHAM_UTIL: les paramètres de la formule n'ont pas été fournis? » 2013-12-20 17:30:24

laconick
Replies: 10

Hello,
I ask for help to the forum because I get a strange message post-processing a linear analysis of a mixed model 3D-1D. I'm using Code_Aster 11.4 .
The interesting part of the comm file is as follows:

T = FORMULE(VALE='sqrt(VY**2+VZ**2)',
            NOM_PARA=('VY','VZ',),);

M = FORMULE(VALE='sqrt(MFY**2+MFZ**2)',
            NOM_PARA=('MFY','MFZ',),);

result=CALC_CHAMP(reuse =result,
                  RESULTAT=result,
                  CONTRAINTE='EFGE_ELNO',
                  CRITERES='SIEQ_NOEU',
                  FORCE='REAC_NODA',
                  CHAM_UTIL=_F(NOM_CHAM='EFGE_ELNO',
                               FORMULE=(M,T,),
                               NUME_CHAM_RESU=2,),);

The error I get:

!------------------------------------------------------------------------------------!
   ! <A> <FONCT0_9>                                                                     !
   !                                                                                    !
   ! Erreur lors de l'interpolation de la fonction 'M'.                                 !
   !                                                                                    !
   ! Les paramètres de la formule n'ont pas été fournis.                                !
   ! Paramètres manquants : 'MFY', 'MFZ'                                                !
   !                                                                                    !
   ! 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 !                             !
   !------------------------------------------------------------------------------------!
   
   
   !----------------------------------------------------------------!
   ! <A> <FONCT0_9>                                                 !
   !                                                                !
   ! Erreur lors de l'interpolation de la fonction 'M'.             !
   !                                                                !
   ! Nombre de paramètres fournis : 1                               !
   ! Noms des paramètres fournis  : N                               !
   !                                                                !
   !                                                                !
   ! Ceci est une alarme. Si vous ne comprenez pas le sens de cette !
   ! alarme, vous pouvez obtenir des résultats inattendus !         !
   !----------------------------------------------------------------!
   
   
   !------------------------------------------------------------------------------------!
   ! <A> <FONCT0_9>                                                                     !
   !                                                                                    !
   ! Erreur lors de l'interpolation de la fonction 'M'.                                 !
   !                                                                                    !
   ! Les paramètres de la formule n'ont pas été fournis.                                !
   ! Paramètres manquants : 'MFY', 'MFZ'                                                !
   !                                                                                    !
   ! 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 !                             !
   !------------------------------------------------------------------------------------!
   
   
   !----------------------------------------------------------------!
   ! <A> <FONCT0_9>                                                 !
   !                                                                !
   ! Erreur lors de l'interpolation de la fonction 'M'.             !
   !                                                                !
   ! Nombre de paramètres fournis : 3                               !
   ! Noms des paramètres fournis  : N VY VZ                         !
   !                                                                !
   !                                                                !
   ! Ceci est une alarme. Si vous ne comprenez pas le sens de cette !
   ! alarme, vous pouvez obtenir des résultats inattendus !         !
   !----------------------------------------------------------------!

However the fields MFY and MFZ are available, I can visualize them opening the result file.
Moreover I'm pretty sure I used the same procedure in the past without any problem. What am I missing?
Thanks for helping.

Nick

#17 Re: Code_Aster installation » STA11.4 not create in a ca 11.4 installation » 2013-07-18 15:11:43

Hi, from what it is said here  the structure of the installation directory is changed.

#18 Re: Code_Aster installation » error installation 11.4 » 2013-07-16 13:20:03

Thomas DE SOZA wrote:

Try to post the contents of the med install directory $ASTER_ROOT/public/med-3.0.6

Here it is:

nicola@darkstar:~/bin/aster/public/med-3.0.6$ ls -l
total 16 
drwxr-xr-x 6 nicola users 4096 Jul 15 16:05 bin/ 
drwxr-xr-x 3 nicola users 4096 Jul 15 16:05 include/ 
drwxr-xr-x 2 nicola users 4096 Jul 15 16:05 lib/ 
drwxr-xr-x 3 nicola users 4096 Jul 15 16:05 share/

#19 Re: Code_Aster installation » error installation 11.4 » 2013-07-16 12:27:03

Sorry for my unsolicited intervention in your discussion but I wanted to point out that I get an error very similar to Jean Perre (logs few posts above) but I'm not on Suse and I performed a fresh install in an empty directory.

Nick

#20 Re: Code_Aster installation » error installation 11.4 » 2013-07-15 16:18:32

I get the same error.
In the setup.cfg I modified only ASTER_ROOT and PREFER_COMPILER_aster
Before launching the installation I sourced the environment for the Intel compilers.
I enclose setup.log and config.log
Thanks for helping

Nick

#21 Re: Code_Aster usage » [SOLVED] Contact issues in 11.3 » 2013-06-20 09:50:26

Thanks Thomas,
I hate posting questions already covered, but I did not find any helpful post applicable to my case.
Anyway your suggestion has produced a marked improvement. With ALGO_RESO_GEOM = 'POINT_FIXE' the solution progress is comparable with that of stable release.
I understand that the weakness of the NEWTON option is a problem related only to the 11.3 release, right?

Nick

#22 Code_Aster usage » [SOLVED] Contact issues in 11.3 » 2013-06-19 17:40:04

laconick
Replies: 3

Hi all,
I switched recently to the version 11.3 and I was wondering if it is really better in solving contact problems. It seems to me that there are more difficulties in convergence.

In this regard I would like to ask for an opinion about a problem that I'm trying to solve. It is a simulation quite challenging because the parts are held together only by contact, but I managed to solve it easily enough with STA10.8 (with the formulation 'CONTINUE' and CONTACT_INIT = 'OUI').
Using the same .comm file and the same mesh, with the version 11.3 I cannot get to convergence. Greatly reducing the time step I get an initial convergence (and the result looks good) but then it diverge rapidly. I admit that I have not re-read all the relevant documentation, but the fact that as_run accept the .comm makes me think that things should not be changed very much.

I enclose two .mess files related to one of the attempts I made with the two versions of code_aster, if someone want to look at them to help me understand.

Thanks.

#23 Re: Code_Aster usage » Effort de presse » 2013-06-18 16:55:57

I'm not particularly competent in large plastic deformation problems, I can only give you a hint for extracting the applied force: If I understand the question, you can extract the field REAC_NODA with CALC_CHAMP (or CALC_NO in pre-11)

#24 Re: Code_Aster usage » Shrink fits/Frettages » 2013-06-18 15:44:07

Interesting observations. I focused on making it work, I didn't study the problem. Indeed, the interference is fully recovered in the first step making it pretty useless to use a step so small ... I remember that in the past CONTACT was inside AFFE_CHAR_MECA and perhaps was influenced by the multiplying function of the loading. Today I do not know if there is any way to divide it in different steps ... I can not answer.

#25 Re: Code_Aster usage » Shrink fits/Frettages » 2013-06-18 11:08:47

I don't entirely agree Jean Pierre, the geometric interference produces a contact pressure, and then a load. Code_Aster can solve this situation.
It also provides for the possibility of imposing interference via command file by means of DIST_MAIT / DIST_ESCL, if you want to model the parts in nominal size.
I enclose a working version of Antoine's comm file.

Nick