j2satx,

Did you download the 1.07 mini app symbols file into your ralph project directory? I see an access violation error from one of your computers but do not see any trace information.

I downloaded 1.07 to all the computers I had attached to Ralph.

However, now that you mention it........I added many more computers today after I noticed WUs were avail on Ralph and I forgot to download 1.07 to those new computers. I will do that in the next hour.

Might not need it now........all the WUs on Ralph are gone already........!!

j2satx,

Did you download the 1.07 mini app symbols file into your ralph project directory? I see an access violation error from one of your computers but do not see any trace information.

I downloaded 1.07 to all the computers I had attached to Ralph.

However, now that you mention it........I added many more computers today after I noticed WUs were avail on Ralph and I forgot to download 1.07 to those new computers. I will do that in the next hour.

Might not need it now........all the WUs on Ralph are gone already........!!

I'll add some more, just let me know when it's best for you.
thanks!

edit:

did this task have the symbols file? It hope it works as expected. I wonder if it needs to be in the slot directory? I don't think it does.
http://ralph.bakerlab.org//result.php?resultid=746732

j2satx,

Did you download the 1.07 mini app symbols file into your ralph project directory? I see an access violation error from one of your computers but do not see any trace information.

I downloaded 1.07 to all the computers I had attached to Ralph.

However, now that you mention it........I added many more computers today after I noticed WUs were avail on Ralph and I forgot to download 1.07 to those new computers. I will do that in the next hour.

Might not need it now........all the WUs on Ralph are gone already........!!

I'll add some more, just let me know when it's best for you.
thanks!

edit:

did this task have the symbols file? It hope it works as expected. I wonder if it needs to be in the slot directory? I don't think it does.
http://ralph.bakerlab.org//result.php?resultid=746732

I'll check on that result...

I think I have 1.07 on all the Windows machines now.

You can throw a few thousand WUs over the fence right now.

j2satx,

Did you download the 1.07 mini app symbols file into your ralph project directory? I see an access violation error from one of your computers but do not see any trace information.

I downloaded 1.07 to all the computers I had attached to Ralph.

However, now that you mention it........I added many more computers today after I noticed WUs were avail on Ralph and I forgot to download 1.07 to those new computers. I will do that in the next hour.

Might not need it now........all the WUs on Ralph are gone already........!!

I'll add some more, just let me know when it's best for you.
thanks!

edit:

did this task have the symbols file? It hope it works as expected. I wonder if it needs to be in the slot directory? I don't think it does.
http://ralph.bakerlab.org//result.php?resultid=746732

The computer that ran 746732 was one I added today without adding the 1.07.

It's a dual-core AMD with Windows XP X64.

1.07 was added moments ago.

Okay, great. I'll add some more jobs on ralph.

j2satx,

Did you download the 1.07 mini app symbols file into your ralph project directory? I see an access violation error from one of your computers but do not see any trace information.

I downloaded 1.07 to all the computers I had attached to Ralph.

However, now that you mention it........I added many more computers today after I noticed WUs were avail on Ralph and I forgot to download 1.07 to those new computers. I will do that in the next hour.

Might not need it now........all the WUs on Ralph are gone already........!!

I'll add some more, just let me know when it's best for you.
thanks!

edit:

did this task have the symbols file? It hope it works as expected. I wonder if it needs to be in the slot directory? I don't think it does.
http://ralph.bakerlab.org//result.php?resultid=746732

The computer that ran 746732 was one I added today without adding the 1.07.

It's a dual-core AMD with Windows XP X64.

1.07 was added moments ago.

One thing i noticed on the few tasks i've done is the progress % doesn't

move for the first 20 to 30 min, then jumps up to 5% or so then it

seems fine after that. I guess it could be the type of workunit.

pete.

---

Depending on where you look on Ralph, there are 6000+ or 10,000+ WUs queued, but I'm getting "no work available" messages.

---

Proudly Banned from Predictator@Home and now Cosmology@home as well. Added SETI to the list today. Temporary ban only - so need to work harder :)



"You can't fix stupid" (Ron White)

I hope this helps. I'm trying to respond to everyones comments and provide useful info.

It does help and it is very much appreciated.

Thank you!

---

Team Helix

Here is a comparison of the status reports (note, we are not planning to support PPC macs with mini):

I have been waiting for this information. Now, if we could get some hints whether Rosetta (5.93 or its successors) will still support the PPC platform, or you plan to phase it out in the foreseeable future...

..... We should take that out of the name since it isn't a beta app and is misleading.

Please do.
Thanks for the explanation on why you pulled mini back.

---

