airavata-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Miller, Mark" <>
Subject RE: "input" and "output" subdirs in working directories
Date Tue, 23 Dec 2014 19:45:26 GMT
I am not sure of the reasoning behind the design, but off-hand it seems to me it would simplify
the job of returning to "input" and "output" files as discrete entities, so if you don't know
which files are which, you would have at least two coarse bins that can be returned under
separate banners.


-----Original Message-----
From: Marlon Pierce [] 
Sent: Tuesday, December 23, 2014 11:01 AM
To: Airavata Dev
Subject: "input" and "output" subdirs in working directories

When Airavata executes a remote command (launching a SLURM job, for example), it creates a
working directory on the target machine's scratch space and two subdirectories, "input" and
"output".  Is there a good reason for creating these two subdirectories?  Why not just do
all the work in the top level of the working directory?  It seems unnecessary.  
Also, I don't understand why these are in the GFAC module, as these should be constructed
from Registry information.

Below is background information.
Below is an example working directory.

$ cd
$ ls -tlr
total 20
drwxr-xr-x 2 ogce sds128 4096 Dec 23 07:17 output
-rw-r--r-- 1 ogce sds128  831 Dec 23 07:39 1203922204.pbs
-rw------- 1 ogce sds128   28 Dec 23 07:40 Gaussian.stdout
-rw------- 1 ogce sds128  663 Dec 23 07:40 Gaussian.stderr drwxr-xr-x 2 ogce sds128 4096 Dec
23 07:47 input

The names of these subdirectories are specified in (as 
files in the GFAC module that use these two constants.

$ find ./modules/gfac -type f -exec grep -il "OUTPUT_DATA_DIR_VAR" {} \; 
| grep java|grep -v target


So we would need to clean these up if we remove the constants.


View raw message