Difference: TCKPresenter (1 vs. 14)

Revision 142010-03-03 - JeskoMerkel

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"

TCK-Presenter

Added:
>
>
Most of the stuff here is probably outdated. The webpage of the TCK Presenter is http://lbtckpresenter.cern.ch/
 

Introduction

The TCK-Presenter is a tool to visualize a con guration of the High Level Trigger from the LHCb experiment. It should e.g. help the expert shifter to understand the trigger configuration or can be used by somebody working on an offine analysis to understand the trigger state which was used while taking data. The main requirements of the TCK-Presenter Project are:
  • to make an intuitive representation of the given TCK

Revision 132009-10-05 - unknown

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"

TCK-Presenter

Line: 36 to 36
 
  • python TCKProducer (the Path is hardcoded in the script, you might want to change it there)

To create trend plots for the rates, please launch the Online Presenter using the following switches:

Changed:
<
<
  • -K: key-file of the trigger configuration services to be trended. This is a simple text file, each line of which is a service identifier, such as: RICH1_Adder_1/GauchoJob/MonitorSvc/monRate/Hlt1Hlt1GlobalLineAccepts. An example file can be found in: /var/www/vhosts/tck_presenter/httpdocs/TCKs/TCK>/basic/dump
>
>
  • -K: key-file of the trigger configuration rate services to be trended. This is a simple text file, each line of which is a service identifier, such as: RICH1_Adder_1/GauchoJob/MonitorSvc/monRate/Hlt1Hlt1GlobalLineAccepts. An example file can be found in: /var/www/vhosts/tck_presenter/httpdocs/TCKs/TCK>/basic/dump
 
  • -I: image path, to dump the plots of the trends, so that the TCKPresenter can pick up the plots. This would currently be: /var/www/vhosts/tck_presenter/httpdocs/historys/ The size can be set using -W and -H. Image plots have a timestamp and partition tag when created, please be careful when monitoring!
  • -M: mode to run the Presenter, in this case "batch" to bypass the GUI.
  • -P: partition to use. This will replace the first member of the service identifiers given in the key file with the partition specified (i.e. FEST)

Revision 122009-08-30 - unknown

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"

TCK-Presenter

Line: 37 to 37
  To create trend plots for the rates, please launch the Online Presenter using the following switches:
  • -K: key-file of the trigger configuration services to be trended. This is a simple text file, each line of which is a service identifier, such as: RICH1_Adder_1/GauchoJob/MonitorSvc/monRate/Hlt1Hlt1GlobalLineAccepts. An example file can be found in: /var/www/vhosts/tck_presenter/httpdocs/TCKs/TCK>/basic/dump
Changed:
<
<
  • -I: image path, to dump the plots of the trends, so that the TCKPresenter can pick up the plots. This would currently be: /var/www/vhosts/tck_presenter/httpdocs/historys/ Image plots have a timestamp when created, please be careful when monitoring!
>
>
  • -I: image path, to dump the plots of the trends, so that the TCKPresenter can pick up the plots. This would currently be: /var/www/vhosts/tck_presenter/httpdocs/historys/ The size can be set using -W and -H. Image plots have a timestamp and partition tag when created, please be careful when monitoring!
 
  • -M: mode to run the Presenter, in this case "batch" to bypass the GUI.
  • -P: partition to use. This will replace the first member of the service identifiers given in the key file with the partition specified (i.e. FEST)

Revision 112009-08-29 - unknown

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"

TCK-Presenter

Line: 35 to 35
 The webpages will be created and are ready for the use of the http-server. If you want to create all TCKs which are not yet created just run:
  • python TCKProducer (the Path is hardcoded in the script, you might want to change it there)
