join einstein they have tons of work, they need to crunch (11,675,302 tasks) to study the latest data from the two LIGO locations.

I'm amazed at the reaction to Rosetta being out of work.

. . . a virtual tradition in the wider world of BOINC projects.

With Rosetta out of work, and the server problems at Seti, there are many refugees who feel lost.

. . . WCG is always an option.

I've EMailed the project team to make certain they are aware of the problem.

---

Rosetta Moderator: Mod.Sense

I think the natural alternative to Rosetta is Human Proteome Folding (WCG) because of one of its two objectives: "further explore the limits of protein structure prediction by further developing Rosetta software structure prediction".

Correct me if i'm wrong.

---

Hmmm... no wonder my house feels colder now. My PCs ain't crunching :(

---

BTW... TFlops are dropping. About 42 right now...

---

I've EMailed the project team to make certain they are aware of the problem.

Hello Mod.Sense,

Thanks for the update.
I hope they will fix the problem quickly.

Have a nice day,
Path7.

Hopefully something will give soon... I am Crunching CPN on the same comp so its not my comp is sitting here idle. I will be patient. Heck my other comp is crunching SETI...lol at least when it can lately.

Server Status as of 27 Aug 2008 14:01:48 UTC

[ Scheduler running ] Queued: 0

---

From what I'm seeing on the home page and the Server Status page, I'm surprised to see the extremely-low number of WUs queued up, especially considering how many are in progress or how many were recently finished. When this happened 1.5 weeks ago, many people (myself included) went to another project just so our computers could be doing something. By the time work was available again, I couldn't download because I was on another project that would take days to complete. Now that those other WUs are finishing up, RAH is now out of work again.

I don't know if this is a feeder problem, a server problem, a plain lack of WUs existing, or if Rosetta as a whole is almost finished (which I can't believe is the case). Whatever the problem is, it needs to be addressed. There has been no word (from what I've seen) on why it happened the first time, let alone this time. <edit: There was one short explanation on another message board from one of the mods, but there was nothing on the home page.> For this to happen twice in two weeks is not acceptable if you want to keep your protein-crunchers.

---

Just when you thought it was safe to go back into the water...lol. I was here when this happened before. As a matter of fact I wound up here because of server issues wuth SETI. was waiting on my comp to finish crunching its last CPN and no work from Rosie. What IS a girl to do?

Server Status as of 27 Aug 2008 14:01:48 UTC

[ Scheduler running ] Queued: 0

A little “BUMP”,
just in case Mod Sense and/or the Techs are not aware of absence of new workunits.

From Boinc:
wo 27 aug 2008 21:58:55 CEST|rosetta@home|Sending scheduler request: To fetch work. Requesting 4173 seconds of work, reporting 0 completed tasks
wo 27 aug 2008 21:59:00 CEST|rosetta@home|Scheduler request succeeded: got 0 new tasks

Have a nice day,
Path7.

bump.

I have a QX9650 that is just waiting to get some Rosetta goodness on it again. It ran out this morning and the server doesn't seem to want to give it any more and it's hungry.

Please help me feed my QX; the Seti wu's are not too filling and it wants a good Rosetta meal! :D

Please help me feed my QX; the Seti wu's are not too filling and it wants a good Rosetta meal! :D

If you want something filling, though not quite as tasty as Rosetta, you could always crunch some World Community Grid (Conquer Cancer, or Proteome phase 2), or BOINC Simap :)

---

My other projects are Malaria and Spinhenge (along with the 'classic' SETI, Einstein, Climate and World Grid).

Please help me feed my QX; the Seti wu's are not too filling and it wants a good Rosetta meal! :D

If you want something filling, though not quite as tasty as Rosetta, you could always crunch some World Community Grid (Conquer Cancer, or Proteome phase 2), or BOINC Simap :)

---

My other projects are Malaria and Spinhenge (along with the 'classic' SETI, Einstein, Climate and World Grid).

Please help me feed my QX; the Seti wu's are not too filling and it wants a good Rosetta meal! :D

If you want something filling, though not quite as tasty as Rosetta, you could always crunch some World Community Grid (Conquer Cancer, or Proteome phase 2), or BOINC Simap :)

Thanks for the info, but that machine managed to snag some Rosetta wu's last night while I was sleeping. Woke up this morning and it's happily crunching some new Rosetta work.

Server Status as of 18 Sep 2008 11:57:02 UTC
[ Scheduler running ] Queued: 8

18-Sep-2008 13:13:20 [rosetta@home] Sending scheduler request: To fetch work. Requesting 101005 seconds of work, reporting 1 completed tasks
18-Sep-2008 13:13:30 [rosetta@home] Scheduler request succeeded: got 0 new tasks
18-Sep-2008 13:19:52 [rosetta@home] Sending scheduler request: To fetch work. Requesting 102317 seconds of work, reporting 0 completed tasks
18-Sep-2008 13:20:02 [rosetta@home] Scheduler request succeeded: got 0 new tasks
18-Sep-2008 13:37:58 [rosetta@home] Sending scheduler request: To fetch work. Requesting 106150 seconds of work, reporting 0 completed tasks
18-Sep-2008 13:38:03 [rosetta@home] Scheduler request succeeded: got 0 new tasks

---

A little similar to the above problem: I'm getting this message constantly this morning (my time zone), but everything on the Rosetta pages is saying that I should be getting work.

10/31/2008 11:27:45|rosetta@home|Requesting 110583 seconds of new work
10/31/2008 11:27:51|rosetta@home|Scheduler RPC succeeded [server version 601]
10/31/2008 11:27:51|rosetta@home|Deferring communication for 1 min 41 sec
10/31/2008 11:27:51|rosetta@home|Reason: no work from project

The deferring communication amount increases with each failed attempt, which I've seen before and expect. But why there's no work from project is beyond my understanding. Help!

---

My guess would be that it has to do with the client they just started to use:
Rosetta Mini with new score terms which must have caused numerous compute
errors. 17 just on my 'puters.