Remarks on the new salome_meca-lgpl-2024.1.0-1-20240327 released today

mf

I forgot to add, that the changes made in the nvliblist.conf file are still in place. See this thread:

https://forum.code-aster.org/public/d/27539-new-version-sm-salome-meca-lgpl-202310-4-20240327-questions/2

Otherwise, no changes have been made.

Mario.

k_zurawski

This is what I'm getting in terminal:
`w2@W2:~$ singularity run salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif

running salome_meca in software rendering mode
++ using container salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif
++ using software rendering mode (should use mesa_salome starter)
AsterStudy: jeu.-09-20:39:41.679 AsterStudy is activating...
AsterStudy: jeu.-09-20:39:41.680 Creating workspace...
AsterStudy: jeu.-09-20:39:41.702 Refreshing configuration on localhost...
AsterStudy: jeu.-09-20:40:59.732 workspace is ready.
AsterStudy: jeu.-09-20:41:01.624 AsterStudy activated
AsterStudy: jeu.-09-20:41:26.662 Refreshing configuration on localhost...
AsterStudy: jeu.-09-20:41:38.440 Refreshing configuration on localhost...
AsterStudy: jeu.-09-20:41:57.849 Refreshing configuration on cronos.hpc.edf.fr...
AsterStudy: jeu.-09-20:41:57.995 exit code: 255
AsterStudy: jeu.-09-20:42:01.650 Refreshing configuration on gaia.hpc.edf.fr...
AsterStudy: jeu.-09-20:42:01.719 exit code: 255
AsterStudy: jeu.-09-20:42:04.671 Refreshing configuration on localhost...
double free or corruption (out)
[W2:00063] *** Process received signal ***
[W2:00063] Signal: Abandon (6)
[W2:00063] Signal code: (-6)
[W2:00063] [ 0] /lib/x86_64-linux-gnu/libpthread.so.0(+0x13140)[0x7f05dc058140]
[W2:00063] [ 1] /lib/x86_64-linux-gnu/libc.so.6(gsignal+0x141)[0x7f05d9453d51]
[W2:00063] [ 2] /lib/x86_64-linux-gnu/libc.so.6(abort+0x123)[0x7f05d943d537]
[W2:00063] [ 3] /lib/x86_64-linux-gnu/libc.so.6(+0x7a458)[0x7f05d9495458]
[W2:00063] [ 4] /lib/x86_64-linux-gnu/libc.so.6(+0x8174a)[0x7f05d949c74a]
[W2:00063] [ 5] /lib/x86_64-linux-gnu/libc.so.6(+0x82d78)[0x7f05d949dd78]
[W2:00063] [ 6] /usr/lib/python3/dist-packages/PyQt5/QtCore.abi3.so(+0x2137ad)[0x7f0577f007ad]
[W2:00063] [ 7] /usr/lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0x1131a7)[0x7f05e368c1a7]
[W2:00063] [ 8] /usr/lib/x86_64-linux-gnu/libpython3.9.so.1.0(+0x2686c7)[0x7f05e37e16c7]
[W2:00063] [ 9] /usr/lib/x86_64-linux-gnu/libpython3.9.so.1.0(Py_FinalizeEx+0x74)[0x7f05e3760a84]
[W2:00063] [10] SALOME_Session_Server_No_Server(Z18AbstractGUIAppMainI14GUIAppNewStyleEiiPPc+0x2651)[0x5647f6779ef1]
[W2:00063] [11] /lib/x86_64-linux-gnu/libc.so.6(__libc_start_main+0xea)[0x7f05d943ed7a]
[W2:00063] [12] SALOME_Session_Server_No_Server(start+0x2a)[0x5647f677517a]
[W2:00063] *** End of error message ***
ERROR:salomeContext:Unexpected error:
ERROR : 20:47:21.418 : Unexpected error: ( callsite is _startSalome of file "/opt/salome_meca/V2024.1.0_scibian_univ/prerequisites/Cea_archive-9120/BINARIES-DB11/SALOME/bin/salome/salomeContext.py" at line 309 )
Traceback (most recent call last):
File "/opt/salome_meca/V2024.1.0_scibian_univ/prerequisites/Cea_archive-9120/BINARIES-DB11/SALOME/bin/salome/salomeContext.py", line 299, in _startSalome
res = getattr(self, command)(options) # run appropriate method
File "/opt/salome_meca/V2024.1.0_scibian_univ/prerequisites/Cea_archive-9120/BINARIES-DB11/SALOME/bin/salome/salomeContext.py", line 390, in sessionless
runSalome.runSalome()
File "/opt/salome_meca/V2024.1.0_scibian_univ/prerequisites/Cea_archive-9120/BINARIES-DB11/KERNEL/bin/salome/runSalome.py", line 338, in runSalome
foreGround(args, ior_fakens_filename)
File "/opt/salome_meca/V2024.1.0_scibian_univ/prerequisites/Cea_archive-9120/BINARIES-DB11/KERNEL/bin/salome/runSalome.py", line 308, in foreGround
killProcessSSL(port,[session_pid])
File "/opt/salome_meca/V2024.1.0_scibian_univ/prerequisites/Cea_archive-9120/BINARIES-DB11/KERNEL/bin/salome/killSalomeWithPort.py", line 313, in killProcessSSL
__killPids(pids_list)
File "/opt/salome_meca/V2024.1.0_scibian_univ/prerequisites/Cea_archive-9120/BINARIES-DB11/KERNEL/bin/salome/killSalomeWithPort.py", line 256, in __killPids
__killProcesses(processes)
File "/opt/salome_meca/V2024.1.0_scibian_univ/prerequisites/Cea_archive-9120/BINARIES-DB11/KERNEL/bin/salome/killSalomeWithPort.py", line 237, in killProcesses
process.terminate()
File "/usr/lib/python3/dist-packages/psutil/init__.py", line 271, in wrapper
raise NoSuchProcess(self.pid, self.name)
psutil.NoSuchProcess: psutil.NoSuchProcess process no longer exists (pid=63)`

