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

You are not logged in.

#1 Re: Code_Aster installation » compilation errors of code-aster on debian10(bullseye). » Today 18:40:53

Hello,

Debian bulleye is Debian 11.
Debian 10 still uses GCC 8.3.

aster-full packages will probably die because a lack of maintainer(s). Compiling some the prerequisites on "all" platform may be a pain!

That's why our effort is to maintain Singularity images that embed all the needed prerequisites to build the stable and development versions.
Singularity images are available from the Download page of salome_meca.
Current containers are based on Debian 9 (which is the reference OS for salome_meca). The 2022 version will be based on Debian 10.
I already know the patch for MUMPS. Feel free to share your patch for Debian 11.

If there are some volunteers to continue aster-full setup scripts. I can try to start a repository of its files.

MC

#2 Re: Code_Aster installation » How to use Code-Aster in the "pythonic way"? » Today 18:29:27

Hello,

The container embeds a convenient starter script. See `singularity run-help NAME.sif`
It tells you to run: `singularity run --app install NAME.sif`
Then just use the created script, named as `NAME` (without .sif)
See `./NAME --help` for options.


Next steps:

$ ./NAME shell
Singularity> /opt/salome_meca/Salome-V2021-s9/tools/Code_aster_stable-1540/bin/run_aster FILENAME.export

See `run_aster --help`

Example: for interactive executions (it will stop before executing FIN):

$ ./NAME shell
Singularity> /opt/salome_meca/Salome-V2021-s9/tools/Code_aster_stable-1540/bin/run_aster -i FILENAME.export

The next version (>16.1) will allow to directly use `run_aster FILENAME.py`...

MC

#4 Re: Code_Aster installation » Install code_aster from 15.4 version » 2022-01-03 11:23:26

Pull repositories (src and devtools) from sourceforge.

but sourcing env_unstable.sh is not required (it just adds paths to devtools/bin tools).

#5 Re: Code_Aster usage » [SOLVED] How to import my own python module into .comm file » 2022-01-03 11:08:21

Hi,

from code_aster.Commands import *

"code_aster.Cata" contains the definition of available keywords.

MC

#6 Re: Code_Aster installation » [SOLVED] waf install failure on linux-ppc64le » 2021-12-22 18:47:38

Here is a patch (on head of default branch) that:
- detect ppc64le as a 64bits platform,
- add option --disable-proc-status not to control VmSize during execution to be passed at configure step.

Should be integrated soon in development branch.

For a quick fix, you can undefined ASTER_ENABLE_PROC_STATUS in generated build/*/*/asterc_config.h files.

MC

#7 Re: Code_Aster installation » [SOL]Problem in launching ASTER-STUDY Module in Salome-Meca-2021(.sif) » 2021-10-11 11:31:45

Hello,

You should see --run-help and execute:

singularity run --app install salome_meca-lgpl-2021.0.0-1-20210811-scibian-9.sif

Then, start salome_meca using the extracted script named `salome_meca-lgpl-2021.0.0-1-20210811-scibian-9`.

MC

#8 Re: Code_Aster installation » The following error occurs when installing code_aster14.4 in ubuntu » 2020-08-25 07:36:25

[edit]
code_aster < 14.3.5 needs python <= 2.7.
code_aster >= 14.3.5 needs python >= 3.

but it seems that the setup script for 14.4 still needs python 2...

#10 Re: Code_Aster usage » 'Bus Error' during execution of parallel version 14.4 » 2020-07-02 08:30:55

Hello,

There is no reason not to use all cores on your system but it will probably be not very efficient.

Each MPI process is allocating its own memory space + its own disk space.
If a process needs 4 GB RAM, you need 24x4 GB on the node + 24x(disk space needed) with 24 concurrent read/write the disk...

You should test your problem with less MPI process (4, 8, 12 mpi_ncpu) and probably 2, 4 or 6 openMP threads (ncpus parameter) to find the best configuration for your problem.

The error message of the first post may be due to a problem in MPI communications, hardware, build of the software or source code mistake...

MC

#11 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?

Hello,

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.

MC

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

Hello!

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


MC

#14 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:

net-tools
libnlopt0

#16 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).

MC

#17 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).

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

Hi,

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

MC

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

Hi,

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!

Mathieu

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

Hello,

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)

MC

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

Hello,

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

terminal : /usr/bin/xterm


MC

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

Curious...

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

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

Bonjour,

WARNING :
  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...

MC

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

Hello,

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?

MC

#25 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?

MC