>>>>      Frameworks Meeting Minutes      <<<<
              ==============================================
      
                 Wednesday 04-Feb-1998 10:30-12:30
                       (Ninth Circle)

Present: Dhiman Chakraborty, Mike Diesburg, Stu Fuess, Herb Greenlee, 
         Jim Kowalkowski, Qizhong Li, Wyatt Merritt, Nobu Oshima, 
         Serban Protopopescu, Gordon Watts, Vicki White
Minutes taker: Qizhong Li

Agenda:
        . GUI Experience                           - Nobuaki Oshima
        
        . Status of batch framework                - Dhiman Chakraborty

        . Hook list                                - Qizhong Li

Nobu showed the event display framework uses GUI in many different ways.
He tried Motif+tk, Python+tk, web browser WIRED (WWW Interactive Remote
Event Display), open GL, etc.
His experience with Python+tk is successful, which could be extended to
be used for frameworks. Unfortunately the system upgrade to IRIX 6 made 
the program does not run temporarily. 

Dhiman gives the status of the batch framework. The code is put into d0cvs.
It has not been released yet because the problem with a makefile. The current
code does not have edm. Dhiman is working on the version using edm. Gordon
said, when the framework code can be released on d0chb, he will make sure
it also works on NT.
Several people asked Dhiman to put comments into the header files. Dhiman
will do it right way.

Qizhong has reviewed the Run I hook list. Total were 32 hooks in D0USER frame.
For Run II we surely want to have a smaller and simpler hook list. A set of
hooks were listed to initiate the discussion.
There were long and detailed discussions on the hook list for the framework.

Here is the hook list we all agreed on:

    . RunInit              (for run number dependent initialization, 
                            i.e. reading calibration constants)

    . MakeEvent            (The MakeEvent including reading event. 
                            There will also be a package MakeEvent, 
                            both hook and package are needed)

    . ProcessEvent         (the event loop)

    . DumpEvent            (Dump certain reconstructed information)

    . StatusReport         (status report)

    . EndRun               (after a run ended)

    . JobSummary           (end of job)

    . SkipEvent            (give a package a chance to skip events in case 
                            is needed)

    
In Run I, the results from a hook is a boolean variable (true or false). For
Run II framework, we decide that the results for each hook will be a class. 
There is an abstract class Results. Then each hook's results inheritates from 
this abstract class and adds its own data members if it is neccessary.


                                                 Qizhong