I have <max_concurrent>0</max_concurrent> for rosetta app, but boinc still computes them.

It's possible there's no zero option. Zero often means no limit in Boinc.

Also check Messages tab in Boinctasks or Event Log in Boinc Manager in case there's an error in your file. It looks ok to me, although the indenting is all over the place, but I think it ignores that. Mine would look like this:

<app_config>
   <app>
      <name>rosetta</name>
      <max_concurrent>0</max_concurrent>
   </app>
   <app>
      <name>rosetta_python_projects</name>
      <max_concurrent>2</max_concurrent>
   </app>
</app_config>

As I said before, RAH gives you want it wants when it wants.
The only control that works is project concurrent.
But you can not separate out 4.2 from Python.
The project does not know anything but Rosetta. 4.2 is Rosetta and Python is Rosetta.
Besides, 4.2 tasks get chewed up very fast from the queue.
Right now there are 28,759 4.2 tasks being processed by 5499 accounts.
That makes around 5 tasks per account before that queue is cleaned out.
I have 8 in process and 34 in queue. 6-8 hours run time per tasks

I have <max_concurrent>0</max_concurrent> for rosetta app, but boinc still computes them.

It's possible there's no zero option. Zero often means no limit in Boinc.

Also check Messages tab in Boinctasks or Event Log in Boinc Manager in case there's an error in your file. It looks ok to me, although the indenting is all over the place, but I think it ignores that. Mine would look like this:

<app_config>
   <app>
      <name>rosetta</name>
      <max_concurrent>0</max_concurrent>
   </app>
   <app>
      <name>rosetta_python_projects</name>
      <max_concurrent>2</max_concurrent>
   </app>
</app_config>

As I said before, RAH gives you want it wants when it wants.
The only control that works is project concurrent.
But you can not separate out 4.2 from Python.
The project does not know anything but Rosetta. 4.2 is Rosetta and Python is Rosetta.
Besides, 4.2 tasks get chewed up very fast from the queue.
Right now there are 28,759 4.2 tasks being processed by 5499 accounts.
That makes around 5 tasks per account before that queue is cleaned out.
I have 8 in process and 34 in queue. 6-8 hours run time per tasks

Well Boinc just told me that "<name>rosetta_python_projects</name>" is valid, so you could use that for example to make sure only 2 pythons run at once. But you can't pick what you receive in the first place.

I have <max_concurrent>0</max_concurrent> for rosetta app, but boinc still computes them.

It's possible there's no zero option. Zero often means no limit in Boinc.

Also check Messages tab in Boinctasks or Event Log in Boinc Manager in case there's an error in your file. It looks ok to me, although the indenting is all over the place, but I think it ignores that. Mine would look like this:

<app_config>
   <app>
      <name>rosetta</name>
      <max_concurrent>0</max_concurrent>
   </app>
   <app>
      <name>rosetta_python_projects</name>
      <max_concurrent>2</max_concurrent>
   </app>
</app_config>

As I said before, RAH gives you want it wants when it wants.
The only control that works is project concurrent.
But you can not separate out 4.2 from Python.
The project does not know anything but Rosetta. 4.2 is Rosetta and Python is Rosetta.
Besides, 4.2 tasks get chewed up very fast from the queue.
Right now there are 28,759 4.2 tasks being processed by 5499 accounts.
That makes around 5 tasks per account before that queue is cleaned out.
I have 8 in process and 34 in queue. 6-8 hours run time per tasks

Well Boinc just told me that "<name>rosetta_python_projects</name>" is valid, so you could use that for example to make sure only 2 pythons run at once. But you can't pick what you receive in the first place.

RAH gives you what it wants to give when it gives it. You have no say.
We never had a choice before python because there was nothing else but python.
They didn't change anything in the server from the looks of it, so to them a task is a task, there is no difference to them if its python or 4.2, its a task. The only thing that matters is the due by date for the results. That is what seems to determine what gets sent out.

Fortunately i can disable vbox tasks if i want to.

RAH gives you what it wants to give when it gives it. You have no say.
We never had a choice before python because there was nothing else but python.
They didn't change anything in the server from the looks of it, so to them a task is a task, there is no difference to them if its python or 4.2, its a task. The only thing that matters is the due by date for the results. That is what seems to determine what gets sent out.

You can switch Python off at the server. You can't switch 4.2 off. But you can limit it locally. If you could limit it to zero (which the other poster found is a Boinc bug) then it would download them and never do them, that would teach them to sort their system out.

RAH gives you what it wants to give when it gives it. You have no say.
We never had a choice before python because there was nothing else but python.
They didn't change anything in the server from the looks of it, so to them a task is a task, there is no difference to them if its python or 4.2, its a task. The only thing that matters is the due by date for the results. That is what seems to determine what gets sent out.

You can switch Python off at the server. You can't switch 4.2 off. But you can limit it locally. If you could limit it to zero (which the other poster found is a Boinc bug) then it would download them and never do them, that would teach them to sort their system out.

Teach them something? HAHAHAHA no...it will not teach them anything.
They haven't learned much from our comments and emails about python, so why would not doing or aborting 4.2 tasks teach them anything? The data will just be passed on to the next computer willing to take it and they will notice nothing.

Looks like a small batch of 600,000 Rosetta 4.2 tasks.
Got na10v7nt on my computers.

Yup, and still some available, surprisingly

---

Looks like a small batch of 600,000 Rosetta 4.2 tasks.
Got na10v7nt on my computers.

Yup, and still some available, surprisingly

600k?
Where?

Rosetta 29685 297048 2.78 (0.08 - 55.18) 6950
rosetta python projects 4999 11515 4.62 (0.6 - 59.22) 981
Tasks ready to send 34679

