# File Name:    Readme
# File Purpose: This file lists all the possible hooks (both files and dirs.) along
#               with a brief description of their function, and how they are run /
#               used from with the Genesis system.
# Last Update:  December 01 2000
############################# Start of notes ###############################

Hook Name:  acquire
File / Dir: File.
Manual Ref: On-line manual 0203 (chapter 9).
Run Method: Called from main Genesis screen File --> Archive --> Acquire.
Hook Notes: This file is a c-shell script which is used to restore data back into
            Genesis from some archive point on the network. This archive point can a
            directory structure (raid disk, pre-mounted optical disk etc.) or a
            seperate archive management program (such as Star). It should be noted
            that the default script will need modification before it can be used to
            communicate with existing archive systems (for example - path names for
            archive points may need changing).

Hook Name:  area_pixmaps
File / Dir: Directory.
Manual Ref: On-line manual 0203 (chapter 9).
Run Method: Not applicable.
Hook Notes: This directory is used to store a collection of bitmap files. These
            files can be used in order to add an image to a polygon within the
            graphics editor. If the polygon being added is given the .area_name
            attribute, and the tex string applied to the .area_name attribute is
            the name of a bitmap file which exists in this directory, then the
            polygon will be filled with the bitmap image.

Hook Name:  camtek.ini
File / Dir: File.
Manual Ref: On-line manuals 0203 (chapter 9) and 0705 (appendix D).
Run Method: Used within the Camtek AOI interface to provide pre-defined system
            settings and parameters.
Hook Notes: This is the fixed format configuration file for the Camtek AOI interface
            package. It
            is the same file as is used by the Camtek AOI machines and sets up various
            pre-defined parameters that are required within this function. There are
            ten parameter sections within this definition file, these are the table
            parameters (which define the AOI table size), the station parameters, the
            resolution/magnification parameters (which specify what will appear in the
            resolution table), the frame parameters (which specify frame size and overlap),
            material calibration parameters (which define the calibration table), the
            margin parameters, the network parameters (which specifies IP addresses and
            names of AOI servers), and runtime parameters (which detail the information
            to appear on the screen). If this file is modified, Genesis must be restarted
            for the changes to take effect.

Hook Name:  camtek_zip
File / Dir: File.
Manual Ref: On-line manual 0203 (chapter 9).
Run Method: Called by the system (if it exists) after Camtek file creation.
Hook Notes: This hook is a c-shell script which is used by the Camtek interface package,
            and is called after the system creates the the output files for a single
            Camtek-set entity. It is not mandatory for this hook to exist. The system
            checks to see if the hook exists and if it does the commands detailed in
            this file are used to compress the directory and the Camtek files in that
            directory into a single .zip file. This single file is then transferred to
            the Camtek AOI machine.

Hook Name:  cdr14.ini
File / Dir: File.
Manual Ref: On-line manuals 0203 (chapter 9) and 0709 (chapter 4).
Run Method: Used within the Orbotech AOI interface to provide pre-defined system
            settings and parameters.
Hook Notes: This file is a fixed format configuration file. It is used within the
            Orbotech AOI interface to set up various pre-defined parameters that
            are required within this function. There are four main sections within
            this definition file, these are the working stage section, the tool-set
            section, the AOI table section, and the exclusion zone section.
            The working stage section defines the process stages where AOI inspection
            may be used. The tool-set section offers the user pre-defined positioning
            of the board within the AOI interface. The AOI table section defines the
            AOI table sizes available within the factory. The exclusion zone section
            offers different types of exclusion zone type which may be output to the
            AOI machine. 

Hook Name:  cprsheet
File / Dir: File.
Manual Ref: On-line manual 0203 (chapter 9).
Run Method: Called from Copper / exposed area --> Report --> Spreadsheet button.
Hook Notes: This file is a c-shell script which can perform any actions that it is
            programmed to do. Typically it is designed to extract copper / exposed
            area information for Genesis, create a formatted file, and load this
            file into a spread-sheet.

Hook Name:  drill_size
File / Dir: File.
Manual Ref: On-line manuals 0203 (chapter 9) and 0404 (appendix D).
Run Method: Called by the drill tool manager package.
Hook Notes: This file is a c-shell script which is run whenever a change is applied
            to a finished hole size, the hole type, the hole tolerance, or the user
            parameters selected in the D.T.M. This script calculates a nominal drill
            size for every hole (based on the finished hole size, the tolerances and
            the user parameters) and then either returns this nominal value, or calls
            an external program (see drill_size.awk below) to check for the closest
            available drill bit in a defined drill table (see drill_size.tab below).
		The drill_size program will set the true drill size and can also set the
            attribute .bit which holds the drill bit designator.

