Salome-Meca 2019 for Windows

Salome-Meca 2019 has been release on Linux few weeks ago and is now ready for Windows at our download page. This version is based on Salome 9.3 and last AsterStudy update 2019.0.1 and includes Code_Aster 14.4 binary for Windows. This update comes with many new features (discussed below) in Code_Aster, Salome and its new Shaper module and AsterStudy with  a new post-processing tool.

Code_Aster

Version 14.4 is set as stable and replace previous version 13.6. The portage to Windows required an important effort due to the transition from Python2.7 to Python3. But the solver pass the tests and has been validated as the previous builds using the official submit list.

Running testcases for Code_Aster 14.4 validation

Salome 9.3

The major change in Salome 9 is the switch from Python2.7 to Python3. Although this seems to be interesting from the developer point of view, this switch is a significant effort on code modernization that shows the willingness to maintain the project over time. The Windows version is now build using MSVC 2015, one should install corresponding redistribuable Package (x64). Anyways, launching the GUI doesn’t change much from the previous versions : double click on run_salome.bat.

launch Salome-Meca 2019 on Windows 10

Salome_Meca 2019 opening on Windows  10

Once the GUI opened, one can notice the new Shaper module, that aim to replace GEOM module (GEOM module subsist in this version).

Salome-Meca 2019 opened on Windows

Shaper

Shaper allows a parametric definition of the Geometry and offers a much better flexibility than GEOM to deal with geometry. One should first create a part.

shaper make a part with Salome-Meca 2019

It is then possible to use the buttons to define, for example, a primitive.

Shaper make a cube on Salome-meca 2019

Once finished, the trick is to use from the menubar Feature -> Export to GEOM before to go to SMESH module.

Shaper export to geom Salome-Meca 2019

Once in SMESH module, only exported to GEOM entities will be accessible to define and compute a new mesh.

SMESH select from geom Salome-Meca 2019

SMESH compute mesh Salome-Meca 2019

AsterStudy enhancements

The new AsterStudy version works the same way as the previous version with no major difference in the workflow but the software is expected to improve fluency. Let’s compare this new version by following the previous tutorial beginning with AsterStudy. Go to tab History View, then in the menubar select Operations -> Import Testcase.

import testcase on AsterStudy 2019

Type “forma01a” in the lineedit to import testcase forma01a.

type testcase name on AsterStudy 2019

From the tab Case View, let’s define an output file.

define output file on AsterStudy 2019

Click button “…”, chose a folder and type “forma01a.rmed’.

type output file AsterStudy 2019

Go back to History View tab, save the study, and click as usual on “+” button and then on Run.

run testcase on AsterStudy 2019

One can notice a new combobox to select refresh mode and a new combobox coming with a graph that aim to show progress of the calculation.

running testcase on AsterStudy_2019

The run ends OK as usual with green, but unfortunately forma01 case uses only one increment and shows nothing in the graph. So let’s load another testcase ssnv504f:

import another testcase on AsterStudy 2019

With ssnv504f case running, we can click on Refresh button for the pending message file to be parsed. Then it is possible to select the value that should be displayed in graph progress (iterations, residuals, etc.) using Graph progress combobox.

select graph progress on AsterStudy 2019

Post processing

AsterStudy has a new tab for post-processing results. Right click on an selected result forma01a.rmed and select Post-process.

open post processing AsterStudy 2019

Wait for the initialization of the new window.

post processing opening on AsterStudy 2019

The Results tab should then be active.

result tab of AsterStudy 2019

This new Results window is really intuitive and ease the management of post-processing comparing to advanced Paravis module.

set color result on AsterStudy 2019

This window is based on Paraview engine, but manage automatically filters and hide the messy interface. That could be really helpful for the average user. This interface can also be used to open a standalone rmed file: from a scratch AsterStudy session, in the CaseView tab, select from the menubar Operations -> Post-process an external MED Results File.

post process external rmed on AsterStudy 2019

