<html><body bgcolor="#FFFFFF"><div>Basically, the functionality we want to replicate is an app that runs on all files in a directory, filling a new directory with output files. Then we run another app on each of those output files, more or less. We don't always know that the first app will generate an output file in each case, though it does >90% of the time. </div><div><br></div><div>Dan</div><div><br>On Apr 11, 2011, at 14:20, Jonathan Monette <<a href="mailto:jon.monette@gmail.com">jon.monette@gmail.com</a>> wrote:<br><br></div><div></div><blockquote type="cite"><div><p>Well the case I have in my scripts would be to only run the reduce on the available elements in the array. I am not sure why the other case would be valid. Not doin the reduce on the array because an outfile was not mapped is the same as what swift currently does. The only difference is that instead of causing the swift system to fail it just tries to continue on the execution. </p>
<div class="gmail_quote">On Apr 11, 2011 2:06 PM, "Mihael Hategan" <<a href="mailto:hategan@mcs.anl.gov"><a href="mailto:hategan@mcs.anl.gov">hategan@mcs.anl.gov</a></a>> wrote:<br type="attribution"></div>
</div></blockquote><blockquote type="cite"><div><span>_______________________________________________</span><br><span>Swift-devel mailing list</span><br><span><a href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a></span><br><span><a href="http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel">http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel</a></span><br></div></blockquote></body></html>