G0Analysis Release 0.15
     Paul King; 2003/05/29, 09:45.

     Incorporates several bug fixes found during the first stage of
     the second pass analysis.

     Changes since release 0.14:
     ===========================
     *  Put the beam cuts we are using in the full replay into 
	the analysis CVS, as g0cuts.in.1steng. This is associated with 
	cut_id 2 in the database.
     *  Some minor changes concerning the replay engine.
	a) In updating the run and analysis table at the end of the
	   replay, now  fill "start_time" into the run table, even the
	   END_EVENT is not reached  in the run. Added the inserting the
	   "number_good_quartets" into the run_table.  
	b) Updated the default replay flag file, replay_flags.in 
	c) Modified WriteToMeasurementTable routine, so that in the 
	   pass (b), where  the slope correction is applied, only the 
	   yields and asymmetries of the "pids"  will be filled in to the
	   measurement table.  
	d) Swapped the location of LinRegCorr() and FillMPSNtuple() 
	   in the main routine.
	e) A minor bug fixed in GetReplayPrms().  
	f) Fixed a bug in G0SQL::StoreReplayFlags(), in which the flags 
	   of the  current replay are stored.  "Write" the "last_event" 
	   as an unsigned int to be consistent with the data type in 
	   the database.
     *  Changes related to the SQL query translator.
	a) Fixed a bug in translating the selection strings,
	   when"(err)" is  involved.  
	b) Implemented the "group by" selection syntax for the measurement
	   table.  So now "[y,a]_detN[pid](err)" will retreive the "pid" 
	   values(errors) from the  measurement table, group by the detector 
	   number (and run_number if applicable).  
	   Similar syntax: "[y,a]_octN[pid](err)","[y,a]_xxxbinN(err)" 
	   is also  supported.
     *  Modified the default flags in replayflags.in
     *  Fixed bug related to the fortran to c array indices conversion 
	in the retrieval of the correlation slopes from the database. 
	The correlation slopes AFTER the linear regression correction were 
	verified close to zero.
     *   Various fixes for the MySQL interface.
	 a) Added timebin_id into the field name look up table. Fixed an 
	    error in the relation lookup table for "slopes" vs "slope_types".
	 b) Now supports quotes text, e.g. 'xxx', "xxx" in the cut string 
	    of the SQL query translator. 
	    Also supports [table_alias].[field_name] syntax in the cut string.