same error here:

<core_client_version>6.2.19</core_client_version>
<![CDATA[
<message>
Unzul�ssige Funktion. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>

ERROR: in::file::zip minirosetta_database.zip does not exist!
ERROR:: Exit from: ....srcappspublicboincminirosetta.cc line: 74
called boinc_finish

</stderr_txt>
]]>

https://boinc.bakerlab.org/rosetta/result.php?resultid=203982392

---

Same error:

<core_client_version>6.2.19</core_client_version>
<![CDATA[
<message>
Unzul�ssige Funktion. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>

ERROR: in::file::zip minirosetta_database.zip does not exist!
ERROR:: Exit from: ....srcappspublicboincminirosetta.cc line: 74
called boinc_finish

</stderr_txt>
]]>

https://boinc.bakerlab.org/rosetta/result.php?resultid=204064551

over 100 unit with !

<core_client_version>6.2.19</core_client_version>
<![CDATA[
<message>
Niepoprawna funkcja. (0x1) - exit code 1 (0x1)
</message>
<stderr_txt>

ERROR: in::file::zip minirosetta_database.zip does not exist!
ERROR:: Exit from: ....srcappspublicboincminirosetta.cc line: 74
called boinc_finish

</stderr_txt>
]]>

not nice

Hm, looks like a general problem with the WU or the client. Ane if you follow up some WUs, there are client errors all over the place.

I wonder, how long the servers can handle the load. More and more clients will run out of 'good' WUs...

Just my 2 cents...

Joe

---

something different.

When looking at the graphics of 1irnA_ZNMP_ABRELAX_tetraR_IGNORE_THE_REST_ZINC_METALLOPROTEIN-1irnA-_4653_1986_0 it shows me about 10 moves and then closes the graphics window.

I can reopen it and then it does this again. Never seen it happen like this before 1.39

Beginning 31 October 20:35 UTC and continuing, every work unit with the application "Rosetta Mini with new score terms" has errored out after less than one second of cpu time. Over 20 work units involved. Work units with the application "Rosetta Mini" are computing without error; approximately 20 units.
Obviously there is a problem, unfortunately. Access my account in any way you wish to evaluate the problem(s). Bill

3 fresh WUs, v1.39, computation error after 14-40 minutes.

02.11.2008 15:21:00|rosetta@home|Computation for task abinitio_nohomfrag_70_A_1jfvA_4466_83424_0 finished
02.11.2008 15:21:00|rosetta@home|Output file abinitio_nohomfrag_70_A_1jfvA_4466_83424_0_0 for task abinitio_nohomfrag_70_A_1jfvA_4466_83424_0 absent
02.11.2008 15:21:00|rosetta@home|Starting abinitio_nohomfrag_70_A_2uzrA_4466_83276_0
02.11.2008 15:21:00|rosetta@home|Starting task abinitio_nohomfrag_70_A_2uzrA_4466_83276_0 using minirosetta version 139
02.11.2008 15:25:41|rosetta@home|Computation for task abinitio_nohomfrag_70_A_2uzrA_4466_83276_0 finished
02.11.2008 15:25:41|rosetta@home|Output file abinitio_nohomfrag_70_A_2uzrA_4466_83276_0_0 for task abinitio_nohomfrag_70_A_2uzrA_4466_83276_0 absent
02.11.2008 15:25:41|rosetta@home|Starting abinitio_nohomfrag_70_A_1unpA_4466_83485_1
02.11.2008 15:25:41|rosetta@home|Starting task abinitio_nohomfrag_70_A_1unpA_4466_83485_1 using minirosetta version 139
02.11.2008 15:42:03|rosetta@home|Computation for task abinitio_nohomfrag_70_A_1unpA_4466_83485_1 finished
02.11.2008 15:42:03|rosetta@home|Output file abinitio_nohomfrag_70_A_1unpA_4466_83485_1_0 for task abinitio_nohomfrag_70_A_1unpA_4466_83485_1 absent

My Minirosetta calcs run fine up to about 94-95% completion when it slows dramatically and the final 5-6% taking a couple of hours or more to complete. Any ideas?

---

My Minirosetta calcs run fine up to about 94-95% completion when it slows dramatically and the final 5-6% taking a couple of hours or more to complete. Any ideas?

Sounds normal for the complex proteins. Look carefully at the graphics and you will see occasional small movements in the side chains and the steps moving up slowly.

---

My Minirosetta calcs run fine up to about 94-95% completion when it slows dramatically and the final 5-6% taking a couple of hours or more to complete. Any ideas?

Sounds normal for the complex proteins. Look carefully at the graphics and you will see occasional small movements in the side chains and the steps moving up slowly.

OK - thanks. Makes a mockery of the "Time to Completion" estimate though . . .

---

The graphics application in 1.39 is very, very unstable. I rarely get the graphics to stay on. For most of the time, they shut down almost immediately. Thankfully the work unit goes on.

I'm using Boinc 6.2.19 on Windows XP SP3, and not utilising the safe mode (for compatibility with older applications' graphics, not that it probably matters much in this respect).

My Minirosetta calcs run fine up to about 94-95% completion when it slows dramatically and the final 5-6% taking a couple of hours or more to complete. Any ideas?

Sounds normal for the complex proteins. Look carefully at the graphics and you will see occasional small movements in the side chains and the steps moving up slowly.

Oh, I had the same last time. Unfortunately it looked like a bit different - I've turned the graphical application on on something like 95% - and than I saw: Model 1, step around 30,000 (and increasing fast) and the early stage of the process - big, "classical" movements.

It looked like a restart or some other "trajectory". What is more, the client was behaving in a different manner than described on the help sites. It did not keep the lowest energy found as a "low energy" state but had some other preferences.

The graphics application in 1.39 is very, very unstable. I rarely get the graphics to stay on. For most of the time, they shut down almost immediately. Thankfully the work unit goes on.

I've noticed the same thing

---

Have a crunching good day!!

The graphics application in 1.39 is very, very unstable. I rarely get the graphics to stay on. For most of the time, they shut down almost immediately. Thankfully the work unit goes on.

I've noticed the same thing

Same here.

---

I haven't noticed any graphics instability with the with 1.39 with the 15 work units I have done/doing today. I have XP (service pack 3) using BOINC 6.2.19

---

I haven't noticed any graphics instability with the with 1.39 with the 15 work units I have done/doing today. I have XP (service pack 3) using BOINC 6.2.19

I think it is related to the Zink-Workunits. Other workunits do not seem to be affected.

---

I haven't noticed any graphics instability with the with 1.39 with the 15 work units I have done/doing today. I have XP (service pack 3) using BOINC 6.2.19

I think it is related to the Zink-Workunits. Other workunits do not seem to be affected.

see my post which I identified one Zinc work unit that the graphics cut out on me. See if you have a matching or similar named task.

These zinc tasks are causing all kinds of fun problems for the team to explore.

Not sure if this actually belongs here, but nevertheless:

I just noticed that the low energy value in the screensaver jumps to a higher value at times.
Is that intended?

Edit: I wouldn't have posted this if that had happened when the computation of a new model started.

I'm having many WU's with this message

--> https://boinc.bakerlab.org/rosetta/result.php?resultid=204831583

What I have to do?