"that crashed and burned"

I recall them to have been more of a flash in the pan.

---

Ralph appears to be fully functional now, so with a bit of luck we might get some new work there to test Rosetta 4.29 (and maybe even the Beta 6.06 application as well that crashed and burned everything that was sent out for it on it's fist try here).
While we're doing that, they can sort out the dead boinc-process server here.

Looks like i posted too soon- Ralph is MIA again.

---

Grant
Darwin NT

Looks like i posted too soon- Ralph is MIA again.

But server daemons on Rosetta has restarted...

---

Looks like i posted too soon- Ralph is MIA again.

But server daemons on Rosetta has restarted...

3 days is better than 3 weeks.

---

Grant
Darwin NT

Looks like i posted too soon- Ralph is MIA again.

But server daemons on Rosetta has restarted...

3 days is better than 3 weeks.

BOTH are better than I saw on Predictor@Home a few years ago,.

The two people who knew how to create workunits properly left that project about the same time.

That left a few people who couldn't do much more than set up more tries on workunits that have failed on all previous tries.

Some workunits reached 50 tries this way before the professor in charge of the project decided to shut the project down until they could start something more useful, but that didn't happen.

And Ralph is now back again, again.

---

Grant
Darwin NT

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.
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.

Are you sure? I used the xml file years ago and i remember it "reset" the project folder and started to download only the selected app.
But, probably, I remember wrong.

And, anyway, this is only attempts, until they decide to insert the possibility to choose in the user's profile...

---

Looks like i posted too soon- Ralph is MIA again.

But server daemons on Rosetta has restarted...

Having been away a couple of days before reading this, it reminded me to look at something that I suspected was missing.
It used to be that tasks that crashed out after running for a reasonable time were given partial credits as a result of a cleanup job that ran once daily.
A small but regular number of tasks have crashed among recent batches, so I've just checked and none of them are being given that partial credit any more.
Not a good thing.

---

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.
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.

Are you sure? I used the xml file years ago and i remember it "reset" the project folder and started to download only the selected app.
But, probably, I remember wrong.

And, anyway, this is only attempts, until they decide to insert the possibility to choose in the user's profile...

I am certain of this. There is no way in any file you can create or modify on your system that will determine whether or not you will be sent tasks for any particular app. That can only be done on the project website, and Rosetta does not give you any choice.

I am certain of this. There is no way in any file you can create or modify on your system that will determine whether or not you will be sent tasks for any particular app. That can only be done on the project website, and Rosetta does not give you any choice.

Agree, the best you can do is cut it down to running one at a time.

I am certain of this. There is no way in any file you can create or modify on your system that will determine whether or not you will be sent tasks for any particular app.

You can if the project supports anonymous platform.
The app_info.xml file contains the information for the applications that your system has, so you will receive work only for those applications & no others.

However, when using this method, you are then the one responsible for making any updates to the application/replacing the application with an updated one when the project comes out with a new version of the application you are using.
And if they come out with another application that you want to use, once again it's up to you to set it up on your system.

---

Grant
Darwin NT

I am certain of this. There is no way in any file you can create or modify on your system that will determine whether or not you will be sent tasks for any particular app.

You can if the project supports anonymous platform.
The app_info.xml file contains the information for the applications that your system has, so you will receive work only for those applications & no others.

Respectfully disagree. Take LHC, for example.
Suppose you are running ATLAS and CMS only, both are mentioned in your app_config.xml file for whatever reasons (number of CPUs per task, max number of tasks for that app, for example). You have never run THEORY tasks, and they are de-selected in your user preferences on LHC. Your client knows nothing about them.
If you now decide you wish to start running THEORY tasks, you need only enable them in your preferences on LHC; no other action is necessary. The next time your client calls in requesting new tasks, you will get them -- guaranteed.

app_info.xml and app_config.xml are different things.
With app_config you can't modify executable.
With app_info i could use YAFU 2.11 instead of 1.34, and make it use CADO-NFS.

Respectfully disagree. Take LHC, for example.
Suppose you are running ATLAS and CMS only, both are mentioned in your app_config.xml

Stop right there & read what you posted, and then read what i posted.

As kotenok2000 pointed out, i was talking about using app_info.xml to make use of the Anonymous Platform function.
app_config.xml is completely, totally and utterly different.

---

Grant
Darwin NT

Respectfully disagree. Take LHC, for example.
Suppose you are running ATLAS and CMS only, both are mentioned in your app_config.xml

Stop right there & read what you posted, and then read what i posted.

As kotenok2000 pointed out, i was talking about using app_info.xml to make use of the Anonymous Platform function.
app_config.xml is completely, totally and utterly different.

TIL.... this is the first time that I can recall anyone mentioning "anonymous platform".
My immediate reaction is to ask just what is the absolute minimum required to prevent Boinc from getting Rosetta beta tasks.

My immediate reaction is to ask just what is the absolute minimum required to prevent Boinc from getting Rosetta beta tasks.

Either the project adds the option in the users account, or they support the anonymous platform function, or BOINC make changes to the supported values for the max_concurrent option in app_config.xml to make it possible to limit the number to less than one (ie- 0),
Any one of those 3 would make it possible.

---

Grant
Darwin NT

Oh, what a surprise.
boinc-process is down again, so there's a Validation backlog once again that continues to grow.

---

Grant
Darwin NT

My immediate reaction is to ask just what is the absolute minimum required to prevent Boinc from getting Rosetta beta tasks.

Either the project adds the option in the users account, or they support the anonymous platform function, or BOINC make changes to the supported values for the max_concurrent option in app_config.xml to make it possible to limit the number to less than one (ie- 0),
Any one of those 3 would make it possible.

I was actually asking if there was some way to do it with the way things are now.

My immediate reaction is to ask just what is the absolute minimum required to prevent Boinc from getting Rosetta beta tasks.

Either the project adds the option in the users account, or they support the anonymous platform function, or BOINC make changes to the supported values for the max_concurrent option in app_config.xml to make it possible to limit the number to less than one (ie- 0),
Any one of those 3 would make it possible.

I was actually asking if there was some way to do it with the way things are now.

Nope.

---

Grant
Darwin NT

Oh, what a surprise.
boinc-process is down again, so there's a Validation backlog once again that continues to grow.

Well, boinc-process is alive again, but Ralph has died completely, again...

---

Grant
Darwin NT