Hardwired Tests

There are two reasons to prefer a hardwired test over the more dynamic programmable test:-

• There is a limit to what can be achieved with the n-tuple syntax used in the FLTR bank.

• Once a test has stabilised it is better to recode it in FORTRAN for speed and to protect against accidental changes - FLTR banks are too vulnerable!

FLT comes with a set of hardwired tests. Each hardwired test has its own name and routine named:-

FLT_xxxx where xxxx = test name, e.g. FLT_USER_1_CUT

There are a number user test routines: FLT_USER_n_CUT, which can be used as testbeds for new tests. See the file FLT_USER_1_CUT.FOR for details. There are symbol table mnemonics for each name e.g. $user_1_cut. See FLT_HWTEST_INI for instructions on how to convert a user test routine into a hardwired filter.

Each test has an optional associated titles bank FLTH (H = Hardwired) that can be used to hold its constants. This permits some execution time control via the set bank command e.g.:-

set bank flth -$user_1_cut word 1 to 20.

Note the rather odd syntax, the test, and their mnemonics, are negative so the minus sign is needed to make the bank number positive. As we build up a set of standard tests, we will probably introduce specific mnemonics that can hide this ugliness.

The remainder of this section describes the following hardwired filters:-

• The Two Pass Hardwired Filter
• The Perm Bank Cut
• The Charge Cut
• The Cluster Cut
• The AMB Cut
• The Fitterless Time Spread (FTS) Cut
• The QvT Cut
• The QCluster Cut
• The Seismic Cut
• The Junk Cut
• The OWL Cut
• The Crate Isotropy Cut
• The Neck Cut
• The ESUM Cut
• The ITC Cut
• The FGC Cut
• The Owl Up Cut
• The OWLEHI Cut
• The Prescale Cut
• The ZeroZero Cut
• The Fork1 Cut
• The Fork2 Cut
• The NCD Oscillatory Noise Cut
• The Flat Trace Cut
• The Narrow Pulse Cut
• The No NCD Info Cut
• The NCD pulser Cut
• The Crate Off Tag
• Sean McGee 3rd reflection cut
• Multiple peaks cut
• Positive signal cut