[Swift-user] output file array

Ketan Maheshwari ketan at mcs.anl.gov
Fri Jan 9 11:17:48 CST 2015

On Thu, Jan 8, 2015 at 12:00 PM, Hategan-Marandiuc, Philip M. <
hategan at mcs.anl.gov> wrote:

> On Thu, 2015-01-08 at 10:53 -0600, Ketan Maheshwari wrote:
> > file appout <single_file_mapper; file=strcat("outdir", i,
> "/appout.txt")>;
> >
> > Currently, this pattern gets honored for stdout/stderr files, ie. Swift
> > creates the outdirN and puts the stdout/stderr files into it.
> Not automagically! You pass the stdout/stderr file names to the app
> command line using stdout= and stderr=.

True. However, the scheme is not quite consistent due to the following

-- When specifying stdout and stderr in command line, I do not specify them
in directories. Yet, if I map them in non-existent directories, Swift will
create those directories and put the stdout/stderr files in them. This does
not happen with other files even if they are specified in command line.

-- If a file is specified as output file in app definition but does not
appear in the command line, Swift will still bring it in as an output.
Again, this will happen only if the file is mapped at top level and not in
any directory.

> So in all cases swift honors what you tell it to honor. The question is
> what is it that you really want here:
> - is it to automatically create multiple versions of files when an app
> specifies the same output file and there are multiple invocations?

Yes. The app specifies it alright but the executable does not specify it on
command line.

> - or is it for swift to ignore the directory in the remote app output
> when staging out files (but not locally)?
> Mihael
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-user/attachments/20150109/a3fa2f09/attachment.html>

More information about the Swift-user mailing list