help > Designing layouts for JIST: exporting files
Showing 1-4 of 4 posts
Dec 7, 2009 10:12 PM | dpolders
Designing layouts for JIST: exporting files
So, you made a nice layout for JIST, one that involves many
different steps, and creates lots of intermediate files for each of
your subjects/experiments. The final result is buried somewhere in
the directory structures, probably called
exp-####-AAABBCCC\[whateverthelastmodule].
How would you go about collecting these final files into one directory for all your experiments?
To accomplish this, I was trying to use the Destinations/output or externalize modules, but they seem to do nothing of the sorts. They donĀ“t even show up on the process manager's task list. Is this a flawed approach?
Daniel
How would you go about collecting these final files into one directory for all your experiments?
To accomplish this, I was trying to use the Destinations/output or externalize modules, but they seem to do nothing of the sorts. They donĀ“t even show up on the process manager's task list. Is this a flawed approach?
Daniel
Dec 16, 2009 02:12 PM | Bennett Landman
RE: Designing layouts for JIST: exporting fil
You were on the right track! Please use the destinations/output
modules (the green ones) to copy specific files to desired output
locations. (Note: Use "OUTPUT" not "EXTERNALIZE".) The "OUTPUT"
modules are used for directing output from a layout. The
"EXTERNALIZE" modules allow one to embed layouts in other layouts
and provide support for dynamically changing the inputs to layouts.
For what you want, use the "Copy Files" module. The input/output ("sources"/"destinations") are special in that they are not treated as modules in the layout manager and they will not be pushed to a grid computer even if one is available. Thus, they are allowed to use LOCAL paths as opposed to a shared/common mount point. The destinations are automatically run once all tasks have finished in the process manager. If you want to manually kick off the "process destinations", select "Scheduler->Process Destinations" from the Process Manager's menu bar.
Thanks!
Bennett
For what you want, use the "Copy Files" module. The input/output ("sources"/"destinations") are special in that they are not treated as modules in the layout manager and they will not be pushed to a grid computer even if one is available. Thus, they are allowed to use LOCAL paths as opposed to a shared/common mount point. The destinations are automatically run once all tasks have finished in the process manager. If you want to manually kick off the "process destinations", select "Scheduler->Process Destinations" from the Process Manager's menu bar.
Thanks!
Bennett
Jan 4, 2010 06:01 PM | Colin Shea
RE: Designing layouts for JIST: exporting files
Daniel-
In addition to Bennett's advice, in my experience it may also be necessary to add a trailing "\" or "/" to the end of the output path in the "Destination Directory" after browsing to the desired folder. I remember running into this problem after many failed attempts to copy output to a desired folder. It really ought to be the default behavior of the browser to retain the required slash or backslash, but give that a try if you're still scratching your head over an empty output folder.
In addition to Bennett's advice, in my experience it may also be necessary to add a trailing "\" or "/" to the end of the output path in the "Destination Directory" after browsing to the desired folder. I remember running into this problem after many failed attempts to copy output to a desired folder. It really ought to be the default behavior of the browser to retain the required slash or backslash, but give that a try if you're still scratching your head over an empty output folder.
Jan 5, 2010 06:01 PM | Bennett Landman
RE: Designing layouts for JIST: exporting fil
I agree that this should be the default behavior (and I think it is
for most cases). if you encounter a situation where the use of "\"
or "/" doesn't make sense, please file a bug report. Please be sure
to tell us what O/S you are using!