You can ask Veneto how to do that modification to block beta work. But I only got one beta and since then nothing but clean 4.20. So is it worth the effort to mess around?

The "usual" app_config.xml
Something like this (if i remember correctly):

<app_config>
    <app>
        <name>rosetta</name>
            <max_concurrent>X</max_concurrent>
    </app>
 </app_config>

(with X you can configure how many cores to use)


P.S.
Veneto is a region (where i live) of Italy. My nickname is boboviz...

---

Stuprd boinc thinks <max_concurrent>0</max_concurrent> is unlimited.

I can read news from page 1, but when i press on page 2 everything is empty.

Stuprd boinc thinks <max_concurrent>0</max_concurrent> is unlimited.

I can read news from page 1, but when i press on page 2 everything is empty.

I only get threads on page 1, all the rest are empty.

---

Grant
Darwin NT

Stuprd boinc thinks <max_concurrent>0</max_concurrent> is unlimited.

I can read news from page 1, but when i press on page 2 everything is empty.

I only get threads on page 1, all the rest are empty.

And after making that above post, "Problems and Technical Issues with Rosetta@home" then went missing from Number Crunching for me.
???

---

Grant
Darwin NT

I can see it as thread 7.

I can see it as thread 7.

UPI Payment spam is the most recent post showing for me, from 2 hours ago.
But on the main forum page, it shows the most recent post in the Number crunching thread was 2 minutes ago.

I've set the messages boards to ignore pinned messages.

I can only find this thread now by looking at my recent posts in my account.

---

Grant
Darwin NT

I've set the messages boards to ignore pinned messages

.
Here is your problem.

Some more Robetta tasks have popped up in the meantime

And again some more in the last 20 minutes #NotDeadYet

---

You can ask Veneto how to do that modification to block beta work. But I only got one beta and since then nothing but clean 4.20. So is it worth the effort to mess around?

The "usual" app_config.xml
Something like this (if i remember correctly):

<app_config>
    <app>
        <name>rosetta</name>
            <max_concurrent>X</max_concurrent>
    </app>
 </app_config>

(with X you can configure how many cores to use)


P.S.
Veneto is a region (where i live) of Italy. My nickname is boboviz...

Sorry about that..couldn't remember your nickname and was in a rush this morning to get out of the house.

I thought he was asking how to block the Beta app so he wouldn't get that work, being that it errors out right now.
Is that even possible?

Wow, the queue got eaten up that fast?
There must be some people that take 100 tasks at a time.

Wow, the queue got eaten up that fast?
There must be some people that take 100 tasks at a time.

Are you sure? I didn't even see a queue appear on the front page, just downloaded 16 (1 per core) 8hrs ago, then nothing, then 8 about 5hrs ago, then nothing again.
Weird thing is, 10 of that first 16 Robetta tasks crashed out after varying amounts of times when they were pretty reliable before.
So, just 14 running successfully atm with nothing to back it up.

Edit: Just checked and they were mainly re-sends, very few new tasks. The ones that crashed out had already crashed on a previous host, so not a sign of anything new going wrong

---

I've set the messages boards to ignore pinned messages

.
Here is your problem.

No, the problem is the database is corrupted.
It should include this thread in the list in order of most recent post to oldest (as per my forum settings), and for some reason, that's no longer occurring.



Edit- a "Rosetta Beta 6.00" is borked as well, it's not being sorted in order of post date/time.


Edit- i thought i'd see what changing the settings fir the message boards would do- and for some reason the how to sort option for the threads had changed from "Newest post first" to "Newest first."
Changed it back and updated- threads are now all being sorted as they should be.


If weird things start happening, check the settings (even if you haven't made any changes to them for years...).

---

Grant
Darwin NT

P.S.
Veneto is a region (where i live) of Italy. My nickname is boboviz...

Sorry about that..couldn't remember your nickname and was in a rush this morning to get out of the house.

No problem :-P

I thought he was asking how to block the Beta app so he wouldn't get that work, being that it errors out right now.
Is that even possible?

With the xml file you force to download the selected app.

---

Since the project has recently restarted I have had some tasks start with a predicted exec. time of 10hr. After crunching for 8 hrs it then says that there are 15-24 more hrs. I am running windows 11. Is this a false estimate, or will it take that much time? To not pour more time into something acting weird I have aborted the task. Is this a problem? Will it be worth crunching? Will I get full credit for all this processing?

---

I don't receive new tasks for weeks now.

Is there a systematic list of checks I should do to discover the reason why?

There used to be a time when I did not get new tasks because I had to enable Python in my web profile, I did that once. Has there been a similar change which expects me to change any preferences which I never heard of before?

---

Fun and success!

Jobs: holzon + 12angebote
Hobbies: doom9/Gleitz + PlaneShift

Since the project has recently restarted I have had some tasks start with a predicted exec. time of 10hr. After crunching for 8 hrs it then says that there are 15-24 more hrs. I am running windows 11. Is this a false estimate, or will it take that much time? To not pour more time into something acting weird I have aborted the task. Is this a problem? Will it be worth crunching? Will I get full credit for all this processing?

It does take 8 hours to process each Task, but as your system is severely over committed, it's taking it 12 hours to do 8 hours worth of work.
You could determine what else is using your CPU time (eg Folding@home) and reduce the number of cores/threads available to BOINC to sort the issue out, or just accept that it takes your system 12 hours to do only 8 hours worth of work.

---

Grant
Darwin NT

I don't receive new tasks for weeks now.

Because the servers were down for several weeks- as was mentioned in this thread earlier.
And even before that outage, work availability was very much random. Sometimes there was work, often there wasn't.

---

Grant
Darwin NT

Aaaand ... I just received new tasks.

---

Fun and success!

Jobs: holzon + 12angebote
Hobbies: doom9/Gleitz + PlaneShift

Current status:

Tasks ready to send 0
Tasks in progress 66224

You can ask Veneto how to do that modification to block beta work. But I only got one beta and since then nothing but clean 4.20. So is it worth the effort to mess around?

The "usual" app_config.xml
Something like this (if i remember correctly):

<app_config>
    <app>
        <name>rosetta</name>
            <max_concurrent>X</max_concurrent>
    </app>
 </app_config>

(with X you can configure how many cores to use)

This won't block Boinc from downloading beta work, and it has no effect all all on the number of cores each task will use.. It will only limit it from running more than X Rosetta tasks simultaneously.

To control the number of cores a task uses, you need to include an <app_version> section in app_config.xml, like this:

<app_version>
        <app_name>ATLAS</app_name>
        <avg_ncpus>2</avg_ncpus>
        <plan_class>vbox64_mt_mcore_atlas</plan_class>
        <cmdline>--nthreads 2</cmdline>
    </app_version>

<avg_ncpus> tells Boinc that tasks will be running on 2 threads, while the cmdline parameter is passed to the program to tell it to do so.

If there were any way to tell Boinc not to download beta tasks, it would be in the cc_config.xml file. I see nothing in the user guide to suggest that is even possible. Therefore, since Rosetta itself does not distinguish between the "old' and beta tasks, it seems there is no way to block a client Boinc from downloading Rosetta beta tasks.