Unrecognized XML in parse_init_data_file: fraction_done_update_period
Skipping: 1.000000
Skipping: /fraction_done_update_period

Linux Boinc 6.2.4, t405__CASP8_JUMPAB_TYPE2_RES81to192_SAVE_ALL_OUT_BARCODE__4233_55_0: task got stuck at 100% and around 3 1/2 hour CPU time, for half day long, after restarting the client progress jumped to 48% and two hours CPU time. Preference is set to 2 hours.

I'll try to let it finish.

... "Maximum disk usage exceeded + ERROR:: Exit from: .refold.cc line: 338", etc. Few debugging outputs.

Once I've noticed in the logs "Aborting task t419N_autoalign_IGNORE_THE_REST_renumbered_4290_6_0: exceeded disk limit: 531.22MB > 476.84MB" - the disk space isue seems to be my fault, the free disk space went down to approx. my BOINC "leave xxxx free" preference. But still the "Report to Microsoft" dialogs should not appear.

WARNING: refold called with uninit torsions
I still copied your coordinates into misc::, hope that was the right thing to do!
WARNING: refold called with uninit torsions
I still copied your coordinates into misc::, hope that was the right thing to do!
WARNING: refold called with uninit torsions
I still copied your coordinates into misc::, hope that was the right thing to do!
...

Same here. All my 't419N' WU's are failing.

<core_client_version>6.2.4</core_client_version>
<![CDATA[ - exit code -1073741819 (0xc0000005)
<stderr_txt>
# cpu_run_time_pref: 7200
# random seed: 1181096

Unhandled Exception Detected...
- Unhandled Exception Record -
Reason: Access Violation (0xc0000005) at address 0x7C911669 read attempt to address 0x00000000
Engaging BOINC Windows Runtime Debugger...

</stderr_txt>
]]>

A slight improvement on this one. This is the first version with any graphics, I can see the text now but still no picture of the atom.

I could already see the minirosetta's texts many versions ago (with BOINC 6.2.x), but similarly with no pictures (which were OTOH available while using BOINC 5.10.45).

A slight improvement on this one. This is the first version with any graphics, I can see the text now but still no picture of the atom.

Unfortunately, my first 1.26 WU failed.

Incorrect function. (0x1) - exit code 1 (0x1)

fragment reading error -- pdb, chain and seqpos mismatch
position: 66; neighbor: 187; line: 2

ERROR: Cannot open file aaT0396_1JR8A_1_0001.pdb
ERROR:: Exit from: ....srccoreiopdbpose_io.cc line: 157

In light of the recent difficulties with memory leaks in Rosetta Mini 1.1x, especially those leaks that took upwards of 20 hours to cause a failure, would it be appropriate to increase the default runtime?

Here's a new one:

ERROR: Cannot open 9-mer fragment library file: 9merfile

process exited with code 1 (0x1, -255)
ERROR: Cannot open 9-mer fragment library file: 9merfile
ERROR:: Exit from: src/protocols/frags/TorsionFragment.cc line: 70

Another compute error to report, although this one needed only 20 seconds to error out.

<message>
process exited with code 1 (0x1, -255)
</message>
<stderr_txt>
WARNING: Override of option -out:nstruct sets a different value

</stderr_txt>

...is it better to prefer testing larger number of workunits (producing less decoys for each one, 1-5), or rather somewhat more decoys (5-15-...) from each WU, at the expense of the number of tested WUs?

This one mini_abinitio-1bk2_-test_2008-2-6_3310_73_0 shows peak memory of 867MB! It's 17hrs in to a 24hr runtime preference on WinXP.

Memory does not seem to be growing without bounds (i.e. no memory leak), just seems to use a lot, then free it again at various times as it runs.

The new version (v1.12) is now released. Post bugs here!

The 2 v1.12 had the same error I had before on v1.10 & 1.11, running Linux.

Same problem for me also.

So I was just wondering...

Would it be better for RALPH to have a bigger cpu run time per WU? Is the default 1 hour run time enough for testing or would it be better for me to raise it up by few hours?
I was just figuring that since this project is focusing on error detection etc., is it really useful to run the WU's longer than the deafault 1 hour?

We would prefer lower run times so that results are returned quicker.

Message from server: No work sent (there was work but you don't have enough disk space allocated)
Message from server: Not enough disk space (only 393.9 MB free for BOINC). Review preferences for maximum disk space used.

unzip:  cannot find zipfile directory in one of minirosetta_database_rev20940.zip or
        minirosetta_database_rev20940.zip.zip, and cannot find minirosetta_database_rev20940.zip.ZIP, period.

Edith says:
I just looked in the projects directory and found the missing .zip, inly a second .ZIP was missing ;). In the described thread in there was the residue_types.txt, but if the stupid minirosetta looks for a double-zipped file, it can't find any of course.
Opening the .zip was no problem

$ unzip -v archive
unzip:  cannot find or open archive, archive.zip or archive.ZIP.

When the new pdb symbols file like http://ralph.bakerlab.org/download/minirosetta_1.09_windows_intelx86.pdb will become available...

The 1.09 version is available now...48MB!