We are starting some limited public testing of a new pulsar search on Einstein@Home. This search uses data from the PALFA collaboration, taken at the Arecibo radio observatory. More information about this search will be released in the next few weeks; we'll use this thread (in the Science Message Board area) to provide updates when more information is available, and to answer questions.
Bugs and problems with the new application should be reported in this thread in the Bugs and Problem Reports Message Board area.

Searching for pulsars in PALFA data from Arecibo
)
You could manually download the einsteinbinary_ABP1_3.02* files from http://einstein.phys.uwm.edu/download/ and add a section for app einsteinbinary_ABP1 to the app_info.xml. However I doubt that this would make much sense right now as we are not issuing any ABP1 work in the next weeks and furthermore you'd miss updates to the einsteinbinary application.
Better help us test the 6.10 Windows Beta App so we can make it official and then switch back to the "official" path.
BM
BM
RE: Any chance to have an
)
No.
The GW search is organized in "runs" that are performed one at a time (neglecting transitions), which have a number of workunits that is fixed at the beginning of the run.
The PALFA search is a more or less constant stream of workunits, it will end when ARECIBO stops taking data (probably we'll then even dig out data from before the start of our search that is still usable). In a sense this search never ends.
BM
BM
Currently Einstein@home is
)
Currently Einstein@home is processing the ARECIBO data slower than we get it, so there's plenty of data left to process. We're working on speeding up the search, but currently we are far from real-time.
BM
BM
ABP1 workunit generation has
)
ABP1 workunit generation has been stopped. The purpose is to test the behavior of the project when there is no ABP work. This means that the ABP1 WUG will stay offline until we don't have any unsent ABP results left and clients will only get S5R6 work.
If issues show up that we can't fix immediately, we'll start the ABP1 work generation again. If, however, all goes well and the project keeps functioning, instead we'll generate and send out the first ABP2 tasks, and the ABP1 WUG will probably never be started again.
ABP2 will perform the same search on the same data as ABP1 currently does. But due to code optimizations and a smaller template bank it does this much faster; also ABP2 results don't validate against ABP1 ones, so we set up a new 'application'. We expect the ABP2 WUs to take ~1/5 of the time of ABP1 WUs.
Note that people that manually opted out of ABP1 in the project preferences will need to do the same for ABP2 (they already can).
BM
BM