Differences

This shows you the differences between two versions of the page.

--- ata_testing [2018/04/10 20:56] – created jrseti
+++ ata_testing [2023/10/28 18:36] (current) – external edit 127.0.0.1
@@ Line 1: / Line 1: @@
-==ATA Testing==
+===ATA Testing===
-===Thoughts from Andrew and Griffin===
+==Feed Measurements==
+  * [[feed_measurements|Feed Measurements]]
+  * [[sefd_measurements|SEFD Measurements]]
+==Data Gathers==
+  * [[data_gathered|These sources have been observed with the Beamformer]]
+==Pulsar Finding==
+  * [[pulsar_finding|Pulsars]]
+==Handful of Sources==
+  * http://adsbit.harvard.edu//full/1994A%26A...284..331O/0000335.000.html
+  * [[http://www.atnf.csiro.au/people/pulsar/psrcat/|Pulsars]]
+  * [[https://github.com/UCBerkeleySETI/breakthrough/blob/master/doc/RAW-File-Format.md|GUPPI Raw format]]
+  * [[https://github.com/UCBerkeleySETI/gbt_seti/blob/master/src/filterbank_mkheader.c|Filterbank header]]
+  * [[http://astro.berkeley.edu/~davidm/rb-blgbt.git|Filterbank Ruby code from Dave]]
+  * [[http://sigproc.sourceforge.net/sigproc.pdf|Filterbank header spec (see section 3)]]
+  * [[https://github.com/UCBerkeleySETI/breakthrough/blob/master/GBT/voyager/voyager.ipynb|Filterbank Voyager1 Tutorial/Jupyter]]
+==Thoughts from Andrew and Griffin==
 Email from August 07, 2017 from Griffin:
@@ Line 43: / Line 67: @@
   >
   > -Griffin
+Email from Andrew on April 10, 2018:
+  I just wanted to restart this conversation.
+  I think Griffin’s suggestions are great, here are a few other ideas.
+  Perhaps you could reduce the on/off time on the flux calibrator sources to the minimum permitted by the beamformer
+  with max ~35% overhead.  e.g. if you can switch positions in 10s, observe for 30s ON, 30s OFF, and repeat a few
+  times.
+  It would also be good to observe a handful of such sources - here is a good list:
+  http://adsbit.harvard.edu//full/1994A%26A...284..331O/0000335.000.html
+  Positions for these sources can be found on SIMBAD, e.g.: http://simbad.u-strasbg.fr/simbad/sim-id?Ident=3C48&NbIdent=1&Radius=2&Radius.unit=arcmin&submit=submit+id
+  I would recommend cross scans at the nominal position in addition to the ON/OFF, as was done in the reference
+  above.
+  For the purposes of analyzing these observations, we will want to be able to produce coarsely channelized and
+  integrated spectral data, e.g. ~1s time integration and 1 MHz frequency resolution.  This should keep the data rate
+  down.  0.1s and 100 kHz might be better for RFI flagging, but not strictly necessary.  As Griffin mentioned,
+  multiple frequencies will allow us to assess performance across the band.
+  For pulsar observations, you can get coordinates and parameters from http://www.atnf.csiro.au/people/pulsar/psrcat/
+  The three pulsars suggested by Griffin below are good places to start.  For these, we will want to generate faster
+  data products (100us integrations) with modest frequency resolution (100 kHz).
+  For the moment, doing these tests with the beamformer configured with a minimum set of operable antennas is a good
+  place to start.  Over the course of the next several months, we will want to repeat these tests with individual
+  antennas.  It will be necessary to create some kind of ’standard’ data product for these tests.  If we start with
+  simple total power (Stokes I), the ‘filterbank’ format makes good sense.
+  Cheers,
+  Andrew
+==Pulsars==
+PSR B0329+54
+  RA: 03h 32m 59.368s
+  Dec: +54° 34′ 43.57″
+  In hours,degrees: 3.5498244,54.5787694
+PSR B0531+21 (Crab Pulsar)
+  RA: 05h 34m 31.97s
+  Dec: +22° 00' 52.1"
+  In hours,degrees: 5.5755472,22.0144722
+PSR B0950+08
+  RA: 09h 53m 09.310s
+  Dec: +07° 55' 35.75"
+  In hours,degrees: 9.8859194,7.9265972