Salome Meca 2024.1 on WSL2 ready to use distribution

hberro

Salome Meca 2024.1 on WSL - Ready to use distribution

We provide the latest Salome Meca (2024.1), packaged and tweaked for use in WSL2, natively, ie without singularity. The beta testing phase showed very reliable results out of the box, comparable to the Linux (official) version.

Installation steps:

Download the following WSL2 distribution file (smeca-2024.1-wsl2-verified.tar.gz)

https://tinyurl.com/smeca-2024-wsl2

Create a folder in C:\smeca, then import the WSL machine in this location

wsl --import smeca-2024 C:\smeca C:\path\to\downloaded\file\smeca-2024.1-wsl2-verified.tar.gz

Once done, a virtual disk should be created in C:\smeca.

Run the WSL distribution using the command.

wsl -d smeca-2024

You should see a welcome message, WSL should log in automatically as the default user smeca-user, the password is codeaster.

To run salome_meca, just type

salome_meca

Other tools that are available (and checked during beta testing) from the command line (aliases are already created) :

run_aster
as_run
astk
If you get a "clicking" issue with the salome main window, press F11 to go to fullscreen and then F11 again to exit full screen. This seems to fix the issue.

Let us know if this works for you.

OL7

hberro
Hello,

As I mainly import IGES drawing (and my CAD software is only windows supported), I have a quite high frequence of connection / disconnection between windows and linux sessions (I have a dual boot).

Then I wish to work only under windows. At this stage, I am facing several issues.
A- Opening with windows WSL2 V9.10 version (downloaded as a 2023 for windows version - asterstudy module version 0.11) of studies completed under linux version '2023' (salome_meca 2023.1.0 - asterstudy module 2023.1.0) go through several error messages prior to reach 'post-procces' and then fail.
= = > Are those two '2023' compatible ?
= = > In order to not redo all the work on previously created with Linux salome_meca 2023.1.0, will the 2024.1 windows WSL2 version be compatible ?

B- In order to test 2024.1 version for windows WSL2, I have strictly followed the process identified 18 days ago (donwnloading with the given link, creating directory on C:\, importing, opening and running).

I am facing these issues
B.1- After launching 'salemo_meca', I have the "ParseXmlFiles Wqrning, two resources with the same name were found, taking the first declaration : Localhost" sentence already identified on January 17th 2025 by Krzysztof (the sentence remains after a 'wsl -- unregister smeca-2024' command and a re-installation)
= = > is it possible to identify where is this double information ?

  B.2- the 2024.1 version works, with a little suprising issue : the salome_meca page is permanently glued on the bottom right of the screen (permanent offset of 1cm in horizontal and vertical directions). Selections with the cursor are affected by the same vertic & horiz offset (see pictures)... which is not that confortable (as I can not reduce, hide or put as full screen the workinng page due to the cursor also not efficient outside of the page).

Even after a 'wsl --unregister smeca-2024' command and a redo of all the process (download, import, etc.), the page behavior remains the same.
= = > is there any accessible (and updatable) parameter to solve this issue ?

Thank you in advance for the attention you will give to my questions.
Regards,
Olivier.

rmoortgat

![
](https://)

Hello hberro,

no welcome smessage, no login

Roger

hberro

rmoortgat ok it seems properly logged in as smeca-user.

Does salome_meca work ?

k_zurawski

hberro
Hello again.
I need to report that running export file by as_run runs into error:

rmoortgat

hberro

salome_meca not opening.
astk gives following error:

smeca-user@DESKTOP-PMGA9BL:/mnt/c/smeca$ astk
smeca-user@DESKTOP-PMGA9BL:/mnt/c/smeca$ application-specific initialization failed: no display name and no $DISPLAY environment variable
Error in startup script: invalid command name "wm"
while executing
"wm withdraw ."
(file "/opt/public/20240327/gcc-openblas-ompi/asrun-2023.0.0/lib/astk/astk.tcl" line 28)

VaclavO

It works out-of-the-box! Amazing - thank you very much.

I've been running SM2022 in WSL since the time you made the youtube tutorial. It was a bit clanky, but this SM2024 seems to be running much smoother. I haven't tested it thoroughly, but everything seems to work fine.

Thank you!

hberro

k_zurawski

Thanks for reporting

Does run_aster do the job ? It has the same syntax.

Also please try

salome_meca shell as_run

k_zurawski

hberro
you need to explain how to run it (salome_meca shell as_run). When I run it in powershell not in WSL I'm getting error that salome_meca is not recognized as the name of a cmdlet

When I run it in WSL I;m getting list of possible functions. I also tried: salome_meca shell as_run --run 06.export

k_zurawski

The same goes to running a study from ASTK. ASTK starts, I can import study, but I can't run it.

k_zurawski

I run a study created from scratch and it works. Study has been saved to user's home folder.

k_zurawski

post processing worked until i pressed that icon:

hberro

k_zurawski

I have seen a reported bug with the "Probe" feature in the integrated post processing, I think it is corrected but in a more recent version of ASTERSTUDY. So for now, it's better not to use it as to avoid crashes (this is not only relative to the windows version, the linux version will probably crash as well !).

k_zurawski

oppening the same rmed in paravis gives SIGSEGV error and crash. The blue lines are from the icon I pressed before:

k_zurawski

is run_aster invoking python? I have never used this command.

hberro

k_zurawski

Hi k_zurawski,

run_aster is the new way of launching code_aster using the full "pythonic" approach.

If you do run_aster <file.export> ; then this executes your case as you would have done with as_run.

If you do run_aster with no arguments, this opens a python interpretor where code_aster python library and all commands are available and you can then build your simulation interactively...

hberro

rmoortgat

Hello rmoortgat

This must be an issue with your version of WSL, please check that you are in version 2 and that you can open graphic apps (independantly of salome...)

k_zurawski

rmoortgat
create a /local00 folder as root and then chown it by the regular user (you need to have read/write rights).
create it in /, not in your home directory. Test if S_M 2024 runs. Then report please.

k_zurawski

hberro
Thank you for the explanation. When I: run_aster 06.export I'm getting only this and I don't know what to do next.

hberro

k_zurawski

Ok it's possible that the run_aster wrapper script which I added in WSL2 is messed up.

You can find its location using the command
which run_aster

And tweak it, it is probably just not passing the arguments (export file) as it should.

My windows machine sleeps in a drawer, I will have to take it out to fix these scripts.

Thanks again for the feedback!

k_zurawski

why are there two instances of solver version per version?

k_zurawski

moving from Paravis to AsterStudy and then Europlexus (which I don't use) gives SIGSEGV error and crash: