Hi Christophe,
Thank you so much for your advice! You're right, the intermediate files are still alive (for now) in the scratch directory. I should have looked before, but I didn't because in the past, the scratch directory has erased files quickly. Since then, I've changed scratch directories and the files last longer.
I wasn't sure how to merge the files manually, but with some trial and error, I copied and adapted the example from the ipy notebooks. From the simulation directory, run:
gretel.py --geo-file T2DGEO --geo-file-format SERAFIND --res-file T2DRES --res-file-format SERAFIND --ncsize X --bnd-file T2DCLI
gretel.py --geo-file GAIGEO --geo-file-format SERAFIND --res-file GAIRES --res-file-format SERAFIND --ncsize X --bnd-file GAICLI
(With X the number of parallel processes used to run the simulation, e.g. 4 or 12). Note that I use double format, so adapt SERAFIND to SERAFIN or MED as needed)
(Also of note, this can likely be adapted to whatever modules you are using. Just find all the *GEO and *CLI files, and change the *RES file name to match in every gretel.py command.)
The above commands automatically find all the partitioned files and merge them. Then, the results files (*RES) can be moved or copied to whatever location:
cp T2DRES ~/path/to/results/telemac-results.slf
cp GAIRES ~/path/to/results/gaia-results.slf
From there, the selafins should work as normal for postprocessing. In my case, I can see that there is some bed rippling forming at the entry, perhaps this is causing numerical instability... but that's a problem for another thread
I hope this can be useful for anyone else in my position. Maybe this can be added as an option in the dico in the future, with default value of NO? I can see why it may not be a good idea, but IMO it would be useful for users to be able to inspect the simulation where it fails, without having to go "under the hood" of TELEMAC.
WRITE RESULTS ON FAILED SIMULATION =YES
PS: the profile settings don't show Windows 10 or GAIA as option, I think
they need to be updated!