[Swift-devel] LQCD mapping

Ben Clifford benc at hawaga.org.uk
Tue May 1 10:18:10 CDT 2007


or you want to be able to return a variable length array from your app?

(which has been mumbled about but never talked about terribly concretely 
on one of the lists before).

anyway, its my birthday somewhere in the world for the next 44 hours or 
so. woo woo party!

On Tue, 1 May 2007, Tiberiu Stef-Praun wrote:

> Since the discussion seems to go in the direction I'm interested in, I
> remember wishing for a filesys mapper extension where I can specify
> some verification code (such as the number of inputs matched, or the
> total file sizes) before the initialization is being done.
> This implies that the mapper retries initialization, and it only
> succeeds when a previous step has produced the right number of
> outputs. This enables sequential procedure invocation in the case when
> I don't know the names or the number of output files from one stage to
> the other.
> Currently I fixed this by archiving the output from stage one, and
> passing it to stage two (fixes the number of unknown outputs)
> 
> Tibi
> 
> On 5/1/07, Veronika V. Nefedova <nefedova at mcs.anl.gov> wrote:
> > At 10:01 AM 5/1/2007, Ben Clifford wrote:
> > 
> > 
> > >On Tue, 1 May 2007, Yong Zhao wrote:
> > >
> > > > I see, then maybe you should not use filesys_mapper, can you try
> > > > simple_mapper instead?
> > >
> > >The code in there looks like it does approximately the right stuff
> > >filename-wise for arrays.
> > >
> > >Maybe Nika can try with her workflow - if not, I'll try it later.
> > >
> > 
> > Sure, I can try that
> > 
> > Nika
> > 
> > >--
> > >
> > >_______________________________________________
> > >Swift-devel mailing list
> > >Swift-devel at ci.uchicago.edu
> > >http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > 
> > 
> > _______________________________________________
> > Swift-devel mailing list
> > Swift-devel at ci.uchicago.edu
> > http://mail.ci.uchicago.edu/mailman/listinfo/swift-devel
> > 
> 
> 
> 



More information about the Swift-devel mailing list