-
Notifications
You must be signed in to change notification settings - Fork 13
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Errors when output dir/files exist #10
Comments
Comment by whophil The system call to Does the code halt on your system? |
Comment by petebachant Seems like it keeps running. Can we do something like |
Comment by whophil Unfortunately that would kill Windows compatibility. |
Comment by petebachant Ah! Oh well. I will just remove the directory each run. |
Comment by whophil I think I see the problem now which arises when you call CACTUS via script and it raises an "Error," potentially halting your script. Of course you could just clean the output directories before you call CACTUS. A more robust solution would be to compile different code bits under different environments using |
Comment by whophil See whophil@e5cb8da I haven't had time to test it on Windows or with Intel Fortran, but it works using GFortran on Linux, which I believe is your environment as well. |
Comment by petebachant Can confirm it works on Linux with GFortran. I don't have an environment setup to compile Fortran on Windows to test though. |
Issue by petebachant
Saturday Apr 16, 2016 at 00:34 GMT
Originally opened as https://github.com/whophil/CACTUS-SNL/issues/32
Making a new
output
dir was a good idea, but it may already exist, and produce errors likeThe text was updated successfully, but these errors were encountered: