Why can't you run Python? I forgot.

I do not have VirtualBox, so I cannot run them.

Do you want to run them?
Then download virtual box 5 not 6.
And enable the option to get them on your profile on this page: https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=5958977 (Thats your windows machine)
But they are memory hogs (can only do 3 tasks) plus the VDI is 9 gigs.

Each Python requires 7629.39 MB of physical memory and an additional 101 to 103 MB of Virtual Memory.
Which is why I put the restriction in place so other tasks from other projects could run.

I do not have VirtualBox, so I cannot run them.

Do you want to run them?
Then download virtual box 5 not 6.
And enable the option to get them on your profile on this page: https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=5958977 (Thats your windows machine)
But they are memory hogs (can only do 3 tasks) plus the VDI is 9 gigs.

While I have python, I do not want to bother installing and running VirtualBox on my machine; it has enough to do already.

[/usr/bin]$ ls -l python*
lrwxrwxrwx. 1 root root    9 Aug 11 06:22 python2 -> python2.7
-rwxr-xr-x. 1 root root 8016 Aug 11 06:22 python2.7
lrwxrwxrwx. 1 root root   25 Oct 26  2020 python3 -> /etc/alternatives/python3
lrwxrwxrwx. 1 root root   31 Aug 11 06:56 python3.6 -> /usr/libexec/platform-python3.6
lrwxrwxrwx. 1 root root   32 Aug 11 06:56 python3.6m -> /usr/libexec/platform-python3.6m

---

And more work was added to the queue.
From 2.2 million to 6 million tasks.

---

And more work was added to the queue.
From 2.2 million to 6 million tasks.

many of these are completing in 1 hour or so, not the 8 hr Target CPU time. So they won't last long at all if most of them are like these initial ones.

---

Grant
Darwin NT

I do not have VirtualBox, so I cannot run them.

Do you want to run them?
Then download virtual box 5 not 6.
And enable the option to get them on your profile on this page: https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=5958977 (Thats your windows machine)
But they are memory hogs (can only do 3 tasks) plus the VDI is 9 gigs.

While I have python, I do not want to bother installing and running VirtualBox on my machine; it has enough to do already.

[/usr/bin]$ ls -l python*
lrwxrwxrwx. 1 root root    9 Aug 11 06:22 python2 -> python2.7
-rwxr-xr-x. 1 root root 8016 Aug 11 06:22 python2.7
lrwxrwxrwx. 1 root root   25 Oct 26  2020 python3 -> /etc/alternatives/python3
lrwxrwxrwx. 1 root root   31 Aug 11 06:56 python3.6 -> /usr/libexec/platform-python3.6
lrwxrwxrwx. 1 root root   32 Aug 11 06:56 python3.6m -> /usr/libexec/platform-python3.6m

Well you can exclude them if you don't want to have them. Same page allows you to opt out.

While I have python, I do not want to bother installing and running VirtualBox on my machine; it has enough to do already.

[/usr/bin]$ ls -l python*
lrwxrwxrwx. 1 root root 9 Aug 11 06:22 python2 -> python2.7
-rwxr-xr-x. 1 root root 8016 Aug 11 06:22 python2.7
lrwxrwxrwx. 1 root root 25 Oct 26 2020 python3 -> /etc/alternatives/python3
lrwxrwxrwx. 1 root root 31 Aug 11 06:56 python3.6 -> /usr/libexec/platform-python3.6
lrwxrwxrwx. 1 root root 32 Aug 11 06:56 python3.6m -> /usr/libexec/platform-python3.6m

Well you can exclude them if you don't want to have them. Same page allows you to opt out.

To what page do you refer?

OTOH, for some reason, I do not get any, though I do get the messages

Fri 10 Dec 2021 10:30:09 AM EST | Rosetta@home | Message from server: VirtualBox is not installed <---<<<
Fri 10 Dec 2021 10:30:09 AM EST | Rosetta@home | Project requested delay of 31 seconds
Fri 10 Dec 2021 12:26:12 PM EST | Rosetta@home | Sending scheduler request: To fetch work.
Fri 10 Dec 2021 12:26:12 PM EST | Rosetta@home | Requesting new tasks for CPU
Fri 10 Dec 2021 12:26:15 PM EST | Rosetta@home | Scheduler request completed: got 9 new tasks

---

To what page do you refer?

The options on the page mentioned aren't there because you don't have VirtualBox installed.

OTOH, for some reason, I do not get any, though I do get the messages

Just as the message says- because you don't have VirtualBox installed, you won't get any.

If you want to do Python Tasks, you must install VirtualBox. If you don't want to do them, or just don't want to install VirtualBox, then don't.

---

Grant
Darwin NT

To what page do you refer?

The options on the page mentioned aren't there because you don't have VirtualBox installed.

OTOH, for some reason, I do not get any, though I do get the messages

Just as the message says- because you don't have VirtualBox installed, you won't get any.

