Pulsar observing Advice - NRAO Skynet 20-meter

Pulsar Observing Advice for the NRAO Skynet 20-meter telescope

Links UNC Skynet 20m skynet interface Log of 20m results. Latest observation NRAO Skynet main

Links	UNC Skynet	20m skynet interface	Log of 20m results.	Latest observation	NRAO Skynet main

Details for various kinds of observing projects

Main Advice Mapping/Imaging Advice Spectrum Observing Advice Pulsar observing

Pulsar Observing

Give the object a name that is a recognizable pulsar name (if it has one), for example, "B0329+54", or "J0953+0755".
- You can personalize the name by appending to the name, e.g. "B0329+54_mypulsar3".
(Here is a list of many known pulsars)
Searching for pulsar data: you can use the "Target Lookup" feature in the "Add New Observation" screen. In the "keywords" box, precede the pulsar name by "psr" so it will search pulsar catalogs, then click "Search". (for example: "psr0329+54") If it finds the object, it will fill in the Observation name and coordinates. At this point, you can modify the obervation name to add your name or other information.
After the observation is complete, the system runs "prepfold" to provide a display of the results. The software compares the coordinates with those in the pulsar list. If there is a match, it uses that pulsar's data for "prepfold". If it cannot identify the pulsar either by the name or coordinates, it uses a period = 1 sec for prepfold.
In the "configure receiver" screen, select "Low Resolution Spectral/Continuum", and check the "Pulsar Mode" box near the bottom.
Chooose the desired filter setting. "HI" or "OH2" has the least RFI contamination.
In the "Choose path settings" screen, select "Track"
Bright pulsars can be detected with a duration of 60 seconds. Longer for weaker pulsars.
Set the integration time to a fraction of the pulsar period, less than 1/100 th of the pulsar period for a good profile plot.
- Possible range of integration times: 0.1 to 0.0001.
- Note: The data acquisition system is unable to keep up with the data rate if the integration time is less than 0.0001 second. It will collect data, but what it collects will be mostly nonsense.
- A minimum sample time of 0.13 millisec and recommentation of 1/100th of the pulsar period means you get good profiles for pulsars with periods greater than 13 ms. You can observe faster pulsars, but the profiles will look coarser.
Important: Use the correct RA/DEC coordinates! Use a position that is good to a few arcseconds; use the above-mentioned catalog. The fit for period and period derivative will not be good unless the position is within a few arcseconds.

After the observation, the system will attempt to run Scott's "prepfold" on the data, if it can find a "par" file, or if it can find the period and DM in a pulsar catalog. The resulting plots from prepfold will be put on the web in the "Skynet quick look" web area: http://www.gb.nrao.edu/20m/peak/latest/

If it cannot find information about the pulsar it will process with period = 1 sec, and will list the name of the "psrfits" file, which you can copy and process offline.

Processing off-line (advice for pulsar experts)

The pulsar fits files will be on "pork" at /raid/scratch/cyborg/SkynetData/
(or if running GBO mode: /raid/scratch/cyborg/GBOdata/ )
Any Green Bank login account should be able to access these files.
Just do: "ssh yourlogin@pork"
The quick-look web page "http://www.gb.nrao.edu/20m/peak/latest/" will show information similar to the following:


         Pulsar: B0329+54
     psrfits file available on
pork:/raid/scratch/cyborg/SkynetData/Skynet_58653_B0329+54_39900/Cyborg/
        Skynet_58653_B0329+54_39900_47831_0001.fits

The path designation following "pork:" is the path where the FITS file is located.
The last line (starting with "Skynet") is the name of the FITS file.

Processing with prepfold:

  source /home/pulsar64/pulsar.bash
  prepfold -help
  prepfold -n 128 -nsub 128 -timing parfile fitsfilename
       parfile is /users/sransom/parfiles/psrname.par
       or /users/pdemores/tzpar/psrname.par 

If you know the period and DM:
  prepfold -n 128 -nsub 128 -nodmsearch <dmvalue> -p <period> fitsfilename

  (the period is in seconds)

Sample time weirdnesses

The rate at which the pulsar data is sampled depends on the "integration time" that you enter in the Skynet web interface, but is not exactly what you enter.

The sample time (i.e., time from one sample to the next) is 2^n (1024/5.0e8) seconds.

The maximum allowed by the present software setup is n=11, i.e., tsample = 4.19ms.

So if you set the integration time to, say, 0.5 seconds, tsample is 4.19ms. In fact, if you set the integration time to anything greater than 4.19ms, the sample time will be 4.19ms.
For shorter integration times, the system will set tsample to the closest power of two submultiple. For example if you set Tint = 0.001 second, what you get is 1.05 ms (i.e., 4.19/4). The smallest tsample that works reasonably well is 0.1ms; if shorter than that the data acquisition cannot keep up with the spectrometer, and most of the data gets lost. So as a practical matter, do not use Tint less than 0.0001 second. (actually 0.131 ms) The system is rigged to prevent Tint shorter than that.

Assuming we should have at least 50 time samples per pulsar period, then we can set a limit on the shortest pulsar period that it would be useful to observe. P ~ 50*(0.0001) = 0.005 seconds, hence observe pulsars with longer periods than 5 ms. You can observe faster pulsars, but the profiles will not look very good.

[Frank D. Ghigo, NRAO-Green Bank, April 2014, rev March 2015, rev June 2019, June 2020]