AsterO'dactyle

No problem for me on my Linux ubuntu 22.04 machine.
Do you use access to Amazon Web Services?

mf

AsterO'dactyle
Hello all,

I have some good news and some bad news.

I managed to compile a stable MPI-version with CA 16.7 in this container salome_meca-lgpl-2024.1.0-1-20240327.

The bad news is: I only managed to do this WITHOUT Metis and without Petsc. I can live without Petsc, but without Metis, the MPI-version does NOT make much sense, now does it?

However, I noticed the following: even in the stable 16.7 in this container there is no Metis. Why is that? Is this intentional, I suppose so? The basic output of this stable 16.7 looks like this (why does it show 'testing' in the first line?):

             -- CODE_ASTER -- VERSION : DÉVELOPPEMENT STABILISÉE (testing) --                  
                           Version 16.7.0 modifiée le 10/12/2024                                
                           révision 5f2fdcddabc5 - branche 'HEAD'                               
                               Copyright EDF R&D 1991 - 2025                                    
                          Exécution du : Fri Jan 10 10:43:02 2025                               
                          Nom de la machine : HP-Z8-G4-Workstation                              
                                    Architecture : 64bit                                        
                                Type de processeur : x86_64                                     
           Système d'exploitation : Linux-6.8.0-51-generic-x86_64-with-glibc2.31                
                              Langue des messages : fr (UTF-8)                                  
                                 Version de Python : 3.9.2                                      
                                 Version de NumPy : 1.19.5                                      
                                 Parallélisme MPI : inactif                                     
                                Parallélisme OpenMP : actif                                     
                          Nombre de processus OpenMP utilisés : 1                               
                           Version de la librairie HDF5 : 1.10.3                                
                            Version de la librairie MED : 4.1.1                                 
                           Version de la librairie MFront : 4.1.0                               
                           Version de la librairie MUMPS : 5.5.1c                               
                              Librairie PETSc : non disponible                                  
                           Version de la librairie SCOTCH : 7.0.1

My questions are, for the moment, because I did not do a test run yet:

