How to get S5R3 workload, got one S5R2 today ?!?
24 Sep 2007 16:55:39 UTC
Topic 193172
(moderation:
Howdy all,
hopefully it is stated somewhere what to do if one want to get S5R3 works to crush .. I changed my Einstein project from "No New tasks" to "Allow new tasks" and got S5R2 work unit ?!
24/09/2007 19:40:32|Einstein@Home|Restarting task h1_0527.35_S5R2__148_S5R2c_2 using einstein_S5R2 version 433
( I'm sure that I had no S5R2-tasks in my task list before this day )
I have the S5R2 4.33 binary and app_info.xml in my einstein folder .. Should I make some dramatic moves as removing both of them ( or even more famcier like editing client_state.xml .. )
-- Lundi --
( I thought that all S2R2 work was already scheduled .. )
How to get S5R3 workload, got one S5R2 today ?!?
)
Hi ho!
There were about (at least) 32000 results of S5R2 left at the time the new S5R3 units were first released, so they still need to be crunched.
Eventually you will have to remove the app_info.xml file in your BOINC/projects/einstein.phys.uwm.edu folder, but doing so will break the currently crunched unit. Best way is to let the currently crunched unit finish and then, after the result was reported to the server and the next unit is freshly beginning to crunch, you can delete the app_info.xml file. This will invalidate yll your remaining S5R2 units in the pipeline, but doing this immediately after a unit completed will result in only minimal loss of crunching time.
If you insist on losing NO work whatsoever, you can set "no new work" and wait until all the tasks in the pipeline are crunched and reported.
CU
Bikeman
You will not get S5R3 work
)
You will not get S5R3 work while you have a Beta application (especially an old one like v4.33) and an app_info.xml file. There was some hope that the final Beta app (v4.40) could handle S5R3 work, but that plan has been cancelled.
From what I can see, all the new S5R2 work has been distributed, but occasional WUs do appear. I've had three new units download onto a box with an app_info like yours, since the start of the S5R3 distribution: all of them were re-issued WUs following errors, missed deadlines etc.
Now you have work, the best thing is to set 'No New tasks' again: wait until this WU has finished and reported: delete the app_info.xml file (you don't need to delete anything alse): stop and re-start BOINC: and only then allow new tasks. You should then download the new application, and new jobs to do with it.
RE: From what I can see,
)
I suspect some appreciable new S5R2 stuff is left.
I have a Core 2 Duo which has munched its way down from:
h1_0547.60_S5R2__269_S5R2c_0
issued on September 13 to
h1_0547.60_S5R2__125_S5R2c_0
sent about five hours ago. (of course it was created in the terminal rush of September 17)
The rate of issue has gone up some, presumably as hosts which finished their bit got added to the pack, but it appears my lot (547.60) still have several days to go just to get all the _0s issued.
RE: I suspect some
)
Some of my S5R2 units are still listed as "Pending" and not yet reissued, so presumably they will be reissued until successfully completed.
RE: RE: I suspect some
)
...and some of us out here are just picking up R2 stuff as we can. The scheduler refuses the 4.33 app if there isn't any R2 work to be picked up...
2007-09-25 02:10:30 [Einstein@Home] Sending scheduler request: Requested by user
2007-09-25 02:10:30 [Einstein@Home] Requesting 8384 seconds of new work
2007-09-25 02:10:35 [Einstein@Home] Scheduler RPC succeeded [server version 601]
2007-09-25 02:10:35 [Einstein@Home] Message from server: To get more Einstein@Home work, finish current work, stop BOINC, remove app_info.xml file, and restart.
2007-09-25 02:10:35 [Einstein@Home] Message from server: No work sent
2007-09-25 02:10:35 [Einstein@Home] Deferring communication for 4 hr 0 min 0 sec
2007-09-25 02:10:35 [Einstein@Home] Reason: requested by project
i haven't received an r3
)
i haven't received an r3 workunit yet, my last r2 workunit was issued on 29 september. i am not running any beta or test apps. any ideas how i can get the new work? the 70hr crunch times are a little much.
thanks
RE: i haven't received an
)
More and more S5R3 units are distrinuted now, the S5R2 units must be in short supply soon. Expect a S5R3 unit in the next few days.
CU
H-BE
thanks, i should have been
)
thanks, i should have been more patient as i received an r3 unit today!
RE: More and more S5R3
)
I think the last never-issued S5R2 unit got sent out sometime in the last few hours. Suddenly the "oldest unsent result" is just a little under seven days old, where it was over twelve days a few hours ago. As the last S5R2's got built in one brief push, that pretty much rules them out.
Still a fair amount of re-issuing going on, and with the long execute time and long deadlines for most of what was getting issued toward the end, I think there will be a good bit of S5R3 re-issue for some weeks to come.
This my host, seems to crunch
)
This my host, seems to crunch all remained S5R2 WUs. And even now I don't see any evidence of S5R3 here. I'm not worry about this. I just comment this. So, please, don't worry. Sometimes any of you will have a chance to participate in S5R3 - we have more than 600 days for this yet.