Closed danrhouck closed 4 years ago
The path you supply in ConfigOutputs -> OutputPath is taken relative to the path you are executing CACTUS from. I see the correct behavior on Mac. Can you please paste your .in
file and the command you used to execute?
From the .in file:
&ConfigOutputs
OutputPath = '../mine/V27TestOutput'
Run command:
drhouck@S1023207 MINGW64 ~/cactus/build
$ ./cactus ../mine/V27.inp
As stated, OutputPath
, (and all other paths included in the .in
file) are relative to the working directory you executed CACTUS from, not relative to the input file itself. I don't know what your full directory tree looks like, but it seems that output files are being put in the right place.
Tree is as follows: CACTUS>build>cactus.exe CACTUS>mine>OutputFolder
I think I have the paths correct, but I'm not certain. This is new to me.
My fault. The path needs a final '/' at the end and I did not include that originally. Without the last slash, it ignores the last part of the path and puts it one folder up.
This is a little thing, but it seems to me that the output files are always placed one level above the folders for the airfoil data and geometry. I haven't done thorough testing, but that's where they always go for me. Would be nice if they actually went in the assigned folder.