Looks like a small batch of 600,000 Rosetta 4.2 tasks.
Got na10v7nt on my computers.

Yup, and still some available, surprisingly

600k?
Where?

Rosetta 29685 297048 2.78 (0.08 - 55.18) 6950
rosetta python projects 4999 11515 4.62 (0.6 - 59.22) 981
Tasks ready to send 34679

I presume he noticed the change on the main page, where it shows the real queue size instead of the little RAM buffer on the server. Trouble is it doesn't distinguish between types there, so you have to notice how much it increased. Einstein is so much better organised, I can see precisely how many tasks until the end of each subproject.

Looks like a small batch of 600,000 Rosetta 4.2 tasks.
Got na10v7nt on my computers.

Yup, and still some available, surprisingly

Due to Boinc being stupid, you may get some of mine. A computer which runs only 6 hours a day has just downloaded too many to do in that time. Although they say they'll take 8 hours each, I notice some are a lot faster nowadays, so I'll see if they get done.

Looks like a small batch of 600,000 Rosetta 4.2 tasks.
Got na10v7nt on my computers.

Yup, and still some available, surprisingly

600k?
Where?

Rosetta 29685 297048 2.78 (0.08 - 55.18) 6950
rosetta python projects 4999 11515 4.62 (0.6 - 59.22) 981
Tasks ready to send 34679

I presume he noticed the change on the main page, where it shows the real queue size instead of the little RAM buffer on the server. Trouble is it doesn't distinguish between types there, so you have to notice how much it increased. Einstein is so much better organised, I can see precisely how many tasks until the end of each subproject.

Yep.

---

Looks like a small batch of 600,000 Rosetta 4.2 tasks.
Got na10v7nt on my computers.

Get it wiped off quick , it makes a mess if it dry`s on

Yup, and still some available, surprisingly
Due to Boinc being stupid, you may get some of mine. A computer which runs only 6 hours a day has just downloaded too many to do in that time.
Although they say they'll take 8 hours each, I notice some are a lot faster nowadays, so I'll see if they get done.

Looks like the `na` tasks take about 3 hours to crunch,

I have set crunching time to one day and 12 hours in settings.

Looks like a small batch of 600,000 Rosetta 4.2 tasks.
Got na10v7nt on my computers.

Get it wiped off quick , it makes a mess if it dry`s on

ROTFPMSL!

Yup, and still some available, surprisingly
Due to Boinc being stupid, you may get some of mine. A computer which runs only 6 hours a day has just downloaded too many to do in that time.
Although they say they'll take 8 hours each, I notice some are a lot faster nowadays, so I'll see if they get done.

Looks like the `na` tasks take about 3 hours to crunch,

Ryzen 9 3900XT, should be pretty fast then. Only runs in the afternoon. Evenings Boinc is off for playing games, nighttime and morning lie-ins, don't need to heat the house so it's off to save money.

I have set crunching time to one day and 12 hours in settings.

Eh? It takes as long as it takes.

My na's are running at 16 CPU hours per my runtime setting.

---

I have set crunching time to one day and 12 hours in settings.

Eh? It takes as long as it takes.

There's a setting on Rosetta preferences that allows you to specify for how long you want each Rosetta 4.2 task to run.
It's called "Target CPU run time" and you can set that from 2 CPU hour to 36 CPU hours.
Rosetta 4.2 tasks will try to respect that setting. You can change the setting at any time and a project update will change the runtime of any running tasks.

To avoid Rosetta 4.2 tasks from running for an "unlimited" time (say, on a "stuck" model), there is a built-in feature called watchdog that will kill any Rosetta task once it passes the Target CPU runtime setting + 10 CPU hours. Eg. CPU target is 8 hours, watchdog will kill the task at 18 hours of CPU time.

---

i get an insufficient memory notice:

Rosetta@home: Notice from server
Rosetta needs 3337.86 MB RAM but only 2879.42 MB is available for use.
1/30/2022 5:47:45 AM

My mobo is constrained to 4gb of RAM, I will never have more, even if I wanted. I know it is an underpowered machine.

Should I withdraw from Rosetta@home?

For info this is my setup:
Operating System Windows 10 Home 64-bit
CPU Intel Pentium E6600 @ 3.06GHz
RAM 4.00GB Single-Channel DDR2 @ 400MHz (6-5-5-17)
Motherboard eMachines EMCP73VT-PM (CPU 1) 33 °C

Thanks

i get an insufficient memory notice:

Rosetta@home: Notice from server
Rosetta needs 3337.86 MB RAM but only 2879.42 MB is available for use.
1/30/2022 5:47:45 AM

My mobo is constrained to 4gb of RAM, I will never have more, even if I wanted. I know it is an underpowered machine.

Should I withdraw from Rosetta@home?

For info this is my setup:
Operating System Windows 10 Home 64-bit
CPU Intel Pentium E6600 @ 3.06GHz
RAM 4.00GB Single-Channel DDR2 @ 400MHz (6-5-5-17)
Motherboard eMachines EMCP73VT-PM (CPU 1) 33 °C

Thanks

You should be able to run the Rosetta 4.20 tasks when they are available, if your settings allow enough RAM and disk space.

---

Looks like a small batch of 600,000 Rosetta 4.2 tasks.
Got na10v7nt on my computers.

Yup, and still some available, surprisingly

600k?
Where?

Rosetta 29685 297048 2.78 (0.08 - 55.18) 6950
rosetta python projects 4999 11515 4.62 (0.6 - 59.22) 981
Tasks ready to send 34679

At that time last night, the 29,685 were Rosetta 4.20 tasks ready to send.
I looked again this morning - all gone already.
Which is good for me - usually I don't mention they were there at all until after they've all gone

---