Next: Correlating your Data Up: Fringe Searching and Pulsar Previous: Finding Fringes and Calculating Contents
Setting up Pulsar Gating
The pulsar that we plan to correlate on is J0034-0721. In your own account, we generate the polyco.dat file for the correlator.
The command line parameters for this are:
polyco pulsar_name start_mjd end_mjd nspan ncoeff maxha nsite freq
defaults are;
nspan = 960 (min)
ncoeff = 12
maxha = 8 (hour)
nsite = 7 (Parkes), but in this case we want 2 (CAT21)
freq = 1400 (MHz), but in this case we want 1658 (MHz)
So we generate polyco.dat like this;
polyco 0034-0721 50660.58 50661.04 960 12 8 2 1658 |
We then ftp this file to cor$pulsar on elleba, and rename the file PSR0031M.polyco there.
The pulsar that we plan to correlate on is J0034-0721. It has a period in seconds, error in last digit of the period, 50% width in milliseconds, and 10% width in milliseconds of;
P | e | W50 | W10 | |
0.94295078486 | 6 | 56.70 | 104 |
This means that if we divide the pulsar into 32 bins, each bin is about 30 milliseconds and the 10% width will fit into 3 bins.
Thus we choose the config file psr32_1b_16_64_2p and enter this into the correlator schedule file.
Finally, add the string ``P'' into the file v088d-3.sch at the end of the lines containing the scans for the pulsar.
Now you are ready to start correlating !
Next: Correlating your Data Up: Fringe Searching and Pulsar Previous: Finding Fringes and Calculating Contents
Paul Jones 2003-06-13