Page 5 of 7
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Tue Mar 23, 2010 10:52 pm
by kasson
Individual reports aren't necessary, thanks (and we unfortunately don't have time to read them). We have all the required information captured and are working with the stats team on a recredit.
We have sufficient information that we should be able to recredit everything *except* the proper bonus values; we will either credit the base values or give everyone a uniform bonus for the missing work units. Our apologies for this snafu. A particular raid array filled up without triggering the normal warning system, causing an unfortunate failure mode where the server received the work units but then didn't know what to do with them.
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Tue Mar 23, 2010 11:14 pm
by orion
kasson wrote:A particular raid array filled up without triggering the normal warning system, causing an unfortunate failure mode where the server received the work units but then didn't know what to do with them.
So was the work lost and needs to be reissued?
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Wed Mar 24, 2010 12:19 am
by DrSpalding
My reading of kasson's posting indicates that they have the results but no way to assign the actual bonus values earned. In other words, it doesn't sound like the science part of FAH was lost, just the accounting of the bonus points only.
kasson wrote:We have all the required information captured and are working with the stats team on a recredit.
We have sufficient information that we should be able to recredit everything *except* the proper bonus values; we will either credit the base values or give everyone a uniform bonus for the missing work units. Our apologies for this snafu. A particular raid array filled up without triggering the normal warning system, causing an unfortunate failure mode where the server received the work units but then didn't know what to do with them.
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Wed Mar 24, 2010 11:54 am
by dezsee
kasson wrote:Individual reports aren't necessary, thanks (and we unfortunately don't have time to read them). We have all the required information captured and are working with the stats team on a recredit.
We have sufficient information that we should be able to recredit everything *except* the proper bonus values; we will either credit the base values or give everyone a uniform bonus for the missing work units. Our apologies for this snafu. A particular raid array filled up without triggering the normal warning system, causing an unfortunate failure mode where the server received the work units but then didn't know what to do with them.
Thanks for the clarification and info.
In the future could we please have this configured to default the fortunate failure modes rather than the unfortunate failure modes.
Thanks
dezsee
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Wed Mar 24, 2010 1:52 pm
by Kougar
kasson wrote:Individual reports aren't necessary, thanks (and we unfortunately don't have time to read them). We have all the required information captured and are working with the stats team on a recredit.
We have sufficient information that we should be able to recredit everything *except* the proper bonus values; we will either credit the base values or give everyone a uniform bonus for the missing work units. Our apologies for this snafu. A particular raid array filled up without triggering the normal warning system, causing an unfortunate failure mode where the server received the work units but then didn't know what to do with them.
Thanks for the information and update!
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Thu Mar 25, 2010 8:47 pm
by DrSpalding
Hi, it has been another 24+ hours since we had news. Is there any news or updates you can share? I have not yet seen any re-crediting evidence as yet for the WU I noted previously.
Thanks!
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Thu Mar 25, 2010 9:44 pm
by bruce
DrSpalding wrote:Hi, it has been another 24+ hours since we had news. Is there any news or updates you can share? I have not yet seen any re-crediting evidence as yet for the WU I noted previously.
Thanks!
It's unrealistic to think that the re-credit will happen in a time-frame measured in hours. The time required to process a re-credit is typically measured in weeks or even months, or at the very best, many days. They process a re-credit very carefully, and a number of different people must check specific steps. Integrating it into many different busy schedules will take time.
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Thu Mar 25, 2010 10:38 pm
by DrSpalding
bruce wrote:It's unrealistic to think that the re-credit will happen in a time-frame measured in hours. The time required to process a re-credit is typically measured in weeks or even months, or at the very best, many days. They process a re-credit very carefully, and a number of different people must check specific steps. Integrating it into many different busy schedules will take time.
Bruce, thanks for providing this information. It is much more comforting to have a rough estimate, even if just an order of magnitude, than it is to sit in a vacuum. I had supposed it would have been as easy (or as hard) as rerunning a transaction log of some sort once the properly identified WUs were flagged out of the sea of data.
Dan
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Sat Mar 27, 2010 5:25 pm
by MacAttack
soooo, did we get some sort of estimate as to when some sort of credit is coming?
I guess the best thing is they DID get the science,,,,right????
Mac
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Sun Mar 28, 2010 5:32 pm
by kasson
We're working on it, hard to estimate. It requires the coordination of several team members, so there can be a lot of limiting stages. In this case, we have to reconstruct some critical lines of the transaction logs from other parts of the log.
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Sun Mar 28, 2010 7:22 pm
by VijayPande
We will give an update once we are ready to run the recredit, but this could easily take a week or perhaps several weeks depending on how complex this one is. Sorry this takes so long, but this means coordinating many different parts of the FAH team for a very irregular task.
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Mon Apr 12, 2010 6:27 pm
by kasson
We just ran a recredit for this server. Sufficient information for the bonus was not captured, so we gave all work units a 2x bonus.
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Mon Apr 12, 2010 9:07 pm
by capreppy
I posted here as well, but it seems as if I only got the base points and not the bonus. Others have indicatd that they received the bonus at the same time as the based credit.
http://foldingforum.org/viewtopic.php?f ... 15#p136464
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Sun Apr 18, 2010 8:00 pm
by Darken1
I finish a -bigadv WU on this server @ 4/18/2010 6:05 AM is 4pm now and no credit for it, i'm 10% in to the next WU, should i delete and start regular smp, i dont like the idea of doing 10 bigadv WU's waiting months for credits or recredits.
Thanks for your help
Darken1
Code: Select all
00:42:31] + Processing work unit
[00:42:31] Core required: FahCore_a2.exe
[00:42:31] Core found.
[00:42:31] Working on queue slot 01 [April 16 00:42:31 UTC]
[00:42:31] + Working ...
[00:42:31]
[00:42:31] *----------------------------- Ensuring status. Please wait.
[00:42:41] - Looking at optimizations...
[00:42:41] - Working with standard loops on this execution.
[00:42:41] - Files status OK
[00:42:48] - Expanded 30332646 -> 159726549 (decompressed 101.7 percent)
[00:42:50] Called DecompressByteArray: compressed_data_size=30332646 data_size=159726549, decompressed_data_size=159726549 diff=0
[00:42:51] - Digital signature verified
[00:42:51]
[00:42:51] Project: 2681 (Run 0, Clone 4, Gen 99)
[00:42:51]
[00:42:51] Entering M.D.
[00:43:15] Completed 0 out of 250000 steps (0%)
[01:18:26] Completed 2500 out of 250000 steps (1%)
[01:53:16] Completed 5000 out of 250000 steps (2%)
[02:27:52] Completed 7500 out of 250000 steps (3%)
[03:02:33] Completed 10000 out of 250000 steps (4%)
[08:07:06] Completed 237500 out of 250000 steps (95%)
[08:42:56] Completed 240000 out of 250000 steps (96%)
[09:18:28] Completed 242500 out of 250000 steps (97%)
[09:52:59] Completed 245000 out of 250000 steps (98%)
[10:27:19] Completed 247500 out of 250000 steps (99%)
[11:01:31] Completed 250000 out of 250000 steps (100%)
[11:01:40] DynamicWrapper: Finished Work Unit: sleep=10000
[11:01:50]
[11:01:50] Finished Work Unit:
[11:01:50] - Reading up to 52713120 from "work/wudata_01.trr": Read 52713120
[11:01:51] trr file hash check passed.
[11:01:51] - Reading up to 47068184 from "work/wudata_01.xtc": Read 47068184
[11:01:52] xtc file hash check passed.
[11:01:52] edr file hash check passed.
[11:01:52] logfile size: 214376
[11:01:52] Leaving Run
[11:01:52] - Writing 100160596 bytes of core data to disk...
[11:02:06] ... Done.
[11:05:18] - Shutting down core
[11:05:18]
[11:05:18] Folding@home Core Shutdown: FINISHED_UNIT
[11:05:35] CoreStatus = 64 (100)
[11:05:35] Sending work to server
[11:05:35] Project: 2681 (Run 0, Clone 4, Gen 99)
[11:05:35] + Attempting to send results [April 18 11:05:35 UTC]
[11:34:57] + Results successfully sent
[11:34:57] Thank you for your contribution to Folding@Home.
[11:34:57] + Number of Units Completed: 33
Re: 171.67.108.22 (bigadv) Missing credits?
Posted: Sun Apr 18, 2010 8:40 pm
by kasson
We had an issue overnight where there was a problem with one of the RAID's on this server. Credits were lost for 168 work units. I just parsed the logs, caught 151 of those, and performed a recredit for those. Fixed bonus -> 2x as before. Our apologies for the inconvenience.