Editing the first page of phat.C for batch operations
         Since  setting of parameters by this online GUI is by definition not possible in a non interacting environment, some quantities must be edited "by hand" in the first page of phat.C to set up the desired running conditions.  It will usually not be necessary to edit below the "usual user edits" comment unless major changes of the environment are needed; generally user task functions will be written into e.g. Mul.C and Mul.h or similar user-controlled scripts. Here is the first part of phat.C, with added comments >>>>>>:

#include "Mul.h"
  //#include "Onl.h"
#include "Spc.h"
>>>>>> Obviously, you only want cases that exist above!
//*************************************************************************

//  Some important variables to edit, or set by interactive GUI if coded:
>>>>>> simbatch was very useful in debugging the batch mode
  Int_t simbatch    = 0;  //Set this to 1 to simulate batch, but with displays
>>>>>> datype 2 is nearly obsolete; this old file doesn't allow most tasks
  Int_t datype      = 1;  // Data type 1 = raw, 2 for cv0_10events.apx.root
>>>>>> Mark B. put these in, similar to Robin V's code.  Useful for debugging. 
  Int_t ReportLevel = 1;  // Verbosity of comments; 3 = highest
  Int_t ReportFreq  = 1; // every ReportFreq events
  Char_t *HitArrayName = "HitArraysfromRawData";// For datype = 1
  //  Char_t *HitArrayName = "MCHitArrays";   // For datype = 2

>>>>>> It's essential for batch that these be set as desired by editing
// Number of events, runs etc.: // (Edit or set via GUI)
  Int_t nEvents = 10000;
  Int_t nSpc    = 100;      // Max. number of events to run Spc on 
  Int_t nRuns =   10000;

//  Flags to turn on or off the individual analysis processes.
//  These may be changed by interactive phatic.C, or for batch use
//  may be edited temporarily for the particular application.

>>>>>> These should be edited to 1 for whatever is to be run for batch.
>>>>>> It's best to set them to 0 for interactive since the blue
>>>>>> buttons don't toggle i.e. only turn on, equivalent to setting = 1 
  Int_t doVtx = 0;  //  Convention: 0 =do not process, 1 = process
  Int_t doOnl = 0;  //  the corresponding data type.  These may be
  Int_t doMul = 0;  //  set to 1 by clicking buttons on the GUI.
  Int_t doSpc = 0;
  Int_t doOut = 0;  //  Write output if not zero

>>>>>> These may be left = 1 in batch since they're ignored then. They
>>>>>> may also be set to 1 via the interactive run phase blue buttons
  Int_t flVtx = 1;  //  Event loop processing flag: 0 = process only,
  Int_t flOnl = 0;  //  otherwise process & display.  The integer value
  Int_t flMul = 1;  //  may be used to select types of displays. (Also
  Int_t flSpc = 1;  //  controls final displays.) 
  Int_t flOut = 1;  //  available for use to control output routine
  //  Integer code for display type may be replaced by e.g. string later?
  //  If in batch, process only, regardless of the state of fl*** above.

//>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>>End of the usual user editables