Salome_Meca 2024 on WSL2 - C_A missing

mf

when I launch the new container, I get the following in the terminal:

(base) mario@HP-Z8-G4-Workstation:~$ ./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11
/home/mario/./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11:433: SyntaxWarning: invalid escape sequence '.'
regexp = re.compile("hwloc_(.).so")
'+ running salome_meca in GPU mode
++ using container salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif
++ prepend system 'libGL' libs

** (SALOME_Session_Server_No_Server:5569): WARNING **: 07:41:01.894: atk-bridge: get_device_events_reply: unknown signature

(I changed the formatting a bit, the + messes with it)

The warnings seen in the 2022 version are long gone, because they were kind of useless. The invalid escape sequence, I don't know about, but it also doesn't seem to cause anything,

Mario.

k_zurawski

mf Thank you

How come are you starting container by ./ not using "singularity run..."?

mf

k_zurawski

It's in the .sh script in the top line of the terminal,

Mario.

k_zurawski

mf OK, don't bother. I give up.

k_zurawski

So it's not exactly what should be done, which might give different results... Could you try by just singularity run salome... ?

mf

k_zurawski
It's would be the same.

Mario.

k_zurawski

mf Thank you for your help.

hberro

k_zurawski

Try binding /local00 to any local directory on your pc.

mkdir /tmp/local00
./salome-meca... -B /tmp/local00:/local00

Let me know if that helps

k_zurawski

hberro
Hello,
Singularity> ./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif -B /tmp/local00:/local00
bash: ./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif: Permission non accordée

w2@W2:~$ ./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif -B /tmp/local00:/local00
-bash: ./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif: Permission denied

what else should I do?

k_zurawski

Yesterday I installed Ubuntu 22.04 under Hyper-V, updated OS and installed Apptainer 1.3.4. The result is the same as in Debian under WSL. I had a gut feeling that there's a communication error between preprocessor and solver. I haven't seen it in WSL, but below screenshot might indicate that. Could anyone comment on this?

When I try to run as_run in shell I'm getting result as below. I'm really illiterate when it comes to dealing with Linux and these kinds of problems.

nicolas_p

You have a problem with as_run since you have no access to /local00/tmp

Try to see if it exists in your system and copy a file.

k_zurawski

nicolas_p
where should it be created? In / or in /home/u22/ ?

nicolas_p

yes directly in /.

k_zurawski

what can I do about it?

nicolas_p

here, this is not a problem with smeca but basic linux problem.

k_zurawski

nicolas_p
ok, so how to deal with it? I'd really appreciate if you could guide me through the whole process. I only know basic Linux commands and I'm far from being "proficient" with it. Please don't look at it as sort of ignorance. I really don't have much time. I'd rather spend it on Code_Aster, not on Linux itself.

jeanpierreaubry

nicolas_p

here, this is not a problem with smeca but basic linux problem.

is this good enough a reason not to help ?

StanislavPavlica

Hello Krzysztof,

try following steps:

I believe you should use singularity not apptainer to run salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif.
I'm not using Windows so I'm not sure of this:

To quickly install the 4.0.0 package singularity use the following commands inside the WSL2 Ubuntu 22.04 window:

wget https://github.com/sylabs/singularity/releases/download/v4.0.0/singularity-ce_4.0.0-jammy_amd64.deb
sudo apt install ./singularity-ce_4.0.0-jammy_amd64.deb

File salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif put in your home directory:
/home/u22/
Or you can make a link in your home directory.
Then run inside the WSL2 Ubuntu 22.04 window this command to install salome_meca (in /home/u22/ directory):
singularity run --app install salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif
This command generate in your home directory a script with same name as a container but without extension .sif:
salome_meca-lgpl-2024.1.0-1-20240327-scibian-11
Then run this script to start salome_meca:
./salome_meca-lgpl-2024.1.0-1-20240327-scibian-11
Script prepare environment to properly run container including access to /local00/tmp

If you start container with command
singularity run salome_meca-lgpl-2024.1.0-1-20240327-scibian-11.sif
this environment is missing and salome _meca is not running properly.

Stano

k_zurawski

StanislavPavlica
I have Apptainer in virtual machine and Singularity 4.2.0 in Debian 12 on WSL. Both don't work. The last one screenshot is from Singularity and Debian.

k_zurawski

StanislavPavlica
I followed your step-by-step guide and AsterStudy sees Code_Aster on my VM. as_run also starts, but I haven't run any simulations yet.
BIG THANKS!!!

I need to replicate the same on WSL and Debian and see if this also solves the issue. If not, I'll try WSL with Ubuntu 22.04 as in case above. Pity I can't have 2 separate workstations, one with Windows and one with Ubuntu.

k_zurawski

Well, I can't run the simulation because the same thing happens as in mf case. When I click on 3 dots to IMPR_RESU Salome_Meca crashes.
I checked WSL+Debian and SM doesn't start. I'm getting additional errors. I'll try later with Ubuntu 22.04 on WSL. I don't want to use VM, VM is only a temporary solution to check if is actually works.