Hello everyone,
I am looking for some technical clarification regarding how parallel I/O and database saving are handled in the newer versions of Code_Aster (17.4.0), specifically concerning the removal of the PROC0 keyword.
In version 16.6.6, the PROC0 option was removed from the FIN() command (the [changelog] (https://gitlab.com/codeaster/changelog/-/blob/main/histor/v16/16.6.6?ref_type=heads
), and the specific [commit](https://gitlab.com/codeaster/src/-/commit/876704fe6bde568c55ec4e6c1bca3dc2b90abe3a
)
To my understanding. previously, PROC0='OUI' explicitly told the code to store the database using only Rank 0. Now that this is removed, I understand that Code_Aster handles this implicitly. However, I am currently using as_run to launch my studies, rather than the newer run_aster wrapper. Could you please kindly clarify the following points regarding the current internal behavior:
How does the CA automatically identify and restrict global database writes strictly to Rank 0 without the user's explicit command? Does relying on as_run instead of run_aster change anything about how this MPI Rank 0 delegation is handled during the FIN() phase? Are there any specific export file parameters I need to be careful with to ensure the database doesn't get corrupted by multiple ranks trying to write simultaneously?
Thank you in advance for your insights!
Meysam
