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

You are not logged in.

#2 Code_Aster development » Is CA still being developed? » 2022-08-28 16:32:33

toltec
Replies: 19

Hi All,

Is Code Aster still being developed? Years ago there were releases every 6 months or so, it all seems pretty quiet at the moment.

Gary

#3 Re: Code_Aster usage » publication of my book "Beginning with Code_Aster" » 2014-01-08 16:25:47

Thank you Jean Pierre Aubry, a fantastic reference book, especially when trying to introduce someone to Aster!

Regards

Gary

#5 Salome-Meca usage » [Closed] Multicore Usage? » 2013-11-05 11:27:03

toltec
Replies: 1

Greetings,

A benchmark analysis of mine, which uses all available cores on an Aster installation compiled by myself using an Intel threaded maths library, only uses one core in Salome-Meca 2013-2.

I have set the number of cores in both ASTK and /opt/SALOME-MECA-2013.2-LGPL/tools/Code_aster_frontend_1131final/etc/codeaster/asrun, but still only one core is used.

Am I missing anything? If someone has an idea how I can get around this I'd be very happy.

Regards

Gary

#6 Re: Code_Aster installation » [SOLVED]install aster-full-src-11.4.0-2 on opensuse 12.3 fails » 2013-07-29 20:06:14

Thanks to the EDF staff for fixing this. CA now compiles (Intel Compilers only) and runs on my Ubuntu 12.04 64bit machine.

Regards

Gary

#7 Re: Code_Aster installation » error installation 11.4 » 2013-07-13 10:14:19

Jeanpierreaubry,

The setup.log file you require was deleted as I have rebooted my machine. When I get a chance I'll recompile and send it to you.

BTW, as mentioned I can compile with GNU but can't launch an analysis, so perhaps my installation isn't working. I think I'll give up on V11.4 until EDF fix this issue.

#8 Re: Code_Aster installation » How to Run 2000+ Test Cases » 2013-07-12 12:17:45

Files attached.

gcc version 4.6.3

Hope this helps

#9 Re: Code_Aster installation » How to Run 2000+ Test Cases » 2013-07-12 10:25:30

Hi jeanpierreaubry,

I can compile OK using the GNU compilers only which is why I want to run the 2000+ tests. I always run these tests to check how robust my installation is... in my experience (perhaps particular to me) the GNU installation always results in many NOOK/ERROR results for astout.export. My Intel installation is always more robust and of course faster.

To answer what I think your question is, I'm still not able to compile v11.4 using Intel. IMHO something in the installation script has changed from V11.3

Please let me know if you find you way around this problem.

Regards

Gary

#10 Re: Code_Aster installation » How to Run 2000+ Test Cases » 2013-07-12 10:04:29

2000+ cases... wow! That'll take forever to build!

What happened to the astout.export method?

#11 Code_Aster installation » How to Run 2000+ Test Cases » 2013-07-12 08:50:13

toltec
Replies: 13

Greetings All,

I've compiled v11.4 using the GNU compilers. I now want to run the 2000+ test cases as documented in README_aster.txt (which I've done many times for previous releases). The installation directory structure has changed from earlier releases. I can find the test input files in the SRC directory, but how do I run all cases using astout.export (which has vanished in V11.4)?

Regards

Gary

#12 Re: Code_Aster installation » error installation 11.4 » 2013-07-11 14:41:52

Hi,

I'm using Intel Composer 2011 and had no problems installing v11.2 and v11.3.  V11.4 installs OK using GNU only. I've tried sourcing from the command line and inserting the following in setup.cfg without success:

OPT_ENV="""
source /opt/intel/bin/iccvars.sh intel64
source /opt/intel/bin/ifortvars.sh intel64
source /opt/intel/bin/compilervars.sh intel64
source /opt/intel/mkl/bin/intel64/mklvars_intel64.sh
"""
WRT LANG, I haven't had to use this for a long time, so I suspect this isn't the issue, but may be wrong.

It seems to me that something in the install script has changed since V11.3?

Regards

Gary

#13 Re: Code_Aster installation » error installation 11.4 » 2013-07-11 09:05:21

Hi Thomas,

Attached is my config.log. I'm compiling using Intel (no GNU) on Ubuntu 12.04. I have libstdc++-devel installed.

Any help would be appreciated.

Regards

Gary

#14 Re: Code_Aster installation » error installation 11.4 » 2013-07-10 16:45:51

Hi Jean Pierre Aubry,

I get this error too (when compiled with Intel only and GNU/Intel). If I find a workaround I'll let you know.

Regards

Gary

#15 Re: Code_Aster usage » Change the defaults of code aster parameters » 2012-09-19 22:47:48

Hello Alex,

I think these can be set in, but may be wrong:

/$ASTER_ROOT/etc/codeaster/asrun.

Setting ncpus=7 in ASTK and saving the .astk file will keep the ncpus setting for that file/analysis (if Aster has been compiled using threading and the correct Intel Maths libraries)

Just my 10 cents worth...

Gary

#17 Re: Code_Aster usage » [SOLVED] SHB8 Output » 2012-08-30 10:57:06

Hi Delmas,

My mesh isn't SHB8, but rather SHB20, so the current bug covers my problem. Sorry for confusion.

