this is more of a comment than a question, I have commited my two computers to work 100% of the time on seti and other projects from BOINC. Sometimes I do not turn on my computers 3 or 4 days. because I am away from home. Still if I have been given tasks for my computers to complete what is the big deal if I do not get credits for late completions. WHAT IT MATTERS IS THAT THE TASKS GET PROCESSED, RIGHT? AM I RIGHT OR WRONG? SO PLEASE IF I AM OVERDUE DO NOT TELL ME TO DELETE THE OVERDUE PROJECTS. IT IS BETTER TO COMPLETE THE LATE TASKS FOR COMPUTING. OR AM I MISSING SOMETHING? THIS RACE OF WHAT TEAM GETS TOPS CREDITS IS MAKING THE ENTIRE PROGRAM LOOSE SIGHT OF WHAT REALLY MATTERS.

JAIME

(LICEO)

---

this is more of a comment than a question, I have commited my two computers to work 100% of the time on seti and other projects from BOINC. Sometimes I do not turn on my computers 3 or 4 days. because I am away from home. Still if I have been given tasks for my computers to complete what is the big deal if I do not get credits for late completions. WHAT IT MATTERS IS THAT THE TASKS GET PROCESSED, RIGHT? AM I RIGHT OR WRONG? SO PLEASE IF I AM OVERDUE DO NOT TELL ME TO DELETE THE OVERDUE PROJECTS. IT IS BETTER TO COMPLETE THE LATE TASKS FOR COMPUTING. OR AM I MISSING SOMETHING? THIS RACE OF WHAT TEAM GETS TOPS CREDITS IS MAKING THE ENTIRE PROGRAM LOOSE SIGHT OF WHAT REALLY MATTERS.

JAIME

(LICEO)

Stop shouting.

And - sorry to break your bubble, but it's stats and competition that brings the majority of PC power to these projects.

---

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)

You can't compare seti and Rosetta.

The WUs that you crunch for seti, have a longer lifecycle. If you encrypt now a message of 1 day ago, and discover a possible sign of life in space, or you do this within 1 month, it doesn't matter.

The results of your crunching for Rosetta will have impact on next targets. So the sooner you deliver a results, the better. If you hand in a result of 1 month ago, they can't do anything with it anymore.

That's the reason

---

Member of Dutch Power Cows

I'm not sure if Rosetta does this, but I think I read on one of the Einstein boards that they will still acceopt WUs that are up to two weeks late. For Rosetta though, if they do it is probably just a few days, if that, for the reasons you mention.

Keep crunching!

---

(Click for detailed stats)

I'm sure they keep accepting late results even for Rosetta. During CASP if you didn't return it quickly, it'd not make the deadline for submissions. However even if it came late, they could still use it for internal testing. Keep in mind that while doing CASP is good publicity and gives Dr Baker and his team a chance to beat other research groups it's not actually getting any 'new' research done.

I really don't think they're deleting old results - storage space is incredibly cheap and you never know when you may want to look at how an older algorithm performed.


If you want the credits though, just cancel the timed out work units (if you haven't started them) - given that the approaches are random, the next WU is just as likely to score a good result.

---

Anguns I am not shouting. I made an observation. You may or may not be right, but you are entitled to your opinion, THE SAME WAY I AM TO MINE, GOT IT???. I do not need stats as you call it to volunteer, Maybe you do, right?

Jaime

---

And to those who gave good a valid reasons, thanks. Maybe because of my work and the need sometimes to be away from home 3 or 4 days in a row it may be better to detach ROSETA and pick another project, Thanks for the valid explanation,
Jaime

---

writing in allcaps is considered shouting :)
and if you are away from home often you should not run 1 day WUs if you ask me.

hi liceo

as doc suggests - reducing the WU duration should help you on that front(?)

Danny

---

Another option would be to leave your computers running while you're away. I can see how not everyone may be comfortable with it, but if something would go wrong (like to processor getting too hot), the computer shuts down automatically.

