At the risk of speaking on behalf of my far more knowledgeable colleagues: The entry-level “MeerKAT beamformer” is embedded in the correlator/beamformer and will provide a maximum of 4, currently 1, tied array beams using CASPER SKARAB hardware and firmware. Currently provides a tied array voltage beam to the Swinburne pulsar timing back end.
The MeerKAT “transient search beamformer” is being provided by Manchester (Ben Stappers) and MPIfR (Michael Kramer), 100s of beams and search engines, GPU based. Ben also has a prototype SKA non-imaging processor (protoNIP) installed in our Cape Town office. The GPUs subscribe to channelized antenna voltage SPEAD data streams emanating from the MeerKAT correlator/beamformer core switch. J > On 25 Jan 2018, at 9:45 PM, Scott Ransom <[email protected]> wrote: > > Hi All, > > I had a discussion with Rich and Omar yesterday. I think they are interested > in slightly more than what is being called a "pulsar backend", but more like > the whole system to allow fast sampled observations in general: i.e. beam > formers or fast-dump correlators and how they are interfacing with back-end > processing, like the VLAs CBE or more traditional pulsar backends like > CASPER-based GUPPI and their ilk. > > I personally don't know much about what is happening with beamformers, for > example, with MeerKAT. Is there any documentation on that? > > Scott > > On 01/25/2018 02:19 PM, Mark Halpern wrote: >> ..or (along with Scott Ransom) contact Emmanual Fonseca or Ingrid Stairs to >> ask about the pulsar timing back end for CHIME. >> Mark >> On 2018-01-25 10:10 AM, Dan Werthimer wrote: >>> >>> hi rich, >>> >>> i know a bit about the meerkat pulsar search. >>> (i'm not on the team, but we've been working with those guys...). >>> i don't know much about meerkat pulsar timing (the timing and search are >>> different groups). >>> >>> scott ransom knows a bit about SKA pulsar search design team at oxford. >>> i know a small bit, but not as much as scott. >>> i can introduce you to some of the oxford ska pulsar team if you want. >>> >>> dan >>> >>> >>> >>> >>> >>> On Thu, Jan 25, 2018 at 7:38 AM, Rich Lacasse <[email protected] >>> <mailto:[email protected]>> wrote: >>> >>> Hi All, >>> >>> A few of us are starting to think about the pulsar backend for the >>> ngVLA. We were wondering if someone on this list might be able to >>> point us to publicly available documentation on what is being done >>> and being planned for MeerKat and SKA. This would give us an >>> excellent starting point. Thanks in advance for any help you can offer! >>> >>> Rich Lacasse, Omar Ojeda, Rob Selina >>> >>> -- You received this message because you are subscribed to the >>> Google >>> Groups "[email protected] >>> <mailto:[email protected]>" group. >>> To unsubscribe from this group and stop receiving emails from it, >>> send an email to [email protected] >>> <mailto:casper%[email protected]>. >>> To post to this group, send email to [email protected] >>> <mailto:[email protected]>. >>> >>> >>> -- >>> You received this message because you are subscribed to the Google Groups >>> "[email protected]" group. >>> To unsubscribe from this group and stop receiving emails from it, send an >>> email to [email protected] >>> <mailto:[email protected]>. >>> To post to this group, send email to [email protected] >>> <mailto:[email protected]>. > > -- > Scott M. Ransom Address: NRAO > Phone: (434) 296-0320 520 Edgemont Rd. > email: [email protected] Charlottesville, VA 22903 USA > GPG Fingerprint: A40A 94F2 3F48 4136 3AC4 9598 92D5 25CB 22A6 7B65 > > -- > You received this message because you are subscribed to the Google Groups > "[email protected]" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. -- You received this message because you are subscribed to the Google Groups "[email protected]" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected].

