Perhaps. But I think all projects should show the larger figure (or both) on the server status page. What the users want to know is how much work is left to come. Most projects don't even list the larger figure anywhere, at least Rosetta puts it on the homepage.

Or they could put both. You're probably right.

It returns more decoys and I think that makes a difference.
I'm not sure what the best setting is either - I'm just eking out the tasks and returning more data while there's a current shortage, which now seems to be solved.
I'll keep it at 12hrs until Sunday, just to make sure the current supply isn't only temporary, then I'll switch back to the default 8hrs.

If they don't need those extra decoys, you're wasting CPU time. Probably better using it for another similar project.

If they do need the extra decoys, they would have set the 8 hours higher themselves.

I think it's entirely about decoys in terms of the results they get. Slower machines do fewer, faster machines do more.
The impression I've always had about runtime is that it's about managing pressure on the server within the deadlines.
But that's also dependent on the supply of tasks. When there are so few about (and the queue has never quite reached a million) increasing runtime means I stockpile fewer and more people get a share. I still think it's a good idea for everyone until a sizeable queue reliably returns. It only takes a second to tweak and there's no downside, only an upside for continuity.

I haven't limited my tasks only to Open Pandemics. I don't see any of their projects as any less important - probably the other parts of the project need some extra attention while everyone else is focussing on CV19 for the more obvious reasons.

It probably evens out actually. Anyone (probably quite a lot of people) with their settings on the default of "take anything that's there" will get whatever others don't select. So people saying "I'm only doing Coronavirus (I refuse to use the technical name) work" aren't actually making it happen faster, because they "do anything" users just end up getting less of it as they've taken WUs out of the queue.

It may well do, but I have seen a lot of the newer people saying they'll only run CV19 tasks and they'll move on if they aren't being supplied any more.
Personally, my priority after CV19 is all the other Rosetta tasks and the same goes at WCG, which makes everything a whole lot easier for me.
I don't think a lot of the vast majority of Boinc projects, if the truth be told. The demise of Seti is the best Boinc news I've had all year, even if no other project was able to do any CV19 tasks at all!

I'm hardly here for my popularity, that's for sure.

---

Why did you say that "The demise of Seti is the best Boinc news I've had all year, even if no other project was able to do any CV19 tasks at all?"

Steven Gaber
Oldsmar, FL

Why did you say that "The demise of Seti is the best Boinc news I've had all year, even if no other project was able to do any CV19 tasks at all?"

Steven Gaber
Oldsmar, FL

Why did you say that "The demise of Seti is the best Boinc news I've had all year, even if no other project was able to do any CV19 tasks at all?"

Someone will be along to correct me, but the project never found anything in its entire existence, then when it ran out of tasks, sent them all out again so they could fail to find anything a second time.

I say 'never found anything' but aiui it didn't even look at most results and that's basically why it's now shut down.

A complete fraud on the Boinc community, when many people were willing to donate considerable processing time at considerable expense and were convinced to waste all of it on precisely nothing.

I know the Boinc platform itself benefitted from the existence of Seti, but that was an incidental by-product.

If we agreed to pretend it never existed, that would be an even better outcome.

---

Someone will be along to correct me

No point.
You have your beliefs, which aren't going to be impacted by any facts. So providing them would be a waste of time & effort, the totally inaccurate statement below is a perfect example of that.

I know the Boinc platform itself benefitted from the existence of Seti, but that was an incidental by-product.

---

Grant
Darwin NT

Someone will be along to correct me, but the project never found anything in its entire existence, then when it ran out of tasks, sent them all out again so they could fail to find anything a second time. I say 'never found anything' but aiui it didn't even look at most results and that's basically why it's now shut down.

Simply, you're completely wrong.
This is a little part of scientific effort of Seti@Home (instrumentations, pulsars, CMBR, etc). And works on data continue.

---

no work available to process, are we down , rosetta@home , kn4mwd
11/1/2020 9:38:51 AM | Rosetta@home | Scheduler request completed: got 0 new tasks

Same here, no rosetta work units. This stared about 3 days ago. I have 2 computers that share work between rosetta and world community grid and all of a sudden all rosetta work was no longer available. IF anyone has an answer for me , please help.
Thanks
JAKE.

Since you are using your GPU, you should reserve a CPU core to support each running GPU WU in order to avoid any impact on GPU work with the CPU trying to use all CPU cores and threads for CPU work as well as supporting the GPU.

Actually that's no longer required, and I've tested it with several machines on 3 projects. GPU work has the CPU part at a higher priority in the OS, so it takes over the CPU core when needed, slowing down the CPU-only WU. You're best getting Boinc to use all the cores, then everything is always maxed out.

---

Same here, no rosetta work units. This stared about 3 days ago. I have 2 computers that share work between rosetta and world community grid and all of a sudden all rosetta work was no longer available. IF anyone has an answer for me , please help.
Thanks
JAKE.