Hook Name:  drill_size.awk
File / Dir: File.
Manual Ref: No on-line manual. See notes in drill_size and drill_size.awk headers.
Run Method: Called by the drill_size program.
Hook Notes: This file is an example of how it can be possible to use an external
            drill table to select the nearest actual drill bit (without just using
            the nominal drill size). This program is written using awk (see the awk
            man pages for more details) and it is called along with the drill bit
            table (see drill_size.tab below). It first reads the drill bit sizes
            into memory and then checks through each one until it finds either an
            exact size match, or the drill bits that are just above and just below
            the nominal drill size. It then selects either the higher or the lower
            dependant on which is closer. The drill bits sizes are then passed back
            to the drill_size program and thus on into the D.T.M. window.

Hook Name:  drill_size.prm
File / Dir: File.
Manual Ref: On-line manuals 0203 (chapter 9) and 0404 (appendix D).
Run Method: Read by the drill tool manager package (creates user parameter menu).
Hook Notes: This file is a simple parameter file which holds the user parameters
            which are available as in menu in the drill tool manager. The user
            selects one of these parameters and this is passed to the drill size
            calculation program (see drill_size above). Note that spaces and upper
            case characters should not be used in this file.

Hook Name:  drill_size.tab
File / Dir: File.
Manual Ref: No on-line manual. See notes in drill_size.tab and drill_size.awk headers.
Run Method: Passed to the drill_size.awk program by the drill_size program.
Hook Notes: This file is an example of a drill bit definition table. It is used by 
            the drill_size.awk program to find the nearest drill bit to the nominal
            drill size calculated by the drill_size script. Only the first two columns
            are used by the drill_size.awk program, the other columns (spindle speed,
            feed rate and maximum hits) are just examples of possible extensions to
            this file. By modifying this file to contain the mils and mm drill sizes
            that are available, the D.T.M. function can be made site specific very
            quickly.

Hook Name:  etec
File / Dir: Directory.
Manual Ref: To be completed.
Run Method: To be completed.
Hook Notes: To be completed.

Hook Name:  ffilters
File / Dir: Directory.
Manual Ref: On-line manuals 0203 (chapter 9) and 0601 (appendix D).
Run Method: See individual hook comments later in this section.
Hook Notes: This is a directory which contains two hooks. These hooks are called names
            and script. They are used in the features filter pop-up to create and run
            the user defined filters. Individual hook notes follow.
            
            Hook Name:  names
            File / Dir: File.
            Run Method: Creates the user defined filter menu in the features filter pop-up.
            Hook Notes: This file is a simple parameter file which contains a series
                        of lines. Each line provides a menu option and a parameter to
                        pass to the file script. The first field (word) in the line
                        is the parameter name that gets passed to script, the rest of
                        the line is the text string(s) that make up the menu option.
            
            Hook Name:  script
            File / Dir: File.
            Run Method: Run when the user selects a user defined filter menu option.
            Hook Notes: This is a c-shell script which is called when the user selects
                        one of the options in the user defined filter (features filter
                        pop-up). The script gets a single parameter which is the first
                        field taken from the line selected (in the file names - see
                        above). Using this parameter, the script can then perform any
                        action it is programmed to do. The default version of this
                        script perfroms only highlight and selection routines. It is
                        possible to include editing routines, but it is sugested that
                        any function performed by this script should be kept within
                        the context that it is called from.

Hook Name:  film_sizes
File / Dir: File.
Manual Ref: On-line manuals 0203 (chapter 9) and 0703 (chapter 3).
Run Method: Read by the film optimisation package (creates film size menu).
Hook Notes: This file is a simple parameter file which holds the film sizes available
            for plotting. The file is a fixed column format with the film name and
            the X and Y sizes. Note that in order to make changes to this file, Genesis
            must be restarted.

Hook Name:  imp
File / Dir: Directory.
Manual Ref: To be completed.
Run Method: To be completed.
Hook Notes: To be completed.

Hook Name:  inc_274x
File / Dir: File.
Manual Ref: To be completed.
Run Method: To be completed.
Hook Notes: To be completed.

Hook Name:  inp_user
File / Dir: File.
Manual Ref: To be completed.
Run Method: To be completed.
Hook Notes: To be completed.

