With three targets out already, is the hope to submit answers for all of them? Or are some targets focused on areas the Rosetta folks don't work on?

---

With three targets out already, is the hope to submit answers for all of them? Or are some targets focused on areas the Rosetta folks don't work on?

we are going to do all of them!

---

With three targets out already, is the hope to submit answers for all of them? Or are some targets focused on areas the Rosetta folks don't work on?

we are going to do all of them!

When this is all done, and Rosetta results are in that we all hope are monumentally successful, I hope the mechanisms and plans are already in place to ensure that maximum press coverage is afforded the project. Interviews all over the science websites, major media outlets like CNN, BBC, etc.

If the enthusiasm of the developers and scientists of this project is any indicator of the liklihood of success then capitalizing on that outcome will be extraordinarily easy.

ps Has the lab's cupboards been stocked with champagne yet? :-)

---

Founder of BOINC GROUP - Objectivists - Philosophically minded rational data crunchers.

Once a target is out... when is the deadline for getting the predictions? Some people have large caches, hence a specific work unit might not bubble to the top for over a week.

---

Once a target is out... when is the deadline for getting the predictions? Some people have large caches, hence a specific work unit might not bubble to the top for over a week.

Here is a chart from CASP. Generally it's a 3week deadline to submit your prediction back to them. They accept late submissions too, but if info. on the true structure should be leaked, they may not accept the late submissions.

---

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/

Once a target is out... when is the deadline for getting the predictions? Some people have large caches, hence a specific work unit might not bubble to the top for over a week.

Mike, I think the project can use the WU's "Report deadline" for this.

Btw, as I've written many times, I really can't understand why people would want to run large (>1 day) caches for Rosetta@home. Work is always available. Plus occasionally the project wants to cancel obsolete/buggy series of WUs, but they can only cancel those sitting on their own BOINC server.

Even some BIG (many 100s of PCs) corporate network, which wants to minimize traffic during workday, can just enable network connectivity during the night and still keep a 1-day cache.

What am I missing?

---

Best UFO Resources
Wikipedia R@h
How-To: Join Distributed Computing projects that benefit humanity

What am I missing?

I agree, R@H work flow and server availability makes it much less of a concern than for other projects.

People with Multiple projects that have less reliable server availability, a cache keeps you crunching through outages. There's only one cache setting, so the one you pick is used for all the projects, not just R@H.

Also, dial-up users. They have to physically sit down to the PC and use the internet. Perhaps they USUALLY do that daily... but they'd like to keep crunching, even if they miss a day. Or perhaps there happens to be a router failure during that short time each day you log on... again, insurance to keep you crunchin' even when Murphy strikes.

---

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/

Once a target is out... when is the deadline for getting the predictions? Some people have large caches, hence a specific work unit might not bubble to the top for over a week.

The Earliest Deadline First (EDF) mode of BOINC should handle this. If you are going to run large queues, then you just have to live with the possibility that at times your systems will be pushed into EDF mode. Frequently projects are blamed for this, but the truth is it is a management decision made by the users for their systems.

However, one place you might get into trouble, is if you load up a large queue and then reset your time preferences to a longer period of time. While the system will still eventually go into EDF mode, it may do so too late to finish the work.

Rather than run larger queues, the preferred approach would be to run a small queue, with a longer time setting. Once your system adjusts to the situation, you will generally have lower network traffic, and fewer work units to deal with if something goes wrong. Eventually you will be able to run a single workunit for up to 4 days (CPU time). It is important to have your time between connections set to a low value when doing this in part to set the smaller queue, but also to have the system check in frequently in case it should be ready to connect. That way when you connect it will be ready to do so. BOINC may complain about not have the network available when it tries to connect, but it will keep working.

---

Moderator9
ROSETTA@home FAQ
Moderator Contact

I am trying hard to keep it running :D but it is still running first target

---