and select forma01a.rmed file directly from disk.

select external rmed on AsterStudy 2019

Errors on Save

Sometime, when a Study.hdf file already exists on disk, it happen that Salome raise an error with permission denied.

overwrite study in Salome-Meca 2019 on Windows 10

permission denied in Salome-Meca 2019 on Windows 10

Indeed if we right click on file -> Property, we can see that the file has been set to read only mode.

Study property Salome-Meca 2019 on Windows 10

read only property on Windows 10

You can simply delete the file or untick read only attribute to make save possible again. Another workaround is to use the attrib command to change permission from cmd prompt. Even better, put  in study folder a file named set_study_rw.bat containing line:

attrib -r Study*.hdf

A double click on set_study_rw.bat will remove readonly flag automatically for all files starting with Study and ending with .hdf, allowing you to save again in all these files.

set study rw for Salome-Meca 2019 on Windows 10

Sometime Salome won’t save even if the readonly flag has been removed.

Salome-Meca error on save

Looking at the console, one can remark that a temporary Med file has failed to be written.

Salome-Meca error creating temporary MED file

Looking for this file, it seems to be created, but with readonly flag set.

Salome-Meca read only flag set on temporary Med file

Since MED format is based on HDF format, it seems to be related to the save kind of error in HDF library.

This can append when a mesh is loaded from disk in SMESH module when AsterStudy needs to retrieve information from mesh.

A workaround is to open SMESH module

Open SMESH module from AsterStudy module

Select the loaded mesh and delete it from your Study

Delete AsterStudy loaded mesh from SMESH module

Salome-Meca won’t need the temporary med file now and you might save your study 🙂

