Minirosetta is currently running well on R@h with a 92% success rate but we would like to make it even better.

If you have experienced errors while running minirosetta and would like to help, we ask that you download our application symbols file on windows platforms so that we can get debugging information. Ideally, the windows symstore utilities that Rom Walton added to boinc would take care of this and automatically retrieve the symbols from our site but it doesn't seem to be working as it did before so we are asking for your help.

The file can be retrieved at:

https://ralph.bakerlab.org/download/minirosetta_1.07_windows_intelx86.pdb

Please place it in the ralph@home project directory of your BOINC installation usually located in 'c:/Program Files/BOINC/projects/ralph.bakerlab.org/'

Thanks in advance!

David K


edit: You can also place the symbols (pdb) file in the Rosetta@home project usually located in
'c:/Program Files/BOINC/projects/boinc,balerkab.org_rosetta/'


edit: The symbols file is 25MB.

---

Minirosetta is currently running well on R@h with a 92% success rate but we would like to make it even better.

If you have experienced errors while running minirosetta and would like to help, we ask that you download our application symbols file on windows platforms so that we can get debugging information. Ideally, the windows symstore utilities that Rom Walton added to boinc would take care of this and automatically retrieve the symbols from our site but it doesn't seem to be working as it did before so we are asking for your help.

The file can be retrieved at:

https://ralph.bakerlab.org/download/minirosetta_1.07_windows_intelx86.pdb

Please place it in the ralph@home project directory of your BOINC installation usually located in 'c:/Program Files/BOINC/projects/ralph.bakerlab.org/'

Thanks in advance!

David K


edit: You can also place the symbols (pdb) file in the Rosetta@home project usually located in
'c:/Program Files/BOINC/projects/boinc,balerkab.org_rosetta/'

We can't help much when you don't give us WUs.

I've only had 19 WUs since 5 Feb on 16 cores.

---

Please let us know if any of you are experiencing errors on either ralph or R@h and have downloaded the symbols file and placed it in the appropriate directories. I'll add more tests on ralph soon.

---

Can you put a larger number on as they are all taken up before before daylight reaches this side of the Atlantic - ie +0 hours Go Make Tea Time.

Does the Linux application not need debugging information as well? Or is it working ok?
I have recently done a couple that went ok on Linux, though much shorter in run time than my preferences.
I have also reported already a problem with a 'mini' WU that did not validate on my Windows machine, KSMarksPhych has also had the same problem, see following two threads

id 357
id 361

---

You could of told us before we downloaded that the file is over 25 MB in size.
What are the uploads likely to be?

---

Oh, shoot! I really meant to but just forgot. Sorry about that. Yeah, the symbol file is pretty big but you just have to download it once for each application version update. sorry again.

The validation bug was fixed in 1.07. There might be another validation bug but it is very very rare. I'm looking into it.

---

No work. Can't debug nothingingness.

---

...and don't forget to enable the mini .exe application in your firewall so that it can send in any dump of the symbol table enabled by downloading the PDB file.

---

First problem (or two)

Ralph (or the mini app) does not appear to honor the runtime preference set in Ralph Preferences

It also does not even recognize the preferences were changed. I had to change the General Preferences for a Boinc manager Update to recognize a change had been made and download new preferences. I still don't know if it has the correct run-time preference set. I configured it for 1 hour, and the "To Completion" in the Boinc Manager shows 5:24:14 for all tasks.

---

Out of work again?? Says there are 6000+ WU queued on the front page, and 10000+ on the server status page. Getting "no work available" messages.

<grump> Can't help if there's no work. </grump>

---

Out of work again?? Says there are 6000+ WU queued on the front page, and 10000+ on the server status page. Getting "no work available" messages.

<grump> Can't help if there's no work. </grump>

Are you still not getting WUs?

All the computers I have attached to Ralph are getting work and have warm and happy CPUs.....Intel, AMD, Windows and Linux, 32-bit and 64-bit.

---

Ralph (or the mini app) does not appear to honor the runtime preference set in Ralph Preferences. [... After] download new preferences. I still don't know if it has the correct run-time preference set. I configured it for 1 hour, and the "To Completion" in the Boinc Manager shows 5:24:14 for all tasks.

Is it just the "To Completion" in Boinc Manager or also the real runtime, which does not honour your prefs? What's your Duration Correction Factor? It seems that the run time estimate is "overestimated" and will be correct just when the DCF settles down.

For instance, my Pentium III has target run time 4 hours, DCF=0.15 and real runtime ~2:46 (average of 8 results, 2:18-3:31, 1-3 decoys). Other machine, C2D T7200 has target runtime 2 hours, DCF=0.29 and real runtime ~1:35 (average of 11 results 1:06-2:16, 1-6 decoys).

Peter

If your preferences did not get updated, then perhaps your runtime preference didn't update until later as well.

Your "to completion" really doesn't tell anyone if your runtime preference took effect or not. The behavior would be that the to completion time would be modified every 5 seconds, and that if your true preference were only an hour, then you'd see like 25 seconds knocked off the completion time with each update.

Once your preference is know, BOINC still uses the time it took your last WU to complete and adjusts the runtime it was sent from Ralph. That's why you have to look at the rate at which it is declining.

---

not sure if this is a problem but i just finished my first mini workunit had been runn slowly for 18and half hours and at 76% showing 8 hours to go about 5mins later to it finished and uploaded with success here the result https://ralph.bakerlab.org/result.php?resultid=747540

---

This WU failed on my system.

current minirosetta 1.07 status



We are still not getting any trace information for debugging so if you are getting errors please download and install our symbols file. See the first post of this thread.

If you use the NOD32 virus scanner w/ IMON (web access protection enabled), you can configure the web access protection to exclude the boinc.exe application from content filtering or add the download url(s) (ralph.bakerlab.org/download* for ralph and *.bakerlab.org/rosetta/download* for r@h) in the list of addresses to exclude. I haven't heard back from anyone at ESET about this issue.

edit: be sure to submit the virus detection for review back to ESET so that they could hopefully include this as a false positive in their databases.

---

This WU failed on my system.

we looked into that error and the only explanation is that the application can't see or open one of the input files. It is specific to your situation and is not a general error. without being able work on your computer, I can't really figure out what is happening. did a file get removed accidentally?

---

I aborted this one on mini 1.07:
It was stuck for over an hour at 92.912%

score13_hb_envtest62_A_1cg5B_3225_1018_0

work unit 665842

I aborted this one on mini 1.07:
It was stuck for over an hour at 92.912%

score13_hb_envtest62_A_1cg5B_3225_1018_0

work unit 665842

If you suspect another stuck work unit can you let it keep going for a while? at least a few times greater than your cpu run time preference.

---