[ADMB Users] directory where *.par, *.cor, *std etc are created in Linux or Mac, when executable is located other than current directory

[yukio_takeuchi at icloud.com]

Hi,

When I do multiple calculations with different dat file but with same 
executable compiled with ADNB, I usually set up directories with 
different dat file and put an executable on one more upper level in ms-
windows. e.g.

c:\simrun\sim.exe
c:\simrun\sim1\sim.dat
c:\simrun\sim2\sim.dat
...
 
The I ususally use batch file like

cd c:\simrun
cd sim1
..\sim.exe

cd ..\sim2
..\sim.exe

cd ..\sim3
...

This allows me to avoid overwriting of output files (*.par,*.cor etc).

When I tried similar approach in Linux as well as mac, using relative 
path or absolute path of executable different from the current 
directory, I found that output files (*.par, *.cor, *.std etc) produced 
from executable were put on the same directory of the executable. 

Is this intended behavior under Linux or mac?

Yukio Takeuchi