Canceled "bad" BRP beams
Bernd Machenschalk
Moderator
Administrator
Joined: 15 Oct 04
Posts: 4314
Credit: 250763253
RAC: 33936
12 May 2015 7:46:09 UTC
Topic 198089
(moderation:
Occasionally we get data from Radio telescopes (usually Arecibo) that doesn't give any usable results when analyzed with our application. We have a few checks implemented in data pre-processing in order to not pass such data to the E@H clients at all, but occasionally a few slip through. All tasks from such a beam would end up as "validate error"s (not as "invalid"!). We do have methods to monitor such validate errors that accumulate on the WUs of single beams. In order to avoid wasting computing power on these, we need to cancel such workunits. Unfortunately this means that you won't get any credit for these tasks.
I set up this thread to notify you of such canceled beams.
BOINC does have a feature to notify clients of canceled workunits on scheduler contacts. However this feature is implemented in a way that, when enabled on E@H, grinds our database to a halt. So we decided not to enable it here.
BM
BM
Canceled "bad" BRP beams
)
I just canceled workunits of the following beams:
p2030.20150119.G66.66-00.73.N.b4s0g0.00000
p2030.20150119.G66.66-00.73.N.b5s0g0.00000
p2030.20150119.G66.66-00.73.N.b6s0g0.00000
BM
BM
p2030.20150119.G66.66-00.73.N
)
p2030.20150119.G66.66-00.73.N.b3s0g0 doesn't seem to be a good one either:
http://einsteinathome.org/workunit/218422058
http://einsteinathome.org/workunit/218422081
-----
Yep. Been watching it for a
)
Yep. Been watching it for a while. Canceled
p2030.20150119.G66.66-00.73.N.b4s0g0.00000
as well.
BM
BM
SETI receives data from the
)
SETI receives data from the same set of Arecibo antennae (7 channels, 2 polarities), and records them to its own recorder. Somewhere in the feed, we sometimes see a channel - B3_P1, in SETI terminology - which gets a bit stuck somewhere in the pipeline, and ruins that channel for sometimes weeks at a time (it seems to be seasonal). I have no way of knowing whether the fault is before or after the SETI feed is branched off the main PALFA source.
It could be a good idea to
)
It could be a good idea to communicate with others which beams are bad. If not already done.. and if the definition of "bad" is similar enough across users.
MrS
Scanning for our furry friends since Jan 2002
We had to cancel WUs of
)
We had to cancel WUs of beam
p2030.20141111.G191.02-00.48.N.b4s0g0.00000
(after half a year of flawless operation).
The E@H pipeline is similar to the other pipelines of the PALFA collaboration. Aside from the actual E@H application we use the very same software ("PRESTO") that PALFA is using and which is specifically written and tuned for pulsar timing. I strongly doubt that this can be used for signals of any other type and thus that it has any similarity with what SETI does.
BM
BM
http://einstein.phys.uwm.edu/
)
http://einsteinathome.org/account/tasks&offset=0&show_names=1&state=4&appid=0
I only got a handful and considering the 450+ valids I got that is not all that far from a flawless operation.
Thanks for the info Bernd
O, I though that "PRESTO" is
)
O, I though that "PRESTO" is an old but good for those times engine of Opera browser until version 12.17 after which it became an another sloooow clone of Google Chrome.
We canceled the following
)
We canceled the following workunits of beam "p2030.20141111.G191.02-00.48.N.b3s0g0.00000":
p2030.20141111.G191.02-00.48.N.b3s0g0.00000_3665
p2030.20141111.G191.02-00.48.N.b3s0g0.00000_3691
p2030.20141111.G191.02-00.48.N.b3s0g0.00000_3695
p2030.20141111.G191.02-00.48.N.b3s0g0.00000_3699
p2030.20141111.G191.02-00.48.N.b3s0g0.00000_3772
p2030.20141111.G191.02-00.48.N.b3s0g0.00000_3790
It currently looks like that only these few workunits with rather high "job numbers" (>3600) are affected, so we didn't cancel the whole beam (yet).
BM
BM
We canceled the workunits for
)
We canceled the workunits for the following beams that accumulated a lot of validation errors:
p2030.20151021.G196.96+00.49.S.b6s0g0.00000
p2030.20151024.G197.22+00.50.N.b3s0g0.00000
p2030.20151029.G180.60-00.37.N.b4s0g0.00000
p2030.20151029.G180.60-00.37.N.b5s0g0.00000
p2030.20151102.G197.50+00.07.N.b0s0g0.00000
p2030.20151102.G197.50+00.07.N.b5s0g0.00000
p2030.20151102.G197.50+00.07.N.b6s0g0.00000
This seems to be a lot but we didn't do this kind of cleaning in a long time. I recently updated our internal overview page for this, so it is now easier to cancel those "bad" beams and associated workunits.