I haven't done any Rosetta@home workunits since July 28 and I have a fair idea why. It appears as though my Recent Average Credit has leveled off at 135.52 and despite the fact that I haven't crunched any new workunits, it remains that way. I therefore think BOINC is fooled into believing that Rosetta has received a reasonable percentage of time recently and, therefore, does not need any new workunits. Has anybody else had this problem and is there any way to fix it?

---

"Everybody seems to think I'm lazy.
I don't mind, I think they're crazy
Running everywhere at such a speed,
Till they find there's no need" - John Lennon

Hi

I think your RAC and not receiving WUs are unrelated - I believe there is a script that can be run to allow the RAC to decay if users are not returning results, but the R@H team haven't implemented that script (yet?).

When you say you aren't getting WUs, is that because you're running other BOINC projects that are currently running, or are you having a problem downloading work?

---

Hi

I think your RAC and not receiving WUs are unrelated - I believe there is a script that can be run to allow the RAC to decay if users are not returning results, but the R@H team haven't implemented that script (yet?).

When you say you aren't getting WUs, is that because you're running other BOINC projects that are currently running, or are you having a problem downloading work?

I'm running several other projects currently (9 others to be exact) so I get the feeling that BOINC thinks Rosetta@home is getting the 8.97% resource share it is given because the Recent Average Credit is so high. All my other projects receive work with no problems.

I had an idea of maybe suspending the other projects for a time so I am forced to receive work from Rosetta@home but I'm not sure if this will reset my RAC or not.

---

"Everybody seems to think I'm lazy.
I don't mind, I think they're crazy
Running everywhere at such a speed,
Till they find there's no need" - John Lennon

Rosetta workunits have a relatively short deadline (1 week), which may explain why you're not getting any with that many projects: Looks like BOINC doesn't think it can finish it in time.

---

Rosetta workunits have a relatively short deadline (1 week), which may explain why you're not getting any with that many projects: Looks like BOINC doesn't think it can finish it in time.

Ok so maybe increasing the resource share would do the trick?...let me give it a try. I did, however, have the same number of projects connected before with the same resource share and I never had a problem...so I'm not quite sure what changed. I am, for instance, also in RALPH@home (which uses the same basic workunits) and continue to receive workunits on an almost daily basis. In fact, now with LHC@home and Predictor@home down for the time being, I receive a large portion of RALPH workunits.

Well I decided to try increasing the resource share to 79%, but I am still receiving no new work from Rosetta. In fact, BOINC is still trying to get LHC workunits (which I haven't had for over 2 months or so).

---

"Everybody seems to think I'm lazy.
I don't mind, I think they're crazy
Running everywhere at such a speed,
Till they find there's no need" - John Lennon

Well after I detached and reattached the project, I seem to be getting workunits again. I still don't really know why this happened (only speculation), but at least I think I solved it (hopefully I keep getting workunits after this batch). Thanks for everyone's help:P

---

"Everybody seems to think I'm lazy.
I don't mind, I think they're crazy
Running everywhere at such a speed,
Till they find there's no need" - John Lennon

RAC has nothing to do with the DL of WUs, but the LTD (long term dept).
If you crunch 9 projects, and one with big WUs and short deadlines gives you a WU, BOINC will crunch this one nearly asap, and then will wait until it's time again to DL the next WU. In the long run your percentage will be met, in the short run not. Detach/Reattach will DL the next WU, as a DL always will happen with the attaching, but in the long run leaving BOINC alone will sort it ouit by itself.

RAC has nothing to do with the DL of WUs, but the LTD (long term dept).
If you crunch 9 projects, and one with big WUs and short deadlines gives you a WU, BOINC will crunch this one nearly asap, and then will wait until it's time again to DL the next WU. In the long run your percentage will be met, in the short run not. Detach/Reattach will DL the next WU, as a DL always will happen with the attaching, but in the long run leaving BOINC alone will sort it ouit by itself.

Yeah I know but over the course of time since July 28, BOINC got probably about 20-30 Einstein workunits and 20-30 SETI workunits (which are about the same length as the default 3-hour Rosetta workunit or even longer) and never once did I notice it asking Rosetta@home for new workunits in Messages. Therefore it seems as though it had a preference for asking other projects for workunits over Rosetta and I thought maybe the RAC had something to do with it.

---

"Everybody seems to think I'm lazy.
I don't mind, I think they're crazy
Running everywhere at such a speed,
Till they find there's no need" - John Lennon

As you are running Windows, I'd like to recommend to you a third-party tool for the monitoring of the LTD and STD. BoincDV. Although it says it'll work with 4.4x on the Add-Ons page afaik it'll wirk with 5.x as well.

As you are running Windows, I'd like to recommend to you a third-party tool for the monitoring of the LTD and STD. BoincDV. Although it says it'll work with 4.4x on the Add-Ons page afaik it'll wirk with 5.x as well.

Hmm...the link seems to be broken or the site is down.

---

"Everybody seems to think I'm lazy.
I don't mind, I think they're crazy
Running everywhere at such a speed,
Till they find there's no need" - John Lennon

What you can do is resetting the project in the BOINC manager, that will zeroes your LTD/STD.

Boinc Debt Viewer. follow all directions. the file you'll point this script to is in "C:programfilesboinc" and is called "clientstate.xml". If you choose the reset option, it will reset all debt for all projects to zero and you're boinc will start honoring your resource share from that point on. It will prompt you to shut down, boinc, this means you need to click "file" then "exit". The red x only shuts down the manager, not the daemon (boinc.exe)

tony

Thanks mmciastro...I'm sure I'll use this fairly often, if only to diagnose problems like this and just to see the state of my projects:P

---

"Everybody seems to think I'm lazy.
I don't mind, I think they're crazy
Running everywhere at such a speed,
Till they find there's no need" - John Lennon

Thanks mmciastro...I'm sure I'll use this fairly often, if only to diagnose problems like this and just to see the state of my projects:P

it may not fix your problem, I'll be here to help you through if that doesn't work :).

tony