Added:
>
>
To create trend plots for the rates, please launch the Online Presenter using the following switches:
  • -K: key-file of the trigger configuration services to be trended. This is a simple text file, each line of which is a service identifier, such as: RICH1_Adder_1/GauchoJob/MonitorSvc/monRate/Hlt1Hlt1GlobalLineAccepts. An example file can be found in: /var/www/vhosts/tck_presenter/httpdocs/TCKs/TCK>/basic/dump
  • -I: image path, to dump the plots of the trends, so that the TCKPresenter can pick up the plots. This would currently be: /var/www/vhosts/tck_presenter/httpdocs/historys/ Image plots have a timestamp when created, please be careful when monitoring!
  • -M: mode to run the Presenter, in this case "batch" to bypass the GUI.
  • -P: partition to use. This will replace the first member of the service identifiers given in the key file with the partition specified (i.e. FEST)
 

Implementation

Several different modules are used in the implementation of the TCK-Presenter. The basis for the visualisation are the return values of the getAlgorithms-function and the getProperties-function in the TCKUtils package. Both functions take a TCK as an argument. The return value of the getAlgorithms function shows the collection of algorithms used in the high level trigger. The getProperties gives thresholds back used in the trigger configuration. The dotcreater script takes those strings and converts them into a dot-string for each webpage (written in the dot language for graph representations), which is then converted into an svg picture embedded into a xhtml site. The conversion is done by pydot. Two main webpage structures are created. One is for the offline view the other is for the online view. The tree structures remain the same. However it is possible to fill additional data in the basic structure for the online view, which will be done by the apache server. After the webpages are created they are saved in a certain directory on plus501. Typically the directory is /var/www/vhosts/tck presenter/hhtpdoc/TCKs/. The basic structure will be put in directory/TCKs/TCK/basic/ the offline structure in directory/TCKs/TCK/offline/. The access to the webpages is given through a startpage, which takes the TCK, partition and the modus (on-/offine). The apache server will load a basic structure or a offline structure of the TCK tree in respect to which modus was choosen.

Revision 102009-08-25 - unknown

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
Changed:
<
<

TCK Presenter Project

  • The LHCb experiment plans to take data at a rate of 1MHz (after reduction by the L0 hardware trigger). This data arrives in the Event Filter Farm, where it is reduced to a few kHz by the (software) High Level Trigger. The HLT is a flexible program, consisting of alleys (a sequence of algorithms to reduce the rate, for example the confirmation of a L0 muon candidate by various subdetectors). The sequences of algorithms inside an alley are called lines. The algorithms reduce the rate to a sufficient low level to allow a full pattern recognition on the remaining events. The configuration of the HLT, which lines to include, and what cuts to apply is determined by a Trigger Configuration Key. The project consists of building a graphical representation of the dataflow though the HLT, starting from the TCK and labeling connections with the cuts applied. It is intended that this tool will be helpful to the person on shift who is responsible for the operation of the experiment, adapting the configuration of the HLT as the running conditions vary.
>
>

TCK-Presenter

 
Changed:
<
<

Goal of the project (summer and beyond...): make a graphical representation of a TCK

  • For the offline user:
    • To visualize the Trigger Configuration which was used to obtain the data set the user wants to analyze.
    • Should be set up like a webpage (similar idea as the bookkeeping) with a tree-type graph with the different trigger paths. The configuration which is used shows up in color...
    • Start with a rough trigger layout (for example for Hlt just the alleys). If the user wants to know more detail (like the settings of the lines in an alley) he should be able to click on the relevant item. This should link to a new webpage with the detailed tree graph.
    • For a given dataset, you should be able to see the different lines which the data went through and the percentages of usage of a certain line.
  • For the online user:
    • When a run starts the shifter should be able to see which TCK is being used and which one was used in the previous run.
    • Extra feature, the rates at every level should be displayed as well.

How to do so

  • Gerhard made a python script that reads a TCK and produces in text format the trigger path TCK talk 19th of March.
  • Using pydot, you can turn this text into a graph.
  • This needs to be saved in SVG "a language for describing two-dimensional graphics and graphical applications in XML".
  • Make the subparts "clickable" and develop further in a webpage (html).
