Re: Monitor additions to BRAT

From: Anders Holm (aholm@alf.nbi.dk)
Date: Thu Jul 27 2000 - 04:03:18 EDT

  • Next message: Peter H. L. Christiansen: "BrTPCPreProcess memory leak"

    Hej Kris 
    
    You are entering a dangerous path:
    
    On Wed, 26 Jul 2000, Kris Hagel wrote:
    
    > Hello,
    > This message is to detail enhancements I made to the
    > monitoring.  The most substantial enhancement is to
    > implement a BrMonitorEvent which can be used in the
    > various detector monitors and be seen across the
    > monitors.  The way it works is follows:
    > 
    > 1. If you have a variable that you have worked hard to
    > unpack and want to give it to your friend in the monitor
    > next door, you would simply put in your code for
    > example:
    > SetEventVal(\"ZDC\",\"LeftAdcSum\",leftAdcSum);
    > SetEventVal(\"ZDC\",\"RightAdcSum\",rightAdcSum);
    > This is obviously if the ZDC monitor wishes to make the
    > variables leftAdcSum and rightAdcSum public to other
    > monitors.
    > 
    > 2. If you are working with another monitor and wish to
    > use for example the leftAdcSum and rightAdcSum
    > information that the ZDC monitor put into the event, the
    > way to access that information would be:
    > GetEventVal(\"ZDC\",\"LeftAdcSum\",leftAdcSum);
    > GetEventVal(\"ZDC\",\"RightAdcSum\",rightAdcSum);
    > Of course, this monitor could create his own information
    > and put it in using another table eg
    > SetEventVal(\"BB\",\"RightMult\",rightMult);
    > 
    > It should be noted that order of execution of the
    > monitors is important.  For example, in the example
    > above, the ZDC monitor supplies some information that BB
    > can use, but any information BB adds to the event cannot
    > be used by ZDC because it has already executed.  The
    > different monitor writers therefore will need to
    > negotiate their placement in the BrSuperMonitor list.
    > 
    > The other semi-substantial enhancement to
    > BrDetectorMonitor is that it now prints on the right
    > hand side under the buttons how much array space is
    > being used by the monitor.
    > 
    > These changes are committed to the repository.
    > 
    > Enjoy
    > 
    > Kris
    > 
    
    What if somone unknowingly brakes the assumed execution order? 
    
    There must be a mechanism to ensure the required execution order or a
    mechanism to give a warning if it is broken (events marked with event
    number and checked by the event receiver).
    
    Anders
    
    =========================================================
    Anders Holm                     email:   aholm@nbi.dk
    Niels Bohr institute            phone:   (45) 35 32 52 13 
    University of Copenhagen        fax:     (45) 35 32 50 16
    Blegdamsvej 17
    DK-2100 Copenhagen
    Denmark
    ========================================================
    



    This archive was generated by hypermail 2b29 : Thu Jul 27 2000 - 04:03:50 EDT