MWAX VCS Commissioning
The recent upgrade to MWAX necessitates verification that the system is capable of observing high time resolution phenomena, such as pulsars. To this end, we put in a successful proposal for an MWA observing campaign to being in the end of 2021 and into the beginning of 2022. The requested observations fall into two categories:
- commissioning observations, and
- the remaining SMART observations.
This page details the progress made in taking the observations and performing the tests to complete the commissioning phase. Progress with the SMART survey is detailed elsewhere.
Commissioning Observations
Goals & Target Pulsars
The stated goals of the commissioning observations are:
- To develop and test the tied-array beamformer for the new VCS data format
- Verification of frequency labelling
- Data recording and timing stability
- Polarimetric verification and leakage assessment
- Full coherent beam sensitivity and timing accuracy
- The voltage dump and trigger mode (in response to external triggers)
- Correlation and imaging of data recorded in the new VCS format
A partial list of requested observations to satisfy the above goals are:
Goal | Number of obs | Duration (mins) | Pulsars (e.g.) |
---|---|---|---|
#1 | 2 | 5-10 | B1749-28, B0031-07 |
#2 | 2 | 20 | J2241-5236 |
#3 | 2 | 60 | J0437-4715, J2145-0750 |
#4 | 4 | 10 | B0628-28, B0737-40, B0740-28, B1749-28 |
#5 | 3 | 20 | J0036-1033 (and B0031-07, J0034-0534) |
Observations
The following link performs a query on the MWA observation database, showing the details of the observations made so far:
The following table is a summary of the same observations, and which of the goals (see the table above) that they are intended to satisfy:
Obsid | Duration (sec) | Files | Pulsar(s) / Calibrator(s) | RA/Dec | PC RA/Dec | Az/El | Goal | Processing | Download folder | VCSBeam version* | Beamforming time |
---|---|---|---|---|---|---|---|---|---|---|---|
1323690320 | 296 | 24 | In-beam calibration (for 1323690616) | 11.8 / -5.8 | 8.5 / -7.4 | 341.6 / 68.0 | 1, 5 |
| /astro/mwavcs/asvo/253001 | v3.3.31_c279695 | |
1323690616 | 1200 | 3600 VCS | B0031-07 J0036-1033 J0034-0534 | 8.0 / -5.2 | 8.5 / -7.4 | 326.3 / 64.7 | 1, 5 |
| /astro/mwavcs/asvo/253008 | v3.3.31_c279695 | 1 channel: 1600s 24 channels: 4200-5000s |
1323708616 | 296 | 24 | In-beam calibration (for 1323709032) | 95.1 / -26.7 | 97.7 / -28.6 | 0.0 / 90.0 | 1, 4 |
| /astro/mwavcs/asvo/253000 | ||
1323708912 | 120 | 24 | PicA (for 1323709032) | 75.9 / -46.4 | 80.0 / -45.8 | 213.7 / 64.7 | 1, 4 |
| /astro/mwavcs/asvo/252998 | ||
1323709032 | 600 | 1800 VCS | B0628-28 | 97.5 / -26.7 | 97.7 / -28.6 | 0.0 / 90.0 | 1, 4 |
| /astro/mwavcs/asvo/253009 | ||
1323776720 | 120 | 24 | PKS2356-61 (for 1323776840) | 4.3 / -62.7 | 359.8 / -60.9 | 191.3 / 52.8 | 1, 2 |
| /astro/mwavcs/asvo/252999 | ||
1323776840 | 1200 | 3600 VCS | J2241-5236 | 346.9 / -51.9 | 340.4 / -52.6 | 216.9 / 53.6 | 1, 2 |
| /astro/mwavcs/asvo/253010 |
*VCSBeam version is the earliest version that was successfully used for the processing. For calibration observations, this means using mwa_plot_calibration
, and for the VCS observations, make_mwa_tied_array_beam
.
Processing details
Setting up Garrawarla environment
module use /pawsey/mwa/software/python3/modulefiles module load singularity module load vcsbeam module load psrcat module load hyperdrive
1323690320
Run Hyperdrive
Create Hyperdrive batch script:
Run the Hyperdrive script (on Garrawarla):
cd /astro/mwavcs/vcs/1323690320/hyperdrive sbatch hyperdrive.sbatch
Run VCSBeam plotting
Create VCSBeam plotting script:
Run plotting script:
cd /astro/mwavcs/vcs/1323690320/hyperdrive sbatch plot.sbatch
Plot the calibration solutions (on your local computer, after downloading a copy of plot_calibration.py
and plot_data.txt
:
plot_calibration.py --phases_png phases.png --amps_png amps.png plot_data.txt
Iterative step
It looks like the solutions are probably fine for most, if not all the antennas (except possibly HexE23, since there's a lot of power in the off-diagonal terms, Dpq and Dqp), but the curviness of the phases makes it hard to tell. Therefore, I will choose a reference antenna to plot all the phases relative to that. Since there's a bunch of tiles whose phases are strongly sloped (near the middle of the plot), I'll choose a reference tile with a negative slope as well, but whose gradient is not as steep... HexE25 will do. To do this, I need to re-run the plotting script with the following change:
-R NONE --> -R HexE25
If I want to keep the old plots, I just make sure I rename the various output files to something different. Remaking the plots gives:
These solutions look fine (the on-diagonal terms, Dpp and Dqq, look straight). At the moment, I'm not trying to do polarimetry, so I don't need to worry about either the reference antenna or the PQ phase. By default, I should probably get rid of the cross terms (taking guidance from the imaging team). Therefore, I should be able to simply apply this solution with the following options to make_mwa_tied_array_beam
:
-R NONE -U 0,0 # (and without -X)
1323690616
Make sure you have a calibration solution ready. this example uses the solution derived from observation 1323690320.
B0031-07
Create a VCSBeam beamforming script:
Prepare a pointings file (PSR B0031-07):
Run the VCSBeam beamforming script:
cd /astro/mwavcs/vcs/1323690616/vcsbeam sbatch vcsbeam_0031.sbatch
Generate an ephemeris:
psrcat -e J0034-0534 > 0034.par
Use PRESTO's prepfold utility to fold on the pulsar's period from the FITS files:
cd /astro/mwavcs/vcs/1323690616/vcsbeam /pawsey/mwa/singularity/presto/presto.sif prepfold -psr J0034-0721 -nosearch -nodmsearch G0057_1323690616_00:34:08.87_-07:21:53.41_ch109-132_00*.fits
Use DSPSR and PSRCHIVE to fold on the pulsar's period from the VDIF files:
cd /astro/mwavcs/vcs/1323690616/vcsbeam for freq in {109..132}; do /pawsey/mwa/singularity/dspsr/dspsr.sif dspsr -E 0031.par -b 512 -L 10 -A -O B0031-07_ch${freq}.ar G0057_1323690616_00:34:08.87_-07:21:53.41_ch${freq}.hdr; done /pawsey/mwa/singularity/dspsr/dspsr.sif psradd -o B0031-07.ar -R B0031-07_ch1* # (Did some pazi flagging: there was something weird in the first subint. This generated B0031-07.ar.pazi) pav -g B0031-07.png/png -DFT B0031-07.ar.pazi
J0036-1033
Create a VCSBeam beamforming script:
Prepare a pointings file (PSR J0036-1033):
Run the VCSBeam beamforming script:
cd /astro/mwavcs/vcs/1323690616/vcsbeam sbatch vcsbeam_0036.sbatch
Get an ephemeris from Nick:
Use PRESTO's prepfold utility to fold on the pulsar's period from the FITS files:
cd /astro/mwavcs/vcs/1323690616/vcsbeam /pawsey/mwa/singularity/presto/presto.sif prepfold -par 0036.par -nosearch -nodmsearch G0057_1323690616_00:36:15.10_-10:33:14.00_ch109-132_00*.fits
Use DSPSR and PSRCHIVE to fold on the pulsar's period from the VDIF files:
cd /astro/mwavcs/vcs/1323690616/vcsbeam for freq in {109..132}; do /pawsey/mwa/singularity/dspsr/dspsr.sif dspsr -E 0036.par -b 512 -L 10 -A -O J0036-1033_ch${freq}.ar G0057_1323690616_00:36:15.10_-10:33:14.00_ch${freq}.hdr; done
J0034-0534
Create a VCSBeam beamforming script:
Prepare a pointings file (PSR J0034-0534):
Run the VCSBeam beamforming script:
cd /astro/mwavcs/vcs/1323690616/vcsbeam sbatch vcsbeam_0034.sbatch
Use PRESTO's prepfold utility to fold on the pulsar's period from the FITS files:
cd /astro/mwavcs/vcs/1323690616/vcsbeam /pawsey/mwa/singularity/presto/presto.sif prepfold -psr J0034-0534 -nosearch -nodmsearch G0057_1323690616_00:34:21.83_-05:34:36.72_ch109-132_00*.fits
FAIL!!
Generate an ephemeris:
psrcat -e J0034-0534 > 0034.par
Use DSPSR and PSRCHIVE to fold on the pulsar's period from the VDIF files:
cd /astro/mwavcs/vcs/1323690616/vcsbeam psrcat -e J0034-0534 > 0034.par for freq in {109..132}; do /pawsey/mwa/singularity/dspsr/dspsr.sif dspsr -E 0034.par -b 512 -L 10 -A -O J0034-0534_ch${freq}.ar G0057_1323690616_00:34:21.83_-05:34:36.72_ch${freq}.hdr; done