Here is a comparison of the status reports (note, we are not planning to support PPC macs with mini):

I have been waiting for this information. Now, if we could get some hints whether Rosetta (5.93 or its successors) will still support the PPC platform, or you plan to phase it out in the foreseeable future...

We'll still support the PPC platform for the old rosetta app, at least until the PPC macs in our lab die.

Depending on where you look on Ralph, there are 6000+ or 10,000+ WUs queued, but I'm getting "no work available" messages.

I don't know why when there is plenty of work. Still having issues? maybe a reset will help.

?

---

Nemesis n. A righteous infliction of retribution manifested by an appropriate agent.

my Pc works slowly with mini 1.07 ,and the wu fails sometimes.Now,my machine works again 5.93 and all is ok.sorry 4 my traslation.S@ludos from spain

On Win XP SP2, Boinc 5.10.42, my Rosetta Mini 1.07 score13_hb_envtest62_A_1ig5A_2908_3409_0 task was preempted (and left in memory) after 00:15:35 CPU time, 6.226%, 04:33:13 more to go. It was later resumed after another task finished, but did not continue to crunch, but consumed zero CPU time. I've suspended the task for the time being. ... Few minutes later it ws terminated by the client.

Looking at the logs, the task's history is deeper. It was twice preempted, once restarted because of client upgrade and complained twice on "Task exited with a DLL initialization error. If this happens repeatedly you may need to reboot your computer." (Might be because a reboot is pending here because of finished automatic Windows upgrade un Tuesday?)

09:30:49 [rosetta@home] Starting score13_hb_envtest62_A_1ig5A_2908_3409_0
09:30:49 [rosetta@home] [cpu_sched] Starting score13_hb_envtest62_A_1ig5A_2908_3409_0 (initial)
09:30:49 [rosetta@home] [task_debug] task_state=EXECUTING for score13_hb_envtest62_A_1ig5A_2908_3409_0 from start
09:30:49 [rosetta@home] Starting task score13_hb_envtest62_A_1ig5A_2908_3409_0 using minirosetta version 107
09:47:09 [rosetta@home] [task_debug] result score13_hb_envtest62_A_1ig5A_2908_3409_0 checkpointed
09:55:53 [---] Exit requested by user
09:55:53 [rosetta@home] [task_debug] task_state=EXITED for score13_hb_envtest62_A_1ig5A_2908_3409_0 from has_task_exited
10:01:34 [---] Starting BOINC client version 5.10.42 for windows_intelx86
10:02:09 [rosetta@home] [cpu_sched] Starting score13_hb_envtest62_A_1ig5A_2908_3409_0(resume)
10:02:09 [rosetta@home] [task_debug] task_state=EXECUTING for score13_hb_envtest62_A_1ig5A_2908_3409_0 from start
10:02:09 [rosetta@home] Restarting task score13_hb_envtest62_A_1ig5A_2908_3409_0 using minirosetta version 107
(at this moment, ALL tasks exited, I suppose a client error?)
10:03:06 [rosetta@home] [task_debug] Process for score13_hb_envtest62_A_1ig5A_2908_3409_0 exited
10:03:06 [rosetta@home] Task score13_hb_envtest62_A_1ig5A_2908_3409_0 exited with a DLL initialization error.
10:03:06 [rosetta@home] If this happens repeatedly you may need to reboot your computer.
10:03:06 [rosetta@home] [task_debug] task_state=UNINITIALIZED for score13_hb_envtest62_A_1ig5A_2908_3409_0 from handle_exit_external
10:03:06 [rosetta@home] [cpu_sched] Starting score13_hb_envtest62_A_1ig5A_2908_3409_0(resume)
10:03:06 [rosetta@home] [task_debug] task_state=EXECUTING for score13_hb_envtest62_A_1ig5A_2908_3409_0 from start
10:03:06 [rosetta@home] Restarting task score13_hb_envtest62_A_1ig5A_2908_3409_0 using minirosetta version 107
(at this moment, again ALL tasks exited, I suppose a client error?)
10:07:18 [rosetta@home] [task_debug] Process for score13_hb_envtest62_A_1ig5A_2908_3409_0 exited
10:07:18 [rosetta@home] Task score13_hb_envtest62_A_1ig5A_2908_3409_0 exited with a DLL initialization error.
10:07:18 [rosetta@home] If this happens repeatedly you may need to reboot your computer.
10:07:18 [rosetta@home] [task_debug] task_state=UNINITIALIZED for score13_hb_envtest62_A_1ig5A_2908_3409_0 from handle_exit_external
10:07:18 [rosetta@home] [cpu_sched] Starting score13_hb_envtest62_A_1ig5A_2908_3409_0(resume)
10:07:18 [rosetta@home] [task_debug] task_state=EXECUTING for score13_hb_envtest62_A_1ig5A_2908_3409_0 from start
10:07:18 [rosetta@home] Restarting task score13_hb_envtest62_A_1ig5A_2908_3409_0 using minirosetta version 107
10:08:16 [rosetta@home] [cpu_sched] Preempting score13_hb_envtest62_A_1ig5A_2908_3409_0 (left in memory)
10:08:16 [rosetta@home] [task_debug] task_state=SUSPENDED for score13_hb_envtest62_A_1ig5A_2908_3409_0 from suspend
14:24:19 [rosetta@home] [cpu_sched] Resuming score13_hb_envtest62_A_1ig5A_2908_3409_0
14:24:19 [rosetta@home] [task_debug] task_state=EXECUTING for score13_hb_envtest62_A_1ig5A_2908_3409_0 from unsuspend
14:24:19 [rosetta@home] Resuming task score13_hb_envtest62_A_1ig5A_2908_3409_0 using minirosetta version 107
14:56:45 [rosetta@home] [cpu_sched] Preempting score13_hb_envtest62_A_1ig5A_2908_3409_0 (left in memory)
14:56:45 [rosetta@home] [task_debug] task_state=SUSPENDED for score13_hb_envtest62_A_1ig5A_2908_3409_0 from suspend
14:59:45 [---] Restarting score13_hb_envtest62_A_1ig5A_2908_3409_0 - message timeout
14:59:45 [rosetta@home] [task_debug] task_state=UNINITIALIZED for score13_hb_envtest62_A_1ig5A_2908_3409_0 from kill_task

