That's a great suggestion. I'll add that functionality.

Please can you post back when you have implemented something so we can check our idle machines - I've got a few that aren't getting any Rosetta tasks at the moment and I have no idea why.

1) There are only 9 tasks in 4.2, so you probably are not getting anything from that
2) If you had any problems in the past running Python, you probably got black listed by the python scheduler (see my quote from ADMIN from earlier)

If 2 applies then your are SOL.

And please reduce the VB tasks RAM requirements in the VB image too!

Unless anyone has seen anything to the contrary, they don't need anywhere near 8GB each - 1GB would probably be more than enough. It's massively limiting the number of tasks that can be run - I've typically for 3 cores running python tasks and 13 idle at the moment.

---

And please reduce the VB tasks RAM requirements in the VB image too!
Unless anyone has seen anything to the contrary, they don't need anywhere near 8GB each - 1GB would probably be more than enough.
It's massively limiting the number of tasks that can be run - I've typically for 3 cores running python tasks and 13 idle at the moment.

Oooo . I`ve found a big one .
Peak working set size 464.75 MB
Peak swap size 492.55 MB
Peak disk usage 3,549.37 MB . . . .
https://boinc.bakerlab.org/rosetta/result.php?resultid=1451421574
I don`t care about disk use, there`s plenty about,

I added an option near the bottom of your host "details" page to "Skip" or "Allow" Vbox VM jobs if your host has the boinc vm client.

I'll talk to the researchers that are currently running VM jobs about reducing the memory requirements. This will take some time since they will have to update the VM image, test it, and cancel and resubmit their jobs.

---

I added an option near the bottom of your host "details" page to "Skip" or "Allow" Vbox VM jobs if your host has the boinc vm client.

I'll talk to the researchers that are currently running VM jobs about reducing the memory requirements. This will take some time since they will have to update the VM image, test it, and cancel and resubmit their jobs.

Sounds good.
Thanks.

Edit: Next to the skip/allow option, there is also the option to delete the machine. It's already present before on merge option.

---

I added an option near the bottom of your host "details" page to "Skip" or "Allow" Vbox VM jobs if your host has the boinc vm client.

I'll talk to the researchers that are currently running VM jobs about reducing the memory requirements.
This will take some time since they will have to update the VM image, test it, and cancel and resubmit their jobs.

Thank you , the memory problem realy is backing the RPP jobs against a wall.
If they can get it down to 2GB or less per VM they will get a lot more done.

ADMIN, I would love to come back, but your slash and burn edit to the python scheduler black listed my system which is apparently why I had to start this thread in the first place. Because of that code, you limited me to 4.2. Now that you can not generate any 4.2 and blacklisted my system in the early stages of this Python adventure, there is no work for me, which is why I left.

I gave you guys 15 years and you block me without saying anything until way later with what? 2 or 3 lines?
That's not a good thing.

I have gotten Vbox to work just fine over on QuChemPed and I have run LHC Atlas for a long time without problems. So I don't think it was really my system that was at fault, rather I think it was errors on your early Python tasks that caused the error you are blocking.

If you don't want me back then I might as well delete any association with this project and say nice knowing you.

ADMIN, I would love to come back, but your slash and burn edit to the python scheduler black listed my system which is apparently why I had to start this thread in the first place. Because of that code, you limited me to 4.2. Now that you can not generate any 4.2 and blacklisted my system in the early stages of this Python adventure, there is no work for me, which is why I left.

I gave you guys 15 years and you block me without saying anything until way later with what? 2 or 3 lines?
That's not a good thing.

I have gotten Vbox to work just fine over on QuChemPed and I have run LHC Atlas for a long time without problems. So I don't think it was really my system that was at fault, rather I think it was errors on your early Python tasks that caused the error you are blocking.

If you don't want me back then I might as well delete any association with this project and say nice knowing you.

It looks like we can turn that "blacklist" flag on and off ourselves now.

---

Want to find one of the largest known primes? Try PrimeGrid. Or help cure disease at WCG.

ADMIN, I would love to come back, but your slash and burn edit to the python scheduler black listed my system which is apparently why I had to start this thread in the first place. Because of that code, you limited me to 4.2. Now that you can not generate any 4.2 and blacklisted my system in the early stages of this Python adventure, there is no work for me, which is why I left.

I gave you guys 15 years and you block me without saying anything until way later with what? 2 or 3 lines?
That's not a good thing.

I have gotten Vbox to work just fine over on QuChemPed and I have run LHC Atlas for a long time without problems. So I don't think it was really my system that was at fault, rather I think it was errors on your early Python tasks that caused the error you are blocking.

If you don't want me back then I might as well delete any association with this project and say nice knowing you.

It looks like we can turn that "blacklist" flag on and off ourselves now.

How?
My understanding of his post was that he put a code in the scheduler to eliminate systems that generated a certain kind of error. If it is in the scheduler, then how do you get around that? Once it knows you IP and account, I don't think you can undo that.

ADMIN, I would love to come back, but your slash and burn edit to the python scheduler black listed my system which is apparently why I had to start this thread in the first place. Because of that code, you limited me to 4.2. Now that you can not generate any 4.2 and blacklisted my system in the early stages of this Python adventure, there is no work for me, which is why I left.

I gave you guys 15 years and you block me without saying anything until way later with what? 2 or 3 lines?
That's not a good thing.

I have gotten Vbox to work just fine over on QuChemPed and I have run LHC Atlas for a long time without problems. So I don't think it was really my system that was at fault, rather I think it was errors on your early Python tasks that caused the error you are blocking.

If you don't want me back then I might as well delete any association with this project and say nice knowing you.

It looks like we can turn that "blacklist" flag on and off ourselves now.

How?
My understanding of his post was that he put a code in the scheduler to eliminate systems that generated a certain kind of error. If it is in the scheduler, then how do you get around that? Once it knows you IP and account, I don't think you can undo that.

Go to the details page for that host. Scroll to the bottom. You'll see, on the last line, a setting "VirtualBox VM jobs", and a blue and red button labelled "Allow". Click on that button. That's it. That turns off the blacklist from the scheduler.

The button will change to "Skip". You can click on the "skip" button if you ever want to turn off the Vbox tasks.

---

Want to find one of the largest known primes? Try PrimeGrid. Or help cure disease at WCG.

By default, its skip. on the details page, but I get no tasks unless I install virtualbox, and then it only loads 16 tasks for a 128 thread 7742 with 128 gig ram.

What is wrong ?

---

By default, its skip. on the details page, but I get no tasks unless I install virtualbox, and then it only loads 16 tasks for a 128 thread 7742 with 128 gig ram.

What is wrong ?

Not enough RAM.
You need 8GB RAM per Python Task (they don't use anywhere near that amount, but that is the hard minimum requirement that has been set for those Tasks). So if you get just over 1TB of RAM in that system, you'll be able to process Python Tasks on all available cores & threads.
Or just keep waiting for some more Rosetta 4.20 work to be released.

---

Grant
Darwin NT

ADMIN, I would love to come back, but your slash and burn edit to the python scheduler black listed my system which is apparently why I had to start this thread in the first place. Because of that code, you limited me to 4.2. Now that you can not generate any 4.2 and blacklisted my system in the early stages of this Python adventure, there is no work for me, which is why I left.

I gave you guys 15 years and you block me without saying anything until way later with what? 2 or 3 lines?
That's not a good thing.

I have gotten Vbox to work just fine over on QuChemPed and I have run LHC Atlas for a long time without problems. So I don't think it was really my system that was at fault, rather I think it was errors on your early Python tasks that caused the error you are blocking.

If you don't want me back then I might as well delete any association with this project and say nice knowing you.

It looks like we can turn that "blacklist" flag on and off ourselves now.

How?
My understanding of his post was that he put a code in the scheduler to eliminate systems that generated a certain kind of error. If it is in the scheduler, then how do you get around that? Once it knows you IP and account, I don't think you can undo that.

Go to the details page for that host. Scroll to the bottom. You'll see, on the last line, a setting "VirtualBox VM jobs", and a blue and red button labelled "Allow". Click on that button. That's it. That turns off the blacklist from the scheduler.

The button will change to "Skip". You can click on the "skip" button if you ever want to turn off the Vbox tasks.

I don't see anything in BOINC or on my preferences page to match what you are talking about.
I think that option is only for people that are not black listed.

Go to my account, devices on this account, click on details on the host you want to run Python on, scroll down to "VirtualBox VM jobs". You should see either "Allow" or "Skip".
Click on Allow to allow VB jobs, click on Skip to forbid VB jobs.

The option only appears on devices that have VirtualBox installed.

---

ADMIN, I would love to come back, but your slash and burn edit to the python scheduler black listed my system which is apparently why I had to start this thread in the first place. Because of that code, you limited me to 4.2. Now that you can not generate any 4.2 and blacklisted my system in the early stages of this Python adventure, there is no work for me, which is why I left.

I gave you guys 15 years and you block me without saying anything until way later with what? 2 or 3 lines?
That's not a good thing.

I have gotten Vbox to work just fine over on QuChemPed and I have run LHC Atlas for a long time without problems. So I don't think it was really my system that was at fault, rather I think it was errors on your early Python tasks that caused the error you are blocking.

If you don't want me back then I might as well delete any association with this project and say nice knowing you.

It looks like we can turn that "blacklist" flag on and off ourselves now.

How?
My understanding of his post was that he put a code in the scheduler to eliminate systems that generated a certain kind of error. If it is in the scheduler, then how do you get around that? Once it knows you IP and account, I don't think you can undo that.

Go to the details page for that host. Scroll to the bottom. You'll see, on the last line, a setting "VirtualBox VM jobs", and a blue and red button labelled "Allow". Click on that button. That's it. That turns off the blacklist from the scheduler.

The button will change to "Skip". You can click on the "skip" button if you ever want to turn off the Vbox tasks.

I don't see anything in BOINC or on my preferences page to match what you are talking about.
I think that option is only for people that are not black listed.

I did not say anything about the preferences page. On any other project, that's where the control would be. But here the change is on the host detail page. Go the your list of computers and select the "details" link for the computer you want to change. There's a different setting for each computer.

Also, I believe that if you don't have vbox installed the server doesn't show that button. The control appears to only be there for computers that have vbox installed.

You definitely CAN turn off the blacklisting. My computer was blacklisted, and now it's not.

The correct page for changing the control for your c omputer is https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=3433065 There should be a gaudy blue and red skip/allow button near the bottom of the page beneath the "update location" button.

---

Want to find one of the largest known primes? Try PrimeGrid. Or help cure disease at WCG.

Good find - I wouldn't have seen that for a long time!

So there options I've got are either:
Skip: For systems already running VB tasks succesfully
Allow: For systems that have been blocked from VB tasks
Missing (no button there): presumably for systems that can't run VB tasks (no virtualisation, no VirtualBox installed, service install etc.)

---

ADMIN, I would love to come back, but your slash and burn edit to the python scheduler black listed my system which is apparently why I had to start this thread in the first place. Because of that code, you limited me to 4.2. Now that you can not generate any 4.2 and blacklisted my system in the early stages of this Python adventure, there is no work for me, which is why I left.

I gave you guys 15 years and you block me without saying anything until way later with what? 2 or 3 lines?
That's not a good thing.

I have gotten Vbox to work just fine over on QuChemPed and I have run LHC Atlas for a long time without problems. So I don't think it was really my system that was at fault, rather I think it was errors on your early Python tasks that caused the error you are blocking.

If you don't want me back then I might as well delete any association with this project and say nice knowing you.

It looks like we can turn that "blacklist" flag on and off ourselves now.

How?
My understanding of his post was that he put a code in the scheduler to eliminate systems that generated a certain kind of error. If it is in the scheduler, then how do you get around that? Once it knows you IP and account, I don't think you can undo that.

Go to the details page for that host. Scroll to the bottom. You'll see, on the last line, a setting "VirtualBox VM jobs", and a blue and red button labelled "Allow". Click on that button. That's it. That turns off the blacklist from the scheduler.

The button will change to "Skip". You can click on the "skip" button if you ever want to turn off the Vbox tasks.

I don't see anything in BOINC or on my preferences page to match what you are talking about.
I think that option is only for people that are not black listed.

I did not say anything about the preferences page. On any other project, that's where the control would be. But here the change is on the host detail page. Go the your list of computers and select the "details" link for the computer you want to change. There's a different setting for each computer.

Also, I believe that if you don't have vbox installed the server doesn't show that button. The control appears to only be there for computers that have vbox installed.

You definitely CAN turn off the blacklisting. My computer was blacklisted, and now it's not.

The correct page for changing the control for your c omputer is https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=3433065 There should be a gaudy blue and red skip/allow button near the bottom of the page beneath the "update location" button.

How freaking amazing!
But:

If VM jobs cannot run due VirtualBox errors, this host will be flagged again to skip VM jobs.
Ok, what errors then. Needs to be more specific.
J got 4 pythons now.
Curious. I backed down to 5.4.22 to get QuChem to run clean. So this should also allow Python to run clean.

Good find - I wouldn't have seen that for a long time!

So there options I've got are either:
Skip: For systems already running VB tasks succesfully
Allow: For systems that have been blocked from VB tasks
Missing (no button there): presumably for systems that can't run VB tasks (no virtualisation, no VirtualBox installed, service install etc.)

Well about time he did this. Why the *^*%$ didn't he do this when they started python?
Seriously.

But did you notice their disclaimer/threat?
If VM jobs cannot run due VirtualBox errors, this host will be flagged again to skip VM jobs.
But in usual RAH fashion, they are not specific.

There is one thing missing still, ADMIN needs to change the preference page to reflect how many cores a person wishes to allocate. You need this to avoid Vbox environment instability.
Again at Qchem I found I can only run 3 tasks without it becoming unstable.
RAH does not allow you to control how many cores or how many tasks to run.
So if it tries to run all 4 at the same time and the environment becomes unstable, I have no way to control that scenario. Hopefully BOINC will know what to do.

So 2 RAH in Vbox, 1 Quchem in Vbox and SiDock was also running but finished.

Good find - I wouldn't have seen that for a long time!

So there options I've got are either:
Skip: For systems already running VB tasks succesfully
Allow: For systems that have been blocked from VB tasks
Missing (no button there): presumably for systems that can't run VB tasks (no virtualisation, no VirtualBox installed, service install etc.)

Well about time he did this. Why the *^*%$ didn't he do this when they started python?
Seriously.

But did you notice their disclaimer/threat?
If VM jobs cannot run due VirtualBox errors, this host will be flagged again to skip VM jobs.
But in usual RAH fashion, they are not specific.

Seriously? Does nothing ever satisfy you?

You’ve been banging on for weeks about not getting RPP WUs, now you have some but no thank you, no well done - just *^*%$ and more complaints!