Draft for an EventView

Introduction

An EventView is a collection of physics objects which are coherent, exhaustive and mutually exclusive. EventViews are not unique; for each event a user may wish to consider the event with multiple different views. From this view, a user may wish to calculate several quantities (thrust, likelihood the event came from a given hypothesis, etc...) and associate it with the view (thus the collection of physics objects may include non-4momentum like entities).

To get more insight on what is really an EventView, go to the UCL workshop summary on AOD web page (http://www.usatlas.bnl.gov/PAT/)

UML diagram

something to think more carefully

class EventView;
namespace EvtView {
 class Manager;
 class Engine;
 class Strategy;
 class Rule;
 class Condition;
 class Consequence;
 class Criteria;
 class Action;
}

The user sets up a Strategy with the type of Actions she wants to take for each Rule which is defined (by the Manager). Each Rule has a set of Conditions (eg: has a track match) as well as a set of Consequences (eg: maybe an electron)

http://en.wikipedia.org/wiki/Fuzzy_logic

The algorithm machinery is hidden to the user and encapsulated in the Engine. The Manager should have two modus operandi :

• Check that some hypothesis can be verified, and returns the according (best or a set of) EventView,
• Find a default EventView from a set of Conditions
• UML-EventView:
  

At some extend, this EventView algorithm can be seen as an Expert System. Here is some preliminary bibliography :

• http://freelock.com/technical/expert.php
• http://en.wikipedia.org/wiki/Expert_system
• http://www.ericdigests.org/pre-9220/expert.htm
• http://www.ghg.net/clips/WhatIsCLIPS.html
• http://en.wikipedia.org/wiki/Prolog
• http://atlas-onlsw.web.cern.ch/Atlas-onlsw/components/RunControl/RunControlProposal.pdf

• SebastienBinet

-- SebastienBinet - 22 Mar 2005