You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
"In addition, it seems also that sumatra really wants to be run from the main repo where the source are... It is quite unsual for the kind of model I'm using. Instead I have a dedicated "run" directory (in fact I have many). When using smt init -r path_to_versioned_source in such directory, smt fails because it tries to clone in the current directory which already contains data, param files, etc. As my repository is on y disk, does smt really need to clone it ?
"
The text was updated successfully, but these errors were encountered:
I would like to second this. I love everything about sumatra, except the fact that every time I want to run simulations in a new place on my filesystem I have to clone my repo into that directory. It just introduces a lot of unnecessary clutter. All my source code usually sits in a single place, and I run simulations in different directories, mountpoints, etc. I don't need to clone the code into those directories.
If someone wants to point me to the relevant places in the source, I could take a shot at adding this.
Ghislain Picard asked on the mailing list:
"In addition, it seems also that sumatra really wants to be run from the main repo where the source are... It is quite unsual for the kind of model I'm using. Instead I have a dedicated "run" directory (in fact I have many). When using smt init -r path_to_versioned_source in such directory, smt fails because it tries to clone in the current directory which already contains data, param files, etc. As my repository is on y disk, does smt really need to clone it ?
"
The text was updated successfully, but these errors were encountered: