"So if it is at all possible for you to increase your rosetta@home cpu time for the next two weeks please do--it will make a huge difference for our collective efforts"

Does he want WU total processing time upping (I run 4 hrs per WU at present but don't mind if it needs to be + 8 hrs), or just more CPU power (like adding an Opty 170 I've got lying around) ?

Cheers for any clarifiaction.

---

He means more resource share for rosetta, suspending other BOINC projects for two weeks and running rosetta@home 24 hours per day if you have been running less lately.

---

list of my results

"So if it is at all possible for you to increase your rosetta@home cpu time for the next two weeks please do--it will make a huge difference for our collective efforts"

Does he want WU total processing time upping (I run 4 hrs per WU at present but don't mind if it needs to be + 8 hrs), or just more CPU power (like adding an Opty 170 I've got lying around) ?

Cheers for any clarifiaction.

i wanted to ask the same question. more time or more cpus?

---

He means more resource share for rosetta, suspending other BOINC projects for two weeks and running rosetta@home 24 hours per day if you have been running less lately.

Jolly good, All but one machines doing Rosetta 24X4 anyway, the other one does a mixture of Rosetta and RALPH so I've suspended RALPH for the time being.

Cheers

---

my question hasn't really been answered. do i have to increase the WU time or just let it as it is (I'm running only rosetta, no other projects at the moment anyway).

---

my question hasn't really been answered. do i have to increase the WU time or just let it as it is (I'm running only rosetta, no other projects at the moment anyway).

Increasing the WU time will only decrease the bandwidth used by you and the Rosetta server. So if you're only running Rosetta, and your current WU time is working for you - then leave it as it is.

Feel free to add more CPUs/Systems to Rosetta, or run the systems you have for more hours each day (if they're not running 24/7).

---

thanks, i'll add another 24h/24h computer tonight

---

"So if it is at all possible for you to increase your rosetta@home cpu time for the next two weeks please do--it will make a huge difference for our collective efforts"

Does he want WU total processing time upping (I run 4 hrs per WU at present but don't mind if it needs to be + 8 hrs), or just more CPU power (like adding an Opty 170 I've got lying around) ?

Cheers for any clarifiaction.

Done. I saw a post on SETI boards about it...

---

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

Team-SciFi has answered Dr. Baker's plea for more power :)

---

The Liver is EVIL. It must be PUNISHED!

Team-SciFi

Yes, what he wants is more hours per day by more machines crunching. Length per WU is not at issue. One WU for 24hrs, 8 WUs for 3... the plea is to get 24hrs of crunching to Rosetta. If you can add a machine, do so. If you can leave your machine on for more hours per day, do so. If you can suspend other projects temporarily, do so. Climate projects won't even notice you missing for a week or two. Just suspend it, and resume after CASP. For other projects with shorter deadlines, select "no new tasks" from the projects tab of BOINC Manager.

In my case, I'd already suspended my climate WUs a couple of weeks ago. I let them run for a few hours about twice a week so they can report a trickle up message, then I suspend them again. My home PC crashed last week, and now this week we have record high temps, so I've had to cut back on one PC. Hope to see cooler temps next week and resume 24hr crunching.

---

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/

Cache is empty. Full power Captain!

---

(oops - response had already been posted) Nevermind!

---

Team Starfire World BOINC

So far the teraflop estimate seems to be hovering between 39 and 40. Two Saturdays ago, it jumped to 46 and I thought WOW! But that Sunday it dropped to 37. If teams are responding to Dr. Baker's request then shouldn't we see a substantial jump in this estimate?

---

So far the teraflop estimate seems to be hovering between 39 and 40. Two Saturdays ago, it jumped to 46 and I thought WOW! But that Sunday it dropped to 37. If teams are responding to Dr. Baker's request then shouldn't we see a substantial jump in this estimate?

Yes, you should but for many (like me) it'll take time for my other projects to run out of work. Then time to run my 24 rosie wus, and then to be credited.

I do apologize then. Good luck to you and all getting your ques cleared. maybe by Wednesday we'll be firing on all eight!

---

Yes, you should but for many (like me) it'll take time for my other projects to run out of work. Then time to run my 24 rosie wus, and then to be credited.

That's what the <NO NEW WORK> & <RESET PROJECT> buttons are for on your BOINC Manager. Trash that other stuff - someone will crunch it later.

Let's get some competitive spirit here!

---

Proudly Banned from Predictator@Home and now Cosmology@home as well. Added SETI to the list today. Temporary ban only - so need to work harder :)



"You can't fix stupid" (Ron White)

...the teraflop estimate...jumped to 46

Keith, it is just an estimate. It is basically based on the amount of work returned on a given day. Several of the large teams have "purge days". One day a week when they report all of their week's work at the same time. Apparently they like to see the little blip on the graph and say "that was US!". So, what you are sometimes seeing is work that has been crunching all week and then reported all on one day. So they are basically pushing the TFLOP measure for their work all in to one day of the week.

As for Angus' comments about resetting projects... noone actually suggested that. This can be disruptive to other projects, and if you are a climate cruncher, could throw away several months of work. But yes, borrow if you can do so without disrupting other projects. Pay them back after CASP, ET and pulsars and such will still be there to be discovered in 3 weeks.

---

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/

If a UW that's due on say Wednesday and it's lumped in with a batch that a team will return say Friday then isn't there a missed deadline for the Wednesday UW?

The reason I say this is that during CASP7 the deadlines are reduced to one week and these UW's are due on various days during a given week.

Just curious.

---

You can set your General Preference to tell BOINC you only connect to network every 7 days, download up to 99 WUs in a single day, they'll all be due 7 days hence, suspend network access, then crunch 'em and report 'em and abort any excess that would miss the deadline away.

...but yes, you're right, and that's part of why some objected to the change from 14 down to 7 day deadlines :)

---

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/

Have you (i.e. the people on server side) ever have thought about a 2 stage deadline?

If the scheduler would tell the client that the deadline is 7 days but tell the database that the deadline is 8 days, the client side would still try its best to finish within 7 days.

If for some reason the client goes into panic mode a little too late, there would still be one day left, a 12,5% tolerance period, where the server would accept an overdue result.

I have quite a small cache so this szenario will not happen to me under normal circumstances but I know that some people have been only a very short time behind the deadline and the server didn't accept the result anymore.