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

You are not logged in.

#1 Re: Salome-Meca installation » [SOLVED] Salome-meca 2019.0.0-1 » 2019-10-07 07:17:17

iwan wrote:

Does Python2 still needed to compile SM2019?


All is provided as binary (the source of these problems!!!), you don't compile anything.

But the installer (post-install step) needs 'python' and it seems that it should be python2...

$(which python) --version
must return a Python2 version.


#2 Re: Salome-Meca installation » [SOLVED] Salome-meca 2019.0.0-1 » 2019-10-02 21:46:06


Thank you for your feedbacks!

We had very few time this year to prepare the LGPL version. We need your help to improve the installation notes on various configurations.

2018 shown at startup, title window, Help/About panel: ok, easy to fix!

Warnings about "improperly configured" SMESH plugins": I don't know why and they are working as expected.

Starting from the desktop icon: that's probably because you need to set the Qt 5.9.1 environment before starting salome_meca.
You can simply change the desktop file and call a wrapper that source Qt 5.9.1 env and then execute "......./salome $@"

A build of Qt-5.9.1 libraries are embedded, could you try if it works with (instead of your own build):

export LD_LIBRARY_PATH=<SMECA INSTALL>/V2019_univ/prerequisites/Qt-591/lib/lib:$LD_LIBRARY_PATH


#4 Re: Salome-Meca installation » [SOLVED] Salome-meca 2019.0.0-1 » 2019-10-01 14:14:09

Hello all!

For the error message at startup "/Kernel/Session" not found, it should be solved by installing these packages:


#6 Re: Code_Aster installation » could not find the python module 'numpy' » 2019-06-30 09:49:10

We do not give enough details: which version are you installing? code_aster / salome_meca?

Versions before 14.3.5 require python 2.7 : please see the README file.
After, only Python 3 will be supported. But there is not yet aster-full package for this version (expected in July for 14.4).


#7 Re: Code_Aster installation » Salome-Meca V2018 on Ubuntu 18.04 » 2019-06-30 09:46:07

You could try with a new user account to check if it is related to your user environment.

Preferences, most recently used files...: $HOME/.config/salome directory may be corrupted. You can remove it (you only loose some prefs).

#8 Re: Code_Aster installation » Any plans to provide a "full-src" package for V14.3? » 2019-06-30 09:39:51


Packages aster-full-src will be available for 13.8 and 14.4.


#9 Re: Code_Aster usage » Assignment of two fields with CREA_RESU [SOLVED] » 2019-04-19 14:49:54


Are you sure that you are using the same code_aster version?
Isn't it a confusion with salome_meca 2018.0.1 "official" and  the "V8_INTEGR" one that might be wrong?

To be sure, can you send me the revision SHA1 that is printed at the beginning of the execution by each version (just run DEBUT/FIN for example)?
Warning: the header is not printed in case of syntax error!


#10 Re: Code_Aster installation » *SOLVED* Code_Aster 13.6.0 installation failed on Ubuntu 18.06 LTS » 2019-04-17 10:24:14


Searching for the message found in setup.dbg ('MPFR assertion failed') points consistency issues between mpfr4/mpfr6...?

The compilation has been successfully tested on Ubuntu 18.04.1 LTS.

These packages are installed:

ii  libmpfr6:amd64             4.0.1-1                           amd64        multiple precision floating-point computation
ii  libopenblas-base:amd64     0.2.20+ds-4                       amd64        Optimized BLAS (linear algebra) library (shared library)
ii  libopenblas-dev:amd64      0.2.20+ds-4                       amd64        Optimized BLAS (linear algebra) library (development files)


#11 Re: Code_Aster installation » [SOLVED] Interactive Follow-up -Terminal Does not Open in Ubuntu 18.04 » 2019-04-17 10:10:16


If you installed xterm, try to add this line in $HOME/.astkrc/prefs:

terminal : /usr/bin/xterm


#12 Re: Code_Aster usage » Assignment of two fields with CREA_RESU [SOLVED] » 2019-04-15 17:38:02


Could you send me the full output (.o + .e from ~/flasheur)?
or the .hdf file + _Files directory?

#13 Re: Code_Aster installation » Erreurs en installant Code Aster 13.6 sur Red Hat 7 » 2019-04-15 12:33:47


  The C/fortran test program calling blas and lapack subroutines failed.

=> ce message au début explique sans doute la suite : mumps et aster ont besoin de blas/lapack (ici mkl).

Un truc bizarre, dans le configure de mumps, on voit des mélanges avec gcc4.4 et gcc4.7...