Hook Name:  job.du
File / Dir: File.
Manual Ref: To be completed.
Run Method: To be completed.
Hook Notes: To be completed.

Hook Name:  kit_export
File / Dir: File.
Manual Ref: On-line manual 0203 (chapter 9).
Run Method: Called by the KIT editor when the Export File option is selected.
Hook Notes: This file is a c-shell script that is designed to automatically e-mail a
            new (or modified) KIT entry directly to Frontline RnD. This script gets
            a single parameter passed to it, which is the name of the KIT item file
            that has just been created. Using a command line (or a series of commands)
            the file can be directly e-mailed to Frontline.

Hook Name:  line_hooks
File / Dir: Directory.
Manual Ref: To be completed.
Run Method: To be completed.
Hook Notes: To be completed.

Hook Name:  lp_prog
File / Dir: File.
Manual Ref: On-line manual 0203 (chapter 9).
Run Method: Called whenever the Genesis system is requested to print something (either
            from a "print" menu option, or by "<Control>P".
Hook Notes: This file as two modes of operation. The first is typically when it is run
            for the first time. It checks to see if the file lp_prog.config exists (this
            is the file which holds the printer names), if it does not it looks around
            the network and tries to find available printers. For every printer available
            it allows to user to test this printer and then add this printer to a list of
            available printers. It also allows a default printer to be set. If the file
            lp_prog.config does exist this file is sourced and the printer information
            is used to print the file. The file to be printed is passed to the lp_prog
            file as a parameter (as is the number of copies required).

Hook Name:  lp_prog.config
File / Dir: File.
Manual Ref: None.
Run Method: Called by the lp_prog hook.
Hook Notes: This file stores printer information which has been set-up the first
            time the lp_prog hook is run. This file is created when the lp_prog
            file is run for the first time and provides the lp_prog file with a
            list of all printers andthe default printer name.

Hook Name:  lyr_rule
File / Dir: File.
Manual Ref: On-line manuals 0203 (chapter 9) and 0401 (appendix D).
Run Method: Called automatically during input identification. Called from matrix
            using menu: Actions --> Rearrange Rows.
Hook Notes: This file contains a series of two line rules, where the first line
            contains a file format and a naming convention which can be matched to
            the customer file name / Genesis layer name, and the second line defines
            the system layer name and the layer properties to assign to that file.
            This gives the ability to automate the matrix set-up by using the customer
            file names / Genesis layer names.

Hook Name:  ncd
File / Dir: Directory.
Manual Ref: On-line manual 0703 (chapters 4/5) and 0703 (appendix D).
Run Method: See individual file comments later in this section.
Hook Notes: This is a directory which contains the Auto Drill Manager files and directory.
            These items are used by the A.D.M. function to customise and configure the
            drill output files.
            
            Hook Name:  set_table
            File / Dir: File.
            Run Method: Called by the A.D.M. function after the machine file is selected.
                        Also called during the final output file creation and can be run
                        by the user from the drill table pop-up.
            Hook Notes: This file is called during the ADM process. It is a c-shell script
                        which can be configured to perform changes to the ADM drill table
                        (and thus the drill output files) dependant on the different tool
                        parameters which are allocated to each tool (type, size, hole/slot
                        etc.). The example program has been written to provide control over
                        most of the functionality through the use of variables at the start
                        of the program. Most site specific configurations should be achievable
                        by setting these variables. 

		Hook Name:  out_file
            File / Dir: File.
            Run Method: Called by the A.D.M. function after the first phase (drill tools
                        and machine settings) is completed. Activated by the action button
                        in the middle of the A.D.M. flow.
            Hook Notes: This file is called during the ADM process. It is a c-shell script
                        which can be configured to provide user and site specific modifications
                        to the drill output files dependant on the different parameters allocated
                        to each tool (type, size, hole/slot etc.) and also the machine file being
                        used. This file can control the following parts of the output files,
                        although it should be noted that this is controlled by the machine file
                        selected (see section below):-
                        1. The header. 
                        2. The end of file. 
                        3. The tool changes.
                        4. The tool finish.
                        5. The step and repeat start.  
                        6. The step and repeat finish.

		Hook Name:  create_slot
            File / Dir: File.
            Run Method: Called by the A.D.M. function during output file creation. This is
                        only used when the nibble type is set to software (sw) and when the
                        machine file has custom slot set to yes.
            Hook Notes: This file is called during the ADM process when a slot needs to be
                        peck drilled in a customised way. It is a c-shell script which is
                        used to calculate a sequence of X/Y co-ordinates which will drill out
                        the slot. 

		Hook Name:  create_nibble
            File / Dir: File.
            Run Method: Called by the A.D.M. function during output file creation. This is
                        only used when the nibble type is set to software (sw) and when the
                        machine file has custom nibble set to yes.
            Hook Notes: This file is called during the ADM process when a hole needs to be
                        nibble drilled in a customised way. It is a c-shell script which is
                        used to calculate a sequence of X/Y co-ordinates which will drill out
                        the hole. 

		Hook Name:  slot_hits
            File / Dir: File.
            Run Method: Called by the A.D.M. function during output file creation. This is
                        only used when the nibble type is set to machine. 
            Hook Notes: This file can be used to calculate the number of drill hits which
                        occur when a machine canned cycle is used (and thus the hit count as
                        shown in the file, where a drilled slot is a single hit) is incorrect.

		Hook Name:  nibble_hits
            File / Dir: File.
            Run Method: Called by the A.D.M. function during output file creation. This is
                        only used when the nibble type is set to machine.
            Hook Notes: This file can be used to calculate the number of drill hits which
                        occur when a machine canned cycle is used (and thus the hit count as
                        shown in the file, where a nibble drilled hole is a single hit) is
                        incorrect.

            Hook Name:  config/machines
            File / Dir: Dirs.
            Run Method: See individual file comments later in this section.
            Hook Notes: This is a directory which holds all the specific machine files used
                        by the A.D.M. function.

                        Hook Name:  User Defined (name of drill machine)
                        File / Dir: File.
                        Run Method: Selected by the user and used to set-up the A.D.M. flow
                                    (first part). The process of selecting this also calls
                                    the set_table file.
                        Hook Notes: There may be many of these files, each one with an
                                    individual name. This is a configuration file which
                                    is used to define the machine specific parameters which
                                    are used by the A.D.M. function. These include panel to
                                    drill table registration, file format, tool assignment,
                                    and out_file parameter control.

Hook Name:  ncr
File / Dir: Directory.
Manual Ref: On-line manual 0704 (chapters 4/5) and 0703 (appendix D).
Run Method: See individual file comments later in this section.
Hook Notes: This is a directory which contains the Auto Rout Manager files and directory.
            These items are used by the A.R.M. function to customise and configure the
            rout output files.
            
            Hook Name:  set_machine
            File / Dir: File.
            Run Method: Called by the A.R.M. function after the machine file is selected.
            Hook Notes: This file is called during the ARM process. It is a c-shell script
                        which can be configured to provide angle and offset parameters to
                        the ARM using machine file names and panel size etc.

            Hook Name:  set_table
            File / Dir: File.
            Run Method: Called by the A.R.M. function after the machine file is selected.
                        Also called during the final output file creation and can be run
                        by the user from the tools table pop-up.
            Hook Notes: This file is called during the ARM process. It is a c-shell script
                        which can be configured to perform changes to the ARM tools table
                        (and thus the rout output files) dependant on the different tool
                        parameters which are allocated to each tool (size, hole/chain etc.).
                        The example program has been written to provide control over most of
                        the functionality through the use of variables at the start of the
                        program. Most site specific configurations should be achievable by
                        setting these variables. 

		Hook Name:  out_file
            File / Dir: File.
            Run Method: Called by the A.R.M. function after the first phase (tools table and
                        machine settings) is completed. Activated by the action button in the
                        middle of the A.R.M. flow.
            Hook Notes: This file is called during the ARM process. It is a c-shell script
                        which can be configured to provide user and site specific modifications
                        to the rout output files dependant on the different parameters allocated
                        to each tool (size, hole/chain etc.) and also the machine file being
                        used. This file can control the following parts of the output files,
                        although it should be noted that this is controlled by the machine file
                        selected (see section below):-
                        1. The header. 
                        2. The end of file. 
                        3. The tool changes.
                        4. The step and repeat start.  
                        5. The step and repeat finish.

            Hook Name:  config/machines
            File / Dir: Dirs.
            Run Method: See individual file comments later in this section.
            Hook Notes: This is a directory which holds all the specific machine files used
                        by the A.R.M. function.

                        Hook Name:  User Defined (name of drill machine)
                        File / Dir: File.
                        Run Method: Selected by the user and used to set-up the A.R.M. flow
                                    (first part). The process of selecting this also calls
                                    the set_machine and the set_table files.
                        Hook Notes: There may be many of these files, each one with an
                                    individual name. This is a configuration file which
                                    is used to define the machine specific parameters which
                                    are used by the A.R.M. function. These include panel to
                                    machine table registration, file format, multi-quadrant
                                    arc definition, and out_file parameter control.

Hook Name:  note_options
File / Dir: File.
Manual Ref: On-line manuals 0203 (chapter 9) and 0401 (appendix D).
Run Method: Read by the electronic notes function, this file is used to create the
            user note menu in the electronic notes pop-up.
Hook Notes: This file is a basic parameter file which defines the user note menu in
            the electronic notes window, when the user selects the add new note option.
            The file consists of a series of lines (one line for each menu option)
            where the first section of each line is the menu option, and the second
            section of each line is the title that will be used when adding the note.

Hook Name:  out_const
File / Dir: File.
Manual Ref: To be completed.
Run Method: To be completed.
Hook Notes: To be completed.

Hook Name:  opfx.params
File / Dir: File.
Manual Ref: On-line manuals 0203 (chapter 9) and 0702 (chapter 4).
Run Method: Read by the output package when working on OPF, OPFX, LP7008, and DP100
            formats.
Hook Notes: This file is a parameter file which provides predefined settings for
            units and film sizes. It is used to create a selection menu in the output
            parameters pop-up. There are two types of entry that can be added to this
            file, units and film size. If the selected format is OPF or OPFX then only
            the unit definitions are used. If the format is LP7008 or DP100, then both
            definitions can be used.

Hook Name:  orbotech_plot_spool.config
File / Dir: File.
Manual Ref: On-line manuals 0203 (chapter 9) and 0702 (chapter 10).
Run Method: Read by the output package when working on LP5008, Xpress, LP7008, and
            DP100 formats.
Hook Notes: This file is a parameter file which provides predefined settings for
            virtual plotter groups, output paths and locations of set-up files (for
            DP100X output). It is used to create a selection menu in the output
            parameters pop-up. It is important to note that some of these parameters
            need to set the same as those set in the plot spooler (the Xpert script),
            and that the output paths in this file will override those defined in the
            main output screen.

Hook Name:  outhdr
File / Dir: File.
Manual Ref: On-line manual 0203 (chapter 9).
Run Method: Read by the output package just prior to the creation of the output
            file(s).
Hook Notes: This file is a look-up file which the system uses to add pre-defined
            headers to files of certain formats. If the output format matches one of
            the lines in this file, and the second part of that line contains a full
            directory path to a file, that file is added to the top of every output
            file. It is not possible to add headers to every output file format, and
            the example hook provided lists all formats stating which can and which
            cannot be used. Note that in order note to create flase errors at output
            stage, all the lines have been commented out.

Hook Name:  panel
File / Dir: Directory.
Manual Ref: On-line manual 0971 (appendix A) (Release notes for Ver. 7.1).
Run Method: See individual file comments later in this section.
Hook Notes: This is a directory which contains three files and one directory (as well as
            a back up of each of these objects). These items are read by the panelisation
            wizard, and are created on-line using the panelisation set-up function.
            
            Hook Name:  job_macros
            File / Dir: File.
            Run Method: Defines job name selection macros within the panel wizard.
            Hook Notes: This is a configuration file which is created by the panelisation 
                        set-up function. This file is used to create the job macros menu
                        and also to store the job macros. A job macro is a statement or
                        regular expression which defines an enhanced job selection which
                        can be used when running the panelisation wizard. It is not
                        advisable to manually edit this file.
            
            Hook Name:  loc_macros
            File / Dir: File.
            Run Method: Defines object location macros within the panel wizard.
            Hook Notes: This is a configuration file which is created by the panelisation 
                        set-up function. This file is used to create the object location
                        macros menu and also to store the location macros. A location macro
                        is a statement or regular expression which defines an enhanced object
                        location routine which can be used when running the panelisation
                        wizard. It is not advisable to manually edit this file.

            Hook Name:  lyr_macros
            File / Dir: File.
            Run Method: Defines layer selection macros within the panel wizard.
            Hook Notes: This is a configuration file which is created by the panelisation 
                        set-up function. This file is used to create the layer selection
                        macros menu and also to store the layer macros. A layer macro is a
                        statement or regular expression which defines an enhanced layer
                        selection routine which can be used when running the panelisation
                        wizard. It is not advisable to manually edit this file.

            Hook Name:  scheme
            File / Dir: Dir.
            Run Method: See individual file comments later in this section.
            Hook Notes: This is a directory which holds all the panelisation scheme files.
                        There is one file for each panelisation scheme (routine) and the
                        file will have the scheme name.

                        Hook Name:  User Defined (name of panel scheme)
                        File / Dir: File.
                        Run Method: Used by the panelisation wizard to define panelisation.
                        Hook Notes: There may be many of these files, each one with an
                                    individual name. This is a configuration file which
                                    is created by the panelisation set-up function. This
                                    file is used to hold all of the placement and thieving
                                    rules, as well as the spacing requirements and all of
                                    the possible panel classes that can be used. It is not
                                    advisable to manually edit this file.

Hook Name:  post_cdr14
File / Dir: File.
Manual Ref: On-line manuals 0203 (chapter 9) and 0709 (appendix D).
Run Method: Called by the system after every output using the Orbotech AOI interface
            is finished.
Hook Notes: This file is a c-shell script and is designed to be used to work on any 
            data that has been created by the CDR (AOI) interface output. It is very
            similar to the post_output hook except that it deals specifically with
            CDR output files. It get passed an external (system created) file name as
            a parameter, and this can be sourced to provide a list of all the affected
            layers (which will dictate the output layers). Note that in the example
            script provided, all example sections have been marked with comment lines. 
            This is to avoid pop-up windows appearing on screen after every output is
            made. To see the effect of these examples, just remove the comment marker
           (#) from the required section.

Hook Name:  post_output
File / Dir: File.
Manual Ref: On-line manuals 0203 (chapter 9) and 0702 (appendix D).
Run Method: Called by the system after every output using the output page is finished.
Hook Notes: This file is a c-shell script and is designed to be used to post-process,
            or move/copy file after output. As it is a c-shell script it can perform
            any functions required. It get passed an external (system created) file
            name as a parameter, and this can be sourced to provide the file output
            path and the output format used. With this information it becomes a simple
            task to define a series of actions based on format, path etc. Note that in
            the example script provided, all example sections have been marked with 
            comment lines. This is to avoid pop-up windows appearing on screen after
            every output is made. To see the effect of these examples, just remove the
            comment marker (#) from the required section.

Hook Name:  Readme
File / Dir: File.
Manual Ref: Not applicable.
Run Method: Not applicable.
Hook Notes: The name of this file. A text file listing all possible hooks, and their
            use.

Hook Name:  rpd.params
File / Dir: File.
Manual Ref: To be completed.
Run Method: To be completed.
Hook Notes: To be completed.

Hook Name:  script_start.csh
File / Dir: File.
Manual Ref: On-line manual 0203 (chapter 9).
Run Method: Called automatically whenever any c-shell script is run.
Hook Notes: This file is a c-shell script which is sourced by the system every time
            a c-shell script is run. Thus, all of the variables, aliases, and parameters
            that are set within this file are passed on to the script being run. It is
            possible to setup different values dependant on things like the local hardware
            being used, the day or date, the user running the script etc. 

Hook Name:  secure
File / Dir: File.
Manual Ref: On-line manual 0203 (chapter 9).
Run Method: Called from main Genesis screen File --> Archive --> Secure.
Hook Notes: This file is a c-shell script which is used to archive data to an archive
            point on the network. This archive point can a directory structure (raid
            disk, pre-mounted optical disk etc.) or a seperate archive management
            program (such as Star). It should be noted that the default script will
            need modification before it can be used to communicate with existing archive
            systems (for example - path names for archive points may need changing,
            methods of data packing may be different).

Hook Name:  stagger
File / Dir: File.
Manual Ref: On-line manuals 0603 (chapter 3) and 0702 (appendix D).
Run Method: Read by the netlist optimiser stagger function, this file is used to create
            the stagger model selection menu in the stagger mode pop-up.
Hook Notes: This file is called by the stagger pop-up within the netlist optimiser. It
            provides a series of models (in a similar way to the ERF files) which can
            be used to define different staggering rules. The user selects the required
            staggering model which is then applied to the data. The file includes the
            definition of default values which are used if the model selected does not
            cover the SMD situation found. Each model can define multiple ranges based
            on the pad pitch and pad length and the staggering method which should be
            used in each case. In addition to this the range can be fine-tuned to include
            a minimum number of pads in the row (for the row to match the range), and also
            the test point radius to use in this case. The staggering method is defined as
            either a numeric pattern or a system code. Examples of all these are described
            in the stagger hook header.
            Additional information can also be found in KIT item 3360.
############################# End of notes ###############################
