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.
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.
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.
Once the GUI opened, one can notice the new Shaper module, that aim to replace GEOM module (GEOM module subsist in this version).
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.
It is then possible to use the buttons to define, for example, a primitive.
Once finished, the trick is to use from the menubar Feature -> Export to GEOM before to go to SMESH module.
Once in SMESH module, only exported to GEOM entities will be accessible to define and compute a new mesh.
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.
Type “forma01a” in the lineedit to import testcase forma01a.
From the tab Case View, let’s define an output file.
Click button “…”, chose a folder and type “forma01a.rmed’.
Go back to History View tab, save the study, and click as usual on “+” button and then on Run.
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.
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:
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.
AsterStudy has a new tab for post-processing results. Right click on an selected result forma01a.rmed and select Post-process.
Wait for the initialization of the new window.
The Results tab should then be active.
This new Results window is really intuitive and ease the management of post-processing comparing to advanced Paravis module.
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.
and select forma01a.rmed file directly from disk.
EDIT January 2021: A new version has been released with a FIX in HDF5 library. This new version is available in our download page and may solve some issues with errors on save.
EDIT May 2022: Even with HDF5 fix, errors on save may still happen sometime for unknown reasons. Please check if you get a workaround on this paragraph
Sometime, when a Study.hdf file already exists on disk, it happen that Salome raise an error with permission denied.
Indeed if we right click on file -> Property, we can see that the file has been set to read only mode.
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.
Sometime Salome won’t save even if the readonly flag has been removed.
Looking at the console, one can remark that a temporary Med file has failed to be written.
Looking for this file, it seems to be created, but with readonly flag set.
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
Select the loaded mesh and delete it from your Study
Same issue can happen for post-processing files. Workaround is to select result and delete from your Study in Paraview module
Salome-Meca won’t need the temporary med file now and you might save your study 🙂