--------------------------------------------
 January 2005  McPherson / von der Schmitt
 Requests and requirements from Commissioning
 --------------------------------------------

  1) We need a strategy for a commissioning release
     build and maintenance.  We expect

       - Frequent small modifications to converters.
       - Occaisional modifications to reconstruction.
       - Frequent additions to monitoring plots.
       - Many non-developer users from detector community
         who will not want to use nightlies, and not
         want to learn how to build sets of new tags
         into private areas.
       - Desire to run on bytestream files from
         both point 1 "commissioning" computers and
         also remote sites.

     We assume that distribution kits will be used for builds 
     at point 1, for the EF, and external sites.
     Therefore, we request the ability to patch small 
     amounts of non-core code into distributes kits 
     in a semi-automatic way.  

     Eg, imagine release X with kit version N is installed
     on a file server at point 1, or at an institute.
     If would be useful if a modification to
     one or more packages could be applied to produce
     the equivalent of kit version N+1, etc.

  2) A simple and robust run-time environment is essential 
     for non-expert use.  The precise definition of "simple"
     and "robust" varies from person to person.
     Some examples of user preferences:

        - A configuration/run script (jobOption) that
          "fits on one screen" (or so), and does not
          require understanding multiple, nested python
          files.  Eg, minimization of depencies in
          python scripts on global variables set/used
          in hidden ways.

        - Ability to run analysis on only selected
          trigger or particle types using simple
          selection tools (eg, trigger selection tools
          in sequencers, or similar functionality).

   3) Detector DB concerns
        - Timescales for COOL/DB, relational POOL w.r.t.
          commissioning timescales.  Encourage agressive
          integration schedule into the offline framework.
        - Connectivity to conditions DB from computers in
          the private pit 1 network in early commissioning
          period.