Error with Gravitational Wave S6 Directed Search (CasA)
17 Jul 2013 12:56:42 UTC
Topic 197066
(moderation:
I have some error here: http://einsteinathome.org/task/391828566
...
ERROR: illegal SFT-version (42 4D 58 24 7 0 0 0) not within [1, 2]
ERROR: File-block '../../projects/einstein.phys.uwm.edu/h1_0287.75_S6Direct:0' is not a valid SFT!
...
Error with Gravitational Wave S6 Directed Search (CasA)
)
I just got an error, too. On a very first workunit immediately after start, but the next two are crunching Ok (so far).
http://einsteinathome.org/task/391997713
Another host the same
)
Another host the same error:
http://einsteinathome.org/task/391801547
another task the same error:
http://einsteinathome.org/task/391828582
the same on wingman host:
http://einsteinathome.org/task/391828583
I do not think that this is a problem on the client side as Brend thought and wrote in this post.
RE: Another host the same
)
Ah. Noted and dev's alerted.
Cheers, Mike.
I have made this letter longer than usual because I lack the time to make it shorter ...
... and my other CPU is a Ryzen 5950X :-) Blaise Pascal
RE: I just got an error,
)
Same here on a PPC Mac. The very first of these tasks bombed out after a few seconds with a checksum error (which seems to be a different error from Sebastian's). The second one's OK so far….
http://einsteinathome.org/task/391726744
NG
NG
Thanks for the reports. Some
)
Thanks for the reports. Some data files are definitely broken on the download mirrors. Strange things is that these files are ok on Albert@Home where we tested the run.
For now I disabled sending out more S6CasA tasks that may refer to broken files, while I continue to investigate and try to find the best way to fix this.
BM
BM
Hi, Here no problems with
)
Hi,
Here no problems with the first two workunits.
http://einsteinathome.org/host/6742381/tasks&offset=0&show_names=1&state=0&appid=24
Another 3 waiting...
Win7-64, i5-3570K @ 4.2GHz, Boinc 7.0.64
Runtime ~ 3:55 hours, 1*CPU (S6) + 3*GPU (Perseus)
Jürgen.
RE: Here no problems with
)
Yep, less than 5% of the 38000 data files are affected. Still thousands, though. I'm afraid there will be no way around distributing new data files to the download mirrors and re-starting the search, which will hopefully happen early next week.
BM
BM
I am also having a strange
)
I am also having a strange problem with a task:
Application: Gravitational Wave S6 Directed Search (CasA) 1.05 (SSE2)
Workunit: h1_0477.00_S6Directed__S6CasAf40a_477.6Hz_26
This workunit is stuck and will not report as finished though it's been at 100% for 3 days. It says it's waiting to run again. I've tried to push it through, but when I update manually, my event log only says that it checks for new workunits and says nothing about reporting finished tasks. I really don't want to abort this task as I spent 111 hours on it. :\
Pardon my n00biness.
As your task is saying
)
As your task is saying "Waiting to run" that's exactly what it's doing, so it's not finished yet.
If you want to push it through you have to suspend a running task to get it running again, just don't forget to resume the paused task again!
RE: As your task is saying
)
actually he may have to suspend a whole slew of tasks depending on the size of his work buffer and the priorities of various tasks in the queue. if he only suspends one running task while there are any tasks with higher priority than the "waiting to run" task in the queue, then one of those tasks with higher priority will start running - not the task that's waiting to run. there is a guaranteed way to get that task running again though...suspend all "ready to start" tasks and one of the currently running tasks. that will guarantee that the one "waiting to run" task will start running again. if a gravitational wave task is at 100% and still running, then you can rest assured that it'll be done within the next 5 minutes (assuming you have a relatively modern CPU and the task data isn't corrupt). in other words, you should only have to suspend a task (or slew of tasks) for no more than 5 minutes or so to get that one GW task finished, uploaded, and reported, at which point you can obviously resume all suspended tasks.