Does this MPI-version even make sense without Metis, will Scotch work (it never worked in my CA-versions in the past)?
I downloaded the prerequisites codeaster-prerequisites-20240327-oss.tar.gz, there is a Metis metis-5.1.0.tar.gz inside, but I cannot untar it, I get an errror something like 'not an archive'. So I cannot include Metis here.

Maybe AsterO'dactyle, can you please comment? Thanks a lot,

Mario.

I will do some testing with this MPI version today. The basic setup is this:

             -- CODE_ASTER -- VERSION : DÉVELOPPEMENT STABILISÉE (testing) --                  
                           Version 16.7.0 modifiée le 10/01/2024                                
                                révision n/a - branche 'n/a'                                    
                               Copyright EDF R&D 1991 - 2025                                    
                          Exécution du : Fri Jan 10 10:33:42 2025                               
                          Nom de la machine : HP-Z8-G4-Workstation                              
                                    Architecture : 64bit                                        
                                Type de processeur : x86_64                                     
           Système d'exploitation : Linux-6.8.0-51-generic-x86_64-with-glibc2.31                
                              Langue des messages : fr (UTF-8)                                  
                                 Version de Python : 3.9.2                                      
                                 Version de NumPy : 1.19.5                                      
                                  Parallélisme MPI : actif                                      
                               Rang du processeur courant : 0                                   
                           Nombre de processeurs MPI utilisés : 1                               
                                Parallélisme OpenMP : actif                                     
                          Nombre de processus OpenMP utilisés : 1                               
                           Version de la librairie HDF5 : 1.10.9                                
                            Version de la librairie MED : 4.1.1                                 
                           Version de la librairie MFront : 4.2.0                               
                          Version de la librairie MUMPS : 5.6.2.2c                              
                              Librairie PETSc : non disponible                                  
                           Version de la librairie SCOTCH : 7.0.4

That's disappointing: I run into an error even before files are copied:

WARNING: If MPI_Abort is called during execution, result files could not be copied.
Running: mpiexec -n 2 --tag-output /opt/salome_meca/V2024.1.0_scibian_univ/tools/Code_aster_MPI-1670/bin/run_aster --wrkdir /tmp/run_aster_jeby4z5j --status-file /home/mario/.tmp_run_aster/run_aster_w8modc0o/status /home/mario/.tmp_run_aster/run_aster_w8modc0o/export.0
++ using container salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif
++ prepend system 'libGL*' libs

What can I do? It cannot write to the /tmp folder it seems. Maybe the used CA version is not correct? Perhaps someone with more knowledge is able to help?

k_zurawski

I'm not using Amazon Web Services, but I have additional level of complexity. I'm running S_M on Windows 11 on Debian 12 through WSL2. Which version of Singularity are you using? I'll try tomorrow with Ubuntu through WSL2 unfortunately.

k_zurawski

Is there anything specific that HOST system, where Singularity is installed should have installed/activated?

nicolas_p

If you use the precompiled prerequisities 20240327, there are only for unstable version 17.*

That is main reason why petsc and metis do not work. Normaly, Scotch works. In MPI, I recommand more Pt-schotch ant Parmetis.

For version 16.*, you should use older prerequisities version. On gitlab project, it is writen

From 16.3.2 : salome_meca-edf-2023.1.0-1-20221225-scibian-10 -> so use 20221225 prequisities

mf

nicolas_p

Hello,

I think I have a deja-vu :-). Do I understand correctly, I cannot use this container for a stable MPI version at all (yet)?
For CA 16.7 I would have to use salome_meca-edf-2023.1.0-1-20221225-scibian-10. The problem is, this container never worked on my system (SIGSEGV errors). See https://forum.code-aster.org/public/d/27539-new-version-sm-salome-meca-lgpl-202310-4-20240327-questions

So for CA 16.7 MPI I can use the container salome_meca-lgpl-2022.1.0-1-20221225-scibian-9 (the latest for 16.*) also?

The other choice would be to go for a 17.x version with this newest container, right away. Maybe I will try this. Or maybe I do both....

