Project: 2653 (Run 37, Clone 17, Gen 104)

[anko1]

I'm guessing that this had some sort of communications error, though it's the first one since I put in the loopback adapter (or is Corestatus 7B a different issue?). This is on Big Red.

Code: Select all

[05:28:29] Completed 500000 out of 500000 steps  (100 percent)
[05:28:29] Writing final coordinates.
[05:28:30] Past main M.D. loop
[05:28:30] Will end MPI now
[05:29:30] 
[05:29:30] Finished Work Unit:
[05:29:30] - Reading up to 3725280 from "work/wudata_02.arc": Read 3725280
[05:29:30] - Reading up to 1780584 from "work/wudata_02.xtc": Read 1780584
[05:29:30] goefile size: 0
[05:29:30] logfile size: 17309
[05:29:30] Leaving Run
[05:29:32] - Writing 5527573 bytes of core data to disk...
[05:29:32]   ... Done.
[05:29:32] - Failed to delete work/wudata_02.sas
[05:29:32] - Failed to delete work/wudata_02.goe
[05:29:32] Warning:  check for stray files
[05:29:32] - Shutting down core
[05:31:32] 
[05:31:32] Folding@home Core Shutdown: FINISHED_UNIT
[05:31:32] 
[05:31:32] Folding@home Core Shutdown: FINISHED_UNIT
[05:31:38] CoreStatus = 7B (123)
[05:31:38] Sending work to server
[05:31:38] Project: 2653 (Run 37, Clone 17, Gen 104)


[05:31:38] + Attempting to send results [January 17 05:31:38 UTC]
[05:31:38] - Reading file work/wuresults_02.dat from core
[05:31:38]   (Read 5527573 bytes from disk)
[05:31:38] Connecting to http://171.64.65.64:8080/
[05:31:50] Posted data.
[05:31:50] Initial: 0000; - Uploaded at ~415 kB/s
[05:31:51] - Averaged speed for that direction ~294 kB/s
[05:31:51] + Results successfully sent
[05:31:51] Thank you for your contribution to Folding@Home.

[toTOW]

There's no error reported in the DB. The WU was completed successfully.

Hi anko1 (team 47815),
Your WU (P2653 R37 C17 G104) was added to the stats database on 2009-01-17 00:28:41 for 1760 points of credit.

[anko1]

Good news. I'm surprised since I didn't get the incremental increase notice and the core status wasn't 100 [which I didn't notice until I was trying to find out why I didn't get the counter message.]. Surprised, but not complaining.

[^w^ing]

Good news. I'm surprised since I didn't get the incremental increase notice and the core status wasn't 100 [which I didn't notice until I was trying to find out why I didn't get the counter message.]. Surprised, but not complaining.

Hmm, thats the exact thing I wanted to post here about, since I updated to 6.23r1 Win client, alot of my WUs end up with CoreStatus 7B (123) instead of 64 (100) after completion, and the local WU count doesnt increment upon upload, which is what it usually does when the WU EUEs. I was concerned if the work server accepts such a results or trash it as an EUEd WU.

[anko1]

I think this is the first time I got to 100% and CoreStatus 7B since I put in the loopback adapter. I either EUE earlier or complete w/ CoreStatus 64 and get recognition for the unit.