<div dir="ltr">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.<br>
<div><br>What's the motivation for the IPython idea? It feels like a lot of moving parts to me.<br><br></div><div>- TIm<br></div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On Thu, May 29, 2014 at 9:32 AM, Michael Wilde <span dir="ltr"><<a href="mailto:wilde@anl.gov" target="_blank">wilde@anl.gov</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
<div bgcolor="#FFFFFF" text="#000000">
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?<br>
<br>
- Mike<br>
<br>
ps. Yadu will return to CI on Mon June 2. He's working remotely this
week.<div><div class="h5"><br>
<br>
<div>On 5/29/14, 9:18 AM, Tim Armstrong
wrote:<br>
</div>
</div></div><blockquote type="cite"><div><div class="h5">
<pre>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:
<a href="https://code.google.com/p/exm-issues/issues/detail?id=581" target="_blank">https://code.google.com/p/exm-issues/issues/detail?id=581</a>
<a href="https://code.google.com/p/exm-issues/issues/detail?id=503" target="_blank">https://code.google.com/p/exm-issues/issues/detail?id=503</a>
<a href="https://code.google.com/p/exm-issues/issues/detail?id=609" target="_blank">https://code.google.com/p/exm-issues/issues/detail?id=609</a>
- Tim
On Thu, May 29, 2014 at 9:08 AM, Michael Wilde <a href="mailto:wilde@anl.gov" target="_blank"><wilde@anl.gov></a> wrote:
</pre>
<blockquote type="cite">
<pre>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:
</pre>
<blockquote type="cite">
<pre>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
</pre>
</blockquote>
<pre>if
</pre>
<blockquote type="cite">
<pre>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
</pre>
</blockquote>
<pre>--
Michael Wilde
Mathematics and Computer Science Computation Institute
Argonne National Laboratory The University of Chicago
_______________________________________________
Swift-devel mailing list
<a href="mailto:Swift-devel@ci.uchicago.edu" target="_blank">Swift-devel@ci.uchicago.edu</a>
<a href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel" target="_blank">https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel</a>
</pre>
</blockquote>
<pre></pre>
<br>
<fieldset></fieldset>
<br>
</div></div><pre>_______________________________________________
Swift-devel mailing list
<a href="mailto:Swift-devel@ci.uchicago.edu" target="_blank">Swift-devel@ci.uchicago.edu</a>
<a href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel" target="_blank">https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel</a><span class="HOEnZb"><font color="#888888">
</font></span></pre><span class="HOEnZb"><font color="#888888">
</font></span></blockquote><span class="HOEnZb"><font color="#888888">
<br>
<pre cols="72">--
Michael Wilde
Mathematics and Computer Science Computation Institute
Argonne National Laboratory The University of Chicago
</pre>
</font></span></div>
<br>_______________________________________________<br>
Swift-devel mailing list<br>
<a href="mailto:Swift-devel@ci.uchicago.edu">Swift-devel@ci.uchicago.edu</a><br>
<a href="https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel" target="_blank">https://lists.ci.uchicago.edu/cgi-bin/mailman/listinfo/swift-devel</a><br>
<br></blockquote></div><br></div>