My host seems to have run the 2257's the past day or so without incident.
https://boinc.bakerlab.org/rosetta/show_host_detail.php?hostid=656908

This one ran well over my run time, even after i reduced it from

8hrs to 6hrs for faster turn round. It had run over the 8hr mark.

2fqm__BOINC_SYMM_FOLD_AND_DOCK_RELAX-2fqm_-crystal_foldanddock__2257_17546_0

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=107955094

pete.

---

Client error 2reb__TREEJUMP_ABRELAX_TOR_EQ_-1_PROB_.1_SAVE_ALL_OUT-2reb_-_BARCODE__2244_6092_1
119063108

---

Jmarks

could someone look at why i have all these errors ???????

could someone look at why i have all these errors ???????

Try restarting your PC.

---

Jmarks

ok thanks ill try it.......

This is just a heads up that tons of MFR_SYMM_FOLD_AND_DOCK_RELAX units are erroring out AFTER crunching for a full runtime, which is annoying. It also errored out for people who got the unit after mine errored out.

Just a heads up!

edit: This isn't just one computer of mine but many different computers, not to mention that other people errored when they got the same unit. So it's not just a faulty computer on my end!

---

I use Show Graphics in Boinc Manager on application version 5.81 and after an little time i closed the window.
This causes an error of the Result with the following error message:
<core_client_version>5.10.28</core_client_version>
<![CDATA[
<message>
- exit code 1073807364 (0x40010004)
</message>
<stderr_txt>
# cpu_run_time_pref: 10800
# random seed: 3802685

</stderr_txt>
]]>

resultid=119553269

Matthias

---

Matthias

1) I note that the "explain" item does not document what a "Compute Error" is....

2) Work unit 106606679
1n0u__TREEJUMP_ABRELAX_NOTOR-1n0u_-_BARCODE__2241_1083
Appears to have failed on two different machines.

Seems like 2nd time that this has happened to me recently... other job was WU 106970621:
2reb__TREEJUMP_ABRELAX_TOR_EQ_-5_PROB_.5_SAVE_ALL_OUT-2reb_-_BARCODE__2243_7638_0

This looks like a programming issue on both counts
in same routine (ERROR:: Exit from: .pose.cc line: 769)
Or, there is a issue with software running
processes on my machine.

---

I got a Client/Compute error for result 119600589. The workunit it is for, MFR_SYMM_FOLD_AND_DOCK_RELAX_GB1_mutant_2286_166, apparently failed previously for someone else, but with a Validate error instead.

This is just a heads up that tons of MFR_SYMM_FOLD_AND_DOCK_RELAX units are erroring out AFTER crunching for a full runtime, which is annoying. It also errored out for people who got the unit after mine errored out.

Just a heads up!

edit: This isn't just one computer of mine but many different computers, not to mention that other people errored when they got the same unit. So it's not just a faulty computer on my end!

I'd agree with that - I haven't had a single MFR_SYMM_FOLD_AND_DOCK_RELAX WU that's worked; they all fail with a -161 error after completion.

Here is one that errored out after 2 runs, neither received credit:

MFR_SYMM_FOLD_AND_DOCK_RELAX_GB1_mutant_2286_18566

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=108650563

And for what it's worth, this is still one of the lowest granting projects, for time computed....

Might be time for a credit adjustment, I only crunch this now when other projects are down. Crunching this project for 2-5 times less credit than others is just unacceptable for a credit counter like me, trying to keep up with the other members of my team. Sorry but I cannot afford to buy 3-5 quads to crunch whatever I want, I have to pick and choose now.

And to all you cross project parity people that IMO screwed this project up....

Have you figured out this is impossible........ just MO

Will not be responding to the naysayers..JMO

---

BETA = Bahhh

Way too many errors, killing both the credit & RAC.

And I still think the (New and Improved) credit system is not ready for prime time...

I'm still having intermittent problems with some work-units never completing. The latest is WU "2p64_BOINC_SYMM_FOLD_AND_DOCK_RELAX_2p64_-crystal_foldanddock_2257_389...".
It has been sitting on CPU Time: 03:05:31 Progress: 94.885% for the last hour.
I will abort it now.

Geoff

---

PPC Mac G5 dual 1.8GHz, 3GB Ram, Mac OSX 10.5
BOINC Manager 5.10.28
Rosetta Beta 5.81

Yep, I've had several MFR_SYMM_FOLD_DOCK_AND_RELAX errors. For example:

• MFR_SYMM_FOLD_AND_DOCK_RELAX_GB1_mutant_2286_593
  
• MFR_SYMM_FOLD_AND_DOCK_RELAX_GB1_mutant_2286_5972 (some other poor soul is trying their luck crunching it now)
  
• MFR_SYMM_FOLD_AND_DOCK_RELAX_GB1_mutant_2286_12146
  

While this may be helpful to other project participants, I'm honestly not sure why we need to list these here for the project... I would think the project could simply query the database for this sort of information. If not, let me know and I'll try to help with that.

cheers,
/trey

Detaching now way tooooo many errors for 0 credit.....Get your act together.

Every rig now has errors...

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=108626751

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=108637515

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=108635707

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=108622177

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=108641769

https://boinc.bakerlab.org/rosetta/workunit.php?wuid=108632329

C'mon....

---

BETA = Bahhh

Way too many errors, killing both the credit & RAC.

And I still think the (New and Improved) credit system is not ready for prime time...

This is just a heads up that tons of MFR_SYMM_FOLD_AND_DOCK_RELAX units are erroring out AFTER crunching for a full runtime {...}

Add me to the list of those bit by the MFR_SYMM_FOLD etc. bug.

WU 108617269

---

Rosie, Rosie, she's our gal,
If she can't do it, no one shall!

im getting bummed out with all these errors :(

I looked for this thread after seeing a batch of computation errors on different workstations -- useful information (albeit all user to user and no Rosetta admin input here). Just went around and aborted all my MFR_SYMM_FOLD workunits (I found about 10 to 15 of them locally). Of course the downside is until there is admin awareness of the problems with this set of work units, they will simply get recycled. If someone can get the attention of the admin folks at Rosetta, perhaps they can purge the outgoing database so that these bad boys don't simply recycle in the user universe.

This is just a heads up that tons of MFR_SYMM_FOLD_AND_DOCK_RELAX units are erroring out AFTER crunching for a full runtime {...}

Add me to the list of those bit by the MFR_SYMM_FOLD etc. bug.

WU 108617269

---

Validation error.
MFR_SYMM_FOLD_AND_DOCK_RELAX_GB1_mutant_2286_7049_1119565586

---

Jmarks

13-Nov-2007 23:25:30 [rosetta@home] Computation for task MFR_SYMM_FOLD_AND_DOCK_RELAX_GB1_mutant_2286_7378_0 finished
13-Nov-2007 23:25:30 [rosetta@home] Output file MFR_SYMM_FOLD_AND_DOCK_RELAX_GB1_mutant_2286_7378_0_0 for task MFR_SYMM_FOLD_AND_DOCK_RELAX_GB1_mutant_2286_7378_0 absent

This WU reported 13 Nov 23.44.32 as 'Validate Error' and resent to computer 596025 13 Nov 23.45.24.

Wishes the new cruncher all the best!!

---