>
>

Introduction

The TCK-Presenter is a tool to visualize a con guration of the High Level Trigger from the LHCb experiment. It should e.g. help the expert shifter to understand the trigger configuration or can be used by somebody working on an offine analysis to understand the trigger state which was used while taking data. The main requirements of the TCK-Presenter Project are:
  • to make an intuitive representation of the given TCK
  • to make the representation technically easy (no additional tools or plugins should be required by the user)
  • to make the code flexible for further implementations
The representation is based on webpages, which show the algorithms of the HLT as a tree. The webpages will conform to the HTML standard, meaning that no plugins for the webbrowser are needed. In addition it is possible to see the rates and retention fractions in the representation. The tree structure contains four levels.
  • HLT1 and HLT2, the two main parts of the HLT
  • alleys
  • lines
  • flow of sequences inside a line (cuts, track extrapolation, vertexing
The nodes contain various information. All nodes have a name, colour and text. There are four types of nodes, which are coloured different. Most of the nodes are green, e.g. the physics alleys and lines. Some of the alleys are for technical reasons and coloured in purple. The cuts in the sequence flow of a line are yellow. The text below a node shows rates and retention fractions. The representation using webpages is split into two parts. The offine and the online part. The difference between them is that the offine part is not filled with any rates or retention fractions, so that no continuous update of the pages is needed. One can choose the TCK, the partition and the modus (off-/online) in the indexpage on plus501. This site contains all available TCKs.

Important points

  • If you change the offline-scripts or the http-server, you might need to reproduce the webpages. If so, just delete the old folder for the TCKs you want to reproduce and rerun the script.
  • pydot and pyROOT are running on plus501. But it was configured very fast. Contact Niko if problems appear.

Meetings

  • Hlt Commissioning meeting: every week Monday at 16h00 (2-1-027).
 

Documentation

  • To get an idea of the general trigger structure. The example of the data flow can be used as an example trigger configuration.
Line: 25 to 28
 

Changed:
<
<

Meetings

  • Hlt Commissioning meeting: every week Monday at 16h00 (2-1-027).
>
>

use the TCK-Presenter

  • The directory used for the TCKs is /var/www/vhosts/Tck presenter/httpdocs/TCKs/ on plus501
To use the TCK-Presenter one needs to go on http://plus501. The Indexpage with various options shows up. If a TCK webpage structure was already created the TCK is available in the combobox of the Indexpage. One needs to choose only a TCK for the offline view and a partition in addition for the online view. If a TCK is not available in the combobox, the TCK needs to be created. Start the TCK-Presenter on plus501 with:
  • python TCKPresenter <TCK> /var/www/vhosts/Tck presenter/httpdocs/TCKs/
The webpages will be created and are ready for the use of the http-server. If you want to create all TCKs which are not yet created just run:
  • python TCKProducer (the Path is hardcoded in the script, you might want to change it there)

Implementation

Several different modules are used in the implementation of the TCK-Presenter. The basis for the visualisation are the return values of the getAlgorithms-function and the getProperties-function in the TCKUtils package. Both functions take a TCK as an argument. The return value of the getAlgorithms function shows the collection of algorithms used in the high level trigger. The getProperties gives thresholds back used in the trigger configuration. The dotcreater script takes those strings and converts them into a dot-string for each webpage (written in the dot language for graph representations), which is then converted into an svg picture embedded into a xhtml site. The conversion is done by pydot. Two main webpage structures are created. One is for the offline view the other is for the online view. The tree structures remain the same. However it is possible to fill additional data in the basic structure for the online view, which will be done by the apache server. After the webpages are created they are saved in a certain directory on plus501. Typically the directory is /var/www/vhosts/tck presenter/hhtpdoc/TCKs/. The basic structure will be put in directory/TCKs/TCK/basic/ the offline structure in directory/TCKs/TCK/offline/. The access to the webpages is given through a startpage, which takes the TCK, partition and the modus (on-/offine). The apache server will load a basic structure or a offline structure of the TCK tree in respect to which modus was choosen.
  • It is important to point out that the view is separated into an offline and online part as well as the creation of the webpages. Both are independent from each other and mean something different.

File structure

The fi le structure on plus501 (basic and offine):

  • /var/www/vhost/tck presenter/httpdocs/TCKs/TCK/basic/ + basic_<pagename>.xhtml
  • /var/www/vhost/tck presenter/httpdocs/TCKs/TCK/offline/ + extended_<pagename>.xhtml
Where <pagename> is de fined as <pagename> := <Hlt>(_<system>(_<alley>(_<line>))) Brackets mean that these part of the naming is optional. Examples for them are:
  • <Hlt>_<system>_<alley>_<line> = Hlt_Hlt1_DiMuon_Hlt1DiMuonNoIPL0Seg
  • <Hlt>_<system>_<alley>_<line> = Hlt_Hlt1_Hadron_Hlt1SoftDiHadron

replacer

TCKUtils.utils is a package in Moore, which contains functions. The getAlgorithms-function returns a string of algorithms deployed by a given TCK. The string contains already the HLT algorithm hierarchy. The string is read in by the dotcreater, who will transform the string in a tree structure.

beschreibe die struktur (whitespaces), hierarchie,

First of all the dot creator reads in the data for a certain TCK given by TCKUtils.utils. Somehow some of the line names may contain letters which can make problems in the svg representation. For this reason, the names are coded in a distinct way.

Important for the handling are the following functions:

  • replacer_to_code( word ) replaces some letters to codings. Important is that "_" is replaced first.
  • replacer_to_html( word ) replaces some letters to html readable signs.
  • replacer_to_sign( word ) replaces some codes back to there original letters.

It should be the case that replacer_to_sign(replacer_to_code( word )) = word for all possible words. As well as the fact that all possible siges which can appear are handled. The rules are in myConst. Here an example:

replacer_to_html(replacer_to_code( "Hlt1L0DiMuon,low_Mult>bla" )) = replacer_to_html( "Hlt1L0DiMuon_002_low_001_Mult_003_bla" ) = "Hlt1L0DiMuon‚low_Mult>bla"

  • "_" was substituted by "_002_"
  • ">" was substituted by "_003_"
 
Changed:
<
<
-- EricvanHerwijnen - 15 May 2009
>
>
-- KlausNeumann - 2009-08-25
 
META FILEATTACHMENT attachment="presenterproject.png" attr="" comment="representes the relations between the scripts" date="1249564952" name="presenterproject.png" path="presenterproject.png" size="2953" stream="presenterproject.png" user="Main.KlausNeumann" version="1"
META FILEATTACHMENT attachment="graphstructure.png" attr="" comment="the structure of the TCK tree" date="1249569223" name="graphstructure.png" path="graphstructure.png" size="6804" stream="graphstructure.png" user="Main.KlausNeumann" version="1"
Added:
>
>
META FILEATTACHMENT attachment="offline_access.PNG" attr="" comment="use case: client wants to see the offline representation of a given TCK" date="1251192586" name="offline_access.PNG" path="offline_access.PNG" size="32415" stream="offline_access.PNG" tmpFilename="/usr/tmp/CGItemp64959" user="klaus_2eneumann_40cern_2ech" version="1"
META FILEATTACHMENT attachment="online_access.PNG" attr="" comment="use case: client wants to see the online representation of a given TCK" date="1251192628" name="online_access.PNG" path="online_access.PNG" size="35253" stream="online_access.PNG" tmpFilename="/usr/tmp/CGItemp65048" user="klaus_2eneumann_40cern_2ech" version="1"

Revision 92009-08-06 - KlausNeumann

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"

TCK Presenter Project

  • The LHCb experiment plans to take data at a rate of 1MHz (after reduction by the L0 hardware trigger). This data arrives in the Event Filter Farm, where it is reduced to a few kHz by the (software) High Level Trigger. The HLT is a flexible program, consisting of alleys (a sequence of algorithms to reduce the rate, for example the confirmation of a L0 muon candidate by various subdetectors). The sequences of algorithms inside an alley are called lines. The algorithms reduce the rate to a sufficient low level to allow a full pattern recognition on the remaining events. The configuration of the HLT, which lines to include, and what cuts to apply is determined by a Trigger Configuration Key. The project consists of building a graphical representation of the dataflow though the HLT, starting from the TCK and labeling connections with the cuts applied. It is intended that this tool will be helpful to the person on shift who is responsible for the operation of the experiment, adapting the configuration of the HLT as the running conditions vary.
Line: 31 to 31
 -- EricvanHerwijnen - 15 May 2009

META FILEATTACHMENT attachment="presenterproject.png" attr="" comment="representes the relations between the scripts" date="1249564952" name="presenterproject.png" path="presenterproject.png" size="2953" stream="presenterproject.png" user="Main.KlausNeumann" version="1"
Added:
>
>
META FILEATTACHMENT attachment="graphstructure.png" attr="" comment="the structure of the TCK tree" date="1249569223" name="graphstructure.png" path="graphstructure.png" size="6804" stream="graphstructure.png" user="Main.KlausNeumann" version="1"

Revision 82009-08-06 - KlausNeumann

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"

TCK Presenter Project

  • The LHCb experiment plans to take data at a rate of 1MHz (after reduction by the L0 hardware trigger). This data arrives in the Event Filter Farm, where it is reduced to a few kHz by the (software) High Level Trigger. The HLT is a flexible program, consisting of alleys (a sequence of algorithms to reduce the rate, for example the confirmation of a L0 muon candidate by various subdetectors). The sequences of algorithms inside an alley are called lines. The algorithms reduce the rate to a sufficient low level to allow a full pattern recognition on the remaining events. The configuration of the HLT, which lines to include, and what cuts to apply is determined by a Trigger Configuration Key. The project consists of building a graphical representation of the dataflow though the HLT, starting from the TCK and labeling connections with the cuts applied. It is intended that this tool will be helpful to the person on shift who is responsible for the operation of the experiment, adapting the configuration of the HLT as the running conditions vary.
Line: 28 to 28
 

Meetings

  • Hlt Commissioning meeting: every week Monday at 16h00 (2-1-027).
Deleted:
<
<
 -- EricvanHerwijnen - 15 May 2009 \ No newline at end of file
Added:
>
>
META FILEATTACHMENT attachment="presenterproject.png" attr="" comment="representes the relations between the scripts" date="1249564952" name="presenterproject.png" path="presenterproject.png" size="2953" stream="presenterproject.png" user="Main.KlausNeumann" version="1"

Revision 72009-05-27 - KimVervink

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"

TCK Presenter Project

  • The LHCb experiment plans to take data at a rate of 1MHz (after reduction by the L0 hardware trigger). This data arrives in the Event Filter Farm, where it is reduced to a few kHz by the (software) High Level Trigger. The HLT is a flexible program, consisting of alleys (a sequence of algorithms to reduce the rate, for example the confirmation of a L0 muon candidate by various subdetectors). The sequences of algorithms inside an alley are called lines. The algorithms reduce the rate to a sufficient low level to allow a full pattern recognition on the remaining events. The configuration of the HLT, which lines to include, and what cuts to apply is determined by a Trigger Configuration Key. The project consists of building a graphical representation of the dataflow though the HLT, starting from the TCK and labeling connections with the cuts applied. It is intended that this tool will be helpful to the person on shift who is responsible for the operation of the experiment, adapting the configuration of the HLT as the running conditions vary.
Line: 15 to 15
 

How to do so

Changed:
<
<
  • Using pydot, you can turn this text into a graph
>
>
  • Using pydot, you can turn this text into a graph.
 
  • This needs to be saved in SVG "a language for describing two-dimensional graphics and graphical applications in XML".
Changed:
<
<
  • Make the subparts "clickable" and develop further in a webpage (html)
  • Something with qdot?
>
>
  • Make the subparts "clickable" and develop further in a webpage (html).
 

Documentation

Changed:
<
<
>
>
 

Meetings

Changed:
<
<
  • Hlt Commissioning meeting: every week at 16h00 (2-1-027)
>
>
  • Hlt Commissioning meeting: every week Monday at 16h00 (2-1-027).
 

-- EricvanHerwijnen - 15 May 2009

Revision 62009-05-18 - KimVervink

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"

TCK Presenter Project

  • The LHCb experiment plans to take data at a rate of 1MHz (after reduction by the L0 hardware trigger). This data arrives in the Event Filter Farm, where it is reduced to a few kHz by the (software) High Level Trigger. The HLT is a flexible program, consisting of alleys (a sequence of algorithms to reduce the rate, for example the confirmation of a L0 muon candidate by various subdetectors). The sequences of algorithms inside an alley are called lines. The algorithms reduce the rate to a sufficient low level to allow a full pattern recognition on the remaining events. The configuration of the HLT, which lines to include, and what cuts to apply is determined by a Trigger Configuration Key. The project consists of building a graphical representation of the dataflow though the HLT, starting from the TCK and labeling connections with the cuts applied. It is intended that this tool will be helpful to the person on shift who is responsible for the operation of the experiment, adapting the configuration of the HLT as the running conditions vary.

Goal of the project (summer and beyond...): make a graphical representation of a TCK

  • For the offline user:
Changed:
<
<
    • To visualise the Trigger Configuration which was used to obtain the data set the user wants to analyse.
>
>
    • To visualize the Trigger Configuration which was used to obtain the data set the user wants to analyze.
 
    • Should be set up like a webpage (similar idea as the bookkeeping) with a tree-type graph with the different trigger paths. The configuration which is used shows up in color...
    • Start with a rough trigger layout (for example for Hlt just the alleys). If the user wants to know more detail (like the settings of the lines in an alley) he should be able to click on the relevant item. This should link to a new webpage with the detailed tree graph.
Added:
>
>
    • For a given dataset, you should be able to see the different lines which the data went through and the percentages of usage of a certain line.
 
  • For the online user:
    • When a run starts the shifter should be able to see which TCK is being used and which one was used in the previous run.
    • Extra feature, the rates at every level should be displayed as well.

Revision 52009-05-17 - KimVervink

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"

TCK Presenter Project

Changed:
<
<
>
>
  • The LHCb experiment plans to take data at a rate of 1MHz (after reduction by the L0 hardware trigger). This data arrives in the Event Filter Farm, where it is reduced to a few kHz by the (software) High Level Trigger. The HLT is a flexible program, consisting of alleys (a sequence of algorithms to reduce the rate, for example the confirmation of a L0 muon candidate by various subdetectors). The sequences of algorithms inside an alley are called lines. The algorithms reduce the rate to a sufficient low level to allow a full pattern recognition on the remaining events. The configuration of the HLT, which lines to include, and what cuts to apply is determined by a Trigger Configuration Key. The project consists of building a graphical representation of the dataflow though the HLT, starting from the TCK and labeling connections with the cuts applied. It is intended that this tool will be helpful to the person on shift who is responsible for the operation of the experiment, adapting the configuration of the HLT as the running conditions vary.
 

Goal of the project (summer and beyond...): make a graphical representation of a TCK

  • For the offline user:
Line: 13 to 13
 
    • Extra feature, the rates at every level should be displayed as well.

How to do so

Changed:
<
<
  • Gerhard made a python script that reads a TCK and produces in text format the trigger path ([[TCK talk 19th of March] [http://indico.cern.ch/getFile.py/access?contribId=89&sessionId=9&resId=1&materialId=slides&confId=52399]).
  • Using pydot you can turn this text into a graph
  • This needs to be saved in SVG "_a language for describing two-dimensional graphics and graphical applications in XML_", so you can easily make the graph "clickable"
  • Develop further in a webpage (html)
  • Something with
>
>
  • Gerhard made a python script that reads a TCK and produces in text format the trigger path TCK talk 19th of March.
  • Using pydot, you can turn this text into a graph
  • This needs to be saved in SVG "a language for describing two-dimensional graphics and graphical applications in XML".
  • Make the subparts "clickable" and develop further in a webpage (html)
  • Something with qdot?
 

Documentation

Changed:
<
<
  • Jint paper: to get an idea of the general trigger structure (no detail). The example of the data flow can be used as an example trigger configuration.
  • Note from Hugo
  • Notes on alleys
>
>

Meetings

  • Hlt Commissioning meeting: every week at 16h00 (2-1-027)
 

-- EricvanHerwijnen - 15 May 2009

Revision 42009-05-16 - KimVervink

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"

TCK Presenter Project

Deleted:
<
<

General information on the Hlt strategy (to read)

  • Jint paper: to get an idea of the general trigger structure (no detail). The example of the data flow can be used as an example trigger configuration.
  • Note from Hugo
  • Notes on alleys
 

Goal of the project (summer and beyond...): make a graphical representation of a TCK

  • For the offline user:
    • To visualise the Trigger Configuration which was used to obtain the data set the user wants to analyse.
Line: 18 to 12
 
    • When a run starts the shifter should be able to see which TCK is being used and which one was used in the previous run.
    • Extra feature, the rates at every level should be displayed as well.

Added:
>
>

How to do so

  • Gerhard made a python script that reads a TCK and produces in text format the trigger path ([[TCK talk 19th of March] [http://indico.cern.ch/getFile.py/access?contribId=89&sessionId=9&resId=1&materialId=slides&confId=52399]).
  • Using pydot you can turn this text into a graph
  • This needs to be saved in SVG "_a language for describing two-dimensional graphics and graphical applications in XML_", so you can easily make the graph "clickable"
  • Develop further in a webpage (html)
  • Something with

Documentation

  • Jint paper: to get an idea of the general trigger structure (no detail). The example of the data flow can be used as an example trigger configuration.
  • Note from Hugo
  • Notes on alleys
 

-- EricvanHerwijnen - 15 May 2009 \ No newline at end of file

Revision 32009-05-15 - KimVervink

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"

TCK Presenter Project

Revision 22009-05-15 - KimVervink

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"

TCK Presenter Project

Added:
>
>

General information on the Hlt strategy (to read)

  • Jint paper: to get an idea of the general trigger structure (no detail). The example of the data flow can be used as an example trigger configuration.
  • Note from Hugo
  • Notes on alleys

Goal of the project (summer and beyond...): make a graphical representation of a TCK

  • For the offline user: * To visualise the Trigger Configuration which was used to obtain the data set the user wants to analyse. * Should be set up like a webpage (similar idea as the bookkeeping) with a tree-type graph with the different trigger paths. The configuration which is used shows up in color... * Start with a rough trigger layout (for example for Hlt just the alleys). If the user wants to know more detail (like the settings of the lines in an alley) he should be able to click on the relevant item. This should link to a new webpage with the detailed tree graph.
  • For the online user:
    • When a run starts the shifter should be able to see which TCK is being used and which one was used in the previous run.
    • Extra feature, the rates at every level should be displayed as well.

 -- EricvanHerwijnen - 15 May 2009 \ No newline at end of file

Revision 12009-05-15 - EricvanHerwijnen

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="LHCbTrigger"

TCK Presenter Project

-- EricvanHerwijnen - 15 May 2009

 
This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback