user unbanned

On a bien d'autres choses à faire que de bannir des utilisateurs !
C'est FLuxBB qui bannit parfois des gens automatiquement, peut-être des problèmes d'échec de connexion, peut-être lié à l'hébergement...

/home/containers != $HOME/containers

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

Pull repositories (src and devtools) from sourceforge.

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

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

[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...

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

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

Hello all!

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

net-tools
libnlopt0

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

Hi,

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

MC