FluffyChicken:
A few obscene posts have been deleted. You'll note there are limits to the no-mods announcement. And a common obscene joke is still obscene.

Please email me/us at the contact email address for further explanation.

---

Rosetta Moderator: Mod.Tymbrimi
ROSETTA@home FAQ
Moderator Contact

Mods, you can remove this bit now.




I don't know but I think a lot of the other posts have been answered, probably also want to clean them.

---

Team mauisun.org

There are Validate errors on Ralph 5.26

http://ralph.bakerlab.org/forum_thread.php?id=253

Anders n

---

Anders n

Please report this on the Ralph boards in this thread.

---

Rosetta Moderator: Mod.Sense

Anders n

Please report this on the Ralph boards in this thread.

Allready done that.

But sins the first error reports was early this morning

and no admin had answerd, I hoped you could e-mail the admins

to check it out.

Anders n

---

The project team is in Seattle. The first post to that thread was about 11PM Seattle time. It is now 8AM Seattle time and I'm sure they're already looking in to the validation issues.

---

Rosetta Moderator: Mod.Sense

2 Nemesis, I see you were unable to revise your signiture line in an acceptable mannar. I am sending a recommending to the project team to revoke your user ID.

What is unacceptable now?

The Dog :)

You need to get you a better looking dog. :)

---

This and no other is the root from which a Tyrant springs; when he first appears he is a protector.”
Plato

2 Nemesis, I see you were unable to revise your signiture line in an acceptable mannar. I am sending a recommending to the project team to revoke your user ID.

What is unacceptable now?

The Dog :)

You need to get you a better looking dog. :)

Everyone has a bad hair day now and then! :)

We'd been out cruising Alki Beach in the convertible - hence the "Doggles".

---

Nemesis n. A righteous infliction of retribution manifested by an appropriate agent.

Sorry, this is not a reply to the message.
I get the error message that my computer is over comitted. Therefore I believe I need to remove a project from GridRepublic/BOINC. After consideration, I decided to 'give Rosetta the axe'.
The DETACH tab is 'blanked' and (of course) does not respond. How can I work around this to remove ROSETTA from my projects?
Thanks, Pete

---

none at this time

Sorry, this is not a reply to the message.
I get the error message that my computer is over comitted. Therefore I believe I need to remove a project from GridRepublic/BOINC. After consideration, I decided to 'give Rosetta the axe'.
The DETACH tab is 'blanked' and (of course) does not respond. How can I work around this to remove ROSETTA from my projects?
Thanks, Pete

There's been a few discussions about projects being labeled as overcommitted in the Number Crunching forum. Before disconnecting from Rosetta, you might want to ask about the over committed status in the Number Crunching forum. They can help identify if it's a Boinc 5.4.11 issue, having a project on your list that hasn't had any work for weeks, etc. Or identify settings you may need to change so you manage to finish more Rosetta WUs without errors.

To stop work being downloaded for a project, you can do what I did to Ralph. Change it to "no new work" status.

---

Rosetta Moderator: Mod.Tymbrimi
ROSETTA@home FAQ
Moderator Contact

Sorry, this is not a reply to the message.
I get the error message that my computer is over comitted. Therefore I believe I need to remove a project from GridRepublic/BOINC. After consideration, I decided to 'give Rosetta the axe'.
The DETACH tab is 'blanked' and (of course) does not respond. How can I work around this to remove ROSETTA from my projects?
Thanks, Pete

Since you are attached to GridRepublic you loose that sort of control at the client end. You need to goto GridRepublic and detach there.
NOTE: If you did detach, like you could in the older versions of BOINC while using GridRepublic or BAM, you would just be reattached automatically since GR/BAM would think you want to be attahced.

I just had a quick look at your stats (o get the project you are in)
http://www.boincstats.com/stats/boinc_user_graph.php?pr=bo&id=d7fac1a81f2b95dc11e50051beb688a1
Seems you only started 3 days ago and have joined lots of projects. That what is probably causing the over commitment.
I would delete all tasks but the CPDN one that you have. BOINC should then only get what it can cope with. The problem usually comes because when you start out BOINC get enough jobs from the first project, then attached to another get more and so on everytime you add another project. At lesat I think this bug is still present. But you don't actually need to detach from any, just let boinc sort itself out (though deleting helps this process speed up)

