Salome-Meca 2018 for Windows is available for download. This version includes AsterStudy 2018.0 and Code_Aster stable 13.6 and testing 14.2 binaries for Windows.
The interface does not change much since 2017 version and It should be possible to follow series of tutorials already available on the Web.
Note that this version is based on Salome 8.3.0 while Linux version uses Salome 8.5.0, but some products such as MED-3.3.1 have been upgraded in the package to make it compatible with new versions of Code_Aster and AsterStudy. Please read the FAQ and report any issues.
30 thoughts on “Salome-Meca 2018 for Windows”
Could not get the binary files. Where to get it?
LikeLiked by 1 person
Whenever I try to edit a command file in text mode, I get an unexpected error. I’ve tried changing my editor preferences to use an external editor for “text stage edition” only to get a “text editor error” message.
Error details (with default editor options) are as follows:
Value: (“‘PyEditor_Editor’ object has no attribute ‘editor'”,)
File “C:\Salome2018\MODULES\ASTERSTUDY\RELEASE\ASTERSTUDY_INSTALL\lib\python2.7\site-packages\asterstudy\gui\astergui.py”, line 865, in edit
File “C:\Salome2018\MODULES\ASTERSTUDY\RELEASE\ASTERSTUDY_INSTALL\lib\python2.7\site-packages\asterstudy\gui\astergui.py”, line 1188, in openStageInEditor
File “C:\Salome2018\MODULES\ASTERSTUDY\RELEASE\ASTERSTUDY_INSTALL\lib\python2.7\site-packages\asterstudy\gui\stagetexteditor.py”, line 133, in setReadOnly
File “C:\Salome2018\MODULES\ASTERSTUDY\RELEASE\ASTERSTUDY_INSTALL\lib\python2.7\site-packages\asterstudy\gui\widgets\texteditor.py”, line 125, in setReadOnly
Already corrected, you should download the last package
A post on this site (and/or a changelog) indicating updates to the 2018 release were made would have been useful. Thanks for the info.
CAW often crashes during start-up. I can only fix this by rebooting my computer (Windows 7). I’ve attached a screenshot of the crash: https://imgur.com/ZzoDWxu
Any fixes for this?
I am getting this error message when trying to mesh a cube (my first attempt at using Salome-Meca apart from running, successfully, forma02a so the installation is, apparently, ok):
“Salome exception: “Can’t load server meshers plugin library”
This happens both with Salome for Windows 8.3.0 and Salome-Meca 2018 for Windows.
Any ideas? Thanks
Hi, maybe firewall or antivirus ? If an issue like this happen also with Salome 8.3.0, you may also get help from Salome forum
I often get the following error when switching to Paravis:
ACCESS VIOLATION at address 0x0000000000000000 during ‘READ’ operation
I then need to close the project and when I reopen Paravis I need to manually display again all windows and toolbars.
Except that it’s working pretty well, thanks!
Yes, this happen when Paravis module is activated after AsterStudy module
Thank you. The problem was solved after reinstalling the software (both Salome and Salome-Meca), running run_salome.bat as administrator and creating firewall exception rules for all networks.
I’m trying to run a two stage study. I want to perform the processing in the first stage; and the post processing in the second. The second stage fails to run. The error in the log file is:
>>> 2018/12/03-12:33:37.385 [Gunzip@C:\Program Files\EDF\Salome-Meca-2018\PRODUCTS\code_aster\lib\python2.7\site-packages\asrun\system.py:607]
gzip -d base-stage1
background : False
follow_output : False
decompressing base-stage1 gzip: base-stage1: unknown suffix — ignored
>>> 2018/12/03-12:33:37.480 [Mess@C:\Program Files\EDF\Salome-Meca-2018\PRODUCTS\code_aster\lib\python2.7\site-packages\asrun\run.py:639]
Warning or error raised :
_DECOMPRESSION error during decompressing base-stage1
File “C:\Program Files\EDF\Salome-Meca-2018\PRODUCTS\code_aster\lib\python2.7\site-packages\asrun\main.py”, line 96, in start
File “C:\Program Files\EDF\Salome-Meca-2018\PRODUCTS\code_aster\lib\python2.7\site-packages\asrun\execute.py”, line 434, in RunAster
copyfiles(run, ‘DATA’, prof)
File “C:\Program Files\EDF\Salome-Meca-2018\PRODUCTS\code_aster\lib\python2.7\site-packages\asrun\execution.py”, line 534, in copyfiles
icomm = copyfileD(run, df, icomm, ncomm)
File “C:\Program Files\EDF\Salome-Meca-2018\PRODUCTS\code_aster\lib\python2.7\site-packages\asrun\execution.py”, line 580, in copyfileD
kret, dest = run.Gunzip(dest, niverr=’_DECOMPRESSION’, verbose=True)
File “C:\Program Files\EDF\Salome-Meca-2018\PRODUCTS\code_aster\lib\python2.7\site-packages\asrun\system.py”, line 607, in Gunzip
return self._gzip_gunzip(‘gunzip’, src, **opts)
File “C:\Program Files\EDF\Salome-Meca-2018\PRODUCTS\code_aster\lib\python2.7\site-packages\asrun\system.py”, line 670, in _gzip_gunzip
self._mess(para[mode][‘msgerr’] % f, niverr)
File “C:\Program Files\EDF\Salome-Meca-2018\PRODUCTS\code_aster\lib\python2.7\site-packages\asrun\system.py”, line 220, in _mess
self.run.Mess(msg, cod, store)
File “C:\Program Files\EDF\Salome-Meca-2018\PRODUCTS\code_aster\lib\python2.7\site-packages\asrun\run.py”, line 639, in Mess
File “C:\Program Files\EDF\Salome-Meca-2018\PRODUCTS\code_aster\lib\python2.7\site-packages\asrun\run.py”, line 817, in DBG
stack_id=stack_id, all=all, prefix=prefix, *args)
File “C:\Program Files\EDF\Salome-Meca-2018\PRODUCTS\code_aster\lib\python2.7\site-packages\asrun\run.py”, line 773, in _printDBG
stack = traceback.format_stack(limit=10)
_DECOMPRESSION error during decompressing base-stage1
Any ideas? Has anyone successfully run a two stage study (and re-used the first stage in the second)?
no, I didn’t succeed either. It works well with the Linux version but not with the Windows one.
Salome LIBBATCH module uses “copy” command on Windows and “cp -r” on Linux to copy input/output files (see CommunicationProtocolSH.cxx line 62) but “copy” on Windows is not able to correctly copy directories, xcopy should be used instead. You can report this to Salome team if you wish
Great work on providing the Salome Meca suite for windows.
I’ve received the error below. It seems to occur during the calculation of results, or writing out of results.
This occurs once my run has a larger number of steps in it. For a smaller number of steps, it is able to successfully complete. I’m guessing I’m running into some sort of memory limit
La mémoire consommée actuellement hors JEVEUX est de 90.08 Mo.
La limite de l’allocation dynamique JEVEUX est fixée à 3457.92
Cette valeur limite a été réactualisée lors de la mise en oeuvre d’un processus de libération
! Program error. !
! Condition not met: !
! iexi.eq.1 !
! File !
! /home/siavelis/PROJETS/code_aster-windows/build/codeaster-src/bibfor/utilitai/dismlg.F90, line 83 !
! Il y a probablement une erreur dans la programmation. !
! Veuillez contacter votre assistance technique. !
! FATAL ERROR detected in Code_Aster for Windows version !
! If an ABNORMAL_ABORT occured, that is not reproductible !
! on official Linux version, or if you need some help to !
! understand the message above, please report issues at: !
! email@example.com !
Traceback returned by pdbhelp:
Criterion of destruction of the file ( 1.00%) associated with the base VOLATILE exceeded 10.44%
Nombre of records used: 935
Occupied disc volume: 730 Mo.
Maximum number of records: 8960
Ouverture en écriture du fichier ./vola.1
Validation of the concept resnonl.
ERREUR UTILISATEUR RECUPEREE PAR LE SUPERVISEUR
You can try testing version. If the issue is still there you can use ARCHIVAGE keyword to reduce number of steps of your “resnonl” concept
I have installed SALOME MECA for windows but the asterstudy stage is no recorded when I save the file. How can I solve that touble in order the get a perfect file saved?
Go to “History View” and then Menu -> Operation -> “Export Case”. It will save the necessary files and an “export file” that can be used to run Code_Aster outside of Salome-Meca. If something goes wrong during “Save”, your study can be restored from an empty AsterStudy instance by importing the “export file” using Menu -> Operation -> “Import Case”
Really great project!
Is there a way to mesh in parallel with Salome?
I don’t think that SMESH module can use more than 1 proc, but you may have a look to SMESH documentation https://docs.salome-platform.org/8/gui/SMESH
LikeLiked by 1 person
You did a great job
I installed Salome Meca 2018 on windows 10 extracting the whole archive but i don’t find Aster module.
I’m a newbye.
Can someone help me?
Thanks for your comment, by the way you can try version 2019
the 2019 version send me some errors while 2018 version is alla right.
So I prefer the latter
You may have a look to the FAQ, your issues may be reported there
First of all, thank you for making Salome-Meca available for Windows.
I installed the 2018 version and it is working fine, but when I tried to open a shell session it gave me nothing, not even an error message, even after setting DEBUG=1 in set_env.bat and erasing the .config directory as suggested in the FAQ.
Is this a feature meant to work at Windows?
Best regards and thanks for any answer.
This feature does not seem to work on windows. You may try to open a cmd prompt and manually source files “set_env.bat” and “env_launch.bat”
Thank you very much.
That’s sad news. I was hoping to play with Astk just as I do in Linux, since there are all the Tcl/Tk resources bundled.
But no bad feelings, the command line and AsterStudy still works.
Dear CAW people,
I tried to use the multi-stage feature in Salome-Meca 2018 and it is behaving like this:
1. When I run the Stage1, its OK (having clicked ‘reutilizable’).
2. When I try to run only the Stage2, even after putting the ‘check/blue’ sign on Stage1, the running ends with an error and no result is produced.
3. The only way I can run Stage2 properly is running Stage1 again simultaneously.
This problem doesn’t happen in Salome-Meca 2018 in my home Linux machine, where I can run shell sessions and ASTK in interactive mode (showing the so desired Python prompt).
When I try to run ASTK on my work Windows10 machine it complains about permission issues. Is it possible to make this package more ‘portable’ in order to have this feature working as second choice? Just in case AsterStudy show some odd behaviour.
What’s the meaning of these annoying messages that keep jumping on my screen when I run ‘as_run exportfile’ at command line? The window says:
injecting hooks into PID=yyyyy
I already did the execution of ‘set_env’ and ‘env_launch’ scripts to set up the environment, so I believe it has nothing to do with paths and libraries.
Any hint is welcome.
Thank you all very much in advance.