Is it possible for forum members to view the bug log?

Thanks for your time.

Regards

Gary

#18 Re: Code_Aster usage » [SOLVED] SHB8 Output » 2012-08-30 10:43:56

Hi Delmas,

It aborts in CALC_CHAMP:


  STATIC=CALC_CHAMP(reuse = STATIC,
                    INFO=1,
                    CRITERE='RELATIF',
                    RESULTAT=STATIC,
                    CRITERES='SIEQ_NOEU',
                    VARI_INTERNE='VARI_NOEU',
                    PRECISION=1.E-06,
                    MODELE=BM,
                    CHAM_MATER=all_mat,
                    );

   
   !----------------------------!
   ! <EXCEPTION> <MODELISA3_27> !
   !                            !
   !  type d élément inconnu    !
   !----------------------------!

Files are attached.

Regards

Gary

#19 Code_Aster usage » [SOLVED] SHB8 Output » 2012-08-30 10:28:32

toltec
Replies: 5

Greetings All,

I want to write results to a .med file for SHB8 elements (V11.2). I want plastic strain equivalent and Mises stress at the nodes, so I figured the following would do (as per solid elements):

STATIC=CALC_CHAMP(reuse =STATIC,
                  MODELE=Assembly,
                  CHAM_MATER=all_mat,
                  RESULTAT=STATIC,
                  CRITERES='SIEQ_NOEU',
                  VARI_INTERNE='VARI_NOEU',);

IMPR_RESU(MODELE=Assembly,
          FORMAT='MED',
          RESU=_F(MAILLAGE=assembly,
                  RESULTAT=STATIC,
                  NOM_CHAM=('SIEQ_NOEU','VARI_NOEU','DEPL',),),);

This aborts with an error -> type d élément inconnu

I've tried various output requests, but the only one that works is  CRITERES='SIEQ_ELGA',);

Can anyone point me in the right direction... should I use POST_CHAMP for SHB8?

Regards

Gary

#20 Re: Code_Aster usage » [SOLVED] Solids Elements with COQUE_3D Skin » 2012-08-23 16:47:37

Thomas, Paul,

Thanks for your suggestions and input. The shell stresses do indeed decrease if I lower the drill stiffness, so at least I now understand what's going on. It's interesting though that a model consisting only of COQUE_3D elements doesn't produce these stresses when rotated. Although these shells are all in the same plane...

Thanks again.

Gary

#21 Re: Code_Aster usage » [SOLVED] Solids Elements with COQUE_3D Skin » 2012-08-23 13:40:15

Hi Paul,

Thanks for your post. Using solids for connectors is a good idea... probably a better strategy given that that is how real world connectors work!

I am however still uncomfortable as to why unloaded shell elements on the face of rotating,unloaded solids produce stress. Either I don't understand something, or the COQUE_3D formulation has a problem with this technique.

Gary

#22 Re: Code_Aster usage » [SOLVED] Solids Elements with COQUE_3D Skin » 2012-08-23 09:54:53

Greetings Thomas,

The shells are intended to stand in for LIAISON_SOLIDE elements in a GROT_GDEP analyses, so they line the holes in the 3D elements and also close the holes. Loads/BCs will be applied to these shells and other parts will connect to them.

To clarify this, attached is a simplified model which demonstrates how these shells generate stresses even though forces in the structure are minimal. I've also included a document describing this model.

Many thanks for to you for your help and for anyone who cares to jump in.

Cheers

Gary

#23 Re: Code_Aster usage » [SOLVED] Solids Elements with COQUE_3D Skin » 2012-08-22 12:29:18

Hi Thomas,

Attached is a document showing my set-up. Rotation occurs by defining a translational displacement at a node which causes the structure to rotate. Unexpected stresses develop at any shells that move.

As a matter of interest when applying a thin shell layer (0.1mm) on the green part these shells also generate stresses in some areas as the structure rotates. Perhaps this has something to do with the shell normals? I've arbitrarily defined them as ANGL_REP=(0,1,)

Cheers

Gary

#24 Code_Aster usage » [SOLVED] Solids Elements with COQUE_3D Skin » 2012-08-21 17:27:29

toltec
Replies: 9

Hello All,

I'm building a non-linear model (STAT_NON_LINE, VMIS_ISOT_TRAC, GROT_GDEP) which will undergo large rotations (car suspension). I cannot use LIAISON_SOLIDE to connect parts as these constraints should not be used with GROT_GDEP (they generate significant stresses). I have therefore used COQUE_3D elements as a skin over solid elements to act as connectors. The attached screen dump shows a "bolt" connection.

To cut a long story short, the model works well with the exception that the "skin" shells generate significant stresses if the unloaded mechanism is rotated. That is, when rotating the suspension (with all forces removed for testing) I would expect zero stresses in the "bolts", but 20MPa is typical. Have I missed something about Aster that makes this model set-up wrong?

Any ideas would be greatly appreciated!

Cheers

Gary

PS I've checked hinge alignment, so forces are not being generated by misalignment.

#25 Re: Code_Aster usage » COQUE_3D + Hex Post Processing » 2012-08-21 17:00:07

Thanks Thomas, I'll take a look at this option.

Gary