29 thoughts on “Salome-Meca 2019 for Windows

  1. First of all, thank you for your work I really appreciate it

    When closing/quitting Salome I get this error message “This application failed to start because it could not find or load the Qt platform plugin “windows” in “”. Reinstalling the application may fix this problem.”

    I don’t know what it is about and it only appears after closing Salome.

    Have a nice evening, Mauro

    Like

  2. Good morning to everybody:
    Congratulations for publishing I appeciate the effort for realeasing the brand new version of SALOME-MECA 2019.
    In my case, I have to report several inconsistencies. The first one, I cannot save my files due to a write protection.
    The second one, ASTERSTUDY is reporting error messages during the loading and it cannot read the previosly saved file.
    the third one, Helpbrowser.exe cannot access to some needed dll.

    How can we resolve these issues? Thank you

    Like

  3. Good morning to everybody:
    Congratulations for publishing I appeciate the effort for realeasing the brand new version of SALOME-MECA 2019.
    In my case, I have to report several inconsistencies. The first one, I cannot save my files due to a write protection.
    The second one, ASTERSTUDY is reporting error messages during the loading and it cannot read the previosly saved file.
    the third one, Helpbrowser.exe cannot access to some needed dll.

    How can we resolve these issues? Thank you

    Like

  4. Hello everyone!

    First of all, Congratulations on this amazing work!

    I´m getting the following message when trying to save my files:

    Can not save file “/(…).hdf”
    possible reasons:
    -permission denied;
    -unsufficient disk space;
    -application error.

    I noticed this problem start happening only when the simulation file becomes bigger, requiring more disk space (for instance, after I generate a big mesh), however I have plenty of disk space!

    Does anyone have a guess on how to solve this?

    Thanks!

    Like

      1. I have read and tried that before posting. It does not refer to the same issue. By the way, the error message I reported is completely different…

        Like

      2. Hello Maximilien, I report the same problem as Henrique even after trying your proposed solution. I also tried other solutions proposed elsewhere.

        I have near-zero experience in code_aster but as I was creating a model (very very simple model) I was successfully saving with different names v1, v2, v3, .. (to avoid changing the folder or file properties every time). I meshed part of the model, saved it, then meshed the second part of the model AND!! after this point i cannot save the file anymore – I tried in different folders with different names, nothing. Is this familiar to you?

        Like

      3. Hello Alexandre,
        It may be related to the same issue. The HDF bug may affect mesh saving because MED, the mesh format file, is based on HDF. I also suspect a temporary scratch file to be saved read only somewhere, in a temporary folder. This file may be a MED file or a pure HDF file

        Like

    1. Hello Henrique, I got the same error as you, have you already solve it? I have the same error in my two computers and I’m not able to solve it. Thank you.

      Can not save file “/(…).hdf”
      possible reasons:
      -permission denied;
      -unsufficient disk space;
      -application error.

      Like

      1. Hi Alexandre, I had the same problem and my conclusion was that only one mesh can be in MESH module. If you have more than one mesh it is not possible to save the HDF file at all.
        Hi hope this comment can help to find a solution to this boring bug.

        Despite the above I have to thank Maximilien for his work in issuing SM for windows.

        Like

  5. Thank you very much indeed for your work.
    I contribute with two findings (only one new):
    – after closing Salome I get the same message in the post of Mauro on 4th November
    – when I run “kill_salome.bat” the starting black window of salome remains open, to close it I need to push the X botton, is it really necessary to run “kill_salome.bat”?

    Thanks for any comments.

    Like

  6. There is a problem while saving any .hdf file. Specially for larger files it becomes impossible to save and the messages are the same:
    insufficient disk
    permission etc.
    Kindly please resolve this issue as it is persistent in every version (2017-19).
    Thank you.

    Like

  7. Hi Maximilien,

    I am using the salome meca windows version 2019. I could not check the reuse command while running the analysis. Only Run and Skip buttons are clickable. Do I have any issues in my installation or is this feature disabled?

    Thanks and regards,
    Hems

    Like

  8. If i run testcase “forma01a” i got:

    AsterStudy
    Unexpected error
    Type: TypeError
    Value: (´expected str, bytes or os.PathLike objekt, not NoneType´,)

    Traceback:
    File “C:\Users\ABel\Salome\MODULES\INSTALL\ASTERSTUDY\RELEASE\ASTERSTUDY_INSTALL\lib\python3.6\site-packages\asterstudy\gui\dashboard.py”, line 428, in
    Q.QTimer.singleShot(50, lambda: self._runClicked(notid))

    File “C:\Users\ABel\Salome\MODULES\INSTALL\ASTERSTUDY\RELEASE\ASTERSTUDY_INSTALL\lib\python3.6\site-packages\asterstudy\gui\dashboard.py”, line 463, in _runClicked
    run_case.make_run_dir()

    File “C:\Users\ABel\Salome\MODULES\INSTALL\ASTERSTUDY\RELEASE\ASTERSTUDY_INSTALL\lib\python3.6\site-packages\asterstudy\datamodel\result\mixing.py”, line 379, in make_run_dir
    self._make_run_dir_helper(stage)

    File “C:\Users\ABel\Salome\MODULES\INSTALL\ASTERSTUDY\RELEASE\ASTERSTUDY_INSTALL\lib\python3.6\site-packages\asterstudy\datamodel\result\mixing.py”, line 389, in _make_run_dir_helper
    embfolder = osp.join(self.model.folder, self.name, ‘Embedded’) # pragma pylint: disable=no-member

    File “C:\Users\ABel\Salome\PRODUCTS\python-3.6.0\Lib\ntpath.py”, line 75, in join
    path = os.fspath(path)

    Whats wrong?

    Like

  9. Mr. Siavelis,
    Congratulations on such an ambitious package for Windows! I was looking forward to using it on my Windows machines and not have to lose massive disk space to a Linux partition.
    Unfortunately, i am having the same problem with saving files. “Permission” fix described above does not work. Having problems on Win10 Pro and Win 10 Home machines. Tried changing folder ownership, etc with no success and tried the “protected folders” fix (it turns out this fix is not applicable to SalomeMeca file saving problem).
    When a folder has “Read Only” box filled (blacked out), it does not mean the “read only” option is selected. It is only selected when there is a check mark in the box.
    Problem occurs when Salome tries to save files and create folders named “xxx_files” (?to store temps). Can still save .med mesh files (no extra folder created) and read those with Code-Aster. Another problem occurs when trying to assign boundary conditions and allocate loads to elements: I can use the interface exactly once, where Code Aster can read the node/facette elements in a mesh and assign a load. When i open the interface again (e.g. to assign a load or a boundary condition), Code Aster gives a Value error (‘not enough values to unpack (expected 3, got 2)’,) and a traceback to line 626 in panel.py (This also sounds like a problem updating temp files).
    So far have not been able to complete a “run” on anything more than the demos 😦
    Hope a fix is coming soon!

    Like

    1. Concerning the “Value error (‘not enough values to unpack (expected 3, got 2)’,) and a traceback to line 626”, same issue on Linux, solved after save study in hdf, fully leaving Salome-Meca, restarting Salome-Meca from fresh and reload the hdf study file

      Like

  10. when I run sm 2019 last, I test code aster in sm using “forma01a”,
    The problem accured at first:
    the program response with “Cannot read output file or empty file.” at first, then run failure,
    with following information:
    “Summary
    Output messages for stage forma01a

    Output messages for stage forma01a – [top / bottom]
    Full job output should be available in the directory ‘D:/ProgramData/working_fea/ca_example/Study1_Files\\RunCase_1\\Result-forma01a\\logs’.

    I understand the problem with python’s path problem, but I don’t know how to deal with the problem

    Like

  11. the problem as following:
    Traceback:
    File “D:\ProgramData\sm2019\MODULES\INSTALL\ASTERSTUDY\RELEASE\ASTERSTUDY_INSTALL\lib\python3.6\site-packages\asterstudy\gui\datafiles\summary.py”, line 222, in _browse_directory
    directory = osp.dirname(file_name)

    File “D:\ProgramData\sm2019\PRODUCTS\python-3.6.0\Lib\ntpath.py”, line 242, in dirname
    return split(p)[0]

    File “D:\ProgramData\sm2019\PRODUCTS\python-3.6.0\Lib\ntpath.py”, line 204, in split
    p = os.fspath(p)

    How to deal with ,
    OS system: windows 7.

    Like

  12. Hello!

    I am a new one in this forum ( and in CodeAster too). Unfortunately, i got the same issue concerning saving files in .hdf. Indeed, i have the problem also from the beginning of a study. Therefore, i am not able to save the project at all. I have read in other forums that such problem is concerning the SALOME platform, indeed the problem is solved in 9.5.0 version.

    I was wondering if any of you have found any alternative solution in the meantime.

    Thanks a lot.

    Gaetano

    Like

  13. Hi,

    My system is Win10 x64. When i’m trying to run Salome-Meca 2019 (9.5.0) i get the error down below. What should i do? Which packages do I need to install?

    runSalome running on DESKTOP-GHK3DI4
    Searching for a free port for naming service: 2812 – OK
    Searching Naming Service ++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++Failed to narrow the root naming context
    Traceback (most recent call last):
    File “C:\SALOME-9.5.0\W64\KERNEL\bin\salome\runSalome.py”, line 680, in useSalome
    clt = startSalome(args, modules_list, modules_root_dir)
    File “C:\SALOME-9.5.0\W64\KERNEL\bin\salome\runSalome.py”, line 476, in startSalome
    clt=orbmodule.client(args)
    File “C:\SALOME-9.5.0\W64\KERNEL\bin\salome\orbmodule.py”, line 56, in __init__
    self.initNS(args or {})
    File “C:\SALOME-9.5.0\W64\KERNEL\bin\salome\orbmodule.py”, line 95, in initNS
    sys.exit(1)
    SystemExit: 1

    — Error during Salome launch —

    Regards,
    Said.

    Like

Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google photo

You are commenting using your Google account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )

Connecting to %s