salome_meca hang-up during file save

Hello,

I am having performance issuers when trying to save .rmed file in latest salome meca release. As one can see in attached screen capture (link) the dialog box takes many seconds to respond to navigate to proper folder. Also, If I start typing in box (to rename result.rmed to some other name), it again hangup and respond a little later.

I also want to mention that during loading of this study, a message appeared saying

RUNCASE_1 could not be loaded.

It would be really helpful if this issue is fixed.

Sometimes If I try to edit file through History tab of salome meca, the same dialog box hangs for a very long time until removed by task manager(end process). The terminal output mentions it has errors recognizing other SSDs size on the system.

Regards

Anirudh Nehra

Hello,

It is highly likely that the AsterStudy module will be removed from salome_meca; it is not a long-term solution.

Hello,

interesting comment! AsterStudy module seem to be a modern and clear way towards .comm files generation and astk replacement . Why is it going to be refused? Does edf plan another approach? Improvement eficas or maybe better plugin to visual studio code? I am very curious about next step

Best regards

Filip

It is no longer possible to maintain this tool given the limited resources allocated to it.

Furthermore, the tool is hardly ever used by EDF’s engineering department, except for training purposes.

We believe that using a tool integrated with VSCode is more appropriate.

Hi,

But for users asterstudy seems to be great pre processor of code_aster to run simple tests. It works good most of time. vscode crashes many times and is too aggressive displaying errors/warnings a lot. Requesting to not remove asterstudy but rather improve it.

Also I’m not convinced by recent efforts to make salome_meca more “windows friendly”.Good for beginners but There are many things that just won’t work well in windows. Especially running MPI calculations with aster. Even wsl is a constrained environment and windows isn’t open source either. Rather efforts could be directed to make salome_meca with asterstudy faster and more robust for linux especially when now linux is going wayland. Just my opinion and everyone can disagree.

Regards

Hello,

In the world of HPC computing, Linux clusters are almost exclusively used. Windows isn’t designed for this.

We have to make trade-offs given our limited resources, and we prefer to focus on the core functionality (the code_aster solver) rather than on graphical interfaces (such as asterStudy).

Hello,

Thank you for response.

Indeed improvement of core functions of aster is most important.

Maybe simvia could take care of asterstudy.

Regards

Hello,

that is quite disappointing news about the discontinuation of Asterstudy. I have no problem to adapt to VSCode, but I don’t see the point why? Why do you have the time to develop a package (or addon, IDK what it is called) for VSCode and at the same time say basically “we do not have time to develop Asterstudy further”?

Isn’t this decision against the “no regression” policy of EDF for software (hint: it is)? Shouldn’t open-source software be about entshitification?

You opened a can of worms with the decision to switch everything to Python, didn’t you?

Moreover: with all the AI-dev tools available in VSCode (Kilo Code …), the continuation of development of Asterstudy should be a piece of cake.

Hopefully somebody will fork it, it is the most important part of Salome-Meca, and made it the ONLY open-source software usable for beginners. There are other FEA-packages that necessitate the use of more than one tool, and that’s exactly what made them worse.

Mario.

Hello, I think that using code_aster with vscode is much faster than salome_meca, but to generate .comm, AsterStudy is great. One can see all the options available and it will generate the right syntax.

It would be great to have AsterStudy separately like it was intended before. I use daily wsl + salome + salome_meca windows (only for asterstudy) and I have found it is the most optimal way so far.

Hello,

It’s a question of efficiency given our dwindling resources. We don’t have enough time or money to devote to maintaining AsterStudy. We haven’t done anything with it for years, as you can see.

And if we do work on it, well, we can’t do anything else…

Within EDF, almost nobody uses it, and as they’re our customers and they’re the ones who fund us, well, there’s nothing we can do. That’s just how it is.

For the time being, AsterStudy is still going. As long as there are no major problems, we’ll carry on. AsterStudy (and its bugs !) is still available in salome_meca.

Hello,

Disappointed to hear that.

What about Salome Platform? Don’t they manage salome part of salome_meca? And if EDF is not interested in salome anyway, salome will likely vanish?

And finally future of code_aster?

I hope EDF not going Siemens way. Just look what Siemens did to Openradioss.

Regards

Anirudh

Hello,

I have an issue regarding mesh generation in salome. I have posted the issue on Salome_platform forum here

link

Highly appreciated If someone could help regarding it.

Regards

Anirudh