---

Team mauisun.org

...The problem usually comes because when you start out BOINC get enough jobs from the first project, then attached to another get more and so on everytime you add another project. At lesat I think this bug is still present.

Not sure there is any bug. It's just that you are moving the target that BOINC is trying to hit. That of getting ENOUGH work, without too much. If that climate work unit now suddenly only has 10% of the CPU time... it's going to take a bit longer then originally estimated to complete.

I just wanted to point out that "overcommitted" does not in any way mean that your machine is having a problem, nor that it is working too hard or anything. I simply means that you presently have more work then BOINC predicts you can handle, based upon it's past experience with how many hours per day your machine tends to be on, and etc.

...and the term overcommitted is in relation to ALL of the projects you are crunching, and has nothing specific to do with Rosetta... although it is certainly possible to see the message when only crunching Rosetta as well. BOINC just wants to crunch through and complete the work you have, before downloading more. That's really all it is trying to tell you. It's trying to tell you that you already have plenty of work for now, and so that is why it won't be requesting anymore when you update to the projects.

---

Add this signature to your EMail:
Running Microsoft's "System Idle Process" will never help cure cancer, AIDS nor Alzheimer's. But running Rosetta@home just might!
https://boinc.bakerlab.org/rosetta/

...The problem usually comes because when you start out BOINC get enough jobs from the first project, then attached to another get more and so on everytime you add another project. At lesat I think this bug is still present.

Not sure there is any bug. It's just that you are moving the target that BOINC is trying to hit. That of getting ENOUGH work, without too much. If that climate work unit now suddenly only has 10% of the CPU time... it's going to take a bit longer then originally estimated to complete.

I just wanted to point out that "overcommitted" does not in any way mean that your machine is having a problem, nor that it is working too hard or anything. I simply means that you presently have more work then BOINC predicts you can handle, based upon it's past experience with how many hours per day your machine tends to be on, and etc.

...and the term overcommitted is in relation to ALL of the projects you are crunching, and has nothing specific to do with Rosetta... although it is certainly possible to see the message when only crunching Rosetta as well. BOINC just wants to crunch through and complete the work you have, before downloading more. That's really all it is trying to tell you. It's trying to tell you that you already have plenty of work for now, and so that is why it won't be requesting anymore when you update to the projects.

I is a bug, since BOINC should not download more than it can handle (fixed in 5.6.? maybe I cannot remember but they did some playing around with it, mmciastro may remember). BOINC is designed not to miss a deadline even if it runs out of work because of it's decision.

---

Team mauisun.org

Maybe time to update this page.

https://boinc.bakerlab.org/rosetta/forum_thread.php?id=669#11192

Anders n

---

This thread should be sticky.

https://boinc.bakerlab.org/rosetta/forum_thread.php?id=1589

Please.

Anders n

---

This thread should be sticky.

Anders, we try to make as few threads as possible sticky to keep the first board clear for active dicussion. The thread was just updated to reflect the current versions of Rosetta. But it wasn't sticky in the past.

Do you agree that because it is referenced in the project information index, which IS sticky on all three forum boards, that is sufficient to find it?

In the future, I also plan to post a link with the announcement in the Version release log.

---

Rosetta Moderator: Mod.Sense

Mods could you get the project devs to look into this post
https://boinc.bakerlab.org/rosetta/forum_thread.php?id=2617

It's showing 5 member with and without credit, except they have 8 members who have all returned creit...

---

Team mauisun.org

I don't know if this is the right place to post this, but.....

Something seems to be amiss on my end. I haven't gotten any new work units for a couple of weeks, and am wondering what went wrong.

I have tried resetting, have detachedd and re-attached to the project but these actions didn't seem to help. Any suggestions?


edit: Found the problem, was another project I had running that had literally taken over the boinc manager. Now have new work units DLed and running.

