since spam in the forums has been cleaned up.

still plenty in the "NEWS" forum/threads

I agree, hence my post. If you're going to quote me, then it would be nice if you quoted me correctly.

12 months (or more) since spam in the forums has been cleaned up.

was what i posted.
ie it is still there 12 months after it was posted.



Although i notice that they've just dumped a load of work, the largest batch in over a month, 2nd largest in 6 months.
However it looks like the run times are 3 hours, so they won't last long. Get them while you can.

---

Grant
Darwin NT

Maybe you have set Target CPU run time to 2 hours?
https://boinc.bakerlab.org/rosetta/prefs.php?subset=project

since spam in the forums has been cleaned up.

still plenty in the "NEWS" forum/threads.
Time for a comment about the `Monty Python Dead Parrot sketch` of late it seems to fit Rosetta quite well .

I have 20 pet parrots and you have directly insulted me. I am reporting you to the admins, the police, and the united nations. Or that's what most snowflakes do nowadays, me, I can take a joke.

Although i notice that they've just dumped a load of work, the largest batch in over a month, 2nd largest in 6 months.
However it looks like the run times are 3 hours, so they won't last long. Get them while you can.

I just got a bunch. They are all 8 hours.

---

Although i notice that they've just dumped a load of work, the largest batch in over a month, 2nd largest in 6 months.
However it looks like the run times are 3 hours, so they won't last long. Get them while you can.

I just got a bunch. They are all 8 hours.

The RB tasks are 8 hours fixed. The hallucinated ones are variable. 3 hours on a fast machine, 10 hours on a slow one.

I've got 93 tasks across my 8 PCs.

Although i notice that they've just dumped a load of work, the largest batch in over a month, 2nd largest in 6 months.
However it looks like the run times are 3 hours, so they won't last long. Get them while you can.

I just got a bunch. They are all 8 hours.

Are they taking 8 hours?
That is the initial Estimated completion time, regardless of your set Target CPU time.

If they are taking 8 hours (for those using the project default), then it must have just been the systems that first returned them were set to 3 hours.

---

Grant
Darwin NT

I have not set my target time, so according to the settings page:
"Target CPU run time
(not selected defaults to 8 hours)"

The last ones I completed were:
Hallucinated task, on an N3700 (slow CPU), 2 hours 55.
Hallucinated task, on a Xeon X5650 (slow CPU), 2 hours 49.
Hallucinated task, on a Xeon X5650 (slow CPU), 2 hours 59.
Hallucinated task, on a Ryzen 9 3900X (fast CPU), 3 hours 1.

Looks like they set it to 3 hours at their end.

Does anyone know what the tasks including the word "hallucinated" might mean?

https://boinc.bakerlab.org/rosetta/forum_thread.php?id=15060#106931
https://theconversation.com/when-researchers-dont-have-the-proteins-they-need-they-can-get-ai-to-hallucinate-new-structures-173209

https://boinc.bakerlab.org/rosetta/forum_thread.php?id=15060#106931
https://theconversation.com/when-researchers-dont-have-the-proteins-they-need-they-can-get-ai-to-hallucinate-new-structures-173209

Thanks for posting those links. That video was amazing and fills me with hope for the future. Two of the diseases he mentioned affect my Aunt and her neighbour (Coeliac disease and Chronic Pain).

I got ten "hallucinated" 4.20 tasks. What are they?
Tullio

---

I got ten "hallucinated" 4.20 tasks. What are they?
Tullio

Presumably to do with the link posted just up there by Kotenok.

Are they taking 8 hours?
That is the initial Estimated completion time, regardless of your set Target CPU time.

If they are taking 8 hours (for those using the project default), then it must have just been the systems that first returned them were set to 3 hours.

I do not know, but the four I have running (these are the first four I got) say they are 50% done and have about 4 hours to go.

---

Are they taking 8 hours?
That is the initial Estimated completion time, regardless of your set Target CPU time.

If they are taking 8 hours (for those using the project default), then it must have just been the systems that first returned them were set to 3 hours.

I do not know, but the four I have running (these are the first four I got) say they are 50% done and have about 4 hours to go.

Are they using a full CPU core? I had some takinga lotlongerthan 3hours,but the CPutiewasalways exactly3 hours. usingBoinctaskswilltellyou yourcputime.

Excusethe lackofspaces,mykeyboardwasjust viciouslyattackedby an African Grey parrotwithout provocation.