---

Is there an option to cancel automatically overdue tasks? I don't want to interact that much with Boinc (but I love it. ^^); just keep it running and want to get credit for calculated workunits. So, my computer should never be overcommitted! When it is overcommitted I won't get credit. :(

Any answers? Any command-line option for this request?

PS: *sorry* liceo, Angus is right. :), but I rated your post with "+".

Is there an option to cancel automatically overdue tasks? I don't want to interact that much with Boinc (but I love it. ^^); just keep it running and want to get credit for calculated workunits. So, my computer should never be overcommitted! When it is overcommitted I won't get credit. :(

Any answers? Any command-line option for this request?

PS: *sorry* liceo, Angus is right. :), but I rated your post with "+".

There's nothing available to do that at the moment unfortunately. I believe it's a BOINC requirement (rather than a Rosetta one) - I've requested a purge function on the BOINC boards, and on Rom Walton's blog, and I know FC has too. Maybe you could give the suggestion a bump over there on the BOINC forum ;D

---

lieco,

There is a easier solution to all this.

If you know what dates your going to be gone in advance, then about 1-2 before you have to leave, tell rosetta server you are not accepting any new work and let the work units you have already run their course.

When they are done and reported/uploaded then take your system offline from rosetta until you get back. Then reconnect for the duration of your home stay until your next departure date.

If you get called away on emergency you can always cancel the work units that will not fit into the time frame you are home.

---

If you get called away on emergency you can always cancel the work units that will not fit into the time frame you are home.

It is worth saying how to do this.

First set "No new work" otherwise the client will try to download new work to replace the stuff you are cancelling.

Abort each of the tasks that have not started, by highlighting in the tasks window and clicking abort. They will then initially show as "aborted by user, 0% complete". Strangely enough, they need to run for a few seconds/couple of minutes each in order to tidy themselves up - let them do this by suspending all the tasks that have not been aborted, and wait till all the aborted tasks show 100% complete. Then resume the other tasks.

The above advice applies to all projects, and is particularly important on the majority of projects where 'redundancy' is used - aborting and reporting means that the project knows right away that it needs to find another host to crunch that work, instead of waiting for the deadline.

Second - and this is a feature special to Rosetta, you can truncate the running of tasks that have already started. Go to the Rosetta website, account -> Rosetta prefs and select a 1 hour target cpu time.

Update Rosetta from the project window - this will report the aborted tasks (provided you made sure they are all at 100%), and will set the running Rosetta tasks to stop as soon as they next checkpoint.

Leave them running and they will complete soon.

If you are *really* in a hurry and are happy to lose any work since the last checkpoint, then after doing that update, stop BOINC, restart BOINC, and all those tasks will start to upload within a few minutes.

All in all, if you have ten minutes notice of needing to turn off the box, you should lose no more than one hour's crunching per box. If you have an hour or so's notice, you should lose nothing.

HTH

PS - when you get back, don't forget to sett "Allow noew work" and don't forget to set your target cpu runtime back how it was!

River~~

---

To add to River's comments... once you're back to normal... don't just rush to set back your WU runtime preference, because now BOINC has gotten used to WUs being done in an hour. If you snap it back to 12 hrs or whereever you had it previously, now it's going to try and get too much work. See caution described here.

---

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/

That's pretty close to what I had in mind, however I was saying just click on no new tasks and let Rosetta finish out what is on your machine already. Then shut down. That is what I did before I left on vacation. So if you know when your going to leave then say the day before you have to leave click on no new tasks and let them run out. Then you can get credit for those tasks as well as complete the work load you have on your system and have those results added to the finished work back at Baker lab.

When you get back you can resume and the scheduler will send new work according to your selections on how much time should be spent per WU that were already in place on your account before you left.

However if you get a real emergency and have little time left then you should follow what the other guys said.

---