hi tom,
there's a lot of current work in the areas you asked about:
terry filiba recently ported the ibob based pulsar instrumentation to roach,
(peter mcmahon and she developed this for parkes pulsar work).
jonathan kocz and mathew bailes are working on roach porting as well.
see peter's thesis and talk with terry and jonathan for more info.
each GPU can handle 100 to 200 MHz dual pol depending on whether
you are doing coherent dedispersion (timing), or spectroscopy (searching).
matthew and jonathan are the experts at reading data from ibob/roach and
using CPU cluster to do pulsar/transient search.
john ford, paul demorest, scott ransom et al are the experts at using
ibob/bee2
to packetize data (800 MHz dual pol) for GPU based pulsar cluster
(see their fantastic GUPPI instrument).
laura spitler, terry and mark wagner are working on porting setispec to
roach.
terry is also working on a GPU seti instrument, using roach or ibob to
course channelize
data, packetize it, and send to CPU/GPU for fine spectral analysis,
thresholding, etc.
andrew siemion and marin anderson have developed a kirtosis spectrometer
for ibob
and bee2, modeled after kirtosis ibob spectrometer developed by zhiwei
liu and dale gary.
best wishes,
dan
On 1/29/2010 3:02 PM, Tom Kuiper wrote:
I'm trying to scope the hardware required for SERENDIP-type science
piggy-backing on DSN down-link (passive, no transmitter) tracks.
As a baseline, I'm assuming one ROACH per antenna per activity.
Possible activities would be:
* searching for pulsars and transient pulses
* SETI
* kurtosis for electrostatic discharges (lightning)
For scoping the first task, is anyone working on a pulsar machine
using one or more ROACH boards? How big a cluster of CPU/GPU units
is reasonable for the real-time searching?
Has anyone looked at porting SETI to a ROACH?
Any suggestions for what else one might do with the unused bandwidth
would be welcome.
Thanks and regards
Tom