Patience is a virtue. We're here to help them, they're not here to keep us busy. As you've got WCG to do, no problem.

---

It may well do, but I have seen a lot of the newer people saying they'll only run CV19 tasks and they'll move on if they aren't being supplied any more.
Personally, my priority after CV19 is all the other Rosetta tasks and the same goes at WCG, which makes everything a whole lot easier for me.
I don't think a lot of the vast majority of Boinc projects, if the truth be told. The demise of Seti is the best Boinc news I've had all year, even if no other project was able to do any CV19 tasks at all!

I'm hardly here for my popularity, that's for sure.

I've actually set WCG to do anything but coronavirus tasks. 9 million cancer deaths a year vs. 2 million coronavirus a year. Guess which one I put the crunching time into? You can avoid a virus, and it will peter out eventually, but cancer is here to stay, is unavoidable, and needs sorted.

---

Thank you.
I had checked that the store on the phone still only supported BOINC v7.4.53 (last updated 3 Jul 2016),
and browsing to the BOINC site from the phone detected the Android device type but also only offered 7.4.53.
So if the phone doesn't have a solution, and there seems no easy way to return completed units meanwhile, is it best to suspend the project to avoid wasting new downloads,
or to do nothing and expect the project to automatically not send new work until BOINC has been updated to a suitable version for the device?

The latest version for Android is 7.16.3. The store is out of date, you need to download manually from Boinc website at the bottom of this page.

---

well got work to do finaly , about 3 hours ago kn4mwd

Someone will be along to correct me, but the project never found anything in its entire existence, then when it ran out of tasks, sent them all out again so they could fail to find anything a second time. I say 'never found anything' but aiui it didn't even look at most results and that's basically why it's now shut down.

Simply, you're completely wrong.
This is a little part of scientific effort of Seti@Home (instrumentations, pulsars, CMBR, etc). And works on data continue.

Thanks for the links. I read the most recent half dozen. Have you?
They're really embarrassing. Please, force yourself to read them (they're turgid at best)

Nothing at all has been found, has it.

When you wrote "Simply, you're completely wrong" you meant to say completely right.
I'm not sure I even appreciated how right. There's nothing even close to anything at all. Just... nothing.

Blimey... I guess you really can fool all the people all the time.

---

Someone will be along to correct me

No point.
You have your beliefs, which aren't going to be impacted by any facts.

I don't have any beliefs. I'd have at least thought the purpose of the project was to remove the need for beliefs by finding something - or even close to something.
Pick the very best link of all. I promise to read every word.
Because by saying "no point" it doesn't make me think there's anything. It makes me think you already know there literally is nothing.

---

It may well do, but I have seen a lot of the newer people saying they'll only run CV19 tasks and they'll move on if they aren't being supplied any more.
Personally, my priority after CV19 is all the other Rosetta tasks and the same goes at WCG, which makes everything a whole lot easier for me.

I've actually set WCG to do anything but coronavirus tasks. 9 million cancer deaths a year vs. 2 million coronavirus a year. Guess which one I put the crunching time into?
You can avoid a virus, and it will peter out eventually, but cancer is here to stay, is unavoidable, and needs sorted.

Understandable and I don't disagree, just that I'm doing all of them as they come.
They don't have any bad sub-projects, so I'm happy to contribute time to any and all of them.
It's the ideal co-project for Rosetta imo as some of them use Rosetta code aiui

---

well got work to do finaly , about 3 hours ago kn4mwd

I'm inclined to think these are timed out tasks that never ran and are just being reissued.
I can't detect any new tasks unfortunately. Especially not for me.
137k tasks out there, but only 70k completed in the last 24hrs in the most recent info.
I'm guessing most of those 137k will get timed out and reissued as well, and that's only enough for a quarter of a day of work.

---

Since you are using your GPU, you should reserve a CPU core to support each running GPU WU in order to avoid any impact on GPU work with the CPU trying to use all CPU cores and threads for CPU work as well as supporting the GPU.

Actually that's no longer required, and I've tested it with several machines on 3 projects. GPU work has the CPU part at a higher priority in the OS, so it takes over the CPU core when needed, slowing down the CPU-only WU. You're best getting Boinc to use all the cores, then everything is always maxed out.

It depends on the gpu, some do and some don't....you are correct it's not a blanket AWLAYS do it thing, it's much more of a case by case basis due to the better gpu's than we used even 3 years ago. It's best to leave one cpu core free and track your numbers, then use the cpu core for ie crunching and see what the numbers are.

Personally I always leave at least one cpu core free because I remote into most of my pc's to manage them and when using every cpu core for crunching the delay is horrible. The gpu benefitting from that is just an offshoot.

I am not getting any work for Rosetta is there an outage?

I am not getting any work for Rosetta is there an outage?