minirosetta is updated to add new protocols for symmetrical oligomers and membrane proteins.

Here is some more information about Oligomers and Membrane proteins from Wikipedia for those who are interested. If I hang around these forums for another 20 years I might learn enough Biochemistry to consider a pre-retirement career change.

---

Does this version ignore the limit of 100 models per workunit?

I have a workunit which has reached 300 models and another has done 200. Both are only about 20% complete.

---

Warped

The 100 model limit is only for certain protocols that are expected to complete models very rapidly. The main reason (to my knowledge anyway) for the imposition of that limit was due to large upload file sizes. Do you happen to know how large the uploads are getting? Size is shown in the transfers tab. But you'd have to catch one before it is sent (suspend network activity for a short time until one completes would be a simple way to orchestrate keeping one around).

---

Rosetta Moderator: Mod.Sense

Thanks for the response, Mod.Sense. My concern was that I had workunits which needed to be aborted.

I have some time yet before my first 2.15 task completes as I have selected a 10-hour run time option.

I'll try to catch the upload but may miss it.

The upload is only 231KB, which is insignificant.

Today i had me first WU https://boinc.bakerlab.org/rosetta/workunit.php?wuid=333863670 with V2.15, i see 1,1GB memmory beeing used, is this normal? And if so, why does is say 512MB minimal memmory requirment on the site?

I have 4 GB machine but with 2 other WU form other projects that exceed 1GB memory requirments, i have to start watching these mmemory requirments to stil do normal work with the machine.

---

I have this WU which uses about 900 MB of RAM, but cpu usage is down to 0%:
T0611_t4_rs_stg0_lrlxjcst_t000__casp9_SAVE_ALL_OUT_22276_368_0

Yesterday I had a WU with the exact same behaviour, eating lots of RAM, but no cpu use, so it must have crashed or something... Pausing and resuming does not fix the problem by the way.

This one crashed yesterday after 40 minutes:
T0528_t4_rs_stg0_lrlxjcst_t000__casp9_SAVE_ALL_OUT_22246_78_0

When it crashed the memory consumption was 1.5 GB. The message says 'Directory not found'.

<message>
Das System kann den angegebenen Pfad nicht finden. (0x3) - exit code 3 (0x3)
</message>

---

Yeah, I have one Rosetta processing using 1.5 Gb of RAM at 2.3% completion and another using 1.15 Gb of RAM at 16% completion. All together Rosetta is using 70% of my 8 gigs of RAM. Granted I have a 6-core processor and therefore 6 threads running, but still, that's a lot of RAM.

The biggest RAM hogs currently, are named T0523_t4_rs_stg0_lrlxjcst_t000_casp9_SAVE_ALL_OUT_22242_375_0 and
T0520_t4_rs_stg0_lrlxjcst_t000_casp9_SAVE_ALL_OUT_22239_376_0


I was away for the weekend. Looking back at my results I show over 20 results that ended as "Compute Error" since 2.15, most of which came Friday or after. Never had one Compute Error in any work unit before that.

---

I also appear to be having problems with WU's starting with T05**. They end up using almost 1.3GB of RAM.

I also appear to be having problems with WU's starting with T05**. They end up using almost 1.3GB of RAM.

I think i have a problem with the T0549_t4_rs_stg0_lrlxjcst_t000__casp9_SAVE_ALL_OUT_22255_997
he run since 21 hours and reach 0.099% when i look at the properties, the calculating time is only 25 second !!!

T0605_t2_rs_stg0_lrlxjcst_t000__casp9_SAVE_ALL_OUT_22177_296_1
ERROR: Error in traceback: pointer doesn't go anywhere!

ERROR:: Exit from: ....srccoresequenceAligner.cc line: 79
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

T0605_t2_rs_stg0_lrlxjcst_t000__casp9_SAVE_ALL_OUT_22177_1921_0
RROR: Error in traceback: pointer doesn't go anywhere!

ERROR:: Exit from: ....srccoresequenceAligner.cc line: 79
BOINC:: Error reading and gzipping output datafile: default.out
called boinc_finish

T0528_tj_rs_stg0_lrlxjcst_t000__casp9_SAVE_ALL_OUT_21880_4843_2
<core_client_version>6.10.58</core_client_version>
<![CDATA[
<message>
The system cannot find the path specified. (0x3) - exit code 3 (0x3)
</message>

I think i have a problem with the T0549_t4_rs_stg0_lrlxjcst_t000__casp9_SAVE_ALL_OUT_22255_997
he run since 21 hours and reach 0.099% when i look at the properties, the calculating time is only 25 second !!!

Ademers, double check the status shown in BOINC for that task. Does BOINC say it is "running"? And does the task manager show some other, higher priority task consuming your available CPU?

But otherwise that sounds like another issue that we see crop up once and a while. Best way to move it along seems to be to exit (not close) and restart BOINC.

---

Rosetta Moderator: Mod.Sense

I think i have a problem with the T0549_t4_rs_stg0_lrlxjcst_t000__casp9_SAVE_ALL_OUT_22255_997
he run since 21 hours and reach 0.099% when i look at the properties, the calculating time is only 25 second !!!

Ademers, double check the status shown in BOINC for that task. Does BOINC say it is "running"? And does the task manager show some other, higher priority task consuming your available CPU?

But otherwise that sounds like another issue that we see crop up once and a while. Best way to move it along seems to be to exit (not close) and restart BOINC.

Good, I exit from BOINC and restart and the application is at 1.8% in 7 minutes and continue to go up !!!

Thank you Mod.Sense

This one failed after 20sec.

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

T0524_t3_rs_stg0_lrlxjcst_t000__casp9_SAVE_ALL_OUT_22207_1756_0

<core_client_version>6.2.14</core_client_version>
<![CDATA[
<message>
process got signal 11
</message>
<stderr_txt>

---

I too am seeing an unusually high number of errors on 3 different machines (and 3 different operating systems) for Rosetta 2.15. 16 WU's in the last few days failed on various errors:

"The system cannot find the path specified. (0x3) - exit code 3 (0x3)"

"Reason: Access Violation (0xc0000005) at address 0x00581B5C write attempt to address 0x00000024"

"Incorrect function. (0x1) - exit code 1 (0x1)" (many different root causes per detailed error messages in the log. <ERROR: Error in traceback: pointer doesn't go anywhere!> occurred multiple times.)

"Reason: Out Of Memory (C++ Exception) (0xe06d7363) at address 0x759AB727"

I am repeatedly getting this message since the upgrade:

"Microsoft Visual C++ Runtime Library

Runtime Error

....Bakerlab.orgminirosetta_2.15_windows_intelx86.exe

This application has requested the Runtime to terminate it in an unusual way. Please contact the application's support team for more information."

It is difficult to remove the message which sometimes locks up the computer. What can be done to prevent this?

+1 to problems with "Txxxx_" tasks on minirosetta 2.15.
Some of them crash and others consume very higt amount of RAM (like 800-1400 Mb per task)
I think crashes was due to lack of memory too - when two such tasks run concurrently (have 2 Gb of RAM on 2 core CPU)

I too have recently seen messages indicating shortage of virtual memory, so have suspended Rosetta.

---