On Wed, Sep 17, 2008 at 4:27 AM, Martin Albrecht <[EMAIL PROTECTED]> wrote: > > On Tuesday 16 September 2008, Yann Le Du wrote: >> Hello, >> >> I tried to email the person apprently responsible for dsage, Yi Qiang, >> about this, to no avail, so I turn to the list. >> >> I use sage, v. 3.1.1, and am trying to build an application (Monte Carlo >> stuff) and use dsage to parallelize the code : very easy stuff, just do a >> series of jobs, done normally in sequence on a single computer, in >> parallel on many. >> >> So I fiddled around with dsage, managed to understand the basics, and I >> find it very good, yet I have a few questions/remarks : >> >> 1/ Why isn't there a clear, publicized, illustrated description of how to >> use dsage ? I managed to make it work, but only after googling hard. >> >> 2/ How can I send a job to a worker that will output intermediate values ? >> I mean, say the job sent to a particular worker computes some value, and >> that it takes 100 iterations, how can I output temporary values every 10 >> iterations and have the server report those intermediate values ? >> >> 3/ I noticed that workers can connect any time, really, and receive jobs >> even if they connect to the server only after the server started some >> sequence of jobs, which is cool. But I also noticed that if a worker gets >> killed, then its job gets lost. Isn't it possible for the server to check >> if a worker is alive, every once in a while, and if not requeue its job ? >> >> 4/ What is the function I can use to check which worker did what, and if >> it's alive, and what job got interrupted. >> >> 5/ What test can I apply to a dsage job to see if it's finished ? Say a >> job outputs a list, and I want to plot it, can I say something like "If >> there is some output, plot it, otherwise wait." ? >> >> 6/ If you have any notes, drafts, illustrating some of dsage >> functionalities, I'd be more than happy to check them out. >> >> Cheers, >> >> -- >> Yann Le Du > > Hi there, > > since nobody with better knowledge answered so far, here's what I can do. > AFAIK Yi isn't actively working on Sage or dSage anymore.
Correct. > Also, he is the > only person really familiar with the code which leaves us in an undesired > situation. Correct. >I think most Sage developers don't use dSage at all and thus > nobody cares too much at this point. Correct. > John Voight (who I BCC in this e-mail) > did work with dSage, so he might know a lot about it. > > In any case, we need to fix the dSage situation. Maybe all the work on "parallel ipython" is coming to fruition these days and they can sweep in and save us. Alternatively, you might want to look at pyprocessing, which is included in Sage and is quite good for certain things (I like it). I've cc'd Fernando Perez (Ipython) who can maybe make some comments. William --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to sage-support@googlegroups.com To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-support URLs: http://www.sagemath.org -~----------~----~----~----~------~----~------~--~---