If you want to do Python Tasks, you must install VirtualBox. If you don't want to do them, or just don't want to install VirtualBox, then don't.

Thanks for the assist.
I forgot that non Vbox users can't see the tasks.
But then again, why should they get the error saying Vbox is not installed?
IF they were smart, then when they detect that Vbox is not installed, just ignore sending any messages to the system. Would save this kind of confusion.

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

I did get a few Robetta tasks that ran the full 8hrs but it looks like all Rosetta 4.20 tasks have been downloaded now.
Won't be long before I'm back running WCG

My resource share is set to Rosetta 29 - WCG 1 but my RAC is 6.5k to 19.6k atm... <sigh>

Sid - not all of that millions is for us. I randomly sampled some of the jobs and found some with RoseTTAFold which is the neural network. There is no way on that page to isolate those from the rest without clicking on each one.

Like this group: Potassium-transporting ATPase alpha chain 2 11 That is all for RoseTTaFold.
And so on.

And more work was added to the queue.
From 2.2 million to 6 million tasks.

many of these are completing in 1 hour or so, not the 8 hr Target CPU time. So they won't last long at all if most of them are like these initial ones.

Some of my tasks are running beyond the 100 decoy mark.
For example, this one.

---

And more work was added to the queue.
From 2.2 million to 6 million tasks.

many of these are completing in 1 hour or so, not the 8 hr Target CPU time. So they won't last long at all if most of them are like these initial ones.

Some of my tasks are running beyond the 100 decoy mark.
For example, this one.

Try this one ....198

I have encountered some virtualbox tasks that takes over a day to run. When task takes over a day to run, I thought that it is stuck in some way and aborted the task. Other thought is that there is some problem in my environment.

Does virtualbox tasks usually take over a day to run? Is there some problem in my environment?



One longlasting task is as follows:

Task 1453463295
Name aagb-mALA_pp-mHPR-mACPenC13T-B3PHE_1_2611271_1_0
Workunit 1297021861
Created 8 Dec 2021, 21:03:21 UTC
Sent 9 Dec 2021, 13:51:23 UTC
Report deadline 12 Dec 2021, 13:51:23 UTC
Received 11 Dec 2021, 12:36:28 UTC
Server state Over
Outcome Computation error
Client state Aborted by user
Exit status 203 (0x000000CB) EXIT_ABORTED_VIA_GUI
Computer ID 2401895
Run time 1 days 2 hours 45 min 39 sec
CPU time 25 min 55 sec
Validate state Invalid
Credit 14.00
Device peak FLOPS 4.90 GFLOPS
Application version rosetta python projects v1.03 (vbox64)
x86_64-pc-linux-gnu
Peak working set size 1,185.08 MB
Peak swap size 2,565.54 MB
Peak disk usage 7,979.68 MB


Computer:

IP address Show IP address
Domain name huono3-desktop
Local Standard Time UTC +2 hours
Created 17 Nov 2015, 17:05:25 UTC
Total credit 4,147,395
Average credit 262.50
Cross project credit BOINCstats.com Free-DC
CPU type GenuineIntel
Intel(R) Pentium(R) CPU G3258 @ 3.20GHz [Family 6 Model 60 Stepping 3]
Number of processors 2
Coprocessors ---
Operating System Linux Ubuntu
Ubuntu 20.04.3 LTS [5.4.0-91-generic|libc 2.31 (Ubuntu GLIBC 2.31-0ubuntu9.2)]
BOINC version 7.16.6
Memory 7639 MB
Cache 3072 KB
Swap space 3905 MB
Total disk space 106.16 GB
Free Disk Space 83.67 GB
Measured floating point speed 4895.56 million ops/sec
Measured integer speed 111568.63 million ops/sec
Average upload rate 160.08 KB/sec
Average download rate 2790.46 KB/sec
Average turnaround time 2.77 days
Application details Show
Tasks 27
Number of times client has contacted server 5500
Last time contacted server 14 Dec 2021, 12:32:40 UTC
Fraction of time BOINC is running 83.79%
While BOINC is running, fraction of time computing is allowed 100.00%
While is BOINC running, fraction of time GPU computing is allowed 100.00%
Task duration correction factor 1

virtual box version: 6.1.26

I have encountered some virtualbox tasks that takes over a day to run. When task takes over a day to run, I thought that it is stuck in some way and aborted the task. Other thought is that there is some problem in my environment.

Does virtualbox tasks usually take over a day to run? Is there some problem in my environment?

There are a few "0 CPU" tasks. Just check the CPU usage. If it is very low, abort that task.
I use BoincTasks to check that easily, but you can look at the CPU runtime in BOINC manager as well.

---

Run time 1 days 2 hours 45 min 39 sec
CPU time 25 min 55 sec

Sitting there doing very little

I wonder if anyone could help me with something that has been puzzling me.

