As of last week, even though it appears the E@H servers are all up and running, I have received no more new WU's.
Preferences appear to be okay, and maybe I missed something on the home page in regards to a possible explanation.
Also, in the "projects" tab of BOINC Manager, it is not set as "no new work" for E@H, nor is suspend. E@H is simply sending no more WU's.
Any thoughts?
Copyright © 2024 Einstein@Home. All rights reserved.
No New WU's
)
Your E@H resource share is 33%. BOINC might just run the other projects to balance debt, see [[Work_Scheduler]].
Michael
PS: I just noticed that you can link directly to the Unofficial WIKI.
Just use [ [ Term ] ] (w/o space).
Team Linux Users Everywhere
I run SETI and CPDN a well.
)
I run SETI and CPDN a well. CPDN has been running steadily during the last few days while SETI has been down. I am somewhat surprised that no new work units have been assigned from E@H. Seems odd, even considering the balance.
RE: As of last week, even
)
no work units for me either been waiting few days now all i get is scheduler request pending
Okay, that's three people and
)
Okay, that's three people and under the scientific method, enough to at least get started in the direction of saying there's seemingly something awry.
RE: Okay, that's three
)
As Michael K. referenced it is likely that BOINC is playing catch up on the work debt that has built up toward other projects. If you want you can force BOINC to download some E@H by setting your other projects to no new work and suspending them and then re enabling everything after new work downloads. But by doing so you may over commit your box and miss wu deadlines.
(To tell the truth, I'm guilty of forcing downloads myself... Sometimes when SIMAP lets loose at the beginning of each month with limited work, part of my boxes will miss getting any so I "help" things along. I know that if I left things alone, it will work itself out in the long run but ::shrug:: As long as I don't over commit I believe I'm doing ok)
RE: Okay, that's three
)
One possibility is that when the ‘surprise’ long WUs started coming out, on quite a few systems BOINC had to give E@h extra CPU time to get them finished before deadline, as Michael K. suggested upthread. In doing so it would have built up some long-term debt, which is now being paid back to other projects.
RE: RE: Okay, that's
)
Well here's another reason why I still find that a little hard to accept:
As I mentioned, I run CPDN and SETI. In the last year, I have finished several CPDN WU's with 2008 deadlines. I average one about every four to five months. Now if BOINC is merely looking at deadlines and estimated times of completion, okay, then what you (generic) say makes sense.
The reality would then be missed by the software.
RE: RE: RE: Okay,
)
Actually you can look up the long term and short term debt in the client_state.xml file in your BOINC directory. Just search for "debt".
CU
BRM