Thanks a lot,

Mario.

mf

Hello,

I tried SM2022 and CA16.7, with this one I succeeded to build the MPI version.
With SM2024 and CA17.2 I still get the above error, maybe something wrong with user rights, IDK (see image below). The 'stable_mpi' was my mistake, should say 'testing_mpi'. This simulation runs fine in all other versions of this SM2024.

Mario.

eedzo

mf Hi Mario, I also cannot get the mpi version to run whenever I input a number greater than 1 into the 'Number of MPI CPU' field. I was having the same issues with SM2023. I have also tried running the compiled stable release from SM2022 in SM2024 but still doesn't run with a number greater than 1 into the 'Number of MPI CPU' field.

mf

Hello,

I finally ran into some trouble with this container, not on the system mentioned above, but on a different one:
Ubuntu 22.04LTS,
no Nvidia GPU, rather onboard Intel HDA
singularity-ce version 4.0.1-jammy
X11 (no Wayland) also applies to system in first message.

When in Asterstudy, I press a save file dialogue like in IMPR_RESU or IMPR_TABLE, the whole SM2024 crashes. It is the button, with the three dots in between unite and localhost:

As soon as the button is pressed, the window crashes and this is printed to the terminal:

AsterStudy: sam.-11-21:05:50.519 AsterStudy activated
(SALOME_Session_Server_No_Server:3246): Gtk-WARNING **: 21:06:07.094: Failed to measure available space: Erreur d’obtention des informations du système de fichiers pour /media/drive2 : Aucun fichier ou dossier de ce type
(SALOME_Session_Server_No_Server:3246): Gtk-WARNING **: 21:06:35.457: Failed to measure available space: Erreur d’obtention des informations du système de fichiers pour /media/drive2 : Aucun fichier ou dossier de ce type

It seems, the save file dialogue itself crashes and takes the whole SM with it. It tries to measure the size of a mounted drive?
Interestingly, all the open file dialogoues in Asterstudy (liken LIRE_MAILLAGE) are not affected:

Notice, these dialogues are in french, which I do not mind, but they are clearly different from all the others in SM2024. All these work on the other system mentioned above. Strange!

This is what a standard open file window looks like in SM2024:

Mario.

hberro

Hi Mario,

Try binding your /media folder for singularity using

-B /media

When calling the SM launcher.

mf

eedzo
Hello,

yes, container, prerequisites and code_aster_mpi don't match yet. The best I could do was SM2022 and CA16.7mpi.

Mario.

AsterO'dactyle

Hello,

I've managed to compile a 17.2 MPI version on container 2024 without any problems.

1/ Pulling src and devtools repositories from Gitlab
2/ Launch the container in shell mode (add --shell)
3/ Go to ~/dev/codeaster/src
4/ ./waf configure
5/ ./waf install test -n zzzz506c

The random test (with two CPUs) runs and is OK.

mf

AsterO'dactyle
Hello,

apart from the test in the command line, have you tried launching something in SM2024? I got the error in message #11,

Mario.

AsterO'dactyle

k_zurawski

AsterO'dactyle So if it's working on your system, could you please share what version of system, singularity, system language, and hardware are you using?

AsterO'dactyle

Integrated post-treatment in AsterStudy is ok too

eedzo

AsterO'dactyle
When 'Number of MPI CPU' is set to greater than 1 this is the error.

AsterO'dactyle

Hello,

You cannot use AsterStudy to launch a MPI>1 version of code_aster. It's not possible. That's sure.

mf

AsterO'dactyle

Hello,

I do not know what you are trying to achieve with this, but we are past that. I have been using SM since 2021 (?) to launch Code_Aster MPI versions. It would be next to useless to me without MPI.

Just ran this, especially for you:

SM2022_CA_MPI_16.7 can be downloaded here:
https://drive.google.com/file/d/1YmbZWEDjsbMarjEy-OHsgqI2ye4JRLSs/view?usp=drive_link

I don't understand what's going on here. How does EDF launch their MPI workloads on a cluster, I assume exactly the same way....

Mario.