[Swift-devel] Back to work

[Tim Armstrong]

The idea would be to have a generic capability that would let you write C
extensions that implement generic executors, plus all of the changes to
ADLB/Turbine that let these run alongside CPU workers.  Potentially you can
add whatever you want.  Adding support to the full language stack from
syntax down is a separate task.

What's the motivation for the IPython idea? It feels like a lot of moving
parts to me.

- TIm


On Thu, May 29, 2014 at 9:32 AM, Michael Wilde <wilde at anl.gov> wrote:

>  Tim, this sounds good.  Could you consider how we'd do an async task
> executor that can use iPython's parallel-remote services, as an alternative
> to coasters?
>
> - Mike
>
> ps. Yadu will return to CI on Mon June 2. He's working remotely this week.
>
>
> On 5/29/14, 9:18 AM, Tim Armstrong wrote:
>
> Welcome back Yadu!
>
> This isn't work for Yadu exactly, but it touches on Yadu's coasters work.
> I was going to flag that I intended to push forward on full integration of
> asynchronous task executors (GeMTC/Coasters/others) into Swift over the
> summer, since it's important but I haven't gotten around to adding proper
> support for multiple worker types, etc:https://code.google.com/p/exm-issues/issues/detail?id=581https://code.google.com/p/exm-issues/issues/detail?id=503https://code.google.com/p/exm-issues/issues/detail?id=609
>
> - Tim
>
>
> On Thu, May 29, 2014 at 9:08 AM, Michael Wilde <wilde at anl.gov> <wilde at anl.gov> wrote:
>
>
>  Hi Yadu, welcome back! (at least, part-way back ;)
>
> Hope you're having a very pleasant holiday with family and friends.
>
> I'll start steering some work your way.  First thing, can you:
>
> a) check on the automated tests and report to me what they are seeing.
> What should I and others (Mihael, Justin, Tim) be looking at to see how
> the tests are doing?
>
> b) Get tests in place, and extend the tests, to test the new "array
> return from app" logic:
> - test with and without provider staging
> - test with and without location= (and other stages)
> - test with a variety of mappers, starting with simple_mapper and
> array_mapper(s)
> - test with and without returning non-array files along with array files
> (in combination with the above...)
>
>  From the list below, 1-3 is good; please set 4 aside for now.
>
> Thanks,
>
> - Mike
>
> On 5/27/14, 2:41 AM, Yadu Nand wrote:
>
>  Hi Mike,
>
> I've been working a couple of hours spread over weeks on pSIMS for some
> additional
> changes Joshua wanted. I have the hours noted for those.
>
> I'll be working in a bit more regular fashion this week, and we can talk
>
>  if
>
>  needed over skype.
>
> Here's what's on my list:
>
> 1. Fix the image issue with compute-engine and mail the list.
>    (My brother is testing this for me)
>
> 2. Documentation for pSIMS.
>
> 3. Get the test-suite to report results better.
>
> 4. Go over the picloud documentation (they've stopped new signups)
>
> If anything of higher priority comes along, I'll be glad to help.
>
> ​Thanks,​
>
> Yadu
>
>
>  --
> Michael Wilde
> Mathematics and Computer Science          Computation Institute
> Argonne National Laboratory               The University of Chicago
>
> _______________________________________________
> Swift-devel mailing listSwift-devel at ci.uchicago.eduhttps://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
>
>
> _______________________________________________
> Swift-devel mailing listSwift-devel at ci.uchicago.eduhttps://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
>
> --
> Michael Wilde
> Mathematics and Computer Science          Computation Institute
> Argonne National Laboratory               The University of Chicago
>
>
> _______________________________________________
> Swift-devel mailing list
> Swift-devel at ci.uchicago.edu
> https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.mcs.anl.gov/pipermail/swift-devel/attachments/20140529/6a9d6070/attachment.html>