Example of a routine to define and read user steerings for the detector simulation. If MODE = 0, then the routine defines keys for FFREAD, if it is 0 then the routine reacts on the values read be FFREAD. So, the calling routine must do something like
CALL ZAORD(0,STEER) . . (other key definitions) . . . CALL FFGO CALL ZAORD(1,STEER) .This is what ZXRUIN does. Note that the variables read in by FFREAD must be in a common, even if SGV uses them only in this routine !
MODE : 0 -> routine should define key-words, and default values. <> 0 -> load values of keys read from the steering file to the right common-blocks, do initialisation etc.
STEER : Steering info. The analysis uses row 4: STEER(4,1) : How to use the detector hits. In the example : 1 -> Use perigee parameters (ie. don't use hits at all) 2 -> Fit track using the right hits. 3 -> Run code to associate hits with tracks (met 1) 4 -> ditto, met 2. ,2) : Minimum number of jets to use event ,3) : 1 -> Make event ntuple ,4) : 1 -> Make jet ntuple ,5) : Vertex fit method : 0 -> Start with all tracks, then exclude tracks until a good vertex can be made. 1 -> Start with two tracks, then include tracks until vertex becomes bad. In addition STEER(1,0) is an error flag: 0 : no error 1 : error, but go on -2 : error, stop this run All other position of the row are free to use.
From /AINVAR/ : local variables used for clarity
To /AINVAR/ : local variables used for clarity, after their values have been set by FFREAD.