#14 Re: Code_Aster installation » [SOLVED]Error reported in the MED library » 2019-04-15 12:24:51


Are you sure that the file does exist? Check the value of UNITE keyword.
Only this file or all med files?
Which version of code_aster? and version of the med file?


#15 Re: Code_Aster usage » Assignment of two fields with CREA_RESU [SOLVED] » 2019-04-15 12:11:57

Hi Ioannis,

The attached study works without error (with the stable version and with the last development version too).

Which version are you using?


#16 Re: Code_Aster installation » Code-Aster sur Cluster avec Slurm » 2019-01-31 10:14:51


Il faut indiquer à asrun qu'il peut utiliser un serveur de batch.

Dans etc/codeaster/asrun, il faut indiquer :

batch : oui

batch_nom : Slurm
# limits
batch_memmax : 512000
batch_tpsmax : 9999:00:00
batch_nbpmax : 24
batch_mpi_nbpmax : 2048

# groups of batch queues and queues in each group (batch_queue_'group name')
batch_queue_group : cn64 cn256 cn512
batch_queue_cn64 : cn64
batch_queue_cn256 : cn256
batch_queue_cn512 : cn512
(les groupes ont là pour minimiser les choix pour l'utilisateur, ici on n'a mis qu'une qos slurm par groupe donc avec un groupe de même nom)

Pour MPI, il faut dans ce même fichier :

# directory shared by all nodes
shared_tmp : /scratch/$LOGNAME

# mpirun command for IntelMPI
mpirun_cmd : mpirun -np %(mpi_nbcpu)s -print-rank-map -prepend-rank -ordered-output %(program)s

# for OpenMPI
# mpirun_cmd : mpirun --tag-output -np %(mpi_nbcpu)s --hostfile %(mpi_hostfile)s %(program)s

# if necessary by the mpi implementation
mpi_hostfile : $ASTER_ETC/codeaster/mpi_hostfile

mpi_get_procid_cmd : echo $PMI_RANK

Chez nous, mpi_hostfile n'est pas nécessaire car il n'est pas utilisé sur la ligne de commande mpirun IntelMPI.
Avec OpenMPI, j'ai simplement "localhost" dans le fichier mpi_hostfile mais je ne l'utilise pas sur cluster.
Essayer sans l'argument --hostfile, sinon il faut voir comment récupérer les noeuds alloués...


#17 Re: Code_Aster installation » TERMINAL is required by 'astk' but not set. Avoiding xterm install. » 2018-12-18 17:31:55


Just define in 'setup.cfg':

TERMINAL = '/bin/true'

I think there is no checking on this parameter...
Of course, "interactive follow-up" will fail on this server.


#19 Re: Code_Aster installation » trouble to build the unstable version » 2018-08-24 07:03:17


This is a regression in devtools that is now fixed and will be available very soon.


#20 Re: Code_Aster installation » Code_Aster inside a Docker container available for everyone » 2018-06-01 12:16:10

Great! Thank you for this contribution.

I hope that it helps some users to test the parallel version.


#21 Re: Salome-Meca installation » OpenSUSE Tumbleweed : Error during salome launch » 2017-12-15 11:33:47


Usually this proble appears when Salome ORB can not connect to its server (locally).
Ensure that you can resolve your hostname: ping $(hostname)

If not, you should have to add your hostname in /etc/hosts on the same line as localhost (ip
=> check that ping now responds

Else you may try to comment ipv6 lines in /etc/hosts...


#22 Re: Code_Aster installation » [SOLVED] 13.4 build-install: MFront and Mumps fail on Ubuntu-14.04 » 2017-09-27 07:02:19


Why not installing Salome-Meca which includes code_aster 13.4 (and 12.8)?


#23 Re: Salome-Meca installation » AsterStudy error in Windows 10 » 2017-09-08 13:59:08


Sure we didn't test anything on Linux inside a window10.

However dateutil is embedded by the matplotlib installation.
On my installation it is in:

A 'egg' is a zip file, maybe it cannot be uncompress under windows...


#24 Re: Salome-Meca installation » [SOLVED]runSession in salome_meca 2017 » 2017-09-04 14:58:47

To set the SALOME environment, just use:

salome shell -- myprogram.sh [arguments]

#25 Re: Salome-Meca installation » [SOLVED]runSession in salome_meca 2017 » 2017-09-04 12:11:39


I don't exactly remember what runSession did but it should be replace by `salome start --terminal myscript.py`