• log onto pavo as pulsar

• cd to $PSRCAT_RUNDIR and either create a new obs??.db file or insert the new entry into one of your existing files (using the PSRCAT format, copy another entry if unsure).

• check that it works with psrcat -all -e <PSR>

• generally, the obs??.db files are symbolic links to files that are checked out of a revision control system, like CVS. Now is a good time to commit any changes made to your database.

• update the TCS file:

• Update the PMCTRL catalog

Adding a new Pulsar to TCS

1. log onto pavo as pulsar

2. cd to $PSRCAT_RUNDIR and either create a new obs??.db file or insert the new entry into one of your existing files (using the PSRCAT format, copy another entry if unsure).

3. check that it works with psrcat -all -e <PSR>

4. generally, the obs??.db files are symbolic links to files that are checked out of a revision control system, like CVS. Now is a good time to commit any changes made to your database.

5. update the TCS file:

cd /psr1/tcs/catalogues
mv PSRCAT PSRCAT.<date>
makePSRCAT

(note that there is no space between make and PSRCAT)

1. Update the PMCTRL catalog

cd $PM_OBS
updcat

You can now observe the new pulsar with TCS, the DFBs, and with PMDAQ.