I have two 4C/4T Intel laptops running RAH. When the 4.20 tasks ran out recently I tried running Pythons on them on Linux without much success.

I then adopted the suggestion from Jim1348 of switching to Windows and trying VirtualBox 5.2.44, which worked (thank you!).

The only problem then was that I could only run 2 tasks at a time instead of 4. So I bought some more memory for one of the laptops, doubling it from 8GB to 16GB. But that laptop would still only run 3 tasks at a time.

Does anyone have any idea why that would be? I had assumed that, if I can run 2 tasks on 8GB, I would certainly be able to run 4 tasks on 16GB. But that assumption appears to have been wrong.

For the moment, I've switched back to 4.20 only, in order to use all the cores. But if anyone has any ideas as to why I can't run 4 Pythons at a time, or otherwise as to how to troubleshoot this issue, I would be very grateful.

I'm happy to buy more memory for the other laptop as well, but it seems a bit of a waste of money just to run 3 Pythons instead of 2.

Cheers,
Mark

Can not say what is reason for that, but usually on my machines one Python (Virtualbox) work unit has taken 7.5GB of RAM.

Grab Emfer Boinc Tasks program so you can monitor cpu usage and memory size of what runs on your system in BOINC. I've had a few tasks that ran 12hrs and when I looked at the cpu on Boinc Tasks I saw it was only .08 of a cpu and there was no progress in the percent run.

I share my system with other projects, but with my "massive" memory of 24GB, I was only running 3 Pythons and 2 GPU's plus FAH. The old pythons were huge memory hogs. I don't recall, think 7 gigs (ah Kompakki has the total...7.5G) a task. [This would limit you 2 tasks]
Now with Cages it is only 2861 per task.
But I am still only running 3 tasks.

But at 7gigs per task (old pythons) your 16 gigs doesn't allow for any more than 2.
When i had 3 old pythons that was 21 gigs of memory gone.

Wait and see if you get the new stuff from python.
Cages is small..only 686
aaa* stuff is 2861 per task.
That is what I am running right now.
With those kinds of numbers your machines should pick up 4 tasks.

I've had to stop getting new tasks for Rosetta. I've been processing with the project since 2007.

I have a 5950X - 32 CPU Threads with 64Gig of RAM, a 3060Ti all running Xubuntu 21.10. My system software and BOINC are fully up to date.

The issue is the same as others are encountering with the vbox64 tasks. They seem to take forever to make almost no progress. The Elapsed counter is ticking over 1second per second but the Remaining (estimated) show's 3 seconds but isn't moving.

So lets assume the estimated process remaining is busted - fine. When I look at my processor usage even though the Rosetta tasks are taking a "slot" they aren't actually using the CPU. If I set 100% CPU utilisation I expect to see 32 processes running. But if I have 4 Rosetta tasks then I only see 28 processes running (running other BOINC projects) and the 4 Rosetta tasks aren't using the CPU. When I check the Rosetta tasks with a ps I can see they aren't using any CPU.

I have 2 remaining Rosetta tasks and when I click properties they show as below:

Application rosetta python projects 1.03 (vbox64)
Name boinc_cages_IL_2728657_17535
State Running
Received Tue 07 Dec 2021 21:24:22
Report deadline Fri 10 Dec 2021 21:24:21
Estimated computation size 80,000 GFLOPs
CPU time 00:27:29
CPU time since checkpoint 00:00:00
Elapsed time 3d 18:47:54
Estimated time remaining 00:00:03
Fraction done 99.999%
Virtual memory size 1.53 GB
Working set size 7.45 GB
Directory slots/8
Process ID 4062
Progress rate 1.080% per hour
Executable vboxwrapper_26198_x86_64-pc-linux-gnu



Application
rosetta python projects 1.03 (vbox64)
Name aagb-mPPR-ACBC-LARE-B3PHE_pp_2_2649998_1
State Running
Received Wed 08 Dec 2021 11:21:11
Report deadline Sat 11 Dec 2021 11:21:10
Estimated computation size 80,000 GFLOPs
CPU time 00:27:10
CPU time since checkpoint 00:00:01
Elapsed time 3d 18:10:43
Estimated time remaining 00:00:04
Fraction done 99.999%
Virtual memory size 1.53 GB
Working set size 2.79 GB
Directory slots/3
Process ID 5141
Progress rate 1.080% per hour
Executable vboxwrapper_26198_x86_64-pc-linux-gnu


If anyone is has resolved this problem or can explain what is going wrong I'd love to hear it.

Thanks, Grant.

with only 27min if cpu time and over 3 days of elapsed time my way to fix that kind of tasks is the `abort` button
those are just timewasters

Those task have hung or the processing inside the VM crashed. Just abort the work unit(s).
If you don't want to run the VM tasks here, and just legacy tasks, you go to your individual computer details and look at the bottom where it says "VirtualBox VM jobs" Just turn off the option. The button is only visible if you have Virtual Box installed and the project was allowing you those tasks.