Looks like about 30000 tasks ready to download. Some of my hosts that were out of work have started to pick some up, and I’m guessing I’ll have work across the board by morning.

per these stats:
https://boinc.bakerlab.org/rosetta/

80,000. Once inactive machines check in, those will be gone in the blink of an eye - which means more tasks need to come, or we'll be back at square one.

---

I've been seeing a steady ~30000 for a while now since the tasks returned, which is typical when there isn't a task shortage.

I went and set up WCG as a backup project, so if the tasks disappear, my Rosetta boxes can smoothly pick up WCG units and crunch them. It's kind of annoying when the Rosetta work units come back, though, since BOINC will randomly suspend the WCG tasks once Rosetta ones return.

the stats on the front page is a more accurate display of the supply. Hence, 80,000 as of 3:00 UTC is the most accurate number. The page you see the near-30k, is a gage of when we're near a shortage if the timing is right - but the rosetta@home homepage lists the full supply of Workunits.

And suspending WCG tasks bc of the client could be due to the deadline differences and/or resource share.

---

The stats on the front page is a more accurate display of the supply. Hence, 80,000 as of 3:00 UTC is the most accurate number. The page you see the near-30k, is a gauge of when we're near a shortage if the timing is right - but the rosetta@home homepage lists the full supply of Workunits.

After half a day we've probably had 400k+ tasks come through and all of them have been grabbed to run and refill buffers.
Prior to the shortage, 600-750k were being completed each day, so we'll be hand-to-mouth for a while yet.
Hopefully everyone's got something to work on in the meantime

---

As of this morning (US Central time), looks like the well has run dry again.

I'd like to figure out a work share setup that would allow WCG tasks to run to completion when the Rosetta tasks come back. I've never liked the "suspend one to do another" approach - I'd rather have what's in the queue finish up regardless of which project it belongs to.

As of this morning (US Central time), looks like the well has run dry again.

I'd like to figure out a work share setup that would allow WCG tasks to run to completion when the Rosetta tasks come back. I've never liked the "suspend one to do another" approach - I'd rather have what's in the queue finish up regardless of which project it belongs to.

That probably won't be easy with the massively different task deadlines, one way to try is to change the resource share settings, ie set WCG at 70 and Rosetta at 7 so WCG has a 10 times larger daily credit advantage. You will have to play with the numbers to see if you can get it to work for you though.

As of this morning (US Central time), looks like the well has run dry again.

I'd like to figure out a work share setup that would allow WCG tasks to run to completion when the Rosetta tasks come back. I've never liked the "suspend one to do another" approach - I'd rather have what's in the queue finish up regardless of which project it belongs to.

That probably won't be easy with the massively different task deadlines, one way to try is to change the resource share settings, ie set WCG at 70 and Rosetta at 7 so WCG has a 10 times larger daily credit advantage. You will have to play with the numbers to see if you can get it to work for you though.

I’ve been using an app_config.xml to set 2 processes for Rosetta and no limit on WCG processes. It may not work long term, but on the short term I’m getting 2 Rosetta processes and 2 WCG processes on my raspberry pis when Rosetta has work, and 4 WCG processes when Rosetta has no work

CASP14, the prediction competition, is going on now. project team maybe busy with that.

https://www.predictioncenter.org/index.cgi

its all about the science.


f.

WCG seems unhappy about Ubuntu 20.04 Server on ARM64:

Message from server: This project doesn't support computers of type aarch64-unknown-linux-gnu

WCG seems unhappy about Ubuntu 20.04 Server on ARM64:

Message from server: This project doesn't support computers of type aarch64-unknown-linux-gnu

See here: https://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,42574

Maybe installing those libraries works.

Google new what to do :-)

https://www.worldcommunitygrid.org/forums/wcg/viewthread_thread,42424_offset,30

=>

in cc_options.xml:

<options>
<alt_platform>arm-unknown-linux-gnueabihf</alt_platform>
</options>

boinccmd --read_cc_config
boinccmd --project http://www.worldcommunitygrid.org update
sudo systemctl restart boinc-client

And my Pi4B with Ubuntu/64 is folding now for WCG

Edit: I also had to go to the WCG webpage and set the profile in the device manager to max. output. Before that the client kept suspending/running tasks.

I wonder if the shortage has anything to do with the July 4th competition set up by Redditors. Maybe people hoarding WUs in preparation for that.

Maybe they found something and are investigating

https://twitter.com/rosettaathome

=>

Rosetta@Home
@RosettaAtHome
·
11h
We have some BIG NEWS: Researchers @UWproteindesign
have succeeded in creating antiviral proteins that neutralize the new coronavirus in the lab. (These experimental drugs are being optimized for animal trials now)

THANK YOU for helping out!

Join in: https://boinc.bakerlab.org

As of this morning (US Central time), looks like the well has run dry again.

I'd like to figure out a work share setup that would allow WCG tasks to run to completion when the Rosetta tasks come back. I've never liked the "suspend one to do another" approach - I'd rather have what's in the queue finish up regardless of which project it belongs to.

There is an option in the BOINC computing preferences "Switch between tasks every xxx minutes"
If you increase this value BOINC will switch between project less often.
And if you increase it above average WU run time BOINC should switch between projects only after fully competing previous WU.

I have it set to 300 min (from default 60 min) and usually BOINC finish already started WUs from WCG before switching back to R@H.

And work share set to 100 for WCG (its a default value) and 200 for R@H.

alas - WUs return. We'll have to wait and see how long it lasts.

---

alas - WUs return. We'll have to wait and see how long it lasts.

Well, at least this isn't Climateprediction.net. WUs come and go, but it's usually pretty stable from my experience.