---

I don't know if this is the right place to post this, but.....

Something seems to be amiss on my end. I haven't gotten any new work units for a couple of weeks, and am wondering what went wrong.

I have tried resetting, have detachedd and re-attached to the project but these actions didn't seem to help. Any suggestions?

Are you BOINCing any other projects? If you have more than two projects on a machine[1], it may be simply that those projects "beats" Rosetta to the "get next project".

I've found mixing two projects on each machine will work better than having three or four projects on one machine.

I've seen posts that explain how to calculate how often the work should be fetched and how many projects you can combine, etc, etc - but it's all a bit difficult... Much simpler to choose one or two projects that you really like, and stick with them... [Most of my machines run only one project: Rosetta].

[1] Single processor machine - on multiprocessors there are more chances to get more work.

--
Mats

---

The only thing that I've found that seems to fix this is to go to

"rosetta@home"

then

"your account"
"preferences"
"rosetta@home preferences" (not the general preferences)

In this area your "resource share" is probably set to 100 (the most likely setting you might pick from when you set up the project- I'm not certain what it defaults to if you don't pick a value, though 100 would make sense). The documentation is kind of vague and it took me while to figure this out (right or wrong). I don't think this should be thought of as 100%: It is more of a priority (kind of like mainframe priorities or Unix nice-ing) - at least as I understand it. It's value might be 100, but that does not mean 100% of resources. Rather, you add the various projects' priorities together - whatever they are - then divide the sum, by the number of projects, for the mean. Projects above this value/point get timeslice priority above "average" or actually above lower projects regardless of the average. Essentially they seem to be asked "do you need attention" more often than the other projects. Note: If you use a default (or the same) value for everything the math will obviously work out to that value. This value might be equal across all projects at 100 (or whatever) but the vaguaries of the way the projects operate within BOINC evidently does not guarantee that they really get equal "functionality" out of BOINC. I WOULDN'T ACTUALLY DO THE MATH AT ALL - NO NEED- IF THE NUMBER IS HIGHER THE PROJECT GETS MORE ATTENTION. I don't think it works out lineal so no reasn to do the math. Just set Rosetta (or which ever project you are not getting response from) higher than the other projects you are running. To do this

click on the bottom at

"edit Rosetta@home prefernces"

edit the "resource share" field's value and input something like 150 or 200. It will take a few minutes to reflect the update, but it will then preferentially prioritize Rosetta. It still runs all the other projects you may have running for their full time slices - which is a different setting - but will now give Rosetta the priority it needs to get new work. It will come back to Rosetta more often so rosetta may end up getting more done (at the expense of others). If this happens you can always scale the Rosetta preference slowly back to as close to 100 as will permit new work to still come down.

In particular, I've noticed if you leave the default settings of 100 for everything, on some machines Rosetta has a hard time contending with Einstein@home. This completely fixed my allocation and timeslicing problems. I now run with Rossetta at 150 and Einstein and Seti both at 100. Eistein still completes more work than Rosetta does, but Rosetta always runs and gets work now.

Note: This does not result in an excessive "slew" or "swap-out" condition with wasted time unloading from memory. That evidently is a different setting. Each of my projects runns for their full 3 hours slice (I upped that too from the default 60? minutes) before swapping out.

I've tried to find other solutions before finding this and the only other thing I can think of is to make the

"target CPU time"

setting in a given project closer to the timeslice or the number of times a day it checks for new work -but I'm completely speculating there - this fixed my probelm so I haven't looked further.

hope this helps,

Jeff A


*********************** In response to ***************************
I don't know if this is the right place to post this, but.....

Something seems to be amiss on my end. I haven't gotten any new work units for a couple of weeks, and am wondering what went wrong.

I have tried resetting, have detachedd and re-attached to the project but these actions didn't seem to help. Any suggestions?[/quote]

Are you BOINCing any other projects? If you have more than two projects on a machine[1], it may be simply that those projects "beats" Rosetta to the "get next project".

I've found mixing two projects on each machine will work better than having three or four projects on one machine.

. . .

Mats

---