Prevent as_run from modifiying the .export file

Msegade

I'm running a study from the command line with:

$ as_run myStudy.export

After that, the file myStudy.export is slightly modified, adding some lines and substituting the name of the input and results files with their full paths. For example:

F comm myStudy.comm D 1

get replaced with:

F comm /home/user/path/to/my/file/truss.comm D 1

I want to keep this file portable, so I don't want it to have the full path of the files for my machine. Is there any way for prventing as_run from doing this?

Thanks

Sound_Spinning

Msegade
Did you, or anyone else found how to do this? Prevent CA from editing the.export file when running jobs from a terminal with as_run? It feels a bit odd that a code will edit the inputs by default.

k_zurawski

I had a script which created a temporary *export file. After it was submitted for analysis the file was deleted automatically. But it's not needed anymore. When you run analysis with run_aster command rather than as_run, the path is not added to the export file.

Sound_Spinning

k_zurawski
Oh, that sounds interesting. What's different when using run_aster, same .export format? And is this in new versions, or we always had run_aster?

Sound_Spinning

k_zurawski
Thanks for the tip on run_aster. Indeed, it doesn't edit the .export file AND it keeps comments, starting with #.
Great, problem solved.

k_zurawski

Sound_Spinning I was told that run_aster is the new way of invoking solver with python language support. If you just write run_aster without referring to any export file you'll see what I mean.