Is that just for now or forever? Because if it is forever, I might as well resign from the project and find another.




Rosetta 4.2 tasks are still being supplied but at a very low rate. There is sporadic Robetta work every day or so and we'll probably see a batch or so every now and then from the Rosetta@home/IPD researchers.




It's done as a full time project for non virtual box type tasks.
SiDock is an alternative to RAH.

SiXock looks more like the WCG open Pandemics work units.

www.worldcommunitygrid.org/research/opn1/overview.s

https://www.sidock.si/sidock/forum_thread.php?id=45#228
Point #3 leads to your idea
Point#4 talks about the current stuff
I run CurieMarieDock on BOINC + zipped input, checkpoints and progress bar v2.00 for the most part
https://www.sidock.si/sidock/server_status.php shows you the progress on the structures they have or are working on. They have their own interface as well like FAH.

I am not getting any Rosetta work on any of my machines, and all of them have a Notice that simply states "Virtualbox not installed." Are these two things related?

Yes.
4.2 tasks are done.
The virtualbox tasks are memory hogs and need virtual box 5.x to run properly and you need to enable virtualization on your motherboard to run this.
They will error out on 6.x

One of these things is not like the other:



"Virtualbox is not installed." That's it. Nothing about why it is needed; why it should be installed; the consequences of not installing it. No links about how to do it. Nothing about equipment or OS requirements.

The entitlement and arrogance is astonishing. We're only worth the time for four words.

I'm giving up on Rosetta. I'll leave it as a project in case they ever decide to go back, but it's going to be a 1 percenter with SiDock getting the hog's share of resources.

I am not getting any Rosetta work on any of my machines, and all of them have a Notice that simply states "Virtualbox not installed." Are these two things related?

Yes.
4.2 tasks are done.
The virtualbox tasks are memory hogs and need virtual box 5.x to run properly and you need to enable virtualization on your motherboard to run this.
They will error out on 6.x

One of these things is not like the other:



"Virtualbox is not installed." That's it. Nothing about why it is needed; why it should be installed; the consequences of not installing it. No links about how to do it. Nothing about equipment or OS requirements.

The entitlement and arrogance is astonishing. We're only worth the time for four words.

I'm giving up on Rosetta. I'll leave it as a project in case they ever decide to go back, but it's going to be a 1 percenter with SiDock getting the hog's share of resources.

You don't need the latest Vbox because it does not work well with Python, so goto this link and download 5.2.x and after that is installed then install the extension pack.
https://www.virtualbox.org/wiki/Download_Old_Builds_5_2
But I should warn you, these python tasks are massive.
The VDI is 9 gigs and will take 10 minutes to download.
The RAM requirement per TASK is 7629.39 real RAM and 1003.xx virtual.
You can set your run time to whatever you want, keep the 8 or switch to 6.
They generate between 126 and 180+ in credits on 6hrs.

We said that 4.2 was non Vbox work and that is hit and miss...mostly miss.
So Vbox is the only thing that is available now as a long term project here at RAH

One of these things is not like the other:



"Virtualbox is not installed." That's it. Nothing about why it is needed; why it should be installed; the consequences of not installing it. No links about how to do it. Nothing about equipment or OS requirements.

The entitlement and arrogance is astonishing. We're only worth the time for four words.

I'm giving up on Rosetta. I'll leave it as a project in case they ever decide to go back, but it's going to be a 1 percenter with SiDock getting the hog's share of resources.

You don't need the latest Vbox because it does not work well with Python, so goto this link and download 5.2.x and after that is installed then install the extension pack.
https://www.virtualbox.org/wiki/Download_Old_Builds_5_2
But I should warn you, these python tasks are massive.
The VDI is 9 gigs and will take 10 minutes to download.
The RAM requirement per TASK is 7629.39 real RAM and 1003.xx virtual.
You can set your run time to whatever you want, keep the 8 or switch to 6.
They generate between 126 and 180+ in credits on 6hrs.

We said that 4.2 was non Vbox work and that is hit and miss...mostly miss.
So Vbox is the only thing that is available now as a long term project here at RAH

I appreciate your replies and your guidance. I'm not going to install and set up that software on my computers just to run Rosetta. I'll move on to SiDock or other projects instead.

