Hello,
I am currently conducting research using AsterStudy in Salome-Meca version 2024.01.
For problems with short runtimes, when an error occurs, it is usually manageable to debug and fix the issue based on the log files, so the burden is relatively small.
However, for problems with long runtimes—especially nonlinear quasi-static analyses—having to restart the entire study from scratch is very costly.
For example, if an error or a power outage occurs at around 90% of the total steps, the resulting frustration is significant.
Even when Salome-Meca is terminated due to a Linux GUI error or forced logout, Code_Aster itself continues running independently.
By exploring the /tmp directory via the terminal, I was able to find files such as glob.1 and vola.1, and I could monitor the analysis progress using the fort.6 file.
I currently have two main issues/questions:
1. Since glob.1 exists in the TMP directory, I believe it should be possible to resume the study.
How can this be done using AsterStudy?
• For reference, in other studies, even after adding a new stage, the Resume button sometimes remains disabled.
2. In the case of a power outage, the entire Run_aster.* directory stored in /tmp disappears, which is very alarming.
How can the working directory be changed in AsterStudy to prevent this?
• Would it be mentally and practically healthier to use ASTK instead?
Thank you in advance for your help.
Additional note:
Please note that I do not have prior knowledge of the Python programming language and currently rely heavily on GPT-based assistance when working with Code_Aster and AsterStudy.
In addition, although I am currently using a Linux-based system, I do not have much prior knowledge or experience with Ubuntu24.04.
