Miracles do happen.
Sever Status page shows all servers back & green, and a bit under 5000 Tasks in progress- they probably released a small batch just to see if things are actually working...

And there is, also, a new Rosetta Beta app (6.06) for all platforms.
Waiting for work...

---

Rosetta Beta failing with computational errors on all machines. None have reported back yet so not sure what the specific error is at the moment.

Update:
<core_client_version>8.0.4</core_client_version>
<![CDATA[
<message>
process exited with code 1 (0x1, -255)</message>
<stderr_txt>
command: ../../projects/boinc.bakerlab.org_rosetta/rosetta_beta_6.06_x86_64-pc-linux-gnu @hal_8a_q_hal_8aa_3jp1226_d11_0001.flags -nstruct 10000 -cpu_run_time 28800 -boinc:max_nstruct 20000 -checkpoint_interval 120 -mute all -database minirosetta_database -in::file::zip minirosetta_database.zip -boinc::watchdog -boinc::cpu_run_timeout 36000 -run::rng mt19937 -constant_seed -jran 2618404
Extracting in project directory: database_f5ae1de8e1.zip
Using database: database_f5ae1de8e1/database

ERROR: Unable to find desired residue 'LEU' with variant 'SIDECHAIN_CONJUGATION'. Attempted to add target variant(s) to ResidueType using both ResidueType base name 'LEU' and base ResidueType. Was attempting to add new variant type 'SIDECHAIN_CONJUGATION'
ERROR:: Exit from: src/core/chemical/ResidueTypeSet.cc line: 980
BOINC:: Error reading and gzipping output datafile: default.out
09:49:38 (113459): called boinc_finish(1)

</stderr_txt>

Rosetta Beta failing with computational errors on all machines. None have reported back yet so not sure what the specific error is at the moment.

Same here, all errors on Windows.
Seems that this app is not tested enough on Ralph (that is down....)

---

Rosetta Beta failing with computational errors on all machines. None have reported back yet so not sure what the specific error is at the moment.

Same here, all errors on Windows.
Seems that this app is not tested enough on Ralph (that is down....)

Maybe they decided it would be too hard to fix Ralph and continue testing there, so they're doing the Alpha testing here now?

---

Grant
Darwin NT

No new tasks yet though.
I wonder if they've saved some tasks up for us during their downtime... (lol)

Oh ye of little faith.
Then again, might as well be none.

I had some robetta tasks come down and they all ran to successful completion, but all the Rosetta Beta 6.06 are dead ducks.

I noticed 1.6m tasks on the front page earlier today, but that's now down to zero, so I think it's safe to say the problem's been spotted, all tasks withdrawn and they'll think again.

We're not dead yet.
Well, not quite anyway...

---

Some more Robetta tasks have popped up in the meantime

---

All rosetta tasks so far today have failed within a few seconds or minutes with "computational error" and "output file... absent" in the log.

Win 11

Richard

Rosetta Beta failing with computational errors on all machines. None have reported back yet so not sure what the specific error is at the moment.

Same here, all errors on Windows.
Seems that this app is not tested enough on Ralph (that is down....)

Maybe they decided it would be too hard to fix Ralph and continue testing there, so they're doing the Alpha testing here now?

That wouldn't surprise me at all.

Maybe they decided it would be too hard to fix Ralph and continue testing there, so they're doing the Alpha testing here now?

That wouldn't surprise me at all.

And it's NOT a good idea.

---

ERROR: DPHE:N_Methylation:AcetylatedNtermConnectionProteinFull doesnt have connection at N
ERROR:: Exit from: src/core/conformation/Conformation.cc line: 1756
BOINC:: Error reading and gzipping output datafile: default.out
19:53:06 (7448): called boinc_finish(1)

This is a hal_8a_p_hal..... task. Everything out now on my system is a rb_08_****** task

Tasks with rb_08_16 and 17 are running good. 2:46 into a 8hr run and no problems so far.
and another at 1:50/8 hrs is also running good.

My hal_8a_p_hal.......... task crashed immediately, but that looks like old work.

I see there are a bunch of Beta 6.06 Tasks Ready to send as well as In Progress. However, the Average computing for those applications is still showing as 0 GigaFLOPS.
I'm thinking the Tasks, application or support files for those Tasks are still borked.

And the problem with that is when a Task errors out, it results in a delay being added to the next time the manager will contact the Scheudler. With every Task erroring out, you end up with multi-hour delays- the more cores/threads, the more Tasks that error out & the longer the delay (this is by design so that systems producing lots of errors don't end up doing a DoS (Denial of Service) attack on the Scheduler. The logic being that projects won't use their main project for alpha or beta testing their applications...). This also stops those systems from getting work that they could actually process OK until they can contact the Scheduler (unless the user iis prepared to sit there & hit update till all of the duds are cleared out).
End result- it is going to take a long time for all of these Tasks to finally clear from the system if the Project doesn't just pull them all now.

---

Grant
Darwin NT

I see there are a bunch of Beta 6.06 Tasks Ready to send as well as In Progress. However, the Average computing for those applications is still showing as 0 GigaFLOPS.
I'm thinking the Tasks, application or support files for those Tasks are still borked.

And the problem with that is when a Task errors out, it results in a delay being added to the next time the manager will contact the Scheudler. With every Task erroring out, you end up with multi-hour delays- the more cores/threads, the more Tasks that error out & the longer the delay (this is by design so that systems producing lots of errors don't end up doing a DoS (Denial of Service) attack on the Scheduler. The logic being that projects won't use their main project for alpha or beta testing their applications...). This also stops those systems from getting work that they could actually process OK until they can contact the Scheduler (unless the user iis prepared to sit there & hit update till all of the duds are cleared out).
End result- it is going to take a long time for all of these Tasks to finally clear from the system if the Project doesn't just pull them all now.

Depends on which beta you got..as I said..the hal_8 stuff is buggy. But I only got one. So if you have hal_8 take a hit and kill them. the rb_08_16 and 17 is clean. I am running those now. I am halfway through 2 of them with no problem.

This is the buggy stuff: https://boinc.bakerlab.org/rosetta/workunit.php?wuid=1407403018

Depends on which beta you got.

No, it doesn't- all of the Tasks for the Beta 6.06 application error out. The Rosetta 4.20 application Tasks are OK (other than the usual odd error).
They are 2 different sets of Tasks being processed by 2 different applications- Beta 6.06 v Rosetta 4.20.

---

Grant
Darwin NT

Depends on which beta you got.

No, it doesn't- all of the Tasks for the Beta 6.06 application error out. The Rosetta 4.20 application Tasks are OK (other than the usual odd error).
They are 2 different sets of Tasks being processed by 2 different applications- Beta 6.06 v Rosetta 4.20.

True, didn't notice that in the middle of the night.

Rosetta 29845 176784 7.01 (0.15 - 43.54) 4933
Rosetta Beta 18000 6699 ---- 0 <-- being withheld or because the errors are recirculating?

>All rosetta tasks so far today have failed within a few seconds or minutes with "computational error" and "output file... absent" in the log.

Al running OK now.

I see those were "beta" tasks. However, I do not see a way to prevent downloading them, is there?
Richard

I see those were "beta" tasks. However, I do not see a way to prevent downloading them, is there?
Richard

Not from your user profile in this site.
You can use, if you want, a configuration file in boinc manager...

---

I see those were "beta" tasks. However, I do not see a way to prevent downloading them, is there?
Richard

Not from your user profile in this site.
You can use, if you want, a configuration file in boinc manager...

Richard - your just unlucky right now. Your getting buggy tasks that have to run through two computers to be flagged as buggy. Your just the lucky wingman in this case.

Just let the server do its thing, eventually you will get clean work.

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? I don't think so. The beta will soon be done. It looks like nothing new is being sent out. 12,680 tasks was where beta was last night at this time. So you should get clean 4.20 soon.

Old news are threads are still not readable.

https://boinc.bakerlab.org/rosetta/forum_forum.php?id=202&sort=5&start=150

Old news are threads are still not readable.

https://boinc.bakerlab.org/rosetta/forum_forum.php?id=202&sort=5&start=150

You have to click the page # below and you can read them...or at least I can.
This link you posted goes to page 4.
The link direct does not work, but if you manually go to page 4 you can see whats going on.