happy to see that my lack of getting tasks is not just me. too bad VirtBox is needed now. too much bloat on my PC. will spend all time on WCG now. too bad, Rosetta was my favourite out of all projects supported.

Rosetta was my favourite out of all projects supported.

It is actually good news. It means that they can do more of their work in-house with the new AI techniques.
They just need us to do the heavy-lifting on memory-intensive development work. They don't want to pay for all of that memory themselves.

---

Looks like another batch of 4.2 work is available.

NKG2D, EPHA2 and BCMA. Reading on all those 3, I guess this work could be cancer-related (I'm assuming this was sent back by the same person/team and that they are all related). Or not at all.

---

Looks like another batch of 4.2 work is available.

NKG2D, EPHA2 and BCMA. Reading on all those 3, I guess this work could be cancer-related (I'm assuming this was sent back by the same person/team and that they are all related). Or not at all.

Looks like there are an extra 1.4 million queued tasks when compared to this morning's 2.2 million Pythons.

---

One of these things is not like the other:



"Virtualbox is not installed." That's it. Nothing about why it is needed; why it should be installed; the consequences of not installing it. No links about how to do it. Nothing about equipment or OS requirements.

The entitlement and arrogance is astonishing. We're only worth the time for four words.

I'm giving up on Rosetta. I'll leave it as a project in case they ever decide to go back, but it's going to be a 1 percenter with SiDock getting the hog's share of resources.

You don't need the latest Vbox because it does not work well with Python, so goto this link and download 5.2.x and after that is installed then install the extension pack.
https://www.virtualbox.org/wiki/Download_Old_Builds_5_2
But I should warn you, these python tasks are massive.
The VDI is 9 gigs and will take 10 minutes to download.
The RAM requirement per TASK is 7629.39 real RAM and 1003.xx virtual.
You can set your run time to whatever you want, keep the 8 or switch to 6.
They generate between 126 and 180+ in credits on 6hrs.

We said that 4.2 was non Vbox work and that is hit and miss...mostly miss.
So Vbox is the only thing that is available now as a long term project here at RAH

I appreciate your replies and your guidance. I'm not going to install and set up that software on my computers just to run Rosetta. I'll move on to SiDock or other projects instead.

If you hurry, you can get a bit of the action in 4.2. 27,000+ queued up at the moment.
122,000 already processed. Only 1967 people on 4.2 at the moment.
That leaves 13 tasks per person to crunch.

As for the protein or bio science (non Vbox), then its just FAH, SiDock and WCG outside of the odds and ends here. TACC is a serious hit and miss program. You can go for weeks without getting any work from them. Not worth the time or electricity. It's just stuff they can't run on their supercomputer. I personally do not know of any other projects in protein folding that have work for PC's.

Looks like another batch of 4.2 work is available.

NKG2D, EPHA2 and BCMA. Reading on all those 3, I guess this work could be cancer-related (I'm assuming this was sent back by the same person/team and that they are all related). Or not at all.

Looks like there are an extra 1.4 million queued tasks when compared to this morning's 2.2 million Pythons.

Yes, but all seem limited to 100 decoys before stopping short, so only running between 1 & 2hrs here.

They won't last long at all

---

Looks like another batch of 4.2 work is available.

Yes it does:

Tue 07 Dec 2021 03:10:29 PM EST | Rosetta@home | Sending scheduler request: To fetch work.
Tue 07 Dec 2021 03:10:29 PM EST | Rosetta@home | Requesting new tasks for CPU
Tue 07 Dec 2021 03:10:33 PM EST | Rosetta@home | Scheduler request completed: got 9 new tasks

 1938180 Dec  7 15:10 epha2_site1_3skj_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_2pa9fe3l.zip
 1943095 Dec  7 15:10 epha2_site1_3skj_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_6gv2zz0m.zip
 1996781 Dec  7 15:10 epha2_site1_3skj_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_8yf2ct8i.zip
 1878391 Dec  7 15:10 epha2_site3_3c8x_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_5rx2cb2v.zip
 1990560 Dec  7 15:10 epha2_site3_3c8x_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_6mw9rn0b.zip
 2165492 Dec  7 15:10 niv_site2_6pd4_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_3me3qk7w.zip
 1953078 Dec  7 15:10 niv_site2_6pd4_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_9wm2tx8g.zip
 1923515 Dec  7 15:10 nkg2d_site1_4s0u_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_1zj8yf9y.zip
 2256771 Dec  7 15:10 nkg2d_site1_4s0u_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_7lu6db8g.zip

---

Looks like another batch of 4.2 work is available.

NKG2D, EPHA2 and BCMA. Reading on all those 3, I guess this work could be cancer-related (I'm assuming this was sent back by the same person/team and that they are all related). Or not at all.

Looks like there are an extra 1.4 million queued tasks when compared to this morning's 2.2 million Pythons.

Yes, but all seem limited to 100 decoys before stopping short, so only running between 1 & 2hrs here.

They won't last long at all

An hour or so ago there was just 27K now its up to 29K but the total systems went up. So the average drops to 8 tasks per system.

Run time to finish is just around 2hrs even though it shows 8 hrs when running.

Looks like another batch of 4.2 work is available.

Yes it does:

Tue 07 Dec 2021 03:10:29 PM EST | Rosetta@home | Sending scheduler request: To fetch work.
Tue 07 Dec 2021 03:10:29 PM EST | Rosetta@home | Requesting new tasks for CPU
Tue 07 Dec 2021 03:10:33 PM EST | Rosetta@home | Scheduler request completed: got 9 new tasks

 1938180 Dec  7 15:10 epha2_site1_3skj_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_2pa9fe3l.zip
 1943095 Dec  7 15:10 epha2_site1_3skj_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_6gv2zz0m.zip
 1996781 Dec  7 15:10 epha2_site1_3skj_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_8yf2ct8i.zip
 1878391 Dec  7 15:10 epha2_site3_3c8x_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_5rx2cb2v.zip
 1990560 Dec  7 15:10 epha2_site3_3c8x_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_6mw9rn0b.zip
 2165492 Dec  7 15:10 niv_site2_6pd4_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_3me3qk7w.zip
 1953078 Dec  7 15:10 niv_site2_6pd4_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_9wm2tx8g.zip
 1923515 Dec  7 15:10 nkg2d_site1_4s0u_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_1zj8yf9y.zip
 2256771 Dec  7 15:10 nkg2d_site1_4s0u_3h_ggraft_1_SAVE_ALL_OUT_IGNORE_THE_REST_7lu6db8g.zip

I still have to keep my project_max in play for when I go back to python.
I don't have time to enable app_config and remove it and put it back all the time.

Yes, but all seem limited to 100 decoys before stopping short, so only running between 1 & 2hrs here.

Here too. All mine hit 100 decoys.

---

Yes, 100 decoys. Mine just took much longer because they are running on my AMD 2500u laptop.

---

Yes, 100 decoys. Mine just took much longer because they are running on my AMD 2500u laptop.

DONE :: 100 starting structures 7075.52 cpu seconds
This process generated 100 decoys from 100 attempts

196 minutes used

Most countries have 60 minutes per hour and 60 seconds per minute but according to your calculation Belgium have 36 minutes per hour :). I know what you are doing but you have a long live ahead of you and someone ought to snap you out of that misconception.

7075/(60*60) = 1,96 hours, not 196 minutes. 1,96 hour = 1 hour and 0,96*60/100 = 57.6 minutes
60+57.6 =117,6 minutes

Most countries have 60 minutes per hour and 60 seconds per minute but according to your calculation Belgium have 36 minutes per hour :). I know what you are doing but you have a long live ahead of you and someone ought to snap you out of that misconception.

7075/(60*60) = 1,96 hours, not 196 minutes. 1,96 hour = 1 hour and 0,96*60/100 = 57.6 minutes
60+57.6 =117,6 minutes

Middle of the night math! LMAO.
Thanks for the correction.

Something different...I have been getting some 4.2 stuff and now I am back to Python.
Anyone figure out the scheduler routine yet?
If I was to up the cores in the app_config (project_max_concurrent) to 3 or 4, would I get all Python or a blend of 4.2 and Python?

Something different...I have been getting some 4.2 stuff and now I am back to Python.
Anyone figure out the scheduler routine yet?
If I was to up the cores in the app_config (project_max_concurrent) to 3 or 4, would I get all Python or a blend of 4.2 and Python?

It seems to be a random mix of whatever of available, rather than a schedule. I suspect that it is whatever they are currently teaching their students to create workunits for.