Index: trunk/MagicSoft/Mars/NEWS
===================================================================
--- trunk/MagicSoft/Mars/NEWS	(revision 8676)
+++ trunk/MagicSoft/Mars/NEWS	(revision 8679)
@@ -132,4 +132,17 @@
       + PostCleanType: 3
 
+   - star/ganymed: The old spark-cuts have been replaced by new ones.
+     These new spark cuts have been cross checked with the sequences
+     84720 (before splitter), 101041 (after splitter) and 223539 (new
+     FADCs). In all cases they seperate pretty well, but of course not
+     perfect. Monte Carlos have suggested to tighten the cuts a little
+     bit further at low sizes. This has been done.
+
+   - ganymed: IMPORTANT - The spark cuts have been changed to match
+     all available data more or less well. This might mean that for 
+     YOUR data there are still sparks visible. 
+     Whenever you do an analysis you have to make sure that NO sparks
+     survive your cuts!
+
    - ganymed: The old hadronness and size cuts have gotten new indices
      (10, 11). The old indices 8 and 9 now mean an additional condition
@@ -188,17 +201,4 @@
      paremtrization set parameter 8 to 0.
 
-   - star/ganymed: The old spark-cuts have been replaced by new ones.
-     These new spark cuts have been cross checked with the sequences
-     84720 (before splitter), 101041 (after splitter) and 223539 (new
-     FADCs). In all cases they seperate pretty well, but of course not
-     perfect. Monte Carlos have suggested to tighten the cuts a little
-     bit further at low sizes. This has been done.
-
-   - ganymed: IMPORTANT - The spark cuts have been changed to match
-     all available data more or less well. This might mean that for 
-     YOUR data there are still sparks visible. 
-     Whenever you do an analysis you have to make sure that NO sparks
-     survive your cuts!
-
    - ganymed: The distribution of observation time versus zenith
      angle is now shown for off- AND on-data.
@@ -209,5 +209,4 @@
      all off-regions from this file. Please do not forget to
      set the scaling in optimwobble.C properly:
-        fit.SetScaleMode(MAlphaFitter::kNone);
         fit.SetScaleUser(1./3);
      it is not yet read in automatically (will follow soon).
@@ -244,9 +243,9 @@
      the information is lost.
 
-   - sponde: added a new tab "EventDist" showing the unweighted event
-     distribution of your sample after cuts. This tells you how many
-     events with this energy you had in your MC files. The same information
-     you get from the error bars of the weighted histograms, but this is
-     less intuitive.
+   - sponde: added a new tab "EventDist" showing the unweighted real
+     absolute number of events of your sample after cuts. This tells
+     you how many events with this energy you had in your MC files.
+     The same information you get from the error bars of the weighted
+     histograms, but this is less intuitive.