-
Notifications
You must be signed in to change notification settings - Fork 20
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
The admb executable called with a path should be stripped. #165
Comments
Hi @jimianelli and @Cole-Monnahan-NOAA, please test the issue165 branch. It should be able to read and write to a directory that is different from where the executable is. |
I built this branch, compiled simple then tried this: C:\Users\cole.monnahan\admb\examples\admb>simple\simple.exe Is that what you wanted me to test? |
Move simple.exe to another directory (ie C:\Users\cole.monnahan\bin\simple.exe). Then call simple.exe with it's full path,
Check that program was able to read input files and write the outputs in the simple directory. |
Still fails. I should note this in Win10. C:\Users\cole.monnahan\admb\examples\admb\simple>C:\Users\cole.monnahan\test\simple\simple.exe -version ADMB-12.2-git safe libraries compiled with GNU C++ 8.3.0 (64bit) C:\Users\cole.monnahan\admb\examples\admb>C:\Users\cole.monnahan\test\simple\simple.exe C:\Users\cole.monnahan\admb\examples\admb>ls C:\Users\cole.monnahan\test\simple |
I misunderstood your original request. The idea is you have one master .exe file and multiple directories with e.g., different inputs and you want the inputs/outputs to always be in the directory. Yes this works: C:\Users\cole.monnahan\admb\examples\admb\simple>C:\Users\cole.monnahan\test\simple\simple.exe Initial statistics: 2 variables; iteration 0; function evaluation 0; phase 1
|
Merge Issue #165: The admb executable called with a path should be stripped.
Currently, if the executable is called with the path, the inputs will be read from the executable path and the outputs would be written to the executable path.
For example,
model.exe would try to read input files from ~/bin, then write outputs to ~/bin instead of ~/run directory. The executable should read and write to the ~/run directory.
@jimianelli requested this feature.
The text was updated successfully, but these errors were encountered: