PMBIRD
The pmbird script is for use on .s. files produced by pmbirdie_hunter. It runs on pm survey
output from a single tape only. Its job is to
identify pointings that must be reobserved because they have too much
interference (listed in $PM_BDHUNT/pm_bad_pointings), then run pmbirdfiles on the remaining good pointings.
The .accu files and .s. files should be in the directory PM_BDHUNT.
The environment variables PM_HOME and PM_BDHUNT should be set
prior to running pmbird.
NOTE: A directory, pointings_with_interference, must exist in PM_BDHUNT.
TO RUN PMBIRD:
type pmbird for the following usage instructions:
Usage: pmbird: tape start_pointing end_pointing
eg: pmbird PM0017 14 38
The script does the following:
- Looks through the directory pm_bdhunt for missing beams using check_s_files .
Dummy files for missing beams are created at this stage, to ensure pmbirdie_summary
numbers all beams properly. If an entire pointing missing at this stage, nothing
is done, as pmbirdfiles handles missing pointings.
- Considers each pointing separately, identifying those with sufficient interference
to warrant reobservation. This is accomplished by running
pmbirdie_summary once for each pointing. Pointings for which pmbirdie_summary finds
more than 7 filters common to more than 4 beams are flagged for reobservation. The
parameter 7 can be changed by editing nfiltersmax in pmbird.
The flagging is done by
running pmdone in a subdirectory of pm_book named for that pointing, with the "i" flag set.
All data for pointings with too much interference are moved to the pm_bdhunt subdirectory
pointings_with_interference. The bad pointings are listed in the file
pm_bad_pointings in the directory pm_bdhunt. Note that when running
pmbirdie_summary, a successful run results in an IEEE announcement of
certain flags enabled. That is a feature of the compiler.
- Runs pmbirdie_summary on all remaining pointings using the script pmbirdfiles .
The resulting .accu files containing filters are left in the pm_bdhunt directory.
- Creates a file (tape).pmbs to announce that that tape has had pmbird run on it.
That file contains the start and end pointing numbers run, along with the data on which
they were run. Different pointings can be run on different dates, as pmbird appends
to this file, so it is also a log. REMEMBER: each time pmbirdie_summary is run, it
overwrites previous filters in the .accu files!