S5R1b behind
14 Mar 2008 13:04:38 UTC
Topic 13657
(moderation:
Hi all!
People might remember the S5R1 run that started in 2006 and the problems we had with the fileserver hardware at the end of that year. Though the project experienced downtimes and slow progress, we didn't actually lose any valuable result files - or so we thought. Recently however it turned out that the (canonical) result files that dropped in on the server during three days at the end of 2006 are corrupted beyond repair or lost completely, probably related to a single crash of the fileserver.
In the near future (1-2 weeks) we'll begin to re-issue the workunits (~150,000) of the lost results with the label S5R3b. They should run with the Apps that we used at the end of S5R1.
As far as we can foresee this shouldn't affect the current run S5R3b at all, the workunits and tasks should just run side by side as it happened many times before during the transition from one run to the next.
BM
BM
S5R1b behind
)
* Post-processing (or final analysis) of the E@H S4 run is finished, but the results are still under internal review.
* Unfortunately the lost S5R1 results span the whole frequency range, no current post-processing of the S5R1 results would work even in a limited frequency band until we have those results (again).
* Yep, there is a result template for S5R3c, but unless we find something going wrong in the current S5R3b I don't think it is of any other use than for internal tests. The next public run will most likely be named S5R4.
BM
BM
We found an error in the
)
We found an error in the calculation of the computing power needed to re-do the lost tasks. So we'll now do this on our own (LSC) clusters and won't bother Einstein@home with it.
Sorry for the confusion.
(actually another Application with tasks with two more run-times different from S5R3 might have been even more confusing)
BM
BM
RE: We found an error in
)
Update for the curious: That's done by now. Took ATLAS a bit more than two days of actual crunching.
BM
BM