I don't have a serious problem with it, if this project "take a break". It's not a problem for me to find something else to do. I'm running Folding@Home now - and not permanently. I will be back.

But I just think it would be nice to get some info about what is happening - or not happening. And why. Just something. Anything.

It would not take many minutes. Please?

I don't have a serious problem with it, if this project "take a break". It's not a problem for me to find something else to do. I'm running Folding@Home now - and not permanently. I will be back.

But I just think it would be nice to get some info about what is happening - or not happening. And why. Just something. Anything.

It would not take many minutes. Please?

Well TN-Grid and World Community Grid both have research work for Covid as a suggestion.

Bill F

---

In October 1969 I took an oath to support and defend the Constitution of the United States against all enemies, foreign and domestic;
There was no expiration date.

Now a larger number of tasks are going out.

Tasks ready to send: 24498
Tasks in progress: 70966

A few hours ago tasks ready to send was zero. It looks like they have fixed whatever the issue was.

---

Well TN-Grid and World Community Grid both have research work for Covid as a suggestion.

Bill F

Also SiDock@home.

https://www.sidock.si/sidock


It looks like most of the jobs shown as queued on the Rosetta@home page are not at a point where the server programs can convert them to tasks ready to send without some human doing some step first - for example, creating one of the input files.

Now a larger number of tasks are going out.

Tasks ready to send: 24498
Tasks in progress: 70966

A few hours ago tasks ready to send was zero. It looks like they have fixed whatever the issue was

You beat me to it. Very surprised.
No idea how long it will last - hopefully sufficient for everyone to get something - fingers crossed.
Grabbed 1 task per core, then found I'm chock-full of WCG tasks so buffer already full <sigh>

---

I had to restart my client for the work to download

I had to restart my client for the work to download

Selecting the project, then Update clears any backoff timers that are delaying contact with a project.

---

Grant
Darwin NT

After a period of receiving no tasks, clients will back off for up to 1½ days before trying again to request more. So it could take a while for unattended machines to notice that work is available again.

I don't have a serious problem with it, if this project "take a break". It's not a problem for me to find something else to do. I'm running Folding@Home now - and not permanently. I will be back.

But I just think it would be nice to get some info about what is happening - or not happening. And why. Just something. Anything.

It would not take many minutes. Please?

Yep, agreed, doesn't take long to post a few lines. Even if it's something as basic as e.g "server's down and we can't connect remotely ,won't be able to fix it until we go in on Monday".

---

Team AnandTech - SETI@H, Muon1 DPAD, F@H, MW@H, A@H, LHC@H, POGS, R@H, DHEP, CPDN

Main - Ryzen 5 3600, TR Ultima90, MSI B450, 32GB DDR4 3200, RX580 8GB, Seasonic Prime PX-550
2nd - i7 4930k @4.1GHz, TR Ultra120 E, 16GB DDR3 1866, HD7870 XT 3GB(DS

You beat me to it. Very surprised.
No idea how long it will last - hopefully sufficient for everyone to get something - fingers crossed.
Grabbed 1 task per core, then found I'm chock-full of WCG tasks so buffer already full <sigh>

Well, the number of tasks ready to send seems to be increasing despite people downloading them (tasks in progress has gone way up) so it's looking good so far.

---

You beat me to it. Very surprised.
No idea how long it will last - hopefully sufficient for everyone to get something - fingers crossed.
Grabbed 1 task per core, then found I'm chock-full of WCG tasks so buffer already full <sigh>

Well, the number of tasks ready to send seems to be increasing despite people downloading them (tasks in progress has gone way up) so it's looking good so far.

452k in progress - pretty much everyone will be stocked up now.
I'm still easing quite a few WCG tasks through to make space for more Rosetta to come down so it'll be a few more days before I get a full buffer. Then my resource share needs to get rebalanced, so I'll be solid on work here right through January, all being well

---

https://munin.kiska.pw/munin/Munin-Node/Munin-Node/results_rosetta.html ;)

Graphics app doesn’t work on drhicks_…_holo tasks

One of my tasks is running much longer than expected - about 20.5 hours so far rather than the expected 8 hours.

https://boinc.bakerlab.org/rosetta/result.php?resultid=1323410090

Is something wrong with this task?

One of my tasks is running much longer than expected - about 20.5 hours so far rather than the expected 8 hours.

https://boinc.bakerlab.org/rosetta/result.php?resultid=1323410090

Is something wrong with this task?

Maybe?
I've got a sebv1 Task that finished in 3 hours. There's a sebv2 Task that is running, and is looking at 10.5 or so to complete- my sebv2 Tasks that have completed have taken 10hrs 45min (2 of them), 4hrs 20min and 5hrs 40min.

---

Grant
Darwin NT

There's a sebv2 Task that is running, and is looking at 10.5 or so to complete

Now looking at 13hrs 15min to completion.

---

Grant
Darwin NT

One of my tasks is running much longer than expected - about 20.5 hours so far rather than the expected 8 hours.

https://boinc.bakerlab.org/rosetta/result.php?resultid=1323410090

Is something wrong with this task?

It finally finished successfully, before it reached 23 hours. I suspect that the sebv2 tasks need much larger time estimates,

I've got a sebv2 task that has come to a near standstill since reaching 99.55% about 20 hours ago. It is now at 99.603%, elapsed time of 1d 21:49:00 and has progressed 0.003% in 45 minutes but has not progressed for the last 15 minutes. The time remaining keeps recalculating to 00:10:55 +- 01 second, adjusting between 00:10:54 and 00:10:57 for hours. I've seen it work down to --:--:-- then, eventually, recalculating to 00:10:55. The deadline is in about 5 hours so I'm just going to let it run and see what happens. Oops!! Just made 0.001% progress after 20 minutes!

All the other Rosetta task running are not sebv2 and are making consistent progress.

---

I've got a sebv2 task that has come to a near standstill since reaching 99.55% about 20 hours ago. It is now at 99.603%, elapsed time of 1d 21:49:00 and has progressed 0.003% in 45 minutes but has not progressed for the last 15 minutes. The time remaining keeps recalculating to 00:10:55 +- 01 second, adjusting between 00:10:54 and 00:10:57 for hours. I've seen it work down to --:--:-- then, eventually, recalculating to 00:10:55. The deadline is in about 5 hours so I'm just going to let it run and see what happens. Oops!! Just made 0.001% progress after 20 minutes!

All the other Rosetta task running are not sebv2 and are making consistent progress.

The timer and percentage figures are typical of a task that’s overrunning its estimate (because the software has no idea how much it will overrun by) and I believe that the sebv2 tasks have been doing that fairly consistently.

The good news is that it will just go to completion suddenly, the bad news is that no-one can tell when.

Server needs a kick - no tasks coming down

Program	        Host	Status
transitioner1	bwsrv1	Not Running

Application	Unsent	In progress
Rosetta	        5	480390

---