I do not know, but the four I have running (these are the first four I got) say they are 50% done and have about 4 hours to go.

Are they using a full CPU core? I had some takinga lotlongerthan 3hours,but the CPutiewasalways exactly3 hours. usingBoinctaskswilltellyou yourcputime.

What do you mean, Are they using a full CPU core? My machine has 16 cores of which I permit 8 of them to be used by the Boinc tasks, and each of the projects is allowed up to four cores. So, I would say yes, they are using a full core.

Task            Work unit	Sent	                    Time reported          Status	        Run time  CPU time  Credit Application

1494624336 	1329099049 	27 Sep 2022, 9:59:08 UTC 27 Sep 2022, 18:54:13 UTC Completed,validated 	28,888.37 28,678.61 662.09  Rosetta v4.20
x86_64-pc-linux-gnu
1494624082 	1329098776 	27 Sep 2022, 9:59:08 UTC 27 Sep 2022, 18:54:13 UTC Completed,validated 	28,479.40 28,275.87 587.82  Rosetta v4.20
x86_64-pc-linux-gnu
1494624396 	1329099169 	27 Sep 2022, 9:59:08 UTC 27 Sep 2022, 18:54:13 UTC Completed,validated 	29,307.91 29,079.61 647.73  Rosetta v4.20
x86_64-pc-linux-gnu
1494623988 	1329098775 	27 Sep 2022, 9:59:08 UTC 27 Sep 2022, 18:54:13 UTC Completed,validated 	28,924.58 28,702.42 594.36  Rosetta v4.20
x86_64-pc-linux-gnu

---

No Rosetta project uses more than one core. If you're only running 8 Rosettas and nothing else, then yes they're getting whole core each. Mine on a variety of computers are all running around 3 hours each. They only take longer if the CPU is overloaded with other things (I also run Folding at Home.)

All my hallucinated tasks take 3 hours (+/- 10 minutes) and my RB ones 8 hours. Not sure why your hallucinated take 8 hours. The only difference I can see is you run Linux. Maybe you got a different batch of work to the Windows users? Or somebody forgot to change the timer for Linux?

No Rosetta project uses more than one core. If you're only running 8 Rosettas and nothing else, then yes they're getting whole core each. Mine on a variety of computers are all running around 3 hours each. They only take longer if the CPU is overloaded with other things (I also run Folding at Home.)

I never said they did use more than one core each work unit. AFAIK, only MilkyWay can take more than one core each. I have it set so those tasks get a total of four cores.
I try to run all 8 cores, but I allow only 4 cores for any one project.

If your task take only three hours each, you have a faster machine than mine. I thought they were set up, by default, to take about 8 hours each. So even if your machine is over twice as fast as mine, then each task should still take about 8 hours, and your machine should just do that much more work.

All my hallucinated tasks take 3 hours (+/- 10 minutes) and my RB ones 8 hours. Not sure why your hallucinated take 8 hours. The only difference I can see is you run Linux. Maybe you got a different batch of work to the Windows users? Or somebody forgot to change the timer for Linux?

I have no idea what an hallucinated task is. I do not believe I run any of those, and I would have no idea how long they would take. My machine runs Red Hat Enterprise Linux release 8.6 (Ootpa), so it should get no Windows work. I do have a little Windows machine and it may be doing what you say. But it does not do much.

What timer would they have forgotten to set?

---

No Rosetta project uses more than one core. If you're only running 8 Rosettas and nothing else, then yes they're getting whole core each. Mine on a variety of computers are all running around 3 hours each. They only take longer if the CPU is overloaded with other things (I also run Folding at Home.)

I never said they did use more than one core each work unit. AFAIK, only MilkyWay can take more than one core each. I have it set so those tasks get a total of four cores.
I try to run all 8 cores, but I allow only 4 cores for any one project.

Ah, I misunderstood when you said "each of the projects is allowed up to four cores", I read it as tasks, not projects.

If your task take only three hours each, you have a faster machine than mine. I thought they were set up, by default, to take about 8 hours each. So even if your machine is over twice as fast as mine, then each task should still take about 8 hours, and your machine should just do that much more work.

I have slow and fast machines, and they all take 3 hours, they used to take 8, but the recent tasks seem to be shorter.

I have no idea what an hallucinated task is.

The last batch have names like "hallu_14_hallucinated_7_1_best_SAVE_ALL_OUT_2917450_982_0"

I do not believe I run any of those, and I would have no idea how long they would take. My machine runs Red Hat Enterprise Linux release 8.6 (Ootpa), so it should get no Windows work. I do have a little Windows machine and it may be doing what you say. But it does not do much.

It's quite possible they sent different types of task to Windows and Linux machines.

What timer would they have forgotten to set?

The default (if you haven't picked your own runtime in your account settings) of how long each task takes. For some reason they like them all to take x hours no matter how fast or slow your computer is. It has always been usually 8, but sometimes there are shorter ones. Anything with hallucinated in the name seems to be 3 hours.

I have slow and fast machines, and they all take 3 hours, they used to take 8, but the recent tasks seem to be shorter.

I have no idea what an hallucinated task is.

The last batch have names like "hallu_14_hallucinated_7_1_best_SAVE_ALL_OUT_2917450_982_0"

OK: all of my current jobs are hallu_14

Tue 27 Sep 2022 05:59:08 AM EDT | Rosetta@home | Requesting new tasks for CPU
Tue 27 Sep 2022 05:59:09 AM EDT | Rosetta@home | Scheduler request completed: got 39 new tasks
Tue 27 Sep 2022 05:59:09 AM EDT | Rosetta@home | Project requested delay of 31 seconds
Tue 27 Sep 2022 05:59:11 AM EDT | Rosetta@home | Started download of hallu_14_hallucinated_180_4_best.zip
Tue 27 Sep 2022 05:59:11 AM EDT | Rosetta@home | Started download of hallu_14_hallucinated_180_4_best.flags
Tue 27 Sep 2022 05:59:13 AM EDT | Rosetta@home | Finished download of hallu_14_hallucinated_180_4_best.zip
Tue 27 Sep 2022 05:59:13 AM EDT | Rosetta@home | Finished download of hallu_14_hallucinated_180_4_best.flags
...

What timer would they have forgotten to set?

The default (if you haven't picked your own runtime in your account settings) of how long each task takes. For some reason they like them all to take x hours no matter how fast or slow your computer is. It has always been usually 8, but sometimes there are shorter ones. Anything with hallucinated in the name seems to be 3 hours.

It is still 8 hours on my machine.

Computer 5910575

Created 	14 Nov 2020, 17:25:40 UTC
Total credit 	1,556,326
Average credit 	753.42

CPU type 	GenuineIntel
Intel(R) Xeon(R) W-2245 CPU @ 3.90GHz [Family 6 Model 85 Stepping 7]
Number of processors 	16
Operating System 	Linux Red Hat Enterprise Linux
Red Hat Enterprise Linux 8.6 (Ootpa) [4.18.0-372.26.1.el8_6.x86_64|libc 2.28]
BOINC version 	7.20.2
Memory 	 63772.82 MB
Cache 	                16896 KB
Swap space 	        15992 MB
Total disk space   488.04 GB
Free Disk Space 	     481 GB
Measured floating point speed 6580.07 million ops/sec
Measured integer speed 	      30457.57 million ops/sec
Average upload rate 	             182.14 KB/sec
Average download rate 	20051.93 KB/sec
Average turnaround time 	1 days

---

I haven't been here for while. No idea why not - just forgot I suppose.
So I've only just realised Python tasks are exhausted and I haven't seen any Rosetta 4.20 tasks for as long or longer.

About time I asked the question, which I'll look to do in the next couple of days.

First, I'm not responsible for hurrying along the Rosetta 4.20 "hallucinated" tasks today.
Tbh, It was their arrival that reminded me to send an email about Pythons etc, which I've now done.
Fwiw, all my Rosetta tasks are running 8hrs, not 3 hours like for some people. No idea what's going on there.
But I now have a response, which I think is pretty useful and I hope you do too.

There are plans for more python tasks, but we are still working on creating the new disk image for the VM.
This image will likely be larger in size since we hope to run some of the latest deep-learning based methods for protein design and validation.

Computing resources are still very much in high demand within the Baker Lab and IPD so Rosetta@home will definitely help once we can get the latest software set up and running.

Also, the standard rosetta application is currently being worked on for an update.
The IPD has hired a software developer specifically to help expedite this.

I am not sure about timelines at the moment but hopefully there should be updates to both projects/apps within the next month or so.

David Kim

---