On Mar 18, 2007, at 6:57 AM, Mike Hansen wrote: > > I seem to be getting a few errors in sage-2.3. I've set worker.conf > to have 15 workers and started them with dsage.worker(). It says it > initialized all 15 on startup. However, when I test things out with > DistributedFactor(D, 11^150+1), I get the following errors: > > > 2007/03/18 06:46 -0700 [Broker,client] [Worker: 1] Got job (qsieve, > DBVtLpnyOA_2) > 2007/03/18 06:46 -0700 [Broker,client] [Errno 17] File exists: > '/home/students/hmc_2007/mwhansen/.sage/dsage/tmp_worker_files/ > DBVtLpnyOA_2' > ... > 2007/03/18 06:46 -0700 [Broker,client] [Worker: 14] Got job (qsieve, > DBVtLpnyOA_2) > 2007/03/18 06:46 -0700 [Broker,client] [Errno 17] File exists: > '/home/students/hmc_2007/mwhansen/.sage/dsage/tmp_worker_files/ > DBVtLpnyOA_2'
That really shouldn't be happening. It looks like Worker 1 and Worker 14 are getting the same job which is definitely not right. Your job database might have gotten screwed up. I think the easiest thing to try right now is to remove the $HOME/.sage/dsage/db and $HOME/.sage/dsage/tmp_worker_files directory and try again. > Also, when I try running my distributed function on an install of > sage-2.1.4, it works fine. But, when I try to run it on the server, I > get the following errors: > > Error: 'Job' object has no attribute 'jdict' > Traceback: None > ... > Error: 'NoneType' object has no attribute 'pickle' > Traceback: None > Are you trying to run DSAGE between different versions of SAGE? The way that jobs are handled changed quite a bit, which is why it complains about some attributes not being there. Try it again using sage-2.3 throughout. Cheers, Yi > > On 3/17/07, Yi Qiang <[EMAIL PROTECTED]> wrote: >> >> >> On Mar 16, 2007, at 10:33 PM, Mike Hansen wrote: >> >>> >>> Hello, >>> I'm running some computations in SAGE for my research, and they are >>> quite time consuming, but proudly parallel. I'd obviously like >>> to use >>> DSAGE to speed them up, but I have a few questions. >> Hi Mike, >> I am glad you are making use of DSAGE! >> >>> 1) Is there an easy/convenient way to start 16 dsage workers on a >>> single machine? >> >> Yes. Edit $HOME/.sage/dsage/worker.conf and change the line: >> 'workers = 2' >> to whatever number you need, i.e. 16. This will spawn 16 workers. >> >>> 2) If the task requires additional functions / classes defined in a >>> .sage file, I assume all >>> workers would need to load/attach that file to carry out the jobs. >>> This works fine on a single machine, but if you wanted to use >>> multiple >>> machines, would you need to include that entire file within each job >>> being passed around? Is there a better way to do that? >> >> Currently you would have to attach the additional information with >> each job. I am not sure of a better way to do that unless you are >> running all the workers from the same SAGE installation (via network >> sharing for example). I think most of the time it's a pretty small >> amount of overhead. Please let me know if your functions/classes are >> so big that it's prohibitive to include them with each job. >> >>> 3) Can you use ipython1 (chainsaw/saw) from within SAGE? >>> >>> 4) I've looked through the sage/dsage/dist_functions and was >>> wondering if there were any other primary pieces of DSAGE >>> documentation that I'm missing. >> >> It depends on what you want to do. If you simply want to write >> distributed functions, than that is all you should need to look at. >> >> Please feel free to ask more specific questions if you have them. >> >> Cheers, >> Yi >> >> >> >> >>> >> > > > --~--~---------~--~----~------------~-------~--~----~ To post to this group, send email to [email protected] To unsubscribe from this group, send email to [EMAIL PROTECTED] For more options, visit this group at http://groups.google.com/group/sage-devel URLs: http://sage.scipy.org/sage/ and http://modular.math.washington.edu/sage/ -~----------~----~----~----~------~----~------~--~---