Taking into account how often was the app harmed, I could imagine that the task did not really receive the wake up signal...

Peter

(PS: Should I leave such reports rather on the Ralph site? Or even Alpha list?)

It finally validated.

Peter

Is the new graphics for miniRosetta going to look the same as the current graphics?

Also, When i leave the graphics on for the current version..when its done with a wu, it closes out the graphics and goes back to my desktop..is there a way to keep the graphics window open while starting another wu?

Is the new graphics for miniRosetta going to look the same as the current graphics?

Posibly not really the same:
David E K wrote:

1. screen saver. currently under dev using the minirosetta game framework, may even be an optional game where people can compete with computers and each other to design/fold proteins.

Or the same like before, but with an additional enhanced entertainment mode ;-)

When i leave the graphics on for the current version..when its done with a wu, it closes out the graphics and goes back to my desktop..is there a way to keep the graphics window open while starting another wu?

I doubt it. AFTER an app (which was showing graphics) is terminated (with already closed graphics window), THEN Boinc will start another application, which is after some initialization capable of opening a graphics window.

Except that on a multi-core machine, one app showing screensaver is being terminated, and immediately another (already running app) can show its screensaver graphics.

Peter

I have a Rosetta mini on my computer at the moment and unless I abort it then it will probably stay there.
It ran for 4:15:09 (h:m:s) with my preference set to 6 hours, and says it has completed 100% but is still sitting there "Waiting to Run" in Boinc Manager.
I am unable to upload it as B/M thinks it has not finished yet.
Should I just abort it?
This is not a Ralph WU but a Rosetta WU.

I tried for 2 hours to copy the screen shot into this forum post but was unable to do so, no matter what I tried (copy/paste = no go, copy to Word then to forum = no go, copy to Open Office then to forum = no go, copy as HTML document = no go, copy as XML document = this worked but it was in the raw format and could not be viewed), so gave up and have described it instead.

---

I have a Rosetta mini on my computer at the moment and unless I abort it then it will probably stay there.
It ran for 4:15:09 (h:m:s) with my preference set to 6 hours, and says it has completed 100% but is still sitting there "Waiting to Run" in Boinc Manager.

Rationale: It hapens occasionally (if it is not some other reason), that application reaches the end of its timeslot (Switch between applications every ... minutes) and should be preempted soon. In such situation the project's ShortTermDebt is usualy already negative. If the app now checkpoints shortly before (or just at) reaching 100%, it is immediately preempted by Boinc client and will silently wait for its next turn (until the STD slowly accumulates to become positive). Depending on the project's resource share, this could take up to one day (or even more?).

I am unable to upload it as B/M thinks it has not finished yet.
Should I just abort it?

No, no need to. Suspend client's network communication, then suspend all other projects and the application should be immediately started and finished soon. After being finished, you can resume the suspended projects and then restore the desired communication state of your client.

Peter