Difference: LHCbTriggerOnlineDocumentation (1 vs. 53)

Revision 532017-07-18 - SaschaStahl

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

HLT Online Reference Guide

Keywords: Setting the accept rate via PVSS,Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Fast run changes,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
Line: 102 to 102
 
  • Logs are kept in the directory /clusterlogs/partitions/LHCb/daq/LHCb.log ( old ones are zipped in the old directory). The logs are continuously appended to, so if you want to analyse one, make a copy.
  • Hlt2 logs are kept in /clusterlogs/partitions/LHCb2/daq/LHCb2.log
  • Error Logger SPAM filter. One can inhibit messages that appear too often:
Changed:
<
<
    • executing the shortcut /group/online/ecs/Shortcuts311/HLT/HLT/HLT_UI_FSM.sh
>
>
    • executing the shortcut /group/online/ecs/Shortcuts315/HLT/HLT/HLT_UI_FSM.sh
 
    • right click on +FARM
    • type in the word (or regular expression) in the box Filter (regular expression)
    • click on Add, then Apply on all subfarms

Revision 522015-09-11 - PatrickOwen

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

HLT Online Reference Guide

Keywords: Setting the accept rate via PVSS,Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Fast run changes,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
Line: 180 to 180
 

M

Monitoring Farm

  • Contact: Eric van Herwijnen
Added:
>
>

Mask output messages from HLT

  • Often it is useful to mask harmless output messages so that shifters can spot real problems easier. To do this:

  • Use TCKsh to find the component that is responsible for the message, for example the warning:

Sep10-182903[WARN] hltc0914: GaudiCheckpoint.exe(LHCb2_HLTC0914_Moore2_106): Hlt2TrackEff_D0ToKpiPionProbeDstDTFFilter.LoKi::DecayTreeFit:
 LoKi::DecayTreeFit:: The WARNING message is suppressed : 'Fitter failed status' StatusCode=111

* $> listProperties(0x010600a7, ".*Hlt2TrackEff_D0ToKpiKaonProbeDstDTFFilter.*", "OutputLevel")

which returns

   Requested Properties for Hlt2TrackEff_D0ToKpiKaonProbeDstDTFFilter.LoKi::DecayTreeFit
      'OutputLevel':4

  Requested Properties for Hlt2TrackEff_D0ToKpiKaonProbeDstDTFFilter
      'OutputLevel':4

  • Best be specific not to kill too many messages, so in this case ".*D0ToKpiKaonProbeDstDTFFilter.*DecayTreeFit" is better.

  • Then look at MooreOnlinePit_v24r1/MooreScripts/python/MooreScripts/runOnline.py and add the regex used to identify the components to the "comps" dictionary.

  • Do a "make install" in /group/hlt/sattelite/MooreOnlinePit_v24r1 as hlt_oper.

  • That will get rid of the warnings once tasks are reset.
 

L

Luminosity Monitoring

Revision 512015-08-27 - MatthewKenzie

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

HLT Online Reference Guide

Keywords: Setting the accept rate via PVSS,Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Fast run changes,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
Line: 94 to 94
 
  • This is what the Shift leader sees (the screen to the right hand side of the 3 main control screens)
  • To get the printouts (i.e. everything that Moore prints using the MsgSvc) of what is running, you need to open the errorLog
  • For that connect to plus with PuTTY
Changed:
<
<
  • Type: errorLog name-of-partition (LHCb, FEST, ...). Here you see the messages from the selected partition. For a different one replace LHCb for TDET or VELOA for instance.
>
>
  • Type: errorLog name-of-partition (LHCb, FEST, ...) - for example to see all messages from HLT2 type "errorLog LHCb2". Here you see the messages from the selected partition. For a different one replace LHCb for TDET or VELOA for instance.
 
  • You should see the error logger with 3 screens as in the screenshot. The top one prints the messages, the bottom left is reserved for the history and the bottom right is for the settings.
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrow and press enter
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.

Revision 502015-08-27 - SaschaStahl

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

HLT Online Reference Guide

Keywords: Setting the accept rate via PVSS,Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Fast run changes,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
Line: 99 to 99
 
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrow and press enter
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.
Changed:
<
<
  • Logs are kept in the directory /clusterlog/partitions/partition/daq/partition_year.month.day.log (e.g. /clusterlog/partitions/LHCb/daq/LHCb_2009.10.05.log). The logs are continuously appended to, so if you want to analyse one, make a copy.
>
>
  • Logs are kept in the directory /clusterlogs/partitions/LHCb/daq/LHCb.log ( old ones are zipped in the old directory). The logs are continuously appended to, so if you want to analyse one, make a copy.
  • Hlt2 logs are kept in /clusterlogs/partitions/LHCb2/daq/LHCb2.log
 
  • Error Logger SPAM filter. One can inhibit messages that appear too often:
    • executing the shortcut /group/online/ecs/Shortcuts311/HLT/HLT/HLT_UI_FSM.sh
    • right click on +FARM

Revision 492015-08-06 - SaschaStahl

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

HLT Online Reference Guide

Keywords: Setting the accept rate via PVSS,Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Fast run changes,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
Line: 101 to 101
 
  • Tip: You may want to disable mona08 to reduce the messages.
  • Logs are kept in the directory /clusterlog/partitions/partition/daq/partition_year.month.day.log (e.g. /clusterlog/partitions/LHCb/daq/LHCb_2009.10.05.log). The logs are continuously appended to, so if you want to analyse one, make a copy.
  • Error Logger SPAM filter. One can inhibit messages that appear too often:
Changed:
<
<
    • executing the shortcut /group/online/ecs/Shortcuts38/HLT/HLT/HLT_UI_FSM.sh
>
>
    • executing the shortcut /group/online/ecs/Shortcuts311/HLT/HLT/HLT_UI_FSM.sh
 
    • right click on +FARM
    • type in the word (or regular expression) in the box Filter (regular expression)
    • click on Add, then Apply on all subfarms

Revision 482012-05-30 - EricvanHerwijnen

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

HLT Online Reference Guide

Keywords: Setting the accept rate via PVSS,Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Fast run changes,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
Line: 91 to 91
 

The Error Logger

  • Contact: Markus Frank
Changed:
<
<
  • This is a diagnostic tool, to be used when Moore goes into error
>
>
  • This is what the Shift leader sees (the screen to the right hand side of the 3 main control screens)
 
  • To get the printouts (i.e. everything that Moore prints using the MsgSvc) of what is running, you need to open the errorLog
  • For that connect to plus with PuTTY
  • Type: errorLog name-of-partition (LHCb, FEST, ...). Here you see the messages from the selected partition. For a different one replace LHCb for TDET or VELOA for instance.
Line: 100 to 100
 
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.
  • Logs are kept in the directory /clusterlog/partitions/partition/daq/partition_year.month.day.log (e.g. /clusterlog/partitions/LHCb/daq/LHCb_2009.10.05.log). The logs are continuously appended to, so if you want to analyse one, make a copy.
Added:
>
>
  • Error Logger SPAM filter. One can inhibit messages that appear too often:
    • executing the shortcut /group/online/ecs/Shortcuts38/HLT/HLT/HLT_UI_FSM.sh
    • right click on +FARM
    • type in the word (or regular expression) in the box Filter (regular expression)
    • click on Add, then Apply on all subfarms
    • Close

 

F

Fast Run changes

Revision 472012-03-09 - EricvanHerwijnen

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

HLT Online Reference Guide

Keywords: Setting the accept rate via PVSS,Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Fast run changes,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
Line: 63 to 63
 interactions in specific bunch-crossings. E.g. the line with name Beam1Gas accepts only events which have ODIN BX Type equal to beam1 (i.e. beam1-empty). All three BG lines use the same C++ algorithms, but set different values for their properties.
Changed:
<
<
The Hlt2 should accept all events with a BG Hlt1 trigger (transparent Hlt2 selection to be implemented). The aimed Hlt output rate of events selected by the BG trigger is ~ 1 Hz. Detailed information about our trigger studies on Monte-Carlo simulated beam-gas events is available here.
>
>
The Hlt2 should accept all events with a BG Hlt1 trigger (transparent Hlt2 selection to be implemented). The aimed Hlt output rate of events selected by the BG trigger is ~ 1 Hz. Detailed information about our trigger studies on Monte-Carlo simulated beam-gas events is available here.
 
Changed:
<
<

Monitoring Reconstructed events with Brunel in the Monitoring Farm

>
>

Monitoring Reconstructed events with Brunel in the Reconstruction Farm

  • Contact: Patrick Koppenburg
 

C

Conditions DB snapshots

Changed:
<
<
  • Contact: Eric van Herwijnen & Gerhard Raven
>
>
  • Contact: Eric van Herwijnen
 
  • See here for a recipe how to make snapshots.
Changed:
<
<

Reading Online Conditions

  • Contact: Gerhard Raven, Clara Gaspar
  • The online conditions (Velo position, Magnetic field current) are written by PVSS at the start of the run in a file LHCB_online.xml, FEST_online.xml, TDET_online.xml. The values for LHCb are real, for FEST they can be set in PVSS, and for TDET they are fake. For none of the other partitions they are written.
>
>

Online Conditions

  • Contact: Clara Gaspar
  • The online conditions (Velo position, Magnetic field polarisation and current,Rich gas, Lumi parameters) are written by PVSS at the start of the run in a file LHCB_online.xml, FEST_online.xml, TDET_online.xml. The values for LHCb are real, for FEST they can be set in PVSS, and for TDET they are fake. For none of the other partitions they are written. They are written in the directory /group/online/hlt/conditions/partitionname.
 
  • All TCKs (except passthrough) require the online.xml file to exist, therefore subdetectors partitions should only use the passthrough TCK, so that it is ignored.

E

The Event Filter Farm (EFF)

Changed:
<
<
  • Contact: Eric van Herwijnen
>
>
  • Contact: Luis Granado Cardoso
 
  • The EFF is where the HLT will run and at the moment there are 50 subfarms installed.
Changed:
<
<
  • There are also a monitoring farm (MF, which gets a best effort fraction of events accepted by the HLT), a reconstruction farm (RF, part of the monitoring farm, and a calibration farm (CF, which gets a small rate of calibration triggers, only in the LHCb partition)
>
>
  • There are also a monitoring farm (MF, which gets a best effort fraction of events accepted by the HLT), a reconstruction farm (RF), and a calibration farm (CF, which gets a small rate, 50 Hz of calibration triggers, only in the LHCb partition)
 
  • Jobs are configured and started via the PVSS run control
  • You can select a 'partition': (LHCb = the default, normally the whole detector; FEST = simulated events are injected into the DAQ; one partition per subdetector including a 'test' subdetector called TDET)
  • Each partition gets allocated resources (part of the EFF, part of the MF & RF, part of the storage system)
Changed:
<
<
  • Each subfarm is called hlta01, hltb10, hltc06 etc and has 11 nodes that are called hlta0101, hlta0102 and so on.
  • Each of these nodes have 8 cores which means each subfarm can and will run 88 HLT processes at the same time.
>
>
  • Each subfarm is called hlta01, hltb10, hltc06 etc and has 27 nodes that are called hlta0101, hlta0102 and so on.
  • Each of these nodes have 16 cores which means each node can and will run 24 (1 master and 23 slaves) HLT processes at the same time. The 'A' farms are slower and only run 10 (1 master and 9 slaves) HLT processes on each node.
 
  • The HLT software ("Moore") is run under a PVSS device unit with the name "GauchoJob".
  • Whenever you need to compile something go to the plus machines (putty to plus).
  • For more information about job submission etc. in the EFF see the online piquet guide.
Line: 102 to 103
 

F

Fast Run changes

Changed:
<
<
  • contact: Gerhard Raven, Clara Gaspar
>
>
  • contact: Trigger group, Clara Gaspar
 A so called 'Fast' run change is obtained by selecting 'STOP TRIGGER' from the run control panel. Now the TCK can be changed by clicking on the Change button. The selection box with the TCKs becomes active and you can select one. By doing GO, triggers will be sent again, the runnumber will be changed, and you have done a fast run change. You can not change the trigger type (it is grayed out)

To change the trigger type, you have to STOP RUN. This first puts the Moore jobs in the READY state. Now, if you click on the Change button, you can also change the trigger type and a TCK inside it. After changing, the TFC, HLT, Storage & Monitoring will be reset, so the Moore jobs can read the new TCK upon initialization. This is a conventional run change.

H

Histograms to look at (Shifter)

Changed:
<
<
  • contact: Kim Vervink
>
>
  • contact: Trigger Group
 To ensure the trigger is functioning properly, the shifter should look at the following histograms:

Global

Global1

Line: 142 to 143
 In case of problems, the HLT piquet can look at the following histograms:

Lumi, LumiDAQMon, Monitoring (HltL0Monitoring, HltMonitoring) ?

HLT code in the pit (Moore)

Changed:
<
<
  • contact: Gerhard Raven
>
>
  • contact: Eric van Herwijnen
 
  • The HLT code installed in the pit is Moore. It is run from /group/hlt/MOORE, not from the release area /sw/lib/lhcb/MOORE
  • The latest version is usually not yet tagged in cvs
  • The HLT that is installed in the Online Cluster is
Line: 169 to 170
 

M

Monitoring Farm

Changed:
<
<
  • Contact: Kim Vervink
>
>
  • Contact: Eric van Herwijnen
 

L

Luminosity Monitoring

Line: 218 to 219
 

[Piquet Shift info and duties

R

Deleted:
<
<

Looking at rates with the histogram Presenter

  • contact: Kim Vervink

Looking at rates with PVSS

  • contact: Eric van Herwijnen
 

Recompiling Moore

Changed:
<
<
  • contact: Gerhard Raven
  • Every version of Moore (say vnrm) is linked with a version of Online (say vxry).
>
>
  • contact: Eric van Herwijnen
  • Every version of Moore (say vnrm) is linked with a version of Online (say vxry). This is because a special version of Gaudi called GaudiOnline is run in the pit.
 
  • Moore is started from the following script: /group/online/ONLINE/Onlinevxry/Online/OnlineTasks/defaultfilter.sh vnrm subfarm partition runtype
    • this executes /group/hlt/MOORE/Moore_vnrm/Hlt/Moore/job/runMooreOnline_EFF.sh subfarm partition runtype
  • To each version of Moore corresponds a 'dev' version: Moore_vnrmdev (linked to Online_vxrydev)
Line: 251 to 248
 
  • For a list of things to look at when you are on piquet duty see here.

T

Deleted:
<
<

The TCK Presenter

  • contact: Stephan Nies
 

Testing Moore on lxplus

Changed:
<
<
  • contact: Gerhard Raven
>
>
  • contact: Eric van Herwijnen
 
  • getpack Hlt/Moore vnrm
  • setup the env: SetupProject Moore vnrm
  • normal way: go to Hlt/Moore/cmt, do cmt config, source setup.csh, cmt br make

Revision 462010-02-16 - EricvanHerwijnen

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

HLT Online Reference Guide

Changed:
<
<
Keywords: Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Fast run changes,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
>
>
Keywords: Setting the accept rate via PVSS,Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Fast run changes,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
 
Changed:
<
<
  1. Nothing yet with A
>
>
  1. Setting the accept rate via PVSS
 
  1. Beam Gas, Brunel output monitoring
  2. Conditions DB snapshots,
Line: 44 to 44
 
Added:
>
>

A

Setting the accpet rate via PVSS

The accept rate for Moore can be set in PVSS, provided this is mentioned in the comment of the selected TCK. For example, the PassThrough HLT Type for Moore v8r6 has the comment 'ODINPhys,Timing acc=1, ODINTech,Aux,NZS,Calib acc=PVSS, TELL1Error acc=0'. This means:

  • ODIN trigger type Phys is always accepted ODIN trigger type Timing is always accepted

  • ODIN trigger type Technical is accepted in a fraction of the events set by PVSS, ODIN trigger type Auxillary is accepted in a fraction of the events set by PVSS, ODIN trigger type Non-Zero-Suppressed is accepted in a fraction of the events set by PVSS, ODIN trigger type Calibration is accepted in a fraction of the events set by PVSS
 

B

Beam Gas

  • Contact: Plamen Hopchev
Line: 58 to 66
 The Hlt2 should accept all events with a BG Hlt1 trigger (transparent Hlt2 selection to be implemented). The aimed Hlt output rate of events selected by the BG trigger is ~ 1 Hz. Detailed information about our trigger studies on Monte-Carlo simulated beam-gas events is available here.

Monitoring Reconstructed events with Brunel in the Monitoring Farm

Deleted:
<
<
  • Contact: Kim Vervink
 

C

Conditions DB snapshots

  • Contact: Eric van Herwijnen & Gerhard Raven
Line: 82 to 89
 

The Error Logger

Deleted:
<
<
 
  • Contact: Markus Frank
  • This is a diagnostic tool, to be used when Moore goes into error
  • To get the printouts (i.e. everything that Moore prints using the MsgSvc) of what is running, you need to open the errorLog
Line: 92 to 98
 
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrow and press enter
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.
Changed:
<
<
  • Logs are kept in the directory /group/online/dataflow/logs/partition/partition_year.month.day.log (e.g. /group/online/dataflow/logs/LHCb/LHCb_2009.10.05.log). The logs are continuously appended to, so if you want to analyse one, make a copy.
>
>
  • Logs are kept in the directory /clusterlog/partitions/partition/daq/partition_year.month.day.log (e.g. /clusterlog/partitions/LHCb/daq/LHCb_2009.10.05.log). The logs are continuously appended to, so if you want to analyse one, make a copy.
 

F

Fast Run changes

Line: 193 to 199
 

P

The online histogram Presenter

  • contact: to be defined: Kim/Eric ?
Changed:
<
<
Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.

Select "Tools" -> "PageEditor"

In the Dialog box: disconect for the DB (histogram data base)

In the windows of the left, click in Cancel

Now you should see 2 new areas
in the right part of the Presenter Window.
One called "DIM Histogram Browser"
and one called "Histograms in Database"

Double click on the nodes name in the "DIM Histogram Browser" in this example "hltc03".

Select "HltGlobalMonitor" and check
"m_histoodinentry" and "m_histoodintype"

Right click and choose "Add checked to Database"

Now the selected data appears in the "Histograms in Database".

Select "Gaucho Job".
Check the data you are interested in.
Right click and select "Add checked histogram(s) to Page"

Now your histograms should appear in the main area of the presenter. You can place them with your mouse. When you press the green "Play" button they'll start updating.

>
>
Connect to plus.
You can start the presenter by typing
"/group/online/presenter/run_presenter.sh -D mona08"
on the command line. -D mona08 means you select the DIM DNS NODE mona08, so you can look at histograms from the top level adder on the EFF, as well as histograms from monitoring algorithms running on the monitoring farm.
Select the partition you are running with, i.e. FEST or LHCb.
 

Can't see histograms with the Presenter

If you can't see any histograms with the Presenter check the following;
Line: 311 to 294
 
  • LHC information published during the scan can be viewed with lumiScanLHCInfo.pnl panel in PVSS project LHCLUMI running at bcmdcs01w machine.
  • We should publish our luminosity counters measurements back to LHC. This is done by Gaudi monitor job at MF selecting and analyzing lumi events and providing DIM publications for LHCLUMI PVSS manager, which in turn sends this information to LHC PVSS project for publishing in DIP. PVSS panels showing this information online are currently under development. LHC uses this data to check the validity of VDM scan or to optimize beam positions.
Deleted:
<
<
<!-- /patternMoved-->
<!-- /patternMainContents-->
<!-- /patternMain-->

<!--  -->

<!-- /patternLeftBarContents-->
<!-- /patternLeftBar-->
<!-- /patternFloatWrap-->

<!-- /patternOuter-->
<!-- /patternWrapper-->
| Powered by TWiki |


  • |
<!-- /patternTopBar-->
This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback
<!-- /patternBottomBarContents-->
<!-- /patternBottomBar-->
<!-- /patternPage-->
<!-- /patternPageShadow-->
<!-- /patternScreen-->
 
META FILEATTACHMENT attachment="trigger-monitoring-070629.txt" attr="" comment="Minutes June 29, 2007" date="1183456511" name="trigger-monitoring-070629.txt" path="trigger-monitoring-070629.txt" size="2547" stream="trigger-monitoring-070629.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070511.txt" attr="" comment="Minutes May 11, 2007" date="1180443880" name="trigger-monitoring-070511.txt" path="trigger-monitoring-070511.txt" size="3000" stream="trigger-monitoring-070511.txt" user="Main.dijkstra" version="1"

Revision 452009-11-26 - EricvanHerwijnen

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

HLT Online Reference Guide

Changed:
<
<
Keywords: Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
>
>
Keywords: Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Fast run changes,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
 
  1. Nothing yet with A
  2. Beam Gas,
Line: 11 to 11
 
  1. Nothing yet with D
  2. The Event Filter Farm, The Error Logger
Changed:
<
<
  1. Nothing yet with F
>
>
  1. Fast Run Changes
 
  1. Nothing yet with G
  2. Histograms to look at (shifter), Histograms to look at (expert),
Line: 94 to 94
 
  • Tip: You may want to disable mona08 to reduce the messages.
  • Logs are kept in the directory /group/online/dataflow/logs/partition/partition_year.month.day.log (e.g. /group/online/dataflow/logs/LHCb/LHCb_2009.10.05.log). The logs are continuously appended to, so if you want to analyse one, make a copy.
Added:
>
>

F

Fast Run changes

  • contact: Gerhard Raven, Clara Gaspar
A so called 'Fast' run change is obtained by selecting 'STOP TRIGGER' from the run control panel. Now the
TCK can be changed by clicking on the Change button. The selection box with the TCKs becomes active and you can select one. By doing GO, triggers will be sent again, the runnumber will be changed, and you have done a fast run change. You can not change the trigger type (it is grayed out)

To change the trigger type, you have to STOP RUN. This first puts the Moore jobs in the READY state. Now, if you click on the Change button, you can also change the trigger type and a TCK inside it. After changing, the TFC, HLT, Storage & Monitoring will be reset, so the Moore jobs can read the new TCK upon initialization. This is a conventional run change.

 

H

Histograms to look at (Shifter)

  • contact: Kim Vervink

Revision 432009-10-29 - JaapPanman

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

HLT Online Reference Guide

Keywords: Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
Line: 161 to 161
 

L

Luminosity Monitoring

  • Contact: Jaap Panman
Added:
>
>
  • Luminosity accounting needs the "LumiTrigger" activated with sufficient rate (PVSS setting). Odin defines 4 (in principle) different random rates for each BXType.
  • The LumiLines in Moore need to be activated (select proper TCK). It can be checked in the HLT monitoring if the LumiLines are accepting any triggers.
  • Triggers accepted uniquely by the LumiLines will be stripped of most of their raw data, only Odin, HltLuminositySummary and DAQ banks survive. These small events are called "nano events".
  • The monitoring farm runs two monitoring tasks: LumiDAQMon just checks the LumiLines technically and produces histograms for the presenter, LumiVDMMon collects data to be send to the PVSS monitoring.
  • Luminosity PVSS panels show trends of luminosity, background, bunch currents etc.., and communicate key data to the LHC. In addition some important numbers are archived.
 

O

LHCb trigger: Online Documentation

Revision 422009-10-24 - unknown

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

HLT Online Reference Guide

Keywords: Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
Line: 47 to 47
 

B

Beam Gas

  • Contact: Plamen Hopchev
Added:
>
>
The beam-gas interactions trigger includes three major components:
  1. The HltBeamGasAlley package, which contains the C++ algorithms who actually do the triggering (inherit HltAlgorithm)
  2. The Configurable HltBeamGasLines which sets the properties of the C++ algorithms. It is part of the Hlt1Lines package
  3. The BeamGasMonitor package which contains monitoring algorithms and configuration files. It is part of the VanDerMeer project and is run in the monitoring farm.
The HltBeamGasLines Configurable creates and configures 3 independent Hlt1Lines. Each of them searches for beam-gas (BG) interactions in specific bunch-crossings. E.g. the line with name Beam1Gas accepts only events which have ODIN BX Type equal to beam1 (i.e. beam1-empty). All three BG lines use the same C++ algorithms, but set different values for their properties.

The Hlt2 should accept all events with a BG Hlt1 trigger (transparent Hlt2 selection to be implemented). The aimed Hlt output rate of events selected by the BG trigger is ~ 1 Hz. Detailed information about our trigger studies on Monte-Carlo simulated beam-gas events is available here.

 

Monitoring Reconstructed events with Brunel in the Monitoring Farm

  • Contact: Kim Vervink

C

Revision 402009-10-22 - EricvanHerwijnen

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

HLT Online Reference Guide

Keywords: Beam Gas,Brunel output monitoring,Conditions DB snapshots,Event Filter Farm,Error Logger,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet Guide, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
>
>

HLT Piquet Guide

Keywords: Beam Gas,Brunel output monitoring,Conditions DB snapshots,Reading Online Conditions,Event Filter Farm,Error Logger,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
 
  1. Nothing yet with A
  2. Beam Gas, Brunel output monitoring
Changed:
<
<
  1. Conditions DB snapshots
>
>
  1. Conditions DB snapshots, Reading Online conditions
 
  1. Nothing yet with D
  2. The Event Filter Farm, The Error Logger
Line: 46 to 47
 

B

Beam Gas

  • Contact: Plamen Hopchev
Deleted:
<
<
The implementation of the beam-gas trigger consists of 3 major components:
  1. ) The HltBeamGasAlley package which contains the C++ algorithms who actually do the triggering
  2. ) The Configurable which sets the values of the properties of the triggering algorithms - HltBeamGasLines.py, which is part of the Hlt1Lines package
  3. ) The monitoring configuration package ( Monitor/BeamGasMonitor ) which sets the monitoring sequence and configures the algorithms to be run in the Monitoring Farm (MF). This package is part of the VanDerMeer project.

The configurable HltBeamGasLines.py configures ...

Hlt2 should accept all events with a BG trigger

The total output rate of the BG alley should be in the order of 1 Hz.

 

Monitoring Reconstructed events with Brunel in the Monitoring Farm

  • Contact: Kim Vervink

C

Conditions DB snapshots

  • Contact: Eric van Herwijnen & Gerhard Raven
  • See here for a recipe how to make snapshots.
Changed:
<
<
>
>

Reading Online Conditions

  • Contact: Gerhard Raven, Clara Gaspar
  • The online conditions (Velo position, Magnetic field current) are written by PVSS at the start of the run in a file LHCB_online.xml, FEST_online.xml, TDET_online.xml. The values for LHCb are real, for FEST they can be set in PVSS, and for TDET they are fake. For none of the other partitions they are written.
  • All TCKs (except passthrough) require the online.xml file to exist, therefore subdetectors partitions should only use the passthrough TCK, so that it is ignored.
 

E

The Event Filter Farm (EFF)

  • Contact: Eric van Herwijnen
Line: 220 to 210
 
  • Click on it, then click on services. You should then see all rates and histograms published.
  • If the one you are looking for, isn't there, select the service LHCb_MONA0801_Adder_0/ Select it, then click on view/send In the window that pops up, type reconfigure This should do the trick.
Changed:
<
<

Piquet Guide

>
>

[Piquet Shift info and duties

 

R

Looking at rates with the histogram Presenter

Revision 392009-10-22 - unknown

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

HLT Online Reference Guide

Keywords: Beam Gas,Brunel output monitoring,Conditions DB snapshots,Event Filter Farm,Error Logger,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet Guide, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
Line: 46 to 46
 

B

Beam Gas

  • Contact: Plamen Hopchev
Added:
>
>
The implementation of the beam-gas trigger consists of 3 major components:
  1. ) The HltBeamGasAlley package which contains the C++ algorithms who actually do the triggering
  2. ) The Configurable which sets the values of the properties of the triggering algorithms - HltBeamGasLines.py, which is part of the Hlt1Lines package
  3. ) The monitoring configuration package ( Monitor/BeamGasMonitor ) which sets the monitoring sequence and configures the algorithms to be run in the Monitoring Farm (MF). This package is part of the VanDerMeer project.

The configurable HltBeamGasLines.py configures ...

Hlt2 should accept all events with a BG trigger

The total output rate of the BG alley should be in the order of 1 Hz.

 

Monitoring Reconstructed events with Brunel in the Monitoring Farm

  • Contact: Kim Vervink

C

Revision 382009-10-22 - EricvanHerwijnen

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

HLT Piquet Guide

Keywords: Beam Gas,Brunel output monitoring,Conditions DB snapshots,Event Filter Farm,Error Logger,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
>
>

HLT Online Reference Guide

Keywords: Beam Gas,Brunel output monitoring,Conditions DB snapshots,Event Filter Farm,Error Logger,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet Guide, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
 
  1. Nothing yet with A
  2. Beam Gas,
Line: 207 to 207
 
  • If the one you are looking for, isn't there, select the service LHCb_MONA0801_Adder_0/ Select it, then click on view/send In the window that pops up, type reconfigure This should do the trick.
Changed:
<
<

Piquet Shift info and duties

  • Declare your (non) availability at: http://lbshiftdb.cern.ch/index.py/login
  • HLT piquet phone: 16-1859 (from outside CERN: +41 76 487-1859)
  • Use the HLT elog-book: http://lblogbook.cern.ch/HLT+Trigger/ (register at same url if first time).
  • Piquet duty is for one week, starting at the end of the Monday HLT operatios meeting 12.00. At the end of the week, the piquet gives a report to the meeting.
  • Less experienced piquets are encouraged to co-piquet with the person doing duty the week before
  • The piquet should be able to get to the pit within 30 mins at any time during the week of shift
  • Read the http://lblogbook.cern.ch/Shift since TMath.Min('last time on shift'.'24 h')
  • The piquet should attend the daily run meetings at 9:00 in the pit
  • The piquet should attend the daily data quality meetings in the afternoon in the offline control room b. 2
  • The piquet should go to the HLT comissioning meeting at 16:00 on monday in Hans' office (Better to go the week before taking over as well)
  • What are the things that the piquet must do during his week to ensure the trigger is performing well, and take note of anything happening to the detector that may influence the data quality:
    • The piquet should subscribe to the lhcb-hlt-operations@cern.ch mailing list: https://e-groups.cern.ch/e-groups/Egroup.do?egroupName=lhcb-hlt-operations
    • At the start of run:
      • when LHCb goes into ERROR after CONFIGURE, do RECOVER then RESET then CONFIGURE
      • when LHCb goes into NOT_READY after CONFIGURE, due to the HLT going into NOT_READY, first RESET the HLT, then CONFIGURE
      • if RESET is not done under these circumstances, the histograms (in the presenter) and the rates (in the rate-presenter) will not be correct
      • if HLT keeps on going into ERROR, click on HLT, and on the unit in ERROR on each subsequent panel until you know what caused the ERROR
    • In the presenter (on the console to the right of the operator's console) open the HLT pages, first look at the Global page
      • check that the histograms are updated correctly (choose the partition and click on the green triangle if necessary)
    • open the rate-presenter * look at the number of processes and check it is correct * look at the rate xyz and compare it to the L0 rate on the operator's panel, it should be the same
    • After 15 minutes of running, check if the savesets are being saved and contain non-empty histograms * for Moore, and the monitoring tasks
    • When all this is ok, the system is configured properly everything is running
    • Now we need to check that the system does what it is supposed to do
    • Histograms and rates to be looked at: to be defined.
    • Offline tasks to do, histograms to look at
>
>

Piquet Guide

 

R

Looking at rates with the histogram Presenter

Revision 372009-10-21 - EricvanHerwijnen

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

HLT Piquet Guide

Changed:
<
<
Keywords: Beam Gas,Brunel output monitoring,Event Filter Farm,Error Logger,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
>
>
Keywords: Beam Gas,Brunel output monitoring,Conditions DB snapshots,Event Filter Farm,Error Logger,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
 
  1. Nothing yet with A
  2. Beam Gas, Brunel output monitoring
Changed:
<
<
  1. Nothing yet with C
>
>
  1. Conditions DB snapshots
 
  1. Nothing yet with D
  2. The Event Filter Farm, The Error Logger
Line: 48 to 48
 
  • Contact: Plamen Hopchev

Monitoring Reconstructed events with Brunel in the Monitoring Farm

  • Contact: Kim Vervink
Added:
>
>

C

Conditions DB snapshots

  • Contact: Eric van Herwijnen & Gerhard Raven
  • See here for a recipe how to make snapshots.
 

E

The Event Filter Farm (EFF)

Line: 61 to 65
 
  • Each of these nodes have 8 cores which means each subfarm can and will run 88 HLT processes at the same time.
  • The HLT software ("Moore") is run under a PVSS device unit with the name "GauchoJob".
  • Whenever you need to compile something go to the plus machines (putty to plus).
Changed:
<
<
  • For more information about the structure of the EFF look here.
>
>
 

The Error Logger

Line: 90 to 94
 Number of accepted events per HLT1 alley. How do the number of entries & integral correspond to the total number of events?

Global2

HLT1 alleys
Changed:
<
<
Figure is the same as on the previous page, just repeated for convenience.
>
>
Figure is the same as on the previous page, repeated for convenience.
 
HltLines Correlations
Correlation of lines vs lines.
HltLines inclusive
Line: 106 to 110
 

rejection stage

error

log (wall time/ms)

Deleted:
<
<

Lumi, LumiDAQMon, Monitoring (HltL0Monitoring, HltMonitoring) ?

 

Histograms to look at (Expert)

  • contact: Kim Vervink
In case of problems, the HLT piquet can look at the following histograms:
Added:
>
>

Lumi, LumiDAQMon, Monitoring (HltL0Monitoring, HltMonitoring) ?

 

HLT code in the pit (Moore)

  • contact: Gerhard Raven
  • The HLT code installed in the pit is Moore. It is run from /group/hlt/MOORE, not from the release area /sw/lib/lhcb/MOORE
Line: 122 to 126
 
  • The Random Alley just pre scales events by a certain factor defined by who is running it and the Physics accepts all the events.

HLT Farm (=EFF) in Error

  • contact: Eric van Herwijnen
Changed:
<
<
>
>
 

Adding Histograms to the Histogram DataBase

  • Contact: to be defined, Kim/Eric?
When the Presenter is running, you can add the display properties of your histograms to the database and save them creating new pages which will be directly available as you start the presenter:
Line: 207 to 211
 
Added:
>
>
  • Piquet duty is for one week, starting at the end of the Monday HLT operatios meeting 12.00. At the end of the week, the piquet gives a report to the meeting.
  • Less experienced piquets are encouraged to co-piquet with the person doing duty the week before
 
  • The piquet should be able to get to the pit within 30 mins at any time during the week of shift
  • Read the http://lblogbook.cern.ch/Shift since TMath.Min('last time on shift'.'24 h')
  • The piquet should attend the daily run meetings at 9:00 in the pit
  • The piquet should attend the daily data quality meetings in the afternoon in the offline control room b. 2
  • The piquet should go to the HLT comissioning meeting at 16:00 on monday in Hans' office (Better to go the week before taking over as well)
Changed:
<
<
  • What are the things that the piquet must do during his week to ensure the trigger is performing well:
>
>
  • What are the things that the piquet must do during his week to ensure the trigger is performing well, and take note of anything happening to the detector that may influence the data quality:
 

Revision 362009-10-21 - EricvanHerwijnen

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

HLT Piquet Guide

Keywords: Beam Gas,Brunel output monitoring,Event Filter Farm,Error Logger,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
Line: 53 to 53
 

The Event Filter Farm (EFF)

  • Contact: Eric van Herwijnen
  • The EFF is where the HLT will run and at the moment there are 50 subfarms installed.
Added:
>
>
  • There are also a monitoring farm (MF, which gets a best effort fraction of events accepted by the HLT), a reconstruction farm (RF, part of the monitoring farm, and a calibration farm (CF, which gets a small rate of calibration triggers, only in the LHCb partition)
  • Jobs are configured and started via the PVSS run control
  • You can select a 'partition': (LHCb = the default, normally the whole detector; FEST = simulated events are injected into the DAQ; one partition per subdetector including a 'test' subdetector called TDET)
  • Each partition gets allocated resources (part of the EFF, part of the MF & RF, part of the storage system)
 
  • Each subfarm is called hlta01, hltb10, hltc06 etc and has 11 nodes that are called hlta0101, hlta0102 and so on.
  • Each of these nodes have 8 cores which means each subfarm can and will run 88 HLT processes at the same time.
Changed:
<
<
  • The HLT software ("Moore") is run under "GauchoJob".
  • There is also a monitoring farm
  • Whenever you want to compile something go to the plus machines to not make the EFF machines busy (putty to plus).
>
>
  • The HLT software ("Moore") is run under a PVSS device unit with the name "GauchoJob".
  • Whenever you need to compile something go to the plus machines (putty to plus).
  • For more information about the structure of the EFF look here.
 

The Error Logger

Line: 76 to 80
 

Histograms to look at (Shifter)

  • contact: Kim Vervink
To ensure the trigger is functioning properly, the shifter should look at the following histograms:
Added:
>
>

Global

Global1

ODIN Trigger type
Number of events vs trigger type. The trigger types are: 0=Physics, 1=Beam Gas, 2=Lumi, 3=. The trigger types should correspond to the choosen TCK.
L0 channel
Number of events vs L0 alley. Check if one of the alleys is 0, or very large.
HLT1 alleys
Number of accepted events per HLT1 alley. How do the number of entries & integral correspond to the total number of events?

Global2

HLT1 alleys
Figure is the same as on the previous page, just repeated for convenience.
HltLines Correlations
Correlation of lines vs lines.
HltLines inclusive
Number of accepted events per line.

Global Time & Memory

Virtual memory per event
(What is plotted against what?)
Virtual memory
Time per event
Time per event dist

Hlt1 Lines

One histogram per line (46):

rejection stage

error

log (wall time/ms)

Lumi, LumiDAQMon, Monitoring (HltL0Monitoring, HltMonitoring) ?

 

Histograms to look at (Expert)

  • contact: Kim Vervink
In case of problems, the HLT piquet can look at the following histograms:

Revision 352009-10-21 - EricvanHerwijnen

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

HLT Piquet Guide

Changed:
<
<
Keywords: Beam Gas,Brunel output monitoring,Event Filter Farm,Error Logger,HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
>
>
Keywords: Beam Gas,Brunel output monitoring,Event Filter Farm,Error Logger,Histograms to look at (shifter),Histograms to look at (expert),HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
 
  1. Nothing yet with A
  2. Beam Gas,
Line: 12 to 12
  The Error Logger
  1. Nothing yet with F
  2. Nothing yet with G
Changed:
<
<
  1. HLT code in pit,
>
>
  1. Histograms to look at (shifter), Histograms to look at (expert), HLT code in pit,
  HLT (=EFF) farm in error, Adding Histograms to the Histogram Database
  1. Nothing yet with I
Line: 71 to 73
 
  • Logs are kept in the directory /group/online/dataflow/logs/partition/partition_year.month.day.log (e.g. /group/online/dataflow/logs/LHCb/LHCb_2009.10.05.log). The logs are continuously appended to, so if you want to analyse one, make a copy.

H

Added:
>
>

Histograms to look at (Shifter)

  • contact: Kim Vervink
To ensure the trigger is functioning properly, the shifter should look at the following histograms:

Histograms to look at (Expert)

  • contact: Kim Vervink
In case of problems, the HLT piquet can look at the following histograms:
 

HLT code in the pit (Moore)

  • contact: Gerhard Raven
  • The HLT code installed in the pit is Moore. It is run from /group/hlt/MOORE, not from the release area /sw/lib/lhcb/MOORE

Revision 342009-10-19 - VladislavBalagura

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

HLT Piquet Guide

Keywords: Beam Gas,Brunel output monitoring,Event Filter Farm,Error Logger,HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
Line: 265 to 265
 

V

Van der Meer

  • contact: Vladik Balagura
Added:
>
>
  • A full Van der Meer scan is performed to determine an absolute luminosity approximately once per month or per several months, while a partial scan (also called Vernier scan at LEP) can be done every fill to optimize positions of the beams.
  • The scan should be announced by LHC in advance. Before the scan, the LumiScan button on the TFC PVSS panel should be pressed to switch on incrementing the calibration step in ODIN. Normally it is off to prevent any LHC communication tests disturb normal LHCb data taking. Calibration step marks different steps during VDM scan when LHC magnets are stable and distinguishes VDM nano-events from normal nano-events.
  • LHC information published during the scan can be viewed with lumiScanLHCInfo.pnl panel in PVSS project LHCLUMI running at bcmdcs01w machine.
  • We should publish our luminosity counters measurements back to LHC. This is done by Gaudi monitor job at MF selecting and analyzing lumi events and providing DIM publications for LHCLUMI PVSS manager, which in turn sends this information to LHC PVSS project for publishing in DIP. PVSS panels showing this information online are currently under development. LHC uses this data to check the validity of VDM scan or to optimize beam positions.
 
<!-- /patternMoved-->
<!-- /patternMainContents-->
<!-- /patternMain-->

Revision 332009-10-19 - EricvanHerwijnen

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

HLT Piquet Guide

Added:
>
>
Keywords: Beam Gas,Brunel output monitoring,Event Filter Farm,Error Logger,HLT code in the pit, HLT in ERROR,Histogram Database,Luminosity Monitoring,Moore,Monitoring Farm,Online Documentation, Logging on to the Online Cluster,Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter,Looking at rates with the Presenter,Looking at rates with PVSS,How to recompile Moore,Run Control Status via Web,Starting a Run with the HLT,TCK Presenter,Testing Moore on lxplus,Testing a new version of Moore in the EFF,Van der Meer
 
  1. Nothing yet with A
  2. Beam Gas, Brunel output monitoring
Line: 149 to 151
 Now your histograms should appear in the main area of the presenter. You can place them with your mouse. When you press the green "Play" button they'll start updating.

Can't see histograms with the Presenter

Added:
>
>
If you can't see any histograms with the Presenter check the following;
  • You have selected the correct partition (normally LHCb)
  • If you see the message: "Error missing sources for ..." it means that the histogram is not being published
  • Check if the correct TCK is being used & if this histogram is published by the used version of Moore
  • Check if the top level Adder is running and is publishing the histogram correctly
  • Go to mona08.
  • Type : did
  • In the "View" menu, select "servers by node".
  • Then look for LHCb_MONA0801_Adder_0
  • Click on it, then click on services. You should then see all rates and histograms published.
  • If the one you are looking for, isn't there, select the service LHCb_MONA0801_Adder_0/ Select it, then click on view/send In the window that pops up, type reconfigure This should do the trick.
 

Piquet Shift info and duties

Revision 322009-10-08 - EricvanHerwijnen

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

HLT Piquet Guide

  1. Nothing yet with A
Line: 157 to 157
 
  • The piquet should be able to get to the pit within 30 mins at any time during the week of shift
  • Read the http://lblogbook.cern.ch/Shift since TMath.Min('last time on shift'.'24 h')
  • The piquet should attend the daily run meetings at 9:00 in the pit
Added:
>
>
  • The piquet should attend the daily data quality meetings in the afternoon in the offline control room b. 2
 
  • The piquet should go to the HLT comissioning meeting at 16:00 on monday in Hans' office (Better to go the week before taking over as well)
  • What are the things that the piquet must do during his week to ensure the trigger is performing well:

Revision 312009-10-07 - EricvanHerwijnen

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

HLT Piquet Guide

  1. Nothing yet with A
Line: 160 to 160
 
  • The piquet should go to the HLT comissioning meeting at 16:00 on monday in Hans' office (Better to go the week before taking over as well)
  • What are the things that the piquet must do during his week to ensure the trigger is performing well:
Added:
>
>
    • At the start of run:
      • when LHCb goes into ERROR after CONFIGURE, do RECOVER then RESET then CONFIGURE
      • when LHCb goes into NOT_READY after CONFIGURE, due to the HLT going into NOT_READY, first RESET the HLT, then CONFIGURE
      • if RESET is not done under these circumstances, the histograms (in the presenter) and the rates (in the rate-presenter) will not be correct
      • if HLT keeps on going into ERROR, click on HLT, and on the unit in ERROR on each subsequent panel until you know what caused the ERROR
    • In the presenter (on the console to the right of the operator's console) open the HLT pages, first look at the Global page
      • check that the histograms are updated correctly (choose the partition and click on the green triangle if necessary)
    • open the rate-presenter * look at the number of processes and check it is correct * look at the rate xyz and compare it to the L0 rate on the operator's panel, it should be the same
    • After 15 minutes of running, check if the savesets are being saved and contain non-empty histograms * for Moore, and the monitoring tasks
    • When all this is ok, the system is configured properly everything is running
    • Now we need to check that the system does what it is supposed to do
 
    • Histograms and rates to be looked at: to be defined.
    • Offline tasks to do, histograms to look at
Line: 190 to 204
 

S

The way the code runs (Starting a run with the HLT)

Changed:
<
<
  • contact: Clara Gaspar
  • Everything in the pit is controlled by PVSS.
>
>
  • Everything in the pit is controlled by PVSS (controls coordinator: Clara Gaspar).
 
  • This means that you have to run everything through PVSS panels. They control everything: High voltage, Data AQuisition, L0, HLT, Storage, Monitoring and so on.
  • You can chose what you want to run and set many properties in the PVSS panels that will make the option files that will be used for running for all the processes.
  • It is possible to run LHCb including as many detectors as one wants and it is also to possible to run a given subdetector in standalone mode (Each of this subdetectors or LHCb are called partitions).
  • There is also the TDET partition that controls 5 test Tell1s that send raw banks in the same format as they come from LHCb. That is the main testing environment we have to see if things work in real data.
Added:
>
>
  • For a list of things to look at when you are on piquet duty see here.
 

T

The TCK Presenter

Revision 302009-10-06 - EricvanHerwijnen

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

HLT Piquet Guide

  1. Nothing yet with A
Changed:
<
<
  1. Beam Gas Monitoring reconstructed events with Brunel in the Monitoring Farm
>
>
  1. Beam Gas, Brunel output monitoring
 
  1. Nothing yet with C
  2. Nothing yet with D
  3. The Event Filter Farm,

Revision 292009-10-05 - EricvanHerwijnen

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

HLT Piquet Guide

  1. Nothing yet with A
Changed:
<
<
  1. Nothing yet with B
>
>
  1. Beam Gas Monitoring reconstructed events with Brunel in the Monitoring Farm
 
  1. Nothing yet with C
  2. Nothing yet with D
  3. The Event Filter Farm,
Line: 15 to 16
 
  1. Nothing yet with I
  2. Nothing yet with J
  3. Nothing yet with K
Changed:
<
<
  1. Nothing yet with L
  2. Moore
>
>
  1. Luminosity Monitoring
  2. Moore,Monitoring Farm
 
  1. Nothing yet with N
Changed:
<
<
  1. Online Documentation, Logging on to the Online Cluster
  2. Piquet shift Info and duties, The online histogram Presenter
>
>
  1. Online Documentation, Logging on to the Online Cluster
  2. Piquet shift Info and duties, The online histogram Presenter, Can't see histograms with the presenter
 
  1. Nothing yet with Q
Changed:
<
<
  1. [[#RatesPresenter][Looking at rates with the Presenter] [[#RatesPresenter][Looking at rates with PVSS]
>
>
  1. Looking at rates with the Presenter, Looking at rates with PVSS,
  How to recompile Moore, Run Control Status via Web
  1. Starting a Run with the HLT
Changed:
<
<
  1. [[#TCKPresenter][TCK Presenter]
>
>
  1. TCK Presenter,
  Testing Moore on lxplus, Testing a new version of Moore in the EFF,
  1. Nothing yet with U
Changed:
<
<
  1. Nothing yet with V
>
>
  1. Van der Meer
 
  1. Nothing yet with W
  2. Nothing yet with X
  3. Nothing yet with Y
  4. Nothing yet with Z


Added:
>
>

B

Beam Gas

  • Contact: Plamen Hopchev

Monitoring Reconstructed events with Brunel in the Monitoring Farm

  • Contact: Kim Vervink
 

E

The Event Filter Farm (EFF)

  • Contact: Eric van Herwijnen
Line: 50 to 58
 

The Error Logger

  • Contact: Markus Frank
Added:
>
>
  • This is a diagnostic tool, to be used when Moore goes into error
 
  • To get the printouts (i.e. everything that Moore prints using the MsgSvc) of what is running, you need to open the errorLog
  • For that connect to plus with PuTTY
  • Type: errorLog name-of-partition (LHCb, FEST, ...). Here you see the messages from the selected partition. For a different one replace LHCb for TDET or VELOA for instance.
Line: 86 to 95
 
  • Write the desired path where the page should be located, the name for this page (label to appear in the left box) and a description of its content
  • Click OK when you are done
Added:
>
>

M

Monitoring Farm

  • Contact: Kim Vervink

L

Luminosity Monitoring

  • Contact: Jaap Panman
 

O

LHCb trigger: Online Documentation

Logging in the Online Cluster

Line: 131 to 148
  Now your histograms should appear in the main area of the presenter. You can place them with your mouse. When you press the green "Play" button they'll start updating.
Changed:
<
<

Piquet Shift info and duties

>
>

Can't see histograms with the Presenter

Piquet Shift info and duties

 
Line: 139 to 158
 
  • Read the http://lblogbook.cern.ch/Shift since TMath.Min('last time on shift'.'24 h')
  • The piquet should attend the daily run meetings at 9:00 in the pit
  • The piquet should go to the HLT comissioning meeting at 16:00 on monday in Hans' office (Better to go the week before taking over as well)
Added:
>
>
  • What are the things that the piquet must do during his week to ensure the trigger is performing well:
 
Added:
>
>
    • Histograms and rates to be looked at: to be defined.
    • Offline tasks to do, histograms to look at
 

R

Changed:
<
<

Recompiling Moore

>
>

Looking at rates with the histogram Presenter

  • contact: Kim Vervink

Looking at rates with PVSS

  • contact: Eric van Herwijnen

Recompiling Moore

 
  • contact: Gerhard Raven
  • Every version of Moore (say vnrm) is linked with a version of Online (say vxry).
  • Moore is started from the following script: /group/online/ONLINE/Onlinevxry/Online/OnlineTasks/defaultfilter.sh vnrm subfarm partition runtype
    • this executes /group/hlt/MOORE/Moore_vnrm/Hlt/Moore/job/runMooreOnline_EFF.sh subfarm partition runtype
  • To each version of Moore corresponds a 'dev' version: Moore_vnrmdev (linked to Online_vxrydev)
Changed:
<
<
  • To recompile the code:
>
>
  • The HLT piquet should never ever recompile Moore without consulting with Gerhard. If you do, proceed as follows:
 
    • NB! if you do it in the directory in use by the EFF, it can affect the run. The procedure is: make your test in the dev area, compile it there, test with TDET or FEST, and when sure that it works, recompile the directory production version.
    • set the project environment:
    • SetupProject Moore vnrm
Line: 162 to 189
 

S

Changed:
<
<

The way the code runs (Starting a run with the HLT)

>
>

The way the code runs (Starting a run with the HLT)

 
  • contact: Clara Gaspar
  • Everything in the pit is controlled by PVSS.
  • This means that you have to run everything through PVSS panels. They control everything: High voltage, Data AQuisition, L0, HLT, Storage, Monitoring and so on.
Line: 206 to 233
 
  • You can open errorLog TDET & and see the errors/warnings
  • When you are done, remember to give back the subfarm! go to FARM:TOP, and then mark remove, and refresh/do it click
Added:
>
>

V

Van der Meer

  • contact: Vladik Balagura
 
<!-- /patternMoved-->
<!-- /patternMainContents-->
<!-- /patternMain-->

Revision 282009-10-05 - EricvanHerwijnen

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

HLT Piquet Guide

Changed:
<
<

>
>
  1. Nothing yet with A
  2. Nothing yet with B
  3. Nothing yet with C
  4. Nothing yet with D
  5. The Event Filter Farm, The Error Logger
  6. Nothing yet with F
  7. Nothing yet with G
  8. HLT code in pit, HLT (=EFF) farm in error, Adding Histograms to the Histogram Database
  9. Nothing yet with I
  10. Nothing yet with J
  11. Nothing yet with K
  12. Nothing yet with L
  13. Moore
  14. Nothing yet with N
  15. Online Documentation, Logging on to the Online Cluster
  16. Piquet shift Info and duties, The online histogram Presenter
  17. Nothing yet with Q
  18. [[#RatesPresenter][Looking at rates with the Presenter] [[#RatesPresenter][Looking at rates with PVSS] How to recompile Moore, Run Control Status via Web
  19. Starting a Run with the HLT
  20. [[#TCKPresenter][TCK Presenter] Testing Moore on lxplus, Testing a new version of Moore in the EFF,
  21. Nothing yet with U
  22. Nothing yet with V
  23. Nothing yet with W
  24. Nothing yet with X
  25. Nothing yet with Y
  26. Nothing yet with Z
 
Changed:
<
<

LHCb trigger: Online Documentation

Piquet Shift info and duties

Run Control Status via Web in real time

Logging in the Online Cluster

  • To login into any machines from the pit you need an account on the Online Cluster. (For HLT Piquets you may use the hlt_shift account).
  • The connection between the Online cluster and the rest of the world has to be done through the gateway (lbgw01.cern.ch if you are in lxplus or gw01 if you are in the Online cluster).
  • The computers you can work from in the Control Room work in a "First come first serve" system. So chose anyone that is free.
  • As there are only Windows machines there you will need to export the display if you connect to any other machine. So starting Exceed is the first thing to do.

  • With Exceed opened you can connect to the machines with PuTTY.
  • But to export the display you should go to the Putty window in Connection > SSH > X11 check the Enable X11 forwarding box and in the X display location type in the machine you are logged in (there is a label with the name in the screen. It is for example lb018w where only the numbers can change).
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!
  • After the session is open you have to type: export DISPLAY=lb018w:0.0

The Event Filter Farm (EFF)

>
>

E

The Event Filter Farm (EFF)

  • Contact: Eric van Herwijnen
 
  • The EFF is where the HLT will run and at the moment there are 50 subfarms installed.
  • Each subfarm is called hlta01, hltb10, hltc06 etc and has 11 nodes that are called hlta0101, hlta0102 and so on.
  • Each of these nodes have 8 cores which means each subfarm can and will run 88 HLT processes at the same time.
Line: 41 to 47
 
  • There is also a monitoring farm
  • Whenever you want to compile something go to the plus machines to not make the EFF machines busy (putty to plus).
Changed:
<
<

HLT code in the pit

  • The HLT that is installed in the Online Cluster is absolutely not what is released and that you all know. It is a much simpler one.
>
>

The Error Logger

  • Contact: Markus Frank
  • To get the printouts (i.e. everything that Moore prints using the MsgSvc) of what is running, you need to open the errorLog
  • For that connect to plus with PuTTY
  • Type: errorLog name-of-partition (LHCb, FEST, ...). Here you see the messages from the selected partition. For a different one replace LHCb for TDET or VELOA for instance.
  • You should see the error logger with 3 screens as in the screenshot. The top one prints the messages, the bottom left is reserved for the history and the bottom right is for the settings.
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrow and press enter
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.
  • Logs are kept in the directory /group/online/dataflow/logs/partition/partition_year.month.day.log (e.g. /group/online/dataflow/logs/LHCb/LHCb_2009.10.05.log). The logs are continuously appended to, so if you want to analyse one, make a copy.

H

HLT code in the pit (Moore)

  • contact: Gerhard Raven
  • The HLT code installed in the pit is Moore. It is run from /group/hlt/MOORE, not from the release area /sw/lib/lhcb/MOORE
  • The latest version is usually not yet tagged in cvs
  • The HLT that is installed in the Online Cluster is
 
  • It has only 2 different alleys: a Random trigger alley (HltRandom?) and a not Random trigger alley (HltPhysics?).
  • The difference is based on the Trigger type defined in the Odin bank.
  • The trigger type contained in Odin is defined per event and can be: Cosmics, Physics, Auxiliary, Random, Periodic, Calibration, Time Aligned Events and are defined in $DAQEVENTROOT/Event/ODIN.h
  • The Random Trigger Alley is called when the type of trigger in Odin is Random (which is 3) and the Physics is called for all the other types.
  • The Random Alley just pre scales events by a certain factor defined by who is running it and the Physics accepts all the events.
Added:
>
>

HLT Farm (=EFF) in Error

Adding Histograms to the Histogram DataBase

  • Contact: to be defined, Kim/Eric?
When the Presenter is running, you can add the display properties of your histograms to the database and save them creating new pages which will be directly available as you start the presenter:
  • Go to tools and select page editor
  • Select login as HISTO_WRITER
  • Create a new page (blank)
  • Select the histos that you want to display from the right-bottom box ("Histograms in Database")
  • Right click and add to page
  • Choose "auto histograms layout"
  • When you are done go to "File" tab and select Save page to database
  • Write the desired path where the page should be located, the name for this page (label to appear in the left box) and a description of its content
  • Click OK when you are done
 
Changed:
<
<

The way the code runs

  • Everything in the pit is controlled by PVSS.
  • This means that you have to run everything through PVSS panels. They control everything: High voltage, Data AQuisition, L0, HLT, Storage, Monitoring and so on.
  • You can chose what you want to run and set many properties in the PVSS panels that will make the option files that will be used for running for all the processes.
  • It is possible to run LHCb including as many detectors as one wants and it is also to possible to run a given subdetector in standalone mode (Each of this subdetectors or LHCb are called partitions).
  • There is also the TDET partition that controls 5 test Tell1s that send raw banks in the same format as they come from LHCb. That is the main testing environment we have to see if things work in real data.

The Error Logger

>
>

O

LHCb trigger: Online Documentation

Logging in the Online Cluster

  • Contact: see for sys admin items, for the online twiki
  • To login into any machines from the pit you need an account on the Online Cluster. (For HLT Piquets you may use the hlt_shift account).
  • The connection between the Online cluster and the rest of the world has to be done through the gateway (lbgw01.cern.ch if you are in lxplus or gw01 if you are in the Online cluster).
  • The computers you can work from in the Control Room work in a "First come first serve" system. So chose anyone that is free.
  • As there are only Windows machines there you will need to export the display if you connect to any other machine. So starting Exceed is the first thing to do.
 
Changed:
<
<
>
>
 
Changed:
<
<
  • To get the printouts of what is running, you need to open the errorLog
  • For that connect to "mona08" with PuTTY?
  • Enter "/group/online/dataflow/scripts/errorLog LHCb". Here is if you want to see what is going on in LHCb partition. For a different one replace LHCb for TDET or VELOA for instance.
  • You should see the error logger with 3 screens as in the screenshot. The top one prints the messages, the bottom left is reserved for the history and the bottom right is for the settings.
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrow and press enter
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.
  • Logs are kept in the directory /group/online/dataflow/logs/partition/partition_year.month.day.log (e.g. /group/online/dataflow/logs/LHCb/LHCb_2009.10.05.log). The logs are continuously appended to, so if you want to analyse one, make a copy.
>
>
  • With Exceed opened you can connect to the machines with PuTTY.
  • But to export the display you should go to the Putty window in Connection > SSH > X11 check the Enable X11 forwarding box and in the X display location type in the machine you are logged in (there is a label with the name in the screen. It is for example lb018w where only the numbers can change).
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!
  • After the session is open you have to type: export DISPLAY=lb018w:0.0
 
Changed:
<
<

The Presenter

Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.
>
>

P

The online histogram Presenter

  • contact: to be defined: Kim/Eric ?
Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.
 
Changed:
<
<
Select "Tools" -> "PageEditor"
>
>
Select "Tools" -> "PageEditor"
 
Changed:
<
<
>
>
  In the Dialog box: disconect for the DB (histogram data base)
Changed:
<
<
In the windows of the left, click in Cancel
>
>
In the windows of the left, click in Cancel
 
Changed:
<
<
>
>
 Now you should see 2 new areas
in the right part of the Presenter Window.
One called "DIM Histogram Browser"
and one called "Histograms in Database"

Double click on the nodes name in the "DIM Histogram Browser" in this example "hltc03".
Changed:
<
<
Select "HltGlobalMonitor" and check
"m_histoodinentry" and "m_histoodintype"
>
>
Select "HltGlobalMonitor" and check
"m_histoodinentry" and "m_histoodintype"
 
Changed:
<
<
Right click and choose "Add checked to Database"
>
>
Right click and choose "Add checked to Database"
 
Changed:
<
<
Now the selected data appears in the "Histograms in Database".

Select "Gaucho Job".
Check the data you are interested in.
Right click and select "Add checked histogram(s) to Page"
>
>
Now the selected data appears in the "Histograms in Database".

Select "Gaucho Job".
Check the data you are interested in.
Right click and select "Add checked histogram(s) to Page"
  Now your histograms should appear in the main area of the presenter. You can place them with your mouse. When you press the green "Play" button they'll start updating.
Changed:
<
<

Adding Histos to the HistosDataBase

After following steps in previous point to access the Histogram presenter, you can add your histograms to the database and save them creating new pages which will be directly available as you start the presenter:
  • Go to tools and select page editor
  • Select login as HISTO_WRITER
  • Create a new page (blank)
  • Select the histos that you want to display from the right-bottom box ("Histograms in Database")
  • Right click and add to page
  • Choose "auto histograms layout"
  • When you are done go to "File" tab and select Save page to database
  • Write the desired path where the page should be located, the name for this page (label to appear in the left box) and a description of its content
  • Click OK when you are done

Recompiling the HLT code in the pit

  • The LHCb Moore at EFF the is started from the following script: /group/online/hlt/scripts/defaultfilter.sh (is a soft link to a script in the hlt area)
    • i.s: defaultfilter.sh -> /group/hlt/devel-20080821/Moore_v5r0/Hlt/Moore/v5r0/job/runMooreOnline_EFF.sh
  • This script runs Moore with an options file, there are two main options files at Hlt/Moore/v5r0/options
    • DEFAULT.opts and DEFAULT_TAE.opts (for Time Alignment Events)
>
>

Piquet Shift info and duties

R

Recompiling Moore

  • contact: Gerhard Raven
  • Every version of Moore (say vnrm) is linked with a version of Online (say vxry).
  • Moore is started from the following script: /group/online/ONLINE/Onlinevxry/Online/OnlineTasks/defaultfilter.sh vnrm subfarm partition runtype
    • this executes /group/hlt/MOORE/Moore_vnrm/Hlt/Moore/job/runMooreOnline_EFF.sh subfarm partition runtype
  • To each version of Moore corresponds a 'dev' version: Moore_vnrmdev (linked to Online_vxrydev)
 
  • To recompile the code:
Changed:
<
<
    • before recompiling the code! if you do it in the directory in use by the EFF, it can affect the run. The procedure is: make a temp directory, compile it there, test in TDET, and when sure that it works, recompile the directory in use.
>
>
    • NB! if you do it in the directory in use by the EFF, it can affect the run. The procedure is: make your test in the dev area, compile it there, test with TDET or FEST, and when sure that it works, recompile the directory production version.
 
    • set the project environment:
Changed:
<
<
    • please set the right CMTPROJECTPATH to the directory where Moore is located, for example:
      • > export CMTPROJECTPATH=/group/hlt/devel-20080821:/sw/lib/lhcb:/sw/lib/lcg/external
    • > go the directory Moore_v5r0/Hlt/Moore/v5r0/cmt
      • > cmt config
      • > source setup.sh
    • If some paths or version has been updated you need to do also:
      • > ./makePath.sh

Testing Moore on lxplus

  • Temporally, you need to create your Moore_v5r1/cmt directory and locate in it the project.cmt file that you can find at $LHCb_release_area/MOORE/MOORE_v5r1/cmt
  • > getpack Hlt/Moore v5r1
  • setup the env: > setenvMoore v5r1 or >SetupProject Moore v5r1
  • normal way: go to Hlt/Moore/v5r0/cmt, do cmt config, source setup.csh, cmt br make
  • You need to run the following script Hlt/Moore/v5r1/job/runMooreOnline.csh
>
>
    • SetupProject Moore vnrm
    • go the directory Moore_vnrm/Hlt/Moore/cmt
    • cmt config
    • source setup.sh
    • make

Run Control Status via Web in real time

S

The way the code runs (Starting a run with the HLT)

  • contact: Clara Gaspar
  • Everything in the pit is controlled by PVSS.
  • This means that you have to run everything through PVSS panels. They control everything: High voltage, Data AQuisition, L0, HLT, Storage, Monitoring and so on.
  • You can chose what you want to run and set many properties in the PVSS panels that will make the option files that will be used for running for all the processes.
  • It is possible to run LHCb including as many detectors as one wants and it is also to possible to run a given subdetector in standalone mode (Each of this subdetectors or LHCb are called partitions).
  • There is also the TDET partition that controls 5 test Tell1s that send raw banks in the same format as they come from LHCb. That is the main testing environment we have to see if things work in real data.

T

The TCK Presenter

  • contact: Stephan Nies

Testing Moore on lxplus

 
  • To see the histogram you need to run the histogram presenter
Changed:
<
<
  • You log in lxplus, and set the Online Project: >SetupProject Online v4r14 or >setenvOnline v4r14
  • >getpack Online/Presenter >cd Online/Presenter/v0r11/cmt >cmt config, source >setup.csh, gmake
  • set the lxplus node in which you are running Moore for the DIM server. > setenv DIM_DNS_NODE lxplus224
  • execute the presenter, in >Online/Presenter/slc4_amd64_gcc34

Testing new code in the EFF (for experts) at TDET

>
>
  • You log in lxplus, and set the Online Project: SetupProject Online vxry
  • getpack Online/Presenter Online/Presenter/cmt, cmt config, source setup.csh, gmake
  • set the lxplus node in which you are running Moore for the DIM server. setenv DIM_DNS_NODE lxplus224
  • execute the presenter, in Online/Presenter/slc4_amd64_gcc34

Testing a new version of Moore in the EFF with TDET

  • contact: Eric van Herwijnen
 
  • Make your own develop directory where to locate your local copy of Moore
  • ask the Online people to make a defaultfilter_test.sh pointing to your Moore script and that the reserved subfarm for the HLT is using your defaultfilter_test.sh.
  • login into the hlt01 machine and execute the PVSS script to control the farm: /group/online/hlt/pvss/HLT_UI_DEN.sh
Line: 145 to 203
 
  • Set the triggers: random, periodic, calibration apply and exit.
  • Now click on go: it starts to send events to the TDET in the selected subfarm
  • You can ssh to the subfarm, open the presenter and see the histograms
Changed:
<
<
  • You can open errorLog TDET & and see the errors/warnings
  • When you are done, remember to give back the subfarm! go to FARM:TOP, and then mark remove, and refresh/do it click
    <!-- /patternTopic-->

What we learn from Bruno's training session:

  • this info is copied at /group/hlt/docs/hlt_training_1.txt
  • logon on gateway (gw01) to run the browser (firefox)
    logon on dumdaq and hlt01
  • logon on dumdaq01
    /group/online/ecs/Shortcuts/TDET/TDDAQ_UI_DEN.sh => to reserve a subfarm
    FSM label, clean in TDDAQ, right clik in TDET, view
    click in the lock and take it (if it is unlook of course)
    now allocate
    TDET_HLT to see what subfarms are taken ==> HLTA02
    logon on hlt01
    /group/online/hlt/pvss/HLT_UI_GEDI.sh ## open the PVSS window to show all
    click in the icon "Para" -> open a window with all the subfarms
    click in a subfarm HLTA02 -> show all the PVSS commands int eh subfarm
    click in FwProcsConf -> open all the processes
    click in a GauchoJob (the Moore application)
    click in path to change the main script to run -> defaultfilter_test.sh
    logon on
    open the errorLog to see the messages
    /group/online/dataflow/scripts/errorLog TDET
    You can change the level of messages in the small left window
    back to TDET:TOP
    to change the print info go to TDET_Runinfo -> edit
    Go back to TDET:TOP, and configure -> look at the errorLog for the messages
    Now you are ready, ->start run -> go
    When you are done
    reset->deallocate
    release the lock of TDET!
    back to errorLog and close (small window, move with tabs)
    back to Para, and restore the script to defaultfilter.sh
    now close

Show attachments (20)

<!-- END twistyPlugin-->
Hide attachments (20)
<!-- END twistyPlugin-->

I Attachment Action Size Date Who Comment
pdfpdf HltMuPlots.pdf manage 594.1 K 04 Sep 2006 - 18:10 Main.leggerf Plots obtained with the new Hlt Muon checking code
pdfpdf Hltcalibration.pdf manage 785.2 K 04 Sep 2006 - 18:08 Main.leggerf Proposal on how to calibrate the Hlt Muon Alley
txttxt MinutesbrainstormingJune14.txt manage 1.4 K 09 Jul 2006 - 16:58 Main.MiriamGandelman Minutes of June 14
pdfpdf Structure_and_guidelines.pdf manage 22.7 K 16 Jun 2006 - 10:02 Main.hruiz Proposal of code structure and guidelines for the alleys
pdfpdf TriggerStreamInStripping.pdf manage 91.2 K 23 Nov 2006 - 16:25 Main.dijkstra Trigger stream proposal (Tomasz)
docdoc \\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc manage 39.0 K 21 Sep 2006 - 16:02 Main.JoseHernando proposal to the HltSummary? class
txttxt hlthowto_conditions.txt manage 2.2 K 14 Jun 2006 - 14:46 Main.hernando
txttxt trigger-monitoring-060714.txt manage 2.6 K 19 Jul 2006 - 14:58 Main.dijkstra Minutes July 14
txttxt trigger-monitoring-060825.txt manage 3.2 K 30 Aug 2006 - 15:34 Main.dijkstra Minutes August 25
txttxt trigger-monitoring-060922.txt manage 2.6 K 03 Oct 2006 - 14:19 Main.dijkstra Minutes Sep 22.
txttxt trigger-monitoring-061020.txt manage 2.0 K 26 Oct 2006 - 15:43 Main.dijkstra Minutes Oct 20, 2006.
txttxt trigger-monitoring-061117.txt manage 1.8 K 23 Nov 2006 - 16:28 Main.dijkstra Minutes Nov 17, 2006
txttxt trigger-monitoring-070209.txt manage 2.5 K 15 Feb 2007 - 11:57 Main.dijkstra Minutes Feb 9, 2007
txttxt trigger-monitoring-070302.txt manage 1.4 K 07 Mar 2007 - 09:54 Main.dijkstra Minutes monitoring meeting March 2, 2007.
txttxt trigger-monitoring-070413.txt manage 2.2 K 17 Apr 2007 - 15:30 Main.dijkstra Minutes April 13, 2007
txttxt trigger-monitoring-070511.txt manage 2.9 K 29 May 2007 - 15:04 Main.dijkstra Minutes May 11, 2007
txttxt trigger-monitoring-070601.txt manage 3.4 K 13 Jun 2007 - 18:16 Main.dijkstra Minutes June 1, 2007
txttxt trigger-monitoring-070629.txt manage 2.5 K 03 Jul 2007 - 11:55 Main.dijkstra Minutes June 29, 2007
txttxt trigger-monitoring-may17-06.txt manage 2.3 K 20 Jun 2006 - 15:20 Main.miriam Minutes May 17 meeting
txttxt trigger-monitoring.txt manage 2.5 K 04 Jul 2006 - 17:19 Main.dijkstra Minutes June 30
<!-- END twistyPlugin-->
<!--//twikiAttachments-->
<!-- /patternContent-->

E dit | W YSIWYG | A ttach | P rintable | C lone | R aw View | Backlinks: We b, A l l Webs | H istory: r20 < r19 < r18 < r17 < r16 | M ore topic actions

>
>
  • You can open errorLog TDET & and see the errors/warnings
  • When you are done, remember to give back the subfarm! go to FARM:TOP, and then mark remove, and refresh/do it click
 
Deleted:
<
<
<!--/patternTopicActions-->
 
<!-- /patternMoved-->
<!-- /patternMainContents-->
<!-- /patternMain-->
Deleted:
<
<
 
Deleted:
<
<
LHCb

CERN Webs

 
<!--  -->
Deleted:
<
<
Create personal sidebar
 
<!-- /patternLeftBarContents-->
<!-- /patternLeftBar-->
<!-- /patternFloatWrap-->

<!-- /patternOuter-->
<!-- /patternWrapper-->
Changed:
<
<
| Powered by TWiki |
>
>
| Powered by TWiki |
 
Changed:
<
<

  • |
    <!-- /patternTopBar-->
    This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
    Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback
    <!-- /patternBottomBarContents-->
    <!-- /patternBottomBar-->
    <!-- /patternPage-->
    <!-- /patternPageShadow-->
    <!-- /patternScreen-->

  • x11forwardscreen:
    hlt1_cut.gif
>
>

  • |
<!-- /patternTopBar-->
This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback
<!-- /patternBottomBarContents-->
<!-- /patternBottomBar-->
<!-- /patternPage-->
<!-- /patternPageShadow-->
<!-- /patternScreen-->
 
META FILEATTACHMENT attachment="trigger-monitoring-070629.txt" attr="" comment="Minutes June 29, 2007" date="1183456511" name="trigger-monitoring-070629.txt" path="trigger-monitoring-070629.txt" size="2547" stream="trigger-monitoring-070629.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
Line: 290 to 242
 
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="hlt1_cut.gif" attr="" comment="x11forwardscreen" date="1254735301" name="hlt1_cut.gif" path="C:\lhcb\hlt\hlt1_cut.gif" size="12286" stream="C:\lhcb\hlt\hlt1_cut.gif" tmpFilename="/usr/tmp/CGItemp63277" user="evh" version="1"

Revision 272009-10-05 - EricvanHerwijnen

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

E ditW YSIWYGA ttachPDFP rintable

<!-- /patternToolBar-->

<!-- /patternTop-->

r20 - 12 Sep 2008 - 10:30:10 - BrunoSouzaDePaula You are here: TWiki > LHCb Web > LHCbTrigger > LHCbTriggerOnlineDocumentation

<!-- /patternHomePath-->

<!-- /ActionTrackerPlugin -->
>
>

HLT Piquet Guide


 
Deleted:
<
<

LHCb trigger: Informal Online Documentation

 
Added:
>
>

LHCb trigger: Online Documentation

 
Changed:
<
<

Shift info

>
>

Piquet Shift info and duties

 
Added:
>
>
  • The piquet should be able to get to the pit within 30 mins at any time during the week of shift
 
Changed:
<
<
  • The HLT piquet should attend the daily run meetings at 9:00 in the pit
  • Also the piquet should go to the HLT comissioning meeting at 15:00 on friday in Hans' office (Better to go the week before
taking over as well)

Actual Run Control Status via Web: http://lbstatus.cern.ch/

>
>

Run Control Status via Web in real time

 
Changed:
<
<

Logging in the Online Cluster

  • To login into any machines from the pit you need an account on the Online Cluster (For HLT Piquets it is the hlt_shift Hans mailed).
>
>

Logging in the Online Cluster

  • To login into any machines from the pit you need an account on the Online Cluster. (For HLT Piquets you may use the hlt_shift account).
 
  • The connection between the Online cluster and the rest of the world has to be done through the gateway (lbgw01.cern.ch if you are in lxplus or gw01 if you are in the Online cluster).
Deleted:
<
<
  • To prevent heavy network traffic you should NOT connect remotely to the Online Cluster unless you have a good reason for that.
 
  • The computers you can work from in the Control Room work in a "First come first serve" system. So chose anyone that is free.
  • As there are only Windows machines there you will need to export the display if you connect to any other machine. So starting Exceed is the first thing to do.
Changed:
<
<
>
>
 
Changed:
<
<
  • With Exceed opened you can connect to the machines with PuTTY?.
>
>
  • With Exceed opened you can connect to the machines with PuTTY.
 
  • But to export the display you should go to the Putty window in Connection > SSH > X11 check the Enable X11 forwarding box and in the X display location type in the machine you are logged in (there is a label with the name in the screen. It is for example lb018w where only the numbers can change).
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!
  • After the session is open you have to type: export DISPLAY=lb018w:0.0
Changed:
<
<

Computers Scheme

  • The EFF (Event Filter Farm) is where the HLT will run and at moment there are 50 subfarms installed.
  • Each subfarm is called hlta01, hltb10, hltc06 etc and has 4 nodes that are called hlta0101, hlta0102 and so on.
  • Each of these nodes have 8 cores which means each subfarm can and will run 32 HLT processes at the same time.
  • There are the machines from the monitoring farm (mona08 is the most used one).
  • Whenever you want to compile something go to the plus machines to not make the EFF machines busy (just putty to plus).
>
>

The Event Filter Farm (EFF)

  • The EFF is where the HLT will run and at the moment there are 50 subfarms installed.
  • Each subfarm is called hlta01, hltb10, hltc06 etc and has 11 nodes that are called hlta0101, hlta0102 and so on.
  • Each of these nodes have 8 cores which means each subfarm can and will run 88 HLT processes at the same time.
  • The HLT software ("Moore") is run under "GauchoJob".
  • There is also a monitoring farm
  • Whenever you want to compile something go to the plus machines to not make the EFF machines busy (putty to plus).
 
Changed:
<
<

HLT code in the pit

>
>

HLT code in the pit

 
  • The HLT that is installed in the Online Cluster is absolutely not what is released and that you all know. It is a much simpler one.
  • It has only 2 different alleys: a Random trigger alley (HltRandom?) and a not Random trigger alley (HltPhysics?).
  • The difference is based on the Trigger type defined in the Odin bank.
Line: 62 to 56
 
  • It is possible to run LHCb including as many detectors as one wants and it is also to possible to run a given subdetector in standalone mode (Each of this subdetectors or LHCb are called partitions).
  • There is also the TDET partition that controls 5 test Tell1s that send raw banks in the same format as they come from LHCb. That is the main testing environment we have to see if things work in real data.
Changed:
<
<

The Error Logger

>
>

The Error Logger

 
Deleted:
<
<
 
  • To get the printouts of what is running, you need to open the errorLog
  • For that connect to "mona08" with PuTTY?
  • Enter "/group/online/dataflow/scripts/errorLog LHCb". Here is if you want to see what is going on in LHCb partition. For a different one replace LHCb for TDET or VELOA for instance.
  • You should see the error logger with 3 screens as in the screenshot. The top one prints the messages, the bottom left is reserved for the history and the bottom right is for the settings.
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrow and press enter
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.
Added:
>
>
  • Logs are kept in the directory /group/online/dataflow/logs/partition/partition_year.month.day.log (e.g. /group/online/dataflow/logs/LHCb/LHCb_2009.10.05.log). The logs are continuously appended to, so if you want to analyse one, make a copy.
 
Changed:
<
<

The Presenter

>
>

The Presenter

 
Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.

Line: 274 to 267
 

  • |
    <!-- /patternTopBar-->
    This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
    Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback
    <!-- /patternBottomBarContents-->
    <!-- /patternBottomBar-->
    <!-- /patternPage-->
    <!-- /patternPageShadow-->
    <!-- /patternScreen-->
Added:
>
>
  • x11forwardscreen:
    hlt1_cut.gif
 
META FILEATTACHMENT attachment="trigger-monitoring-070629.txt" attr="" comment="Minutes June 29, 2007" date="1183456511" name="trigger-monitoring-070629.txt" path="trigger-monitoring-070629.txt" size="2547" stream="trigger-monitoring-070629.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070511.txt" attr="" comment="Minutes May 11, 2007" date="1180443880" name="trigger-monitoring-070511.txt" path="trigger-monitoring-070511.txt" size="3000" stream="trigger-monitoring-070511.txt" user="Main.dijkstra" version="1"
Line: 294 to 290
 
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"
Added:
>
>
META FILEATTACHMENT attachment="hlt1_cut.gif" attr="" comment="x11forwardscreen" date="1254735301" name="hlt1_cut.gif" path="C:\lhcb\hlt\hlt1_cut.gif" size="12286" stream="C:\lhcb\hlt\hlt1_cut.gif" tmpFilename="/usr/tmp/CGItemp63277" user="evh" version="1"

Revision 262009-01-28 - AntonioPerezCalero

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
Line: 96 to 96
  Now your histograms should appear in the main area of the presenter. You can place them with your mouse. When you press the green "Play" button they'll start updating.
Added:
>
>

Adding Histos to the HistosDataBase

After following steps in previous point to access the Histogram presenter, you can add your histograms to the database and save them creating new pages which will be directly available as you start the presenter:
  • Go to tools and select page editor
  • Select login as HISTO_WRITER
  • Create a new page (blank)
  • Select the histos that you want to display from the right-bottom box ("Histograms in Database")
  • Right click and add to page
  • Choose "auto histograms layout"
  • When you are done go to "File" tab and select Save page to database
  • Write the desired path where the page should be located, the name for this page (label to appear in the left box) and a description of its content
  • Click OK when you are done
 

Recompiling the HLT code in the pit

  • The LHCb Moore at EFF the is started from the following script: /group/online/hlt/scripts/defaultfilter.sh (is a soft link to a script in the hlt area)
    • i.s: defaultfilter.sh -> /group/hlt/devel-20080821/Moore_v5r0/Hlt/Moore/v5r0/job/runMooreOnline_EFF.sh

Revision 252008-11-18 - JoseHernando

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
Changed:
<
<
>
>
 
Changed:
<
<
E ditW YSIWYGA ttachPDFP rintable
>
>
E ditW YSIWYGA ttachPDFP rintable
 
<!-- /patternToolBar-->

<!-- /patternTop-->
Changed:
<
<
r20 - 12 Sep 2008 - 10:30:10 - BrunoSouzaDePaula You are here: TWiki > LHCb Web > LHCbTrigger > LHCbTriggerOnlineDocumentation
<!-- /patternHomePath-->
>
>
r20 - 12 Sep 2008 - 10:30:10 - BrunoSouzaDePaula You are here: TWiki > LHCb Web > LHCbTrigger > LHCbTriggerOnlineDocumentation
<!-- /patternHomePath-->
 
<!-- /ActionTrackerPlugin -->
Line: 65 to 64
 

The Error Logger

Changed:
<
<
>
>
 
Changed:
<
<
  • To get the printouts of what is running, you need to open the errorLog
  • For that connect to "mona08" with PuTTY?
  • Enter "/group/online/dataflow/scripts/errorLog LHCb". Here is if you want to see what is going on in LHCb partition. For a different one replace LHCb for TDET or VELOA for instance.
  • You should see the error logger with 3 screens as in the screenshot. The top one prints the messages, the bottom left is reserved for the history and the bottom right is for the settings.
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrow and press enter
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.
>
>

  • To get the printouts of what is running, you need to open the errorLog
  • For that connect to "mona08" with PuTTY?
  • Enter "/group/online/dataflow/scripts/errorLog LHCb". Here is if you want to see what is going on in LHCb partition. For a different one replace LHCb for TDET or VELOA for instance.
  • You should see the error logger with 3 screens as in the screenshot. The top one prints the messages, the bottom left is reserved for the history and the bottom right is for the settings.
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrow and press enter
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.
 

The Presenter

Changed:
<
<
Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.
>
>
Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.
 
Changed:
<
<
Select "Tools" -> "PageEditor"
>
>
Select "Tools" -> "PageEditor"
 
Changed:
<
<
>
>
  In the Dialog box: disconect for the DB (histogram data base)

In the windows of the left, click in Cancel

Changed:
<
<
Now you should see 2 new areas
in the right part of the Presenter Window.
One called "DIM Histogram Browser"
and one called "Histograms in Database"

Double click on the nodes name in the "DIM Histogram Browser" in this example "hltc03".
>
>
Now you should see 2 new areas
in the right part of the Presenter Window.
One called "DIM Histogram Browser"
and one called "Histograms in Database"

Double click on the nodes name in the "DIM Histogram Browser" in this example "hltc03".
 
Changed:
<
<
Select "HltGlobalMonitor" and check
"m_histoodinentry" and "m_histoodintype"
>
>
Select "HltGlobalMonitor" and check
"m_histoodinentry" and "m_histoodintype"
 
Changed:
<
<
Right click and choose "Add checked to Database"
>
>
Right click and choose "Add checked to Database"
 
Changed:
<
<
Now the selected data appears in the "Histograms in Database".

Select "Gaucho Job".
Check the data you are interested in.
Right click and select "Add checked histogram(s) to Page"
>
>
Now the selected data appears in the "Histograms in Database".

Select "Gaucho Job".
Check the data you are interested in.
Right click and select "Add checked histogram(s) to Page"
  Now your histograms should appear in the main area of the presenter. You can place them with your mouse. When you press the green "Play" button they'll start updating.
Line: 143 to 143
 
  • You can ssh to the subfarm, open the presenter and see the histograms
  • You can open errorLog TDET & and see the errors/warnings
  • When you are done, remember to give back the subfarm! go to FARM:TOP, and then mark remove, and refresh/do it click
    <!-- /patternTopic-->
Added:
>
>

What we learn from Bruno's training session:

  • this info is copied at /group/hlt/docs/hlt_training_1.txt
  • logon on gateway (gw01) to run the browser (firefox)
    logon on dumdaq and hlt01
  • logon on dumdaq01
    /group/online/ecs/Shortcuts/TDET/TDDAQ_UI_DEN.sh => to reserve a subfarm
    FSM label, clean in TDDAQ, right clik in TDET, view
    click in the lock and take it (if it is unlook of course)
    now allocate
    TDET_HLT to see what subfarms are taken ==> HLTA02
    logon on hlt01
    /group/online/hlt/pvss/HLT_UI_GEDI.sh ## open the PVSS window to show all
    click in the icon "Para" -> open a window with all the subfarms
    click in a subfarm HLTA02 -> show all the PVSS commands int eh subfarm
    click in FwProcsConf -> open all the processes
    click in a GauchoJob (the Moore application)
    click in path to change the main script to run -> defaultfilter_test.sh
    logon on
    open the errorLog to see the messages
    /group/online/dataflow/scripts/errorLog TDET
    You can change the level of messages in the small left window
    back to TDET:TOP
    to change the print info go to TDET_Runinfo -> edit
    Go back to TDET:TOP, and configure -> look at the errorLog for the messages
    Now you are ready, ->start run -> go
    When you are done
    reset->deallocate
    release the lock of TDET!
    back to errorLog and close (small window, move with tabs)
    back to Para, and restore the script to defaultfilter.sh
    now close
 
Changed:
<
<
Show attachments (20)
<!-- END twistyPlugin-->
Hide attachments (20)
<!-- END twistyPlugin-->
>
>
Show attachments (20)
<!-- END twistyPlugin-->
Hide attachments (20)
<!-- END twistyPlugin-->
 
Changed:
<
<
I Attachment Action Size Date Who Comment
pdfpdf HltMuPlots.pdf manage 594.1 K 04 Sep 2006 - 18:10 Main.leggerf Plots obtained with the new Hlt Muon checking code
pdfpdf Hltcalibration.pdf manage 785.2 K 04 Sep 2006 - 18:08 Main.leggerf Proposal on how to calibrate the Hlt Muon Alley
txttxt MinutesbrainstormingJune14.txt manage 1.4 K 09 Jul 2006 - 16:58 MiriamGandelman Minutes of June 14
pdfpdf Structure_and_guidelines.pdf manage 22.7 K 16 Jun 2006 - 10:02 Main.hruiz Proposal of code structure and guidelines for the alleys
pdfpdf TriggerStreamInStripping.pdf manage 91.2 K 23 Nov 2006 - 16:25 Main.dijkstra Trigger stream proposal (Tomasz)
docdoc \\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc manage 39.0 K 21 Sep 2006 - 16:02 JoseHernando proposal to the HltSummary? class
txttxt hlthowto_conditions.txt manage 2.2 K 14 Jun 2006 - 14:46 Main.hernando
txttxt trigger-monitoring-060714.txt manage 2.6 K 19 Jul 2006 - 14:58 Main.dijkstra Minutes July 14
txttxt trigger-monitoring-060825.txt manage 3.2 K 30 Aug 2006 - 15:34 Main.dijkstra Minutes August 25
txttxt trigger-monitoring-060922.txt manage 2.6 K 03 Oct 2006 - 14:19 Main.dijkstra Minutes Sep 22.
txttxt trigger-monitoring-061020.txt manage 2.0 K 26 Oct 2006 - 15:43 Main.dijkstra Minutes Oct 20, 2006.
txttxt trigger-monitoring-061117.txt manage 1.8 K 23 Nov 2006 - 16:28 Main.dijkstra Minutes Nov 17, 2006
txttxt trigger-monitoring-070209.txt manage 2.5 K 15 Feb 2007 - 11:57 Main.dijkstra Minutes Feb 9, 2007
txttxt trigger-monitoring-070302.txt manage 1.4 K 07 Mar 2007 - 09:54 Main.dijkstra Minutes monitoring meeting March 2, 2007.
txttxt trigger-monitoring-070413.txt manage 2.2 K 17 Apr 2007 - 15:30 Main.dijkstra Minutes April 13, 2007
txttxt trigger-monitoring-070511.txt manage 2.9 K 29 May 2007 - 15:04 Main.dijkstra Minutes May 11, 2007
txttxt trigger-monitoring-070601.txt manage 3.4 K 13 Jun 2007 - 18:16 Main.dijkstra Minutes June 1, 2007
txttxt trigger-monitoring-070629.txt manage 2.5 K 03 Jul 2007 - 11:55 Main.dijkstra Minutes June 29, 2007
txttxt trigger-monitoring-may17-06.txt manage 2.3 K 20 Jun 2006 - 15:20 Main.miriam Minutes May 17 meeting
txttxt trigger-monitoring.txt manage 2.5 K 04 Jul 2006 - 17:19 Main.dijkstra Minutes June 30
<!-- END twistyPlugin-->
<!--//twikiAttachments-->
<!-- /patternContent-->
>
>
I Attachment Action Size Date Who Comment
pdfpdf HltMuPlots.pdf manage 594.1 K 04 Sep 2006 - 18:10 Main.leggerf Plots obtained with the new Hlt Muon checking code
pdfpdf Hltcalibration.pdf manage 785.2 K 04 Sep 2006 - 18:08 Main.leggerf Proposal on how to calibrate the Hlt Muon Alley
txttxt MinutesbrainstormingJune14.txt manage 1.4 K 09 Jul 2006 - 16:58 Main.MiriamGandelman Minutes of June 14
pdfpdf Structure_and_guidelines.pdf manage 22.7 K 16 Jun 2006 - 10:02 Main.hruiz Proposal of code structure and guidelines for the alleys
pdfpdf TriggerStreamInStripping.pdf manage 91.2 K 23 Nov 2006 - 16:25 Main.dijkstra Trigger stream proposal (Tomasz)
docdoc \\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc manage 39.0 K 21 Sep 2006 - 16:02 Main.JoseHernando proposal to the HltSummary? class
txttxt hlthowto_conditions.txt manage 2.2 K 14 Jun 2006 - 14:46 Main.hernando
txttxt trigger-monitoring-060714.txt manage 2.6 K 19 Jul 2006 - 14:58 Main.dijkstra Minutes July 14
txttxt trigger-monitoring-060825.txt manage 3.2 K 30 Aug 2006 - 15:34 Main.dijkstra Minutes August 25
txttxt trigger-monitoring-060922.txt manage 2.6 K 03 Oct 2006 - 14:19 Main.dijkstra Minutes Sep 22.
txttxt trigger-monitoring-061020.txt manage 2.0 K 26 Oct 2006 - 15:43 Main.dijkstra Minutes Oct 20, 2006.
txttxt trigger-monitoring-061117.txt manage 1.8 K 23 Nov 2006 - 16:28 Main.dijkstra Minutes Nov 17, 2006
txttxt trigger-monitoring-070209.txt manage 2.5 K 15 Feb 2007 - 11:57 Main.dijkstra Minutes Feb 9, 2007
txttxt trigger-monitoring-070302.txt manage 1.4 K 07 Mar 2007 - 09:54 Main.dijkstra Minutes monitoring meeting March 2, 2007.
txttxt trigger-monitoring-070413.txt manage 2.2 K 17 Apr 2007 - 15:30 Main.dijkstra Minutes April 13, 2007
txttxt trigger-monitoring-070511.txt manage 2.9 K 29 May 2007 - 15:04 Main.dijkstra Minutes May 11, 2007
txttxt trigger-monitoring-070601.txt manage 3.4 K 13 Jun 2007 - 18:16 Main.dijkstra Minutes June 1, 2007
txttxt trigger-monitoring-070629.txt manage 2.5 K 03 Jul 2007 - 11:55 Main.dijkstra Minutes June 29, 2007
txttxt trigger-monitoring-may17-06.txt manage 2.3 K 20 Jun 2006 - 15:20 Main.miriam Minutes May 17 meeting
txttxt trigger-monitoring.txt manage 2.5 K 04 Jul 2006 - 17:19 Main.dijkstra Minutes June 30
<!-- END twistyPlugin-->
<!--//twikiAttachments-->
<!-- /patternContent-->
 
Changed:
<
<
E dit | W YSIWYG | A ttach | P rintable | C lone | R aw View | Backlinks: We b, A l l Webs | H istory: r20 < r19 < r18 < r17 < r16 | M ore topic actions
>
>
E dit | W YSIWYG | A ttach | P rintable | C lone | R aw View | Backlinks: We b, A l l Webs | H istory: r20 < r19 < r18 < r17 < r16 | M ore topic actions
 
<!--/patternTopicActions-->
Line: 254 to 257
 
<!-- /patternLeftBarContents-->
<!-- /patternLeftBar-->
<!-- /patternFloatWrap-->

<!-- /patternOuter-->
<!-- /patternWrapper-->
Changed:
<
<
| Powered by TWiki |
>
>
| Powered by TWiki |
 
Changed:
<
<

  • |
    <!-- /patternTopBar-->
    This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
    Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback
    <!-- /patternBottomBarContents-->
    <!-- /patternBottomBar-->
    <!-- /patternPage-->
    <!-- /patternPageShadow-->
    <!-- /patternScreen-->
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Oct 20, 2006." date="1161870232" name="trigger-monitoring-061020.txt" path="trigger-monitoring-061020.txt" size="2030" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Trigger stream proposal (Tomasz)" date="1164295504" name="TriggerStreamInStripping.pdf" path="TriggerStreamInStripping.pdf" size="93429" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Plots obtained with the new Hlt Muon checking code" date="1157386211" name="HltMuPlots.pdf" path="HltMuPlots.pdf" size="608372" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes August 25" date="1156944866" name="trigger-monitoring-060825.txt" path="trigger-monitoring-060825.txt" size="3289" user="Main.dijkstra" version="2"
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1150289218" name="hlthowto_conditions.txt" path="hlthowto_conditions.txt" size="2291" user="hernando" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes of June 14" date="1152457117" name="MinutesbrainstormingJune14.txt" path="MinutesbrainstormingJune14.txt" size="1402" user="Main.MiriamGandelman" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes June 30" date="1152026364" name="trigger-monitoring.txt" path="trigger-monitoring.txt" size="2574" user="Main.dijkstra" version="4"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Feb 9, 2007" date="1171537060" name="trigger-monitoring-070209.txt" path="trigger-monitoring-070209.txt" size="2582" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="proposal to the HltSummary class" date="1158847337" name="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" path="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" size="39936" user="Main.JoseHernando" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes May 17 meeting" date="1150809623" name="trigger-monitoring-may17-06.txt" path="trigger-monitoring-may17-06.txt" size="2345" user="miriam" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal of code structure and guidelines for the alleys" date="1150444954" name="Structure_and_guidelines.pdf" path="Structure_and_guidelines.pdf" size="23237" user="hruiz" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal on how to calibrate the Hlt Muon Alley" date="1157386085" name="Hltcalibration.pdf" path="Hltcalibration.pdf" size="804062" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes July 14" date="1153313915" name="trigger-monitoring-060714.txt" path="trigger-monitoring-060714.txt" size="2614" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070413.txt" attr="" comment="Minutes April 13, 2007" date="1176816617" name="trigger-monitoring-070413.txt" path="trigger-monitoring-070413.txt" size="2287" stream="trigger-monitoring-070413.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070511.txt" attr="" comment="Minutes May 11, 2007" date="1180443880" name="trigger-monitoring-070511.txt" path="trigger-monitoring-070511.txt" size="3000" stream="trigger-monitoring-070511.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
>
>

  • |
    <!-- /patternTopBar-->
    This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
    Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback
    <!-- /patternBottomBarContents-->
    <!-- /patternBottomBar-->
    <!-- /patternPage-->
    <!-- /patternPageShadow-->
    <!-- /patternScreen-->
 
META FILEATTACHMENT attachment="trigger-monitoring-070629.txt" attr="" comment="Minutes June 29, 2007" date="1183456511" name="trigger-monitoring-070629.txt" path="trigger-monitoring-070629.txt" size="2547" stream="trigger-monitoring-070629.txt" user="Main.dijkstra" version="1"
Added:
>
>
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070511.txt" attr="" comment="Minutes May 11, 2007" date="1180443880" name="trigger-monitoring-070511.txt" path="trigger-monitoring-070511.txt" size="3000" stream="trigger-monitoring-070511.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070413.txt" attr="" comment="Minutes April 13, 2007" date="1176816617" name="trigger-monitoring-070413.txt" path="trigger-monitoring-070413.txt" size="2287" stream="trigger-monitoring-070413.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes July 14" date="1153313915" name="trigger-monitoring-060714.txt" path="trigger-monitoring-060714.txt" size="2614" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal on how to calibrate the Hlt Muon Alley" date="1157386085" name="Hltcalibration.pdf" path="Hltcalibration.pdf" size="804062" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal of code structure and guidelines for the alleys" date="1150444954" name="Structure_and_guidelines.pdf" path="Structure_and_guidelines.pdf" size="23237" user="hruiz" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes May 17 meeting" date="1150809623" name="trigger-monitoring-may17-06.txt" path="trigger-monitoring-may17-06.txt" size="2345" user="miriam" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="proposal to the HltSummary class" date="1158847337" name="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" path="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" size="39936" user="Main.JoseHernando" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Feb 9, 2007" date="1171537060" name="trigger-monitoring-070209.txt" path="trigger-monitoring-070209.txt" size="2582" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes June 30" date="1152026364" name="trigger-monitoring.txt" path="trigger-monitoring.txt" size="2574" user="Main.dijkstra" version="4"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes of June 14" date="1152457117" name="MinutesbrainstormingJune14.txt" path="MinutesbrainstormingJune14.txt" size="1402" user="Main.MiriamGandelman" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1150289218" name="hlthowto_conditions.txt" path="hlthowto_conditions.txt" size="2291" user="hernando" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes August 25" date="1156944866" name="trigger-monitoring-060825.txt" path="trigger-monitoring-060825.txt" size="3289" user="Main.dijkstra" version="2"
META FILEATTACHMENT attr="" autoattached="1" comment="Plots obtained with the new Hlt Muon checking code" date="1157386211" name="HltMuPlots.pdf" path="HltMuPlots.pdf" size="608372" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Trigger stream proposal (Tomasz)" date="1164295504" name="TriggerStreamInStripping.pdf" path="TriggerStreamInStripping.pdf" size="93429" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Oct 20, 2006." date="1161870232" name="trigger-monitoring-061020.txt" path="trigger-monitoring-061020.txt" size="2030" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"

Revision 242008-10-31 - JoseHernando

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
Changed:
<
<
>
>
 
Changed:
<
<
E ditW YSIWYGA ttachPDFP rintable
>
>
E ditW YSIWYGA ttachPDFP rintable
 
<!-- /patternToolBar-->

<!-- /patternTop-->
Changed:
<
<
r20 - 12 Sep 2008 - 10:30:10 - BrunoSouzaDePaula You are here: TWiki > LHCb Web > LHCbTrigger > LHCbTriggerOnlineDocumentation
<!-- /patternHomePath-->
>
>
r20 - 12 Sep 2008 - 10:30:10 - BrunoSouzaDePaula You are here: TWiki > LHCb Web > LHCbTrigger > LHCbTriggerOnlineDocumentation
<!-- /patternHomePath-->
 
<!-- /ActionTrackerPlugin -->
Line: 18 to 18
 

Shift info

Deleted:
<
<
 
Line: 26 to 25
 
  • The HLT piquet should attend the daily run meetings at 9:00 in the pit
  • Also the piquet should go to the HLT comissioning meeting at 15:00 on friday in Hans' office (Better to go the week before
taking over as well)
Deleted:
<
<
 

Actual Run Control Status via Web: http://lbstatus.cern.ch/

Logging in the Online Cluster

Line: 36 to 34
 
  • The computers you can work from in the Control Room work in a "First come first serve" system. So chose anyone that is free.
  • As there are only Windows machines there you will need to export the display if you connect to any other machine. So starting Exceed is the first thing to do.
Changed:
<
<

>
>
 
  • With Exceed opened you can connect to the machines with PuTTY?.
  • But to export the display you should go to the Putty window in Connection > SSH > X11 check the Enable X11 forwarding box and in the X display location type in the machine you are logged in (there is a label with the name in the screen. It is for example lb018w where only the numbers can change).
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!
Changed:
<
<
  • After the session is open you have to type: export DISPLAY=lb018w:0.0
>
>
  • After the session is open you have to type: export DISPLAY=lb018w:0.0
 

Computers Scheme

  • The EFF (Event Filter Farm) is where the HLT will run and at moment there are 50 subfarms installed.
Line: 69 to 65
 

The Error Logger

Changed:
<
<
>
>
 
  • To get the printouts of what is running, you need to open the errorLog
  • For that connect to "mona08" with PuTTY?
  • Enter "/group/online/dataflow/scripts/errorLog LHCb". Here is if you want to see what is going on in LHCb partition. For a different one replace LHCb for TDET or VELOA for instance.
  • You should see the error logger with 3 screens as in the screenshot. The top one prints the messages, the bottom left is reserved for the history and the bottom right is for the settings.
Changed:
<
<
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrows.
>
>
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrow and press enter
 
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.
Deleted:
<
<
 

The Presenter

Changed:
<
<
Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.
>
>
Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.
 
Changed:
<
<
Select "Tools" -> "PageEditor"
>
>
Select "Tools" -> "PageEditor"
 
Changed:
<
<
>
>
  In the Dialog box: disconect for the DB (histogram data base)

In the windows of the left, click in Cancel

Deleted:
<
<
 
Changed:
<
<
Now you should see 2 new areas
in the right part of the Presenter Window.
One called "DIM Histogram Browser"
and one called "Histograms in Database"

Double click on the nodes name in the "DIM Histogram Browser" in this example "hltc03".
>
>
Now you should see 2 new areas
in the right part of the Presenter Window.
One called "DIM Histogram Browser"
and one called "Histograms in Database"

Double click on the nodes name in the "DIM Histogram Browser" in this example "hltc03".
 
Changed:
<
<
Select "HltGlobalMonitor" and check
"m_histoodinentry" and "m_histoodintype"
>
>
Select "HltGlobalMonitor" and check
"m_histoodinentry" and "m_histoodintype"
 
Changed:
<
<
Right click and choose "Add checked to Database"
>
>
Right click and choose "Add checked to Database"
 
Changed:
<
<
Now the selected data appears in the "Histograms in Database".

Select "Gaucho Job".
Check the data you are interested in.
Right click and select "Add checked histogram(s) to Page"
>
>
Now the selected data appears in the "Histograms in Database".

Select "Gaucho Job".
Check the data you are interested in.
Right click and select "Add checked histogram(s) to Page"
  Now your histograms should appear in the main area of the presenter. You can place them with your mouse. When you press the green "Play" button they'll start updating.
Line: 150 to 142
 
  • Now click on go: it starts to send events to the TDET in the selected subfarm
  • You can ssh to the subfarm, open the presenter and see the histograms
  • You can open errorLog TDET & and see the errors/warnings
Changed:
<
<
  • When you are done, remember to give back the subfarm! go to FARM:TOP, and then mark remove, and refresh/do it click
    <!-- /patternTopic-->
>
>
  • When you are done, remember to give back the subfarm! go to FARM:TOP, and then mark remove, and refresh/do it click
    <!-- /patternTopic-->
  Show attachments (20)
<!-- END twistyPlugin-->
Hide attachments (20)
<!-- END twistyPlugin-->
Changed:
<
<
I Attachment Action Size Date Who Comment
pdfpdf HltMuPlots.pdf manage 594.1 K 04 Sep 2006 - 18:10 Main.leggerf Plots obtained with the new Hlt Muon checking code
pdfpdf Hltcalibration.pdf manage 785.2 K 04 Sep 2006 - 18:08 Main.leggerf Proposal on how to calibrate the Hlt Muon Alley
txttxt MinutesbrainstormingJune14.txt manage 1.4 K 09 Jul 2006 - 16:58 MiriamGandelman Minutes of June 14
pdfpdf Structure_and_guidelines.pdf manage 22.7 K 16 Jun 2006 - 10:02 Main.hruiz Proposal of code structure and guidelines for the alleys
pdfpdf TriggerStreamInStripping.pdf manage 91.2 K 23 Nov 2006 - 16:25 Main.dijkstra Trigger stream proposal (Tomasz)
docdoc \\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc manage 39.0 K 21 Sep 2006 - 16:02 JoseHernando proposal to the HltSummary? class
txttxt hlthowto_conditions.txt manage 2.2 K 14 Jun 2006 - 14:46 Main.hernando
txttxt trigger-monitoring-060714.txt manage 2.6 K 19 Jul 2006 - 14:58 Main.dijkstra Minutes July 14
txttxt trigger-monitoring-060825.txt manage 3.2 K 30 Aug 2006 - 15:34 Main.dijkstra Minutes August 25
txttxt trigger-monitoring-060922.txt manage 2.6 K 03 Oct 2006 - 14:19 Main.dijkstra Minutes Sep 22.
txttxt trigger-monitoring-061020.txt manage 2.0 K 26 Oct 2006 - 15:43 Main.dijkstra Minutes Oct 20, 2006.
txttxt trigger-monitoring-061117.txt manage 1.8 K 23 Nov 2006 - 16:28 Main.dijkstra Minutes Nov 17, 2006
txttxt trigger-monitoring-070209.txt manage 2.5 K 15 Feb 2007 - 11:57 Main.dijkstra Minutes Feb 9, 2007
txttxt trigger-monitoring-070302.txt manage 1.4 K 07 Mar 2007 - 09:54 Main.dijkstra Minutes monitoring meeting March 2, 2007.
txttxt trigger-monitoring-070413.txt manage 2.2 K 17 Apr 2007 - 15:30 Main.dijkstra Minutes April 13, 2007
txttxt trigger-monitoring-070511.txt manage 2.9 K 29 May 2007 - 15:04 Main.dijkstra Minutes May 11, 2007
txttxt trigger-monitoring-070601.txt manage 3.4 K 13 Jun 2007 - 18:16 Main.dijkstra Minutes June 1, 2007
txttxt trigger-monitoring-070629.txt manage 2.5 K 03 Jul 2007 - 11:55 Main.dijkstra Minutes June 29, 2007
txttxt trigger-monitoring-may17-06.txt manage 2.3 K 20 Jun 2006 - 15:20 Main.miriam Minutes May 17 meeting
txttxt trigger-monitoring.txt manage 2.5 K 04 Jul 2006 - 17:19 Main.dijkstra Minutes June 30
<!-- END twistyPlugin-->
<!--//twikiAttachments-->
<!-- /patternContent-->
>
>
I Attachment Action Size Date Who Comment
pdfpdf HltMuPlots.pdf manage 594.1 K 04 Sep 2006 - 18:10 Main.leggerf Plots obtained with the new Hlt Muon checking code
pdfpdf Hltcalibration.pdf manage 785.2 K 04 Sep 2006 - 18:08 Main.leggerf Proposal on how to calibrate the Hlt Muon Alley
txttxt MinutesbrainstormingJune14.txt manage 1.4 K 09 Jul 2006 - 16:58 MiriamGandelman Minutes of June 14
pdfpdf Structure_and_guidelines.pdf manage 22.7 K 16 Jun 2006 - 10:02 Main.hruiz Proposal of code structure and guidelines for the alleys
pdfpdf TriggerStreamInStripping.pdf manage 91.2 K 23 Nov 2006 - 16:25 Main.dijkstra Trigger stream proposal (Tomasz)
docdoc \\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc manage 39.0 K 21 Sep 2006 - 16:02 JoseHernando proposal to the HltSummary? class
txttxt hlthowto_conditions.txt manage 2.2 K 14 Jun 2006 - 14:46 Main.hernando
txttxt trigger-monitoring-060714.txt manage 2.6 K 19 Jul 2006 - 14:58 Main.dijkstra Minutes July 14
txttxt trigger-monitoring-060825.txt manage 3.2 K 30 Aug 2006 - 15:34 Main.dijkstra Minutes August 25
txttxt trigger-monitoring-060922.txt manage 2.6 K 03 Oct 2006 - 14:19 Main.dijkstra Minutes Sep 22.
txttxt trigger-monitoring-061020.txt manage 2.0 K 26 Oct 2006 - 15:43 Main.dijkstra Minutes Oct 20, 2006.
txttxt trigger-monitoring-061117.txt manage 1.8 K 23 Nov 2006 - 16:28 Main.dijkstra Minutes Nov 17, 2006
txttxt trigger-monitoring-070209.txt manage 2.5 K 15 Feb 2007 - 11:57 Main.dijkstra Minutes Feb 9, 2007
txttxt trigger-monitoring-070302.txt manage 1.4 K 07 Mar 2007 - 09:54 Main.dijkstra Minutes monitoring meeting March 2, 2007.
txttxt trigger-monitoring-070413.txt manage 2.2 K 17 Apr 2007 - 15:30 Main.dijkstra Minutes April 13, 2007
txttxt trigger-monitoring-070511.txt manage 2.9 K 29 May 2007 - 15:04 Main.dijkstra Minutes May 11, 2007
txttxt trigger-monitoring-070601.txt manage 3.4 K 13 Jun 2007 - 18:16 Main.dijkstra Minutes June 1, 2007
txttxt trigger-monitoring-070629.txt manage 2.5 K 03 Jul 2007 - 11:55 Main.dijkstra Minutes June 29, 2007
txttxt trigger-monitoring-may17-06.txt manage 2.3 K 20 Jun 2006 - 15:20 Main.miriam Minutes May 17 meeting
txttxt trigger-monitoring.txt manage 2.5 K 04 Jul 2006 - 17:19 Main.dijkstra Minutes June 30
<!-- END twistyPlugin-->
<!--//twikiAttachments-->
<!-- /patternContent-->
 
Changed:
<
<
E dit | W YSIWYG | A ttach | P rintable | C lone | R aw View | Backlinks: We b, A l l Webs | H istory: r20 < r19 < r18 < r17 < r16 | M ore topic actions
>
>
E dit | W YSIWYG | A ttach | P rintable | C lone | R aw View | Backlinks: We b, A l l Webs | H istory: r20 < r19 < r18 < r17 < r16 | M ore topic actions
 
<!--/patternTopicActions-->
Changed:
<
<
<!-- /patternMoved-->
<!-- /patternMainContents-->
<!-- /patternMain-->
>
>
<!-- /patternMoved-->
<!-- /patternMainContents-->
<!-- /patternMain-->
  LHCb
  • LHCb Web
Line: 263 to 253
 Create personal sidebar
<!-- /patternLeftBarContents-->
<!-- /patternLeftBar-->
<!-- /patternFloatWrap-->
Changed:
<
<
<!-- /patternOuter-->
<!-- /patternWrapper-->
| Powered by TWiki |

|
<!-- /patternTopBar-->
This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback
<!-- /patternBottomBarContents-->
<!-- /patternBottomBar-->
<!-- /patternPage-->
<!-- /patternPageShadow-->
<!-- /patternScreen-->

META FILEATTACHMENT attachment="trigger-monitoring-070629.txt" attr="" comment="Minutes June 29, 2007" date="1183456511" name="trigger-monitoring-070629.txt" path="trigger-monitoring-070629.txt" size="2547" stream="trigger-monitoring-070629.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070511.txt" attr="" comment="Minutes May 11, 2007" date="1180443880" name="trigger-monitoring-070511.txt" path="trigger-monitoring-070511.txt" size="3000" stream="trigger-monitoring-070511.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070413.txt" attr="" comment="Minutes April 13, 2007" date="1176816617" name="trigger-monitoring-070413.txt" path="trigger-monitoring-070413.txt" size="2287" stream="trigger-monitoring-070413.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes July 14" date="1153313915" name="trigger-monitoring-060714.txt" path="trigger-monitoring-060714.txt" size="2614" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal on how to calibrate the Hlt Muon Alley" date="1157386085" name="Hltcalibration.pdf" path="Hltcalibration.pdf" size="804062" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal of code structure and guidelines for the alleys" date="1150444954" name="Structure_and_guidelines.pdf" path="Structure_and_guidelines.pdf" size="23237" user="hruiz" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes May 17 meeting" date="1150809623" name="trigger-monitoring-may17-06.txt" path="trigger-monitoring-may17-06.txt" size="2345" user="miriam" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="proposal to the HltSummary class" date="1158847337" name="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" path="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" size="39936" user="Main.JoseHernando" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Feb 9, 2007" date="1171537060" name="trigger-monitoring-070209.txt" path="trigger-monitoring-070209.txt" size="2582" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes June 30" date="1152026364" name="trigger-monitoring.txt" path="trigger-monitoring.txt" size="2574" user="Main.dijkstra" version="4"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes of June 14" date="1152457117" name="MinutesbrainstormingJune14.txt" path="MinutesbrainstormingJune14.txt" size="1402" user="Main.MiriamGandelman" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1150289218" name="hlthowto_conditions.txt" path="hlthowto_conditions.txt" size="2291" user="hernando" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes August 25" date="1156944866" name="trigger-monitoring-060825.txt" path="trigger-monitoring-060825.txt" size="3289" user="Main.dijkstra" version="2"
META FILEATTACHMENT attr="" autoattached="1" comment="Plots obtained with the new Hlt Muon checking code" date="1157386211" name="HltMuPlots.pdf" path="HltMuPlots.pdf" size="608372" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Trigger stream proposal (Tomasz)" date="1164295504" name="TriggerStreamInStripping.pdf" path="TriggerStreamInStripping.pdf" size="93429" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Oct 20, 2006." date="1161870232" name="trigger-monitoring-061020.txt" path="trigger-monitoring-061020.txt" size="2030" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
>
>
<!-- /patternOuter-->
<!-- /patternWrapper-->
| Powered by TWiki |

  • |
<!-- /patternTopBar-->
This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback
<!-- /patternBottomBarContents-->
<!-- /patternBottomBar-->
<!-- /patternPage-->
<!-- /patternPageShadow-->
<!-- /patternScreen-->
 
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"
Added:
>
>
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Oct 20, 2006." date="1161870232" name="trigger-monitoring-061020.txt" path="trigger-monitoring-061020.txt" size="2030" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Trigger stream proposal (Tomasz)" date="1164295504" name="TriggerStreamInStripping.pdf" path="TriggerStreamInStripping.pdf" size="93429" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Plots obtained with the new Hlt Muon checking code" date="1157386211" name="HltMuPlots.pdf" path="HltMuPlots.pdf" size="608372" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes August 25" date="1156944866" name="trigger-monitoring-060825.txt" path="trigger-monitoring-060825.txt" size="3289" user="Main.dijkstra" version="2"
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1150289218" name="hlthowto_conditions.txt" path="hlthowto_conditions.txt" size="2291" user="hernando" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes of June 14" date="1152457117" name="MinutesbrainstormingJune14.txt" path="MinutesbrainstormingJune14.txt" size="1402" user="Main.MiriamGandelman" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes June 30" date="1152026364" name="trigger-monitoring.txt" path="trigger-monitoring.txt" size="2574" user="Main.dijkstra" version="4"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Feb 9, 2007" date="1171537060" name="trigger-monitoring-070209.txt" path="trigger-monitoring-070209.txt" size="2582" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="proposal to the HltSummary class" date="1158847337" name="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" path="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" size="39936" user="Main.JoseHernando" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes May 17 meeting" date="1150809623" name="trigger-monitoring-may17-06.txt" path="trigger-monitoring-may17-06.txt" size="2345" user="miriam" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal of code structure and guidelines for the alleys" date="1150444954" name="Structure_and_guidelines.pdf" path="Structure_and_guidelines.pdf" size="23237" user="hruiz" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal on how to calibrate the Hlt Muon Alley" date="1157386085" name="Hltcalibration.pdf" path="Hltcalibration.pdf" size="804062" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes July 14" date="1153313915" name="trigger-monitoring-060714.txt" path="trigger-monitoring-060714.txt" size="2614" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070413.txt" attr="" comment="Minutes April 13, 2007" date="1176816617" name="trigger-monitoring-070413.txt" path="trigger-monitoring-070413.txt" size="2287" stream="trigger-monitoring-070413.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070511.txt" attr="" comment="Minutes May 11, 2007" date="1180443880" name="trigger-monitoring-070511.txt" path="trigger-monitoring-070511.txt" size="3000" stream="trigger-monitoring-070511.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070629.txt" attr="" comment="Minutes June 29, 2007" date="1183456511" name="trigger-monitoring-070629.txt" path="trigger-monitoring-070629.txt" size="2547" stream="trigger-monitoring-070629.txt" user="Main.dijkstra" version="1"

Revision 232008-10-01 - JaapPanman

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
Line: 8 to 8
 
<!-- /patternTop-->
Changed:
<
<
r20 - 12 Sep 2008 - 10:30:10 - BrunoSouzaDePaula You are here: TWiki> LHCb Web> LHCbTrigger >LHCbTriggerOnlineDocumentation
>
>
r20 - 12 Sep 2008 - 10:30:10 - BrunoSouzaDePaula You are here: TWiki > LHCb Web > LHCbTrigger > LHCbTriggerOnlineDocumentation
 
<!-- /patternHomePath-->

<!-- /ActionTrackerPlugin -->
Line: 31 to 31
 

Logging in the Online Cluster

  • To login into any machines from the pit you need an account on the Online Cluster (For HLT Piquets it is the hlt_shift Hans mailed).
Changed:
<
<
  • The connection between the Online cluster and the rest of the world has to be done through the gateway (lbgw01.cern.ch if you are in lxplus or gw01.cern.ch if you are in the Online cluster).
>
>
  • The connection between the Online cluster and the rest of the world has to be done through the gateway (lbgw01.cern.ch if you are in lxplus or gw01 if you are in the Online cluster).
 
  • To prevent heavy network traffic you should NOT connect remotely to the Online Cluster unless you have a good reason for that.
  • The computers you can work from in the Control Room work in a "First come first serve" system. So chose anyone that is free.
  • As there are only Windows machines there you will need to export the display if you connect to any other machine. So starting Exceed is the first thing to do.
Line: 155 to 155
  Show attachments (20)
<!-- END twistyPlugin-->
Hide attachments (20)
<!-- END twistyPlugin-->
Changed:
<
<
I Attachment Action Size Date Who Comment
pdfpdf HltMuPlots.pdf manage 594.1K 04 Sep 2006 - 18:10 Main.leggerf Plots obtained with the new Hlt Muon checking code
pdfpdf Hltcalibration.pdf manage 785.2K 04 Sep 2006 - 18:08 Main.leggerf Proposal on how to calibrate the Hlt Muon Alley
txttxt MinutesbrainstormingJune14.txt manage 1.4K 09 Jul 2006 - 16:58 MiriamGandelman Minutes of June 14
pdfpdf Structure_and_guidelines.pdf manage 22.7K 16 Jun 2006 - 10:02 Main.hruiz Proposal of code structure and guidelines for the alleys
pdfpdf TriggerStreamInStripping.pdf manage 91.2K 23 Nov 2006 - 16:25 Main.dijkstra Trigger stream proposal (Tomasz)
docdoc \\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc manage 39.0K 21 Sep 2006 - 16:02 JoseHernando proposal to the HltSummary? class
txttxt hlthowto_conditions.txt manage 2.2K 14 Jun 2006 - 14:46 Main.hernando
txttxt trigger-monitoring-060714.txt manage 2.6K 19 Jul 2006 - 14:58 Main.dijkstra Minutes July 14
txttxt trigger-monitoring-060825.txt manage 3.2K 30 Aug 2006 - 15:34 Main.dijkstra Minutes August 25
txttxt trigger-monitoring-060922.txt manage 2.6K 03 Oct 2006 - 14:19 Main.dijkstra Minutes Sep 22.
txttxt trigger-monitoring-061020.txt manage 2.0K 26 Oct 2006 - 15:43 Main.dijkstra Minutes Oct 20, 2006.
txttxt trigger-monitoring-061117.txt manage 1.8K 23 Nov 2006 - 16:28 Main.dijkstra Minutes Nov 17, 2006
txttxt trigger-monitoring-070209.txt manage 2.5K 15 Feb 2007 - 11:57 Main.dijkstra Minutes Feb 9, 2007
txttxt trigger-monitoring-070302.txt manage 1.4K 07 Mar 2007 - 09:54 Main.dijkstra Minutes monitoring meeting March 2, 2007.
txttxt trigger-monitoring-070413.txt manage 2.2K 17 Apr 2007 - 15:30 Main.dijkstra Minutes April 13, 2007
txttxt trigger-monitoring-070511.txt manage 2.9K 29 May 2007 - 15:04 Main.dijkstra Minutes May 11, 2007
txttxt trigger-monitoring-070601.txt manage 3.4K 13 Jun 2007 - 18:16 Main.dijkstra Minutes June 1, 2007
txttxt trigger-monitoring-070629.txt manage 2.5K 03 Jul 2007 - 11:55 Main.dijkstra Minutes June 29, 2007
txttxt trigger-monitoring-may17-06.txt manage 2.3K 20 Jun 2006 - 15:20 Main.miriam Minutes May 17 meeting
txttxt trigger-monitoring.txt manage 2.5K 04 Jul 2006 - 17:19 Main.dijkstra Minutes June 30
>
>
I Attachment Action Size Date Who Comment
pdfpdf HltMuPlots.pdf manage 594.1 K 04 Sep 2006 - 18:10 Main.leggerf Plots obtained with the new Hlt Muon checking code
pdfpdf Hltcalibration.pdf manage 785.2 K 04 Sep 2006 - 18:08 Main.leggerf Proposal on how to calibrate the Hlt Muon Alley
txttxt MinutesbrainstormingJune14.txt manage 1.4 K 09 Jul 2006 - 16:58 MiriamGandelman Minutes of June 14
pdfpdf Structure_and_guidelines.pdf manage 22.7 K 16 Jun 2006 - 10:02 Main.hruiz Proposal of code structure and guidelines for the alleys
pdfpdf TriggerStreamInStripping.pdf manage 91.2 K 23 Nov 2006 - 16:25 Main.dijkstra Trigger stream proposal (Tomasz)
docdoc \\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc manage 39.0 K 21 Sep 2006 - 16:02 JoseHernando proposal to the HltSummary? class
txttxt hlthowto_conditions.txt manage 2.2 K 14 Jun 2006 - 14:46 Main.hernando
txttxt trigger-monitoring-060714.txt manage 2.6 K 19 Jul 2006 - 14:58 Main.dijkstra Minutes July 14
txttxt trigger-monitoring-060825.txt manage 3.2 K 30 Aug 2006 - 15:34 Main.dijkstra Minutes August 25
txttxt trigger-monitoring-060922.txt manage 2.6 K 03 Oct 2006 - 14:19 Main.dijkstra Minutes Sep 22.
txttxt trigger-monitoring-061020.txt manage 2.0 K 26 Oct 2006 - 15:43 Main.dijkstra Minutes Oct 20, 2006.
txttxt trigger-monitoring-061117.txt manage 1.8 K 23 Nov 2006 - 16:28 Main.dijkstra Minutes Nov 17, 2006
txttxt trigger-monitoring-070209.txt manage 2.5 K 15 Feb 2007 - 11:57 Main.dijkstra Minutes Feb 9, 2007
txttxt trigger-monitoring-070302.txt manage 1.4 K 07 Mar 2007 - 09:54 Main.dijkstra Minutes monitoring meeting March 2, 2007.
txttxt trigger-monitoring-070413.txt manage 2.2 K 17 Apr 2007 - 15:30 Main.dijkstra Minutes April 13, 2007
txttxt trigger-monitoring-070511.txt manage 2.9 K 29 May 2007 - 15:04 Main.dijkstra Minutes May 11, 2007
txttxt trigger-monitoring-070601.txt manage 3.4 K 13 Jun 2007 - 18:16 Main.dijkstra Minutes June 1, 2007
txttxt trigger-monitoring-070629.txt manage 2.5 K 03 Jul 2007 - 11:55 Main.dijkstra Minutes June 29, 2007
txttxt trigger-monitoring-may17-06.txt manage 2.3 K 20 Jun 2006 - 15:20 Main.miriam Minutes May 17 meeting
txttxt trigger-monitoring.txt manage 2.5 K 04 Jul 2006 - 17:19 Main.dijkstra Minutes June 30
 
<!-- END twistyPlugin-->
<!--//twikiAttachments-->
<!-- /patternContent-->
Changed:
<
<
E dit|W YSIWYG|A ttach|P rintable|C lone|R aw View|Backlinks: We b, A l l Webs|H istory: r20 < r19 < r18 < r17 < r16|M ore topic actions
>
>
E dit | W YSIWYG | A ttach | P rintable | C lone | R aw View | Backlinks: We b, A l l Webs | H istory: r20 < r19 < r18 < r17 < r16 | M ore topic actions
 
<!--/patternTopicActions-->
Line: 263 to 263
 Create personal sidebar
<!-- /patternLeftBarContents-->
<!-- /patternLeftBar-->
<!-- /patternFloatWrap-->
Changed:
<
<
>
>
 
<!-- /patternOuter-->
<!-- /patternWrapper-->
| Powered by TWiki |

|
<!-- /patternTopBar-->
This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback
<!-- /patternBottomBarContents-->
<!-- /patternBottomBar-->
<!-- /patternPage-->
<!-- /patternPageShadow-->
<!-- /patternScreen-->

META FILEATTACHMENT attachment="trigger-monitoring-070629.txt" attr="" comment="Minutes June 29, 2007" date="1183456511" name="trigger-monitoring-070629.txt" path="trigger-monitoring-070629.txt" size="2547" stream="trigger-monitoring-070629.txt" user="Main.dijkstra" version="1"

Revision 222008-09-19 - BrunoSouzaDePaula

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
Line: 42 to 42
 
  • With Exceed opened you can connect to the machines with PuTTY?.
  • But to export the display you should go to the Putty window in Connection > SSH > X11 check the Enable X11 forwarding box and in the X display location type in the machine you are logged in (there is a label with the name in the screen. It is for example lb018w where only the numbers can change).
Changed:
<
<
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!
>
>
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!
  • After the session is open you have to type: export DISPLAY=lb018w:0.0
 

Computers Scheme

  • The EFF (Event Filter Farm) is where the HLT will run and at moment there are 50 subfarms installed.

Revision 212008-09-16 - BrunoSouzaDePaula

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
Changed:
<
<
<!-- /ActionTrackerPlugin -->
>
>
 
Changed:
<
<

LHCb trigger: Informal Online Documentation

>
>
E ditW YSIWYGA ttachPDFP rintable

<!-- /patternToolBar-->

<!-- /patternTop-->

r20 - 12 Sep 2008 - 10:30:10 - BrunoSouzaDePaula You are here: TWiki> LHCb Web> LHCbTrigger >LHCbTriggerOnlineDocumentation

<!-- /patternHomePath-->

<!-- /ActionTrackerPlugin -->

LHCb trigger: Informal Online Documentation

 
Changed:
<
<

Shift info

>
>

Shift info

 
  • HLT piquet phone: 16-1859 (from outside CERN: +41 76 487-1859)
Changed:
<
<

Actual Run Control Status via Web: http://lbstatus.cern.ch/

>
>
  • Use the HLT elog-book: http://lblogbook.cern.ch/HLT+Trigger/ (register at same url if first time).
  • Read the http://lblogbook.cern.ch/Shift since TMath.Min('last time on shift'.'24 h')
  • The HLT piquet should attend the daily run meetings at 9:00 in the pit
  • Also the piquet should go to the HLT comissioning meeting at 15:00 on friday in Hans' office (Better to go the week before
taking over as well)

Actual Run Control Status via Web: http://lbstatus.cern.ch/

 
Changed:
<
<

Logging in the Online Cluster

>
>

Logging in the Online Cluster

 
  • To login into any machines from the pit you need an account on the Online Cluster (For HLT Piquets it is the hlt_shift Hans mailed).
  • The connection between the Online cluster and the rest of the world has to be done through the gateway (lbgw01.cern.ch if you are in lxplus or gw01.cern.ch if you are in the Online cluster).
  • To prevent heavy network traffic you should NOT connect remotely to the Online Cluster unless you have a good reason for that.
  • The computers you can work from in the Control Room work in a "First come first serve" system. So chose anyone that is free.
  • As there are only Windows machines there you will need to export the display if you connect to any other machine. So starting Exceed is the first thing to do.
Changed:
<
<
>
>

 
Changed:
<
<
  • With Exceed opened you can connect to the machines with PuTTY.
>
>
  • With Exceed opened you can connect to the machines with PuTTY?.
 
  • But to export the display you should go to the Putty window in Connection > SSH > X11 check the Enable X11 forwarding box and in the X display location type in the machine you are logged in (there is a label with the name in the screen. It is for example lb018w where only the numbers can change).
Changed:
<
<
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!
>
>
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!
 
Changed:
<
<

Computers Scheme

>
>

Computers Scheme

 
  • The EFF (Event Filter Farm) is where the HLT will run and at moment there are 50 subfarms installed.
  • Each subfarm is called hlta01, hltb10, hltc06 etc and has 4 nodes that are called hlta0101, hlta0102 and so on.
  • Each of these nodes have 8 cores which means each subfarm can and will run 32 HLT processes at the same time.
  • There are the machines from the monitoring farm (mona08 is the most used one).
  • Whenever you want to compile something go to the plus machines to not make the EFF machines busy (just putty to plus).
Changed:
<
<

HLT code in the pit

>
>

HLT code in the pit

 
  • The HLT that is installed in the Online Cluster is absolutely not what is released and that you all know. It is a much simpler one.
Changed:
<
<
  • It has only 2 different alleys: a Random trigger alley (HltRandom) and a not Random trigger alley (HltPhysics).
  • The difference is based on the Trigger type defined in the Odin bank.
>
>
  • It has only 2 different alleys: a Random trigger alley (HltRandom?) and a not Random trigger alley (HltPhysics?).
  • The difference is based on the Trigger type defined in the Odin bank.
 
  • The trigger type contained in Odin is defined per event and can be: Cosmics, Physics, Auxiliary, Random, Periodic, Calibration, Time Aligned Events and are defined in $DAQEVENTROOT/Event/ODIN.h
  • The Random Trigger Alley is called when the type of trigger in Odin is Random (which is 3) and the Physics is called for all the other types.
  • The Random Alley just pre scales events by a certain factor defined by who is running it and the Physics accepts all the events.
Changed:
<
<

The way the code runs

>
>

The way the code runs

 
  • Everything in the pit is controlled by PVSS.
  • This means that you have to run everything through PVSS panels. They control everything: High voltage, Data AQuisition, L0, HLT, Storage, Monitoring and so on.
  • You can chose what you want to run and set many properties in the PVSS panels that will make the option files that will be used for running for all the processes.
  • It is possible to run LHCb including as many detectors as one wants and it is also to possible to run a given subdetector in standalone mode (Each of this subdetectors or LHCb are called partitions).
  • There is also the TDET partition that controls 5 test Tell1s that send raw banks in the same format as they come from LHCb. That is the main testing environment we have to see if things work in real data.
Changed:
<
<

The Error Logger

>
>

The Error Logger

 
Changed:
<
<
  • To get the printouts of what is running, you need to open the errorLog
  • For that connect to "mona08" with PuTTY
  • Enter "/group/online/dataflow/scripts/errorLog LHCb". Here is if you want to see what is going on in LHCb partition. For a different one replace LHCb for TDET or VELOA for instance.
  • You should see the error logger with 3 screens as in the screenshot. The top one prints the messages, the bottom left is reserved for the history and the bottom right is for the settings.
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrows.
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.
>
>
 
Changed:
<
<
>
>
  • To get the printouts of what is running, you need to open the errorLog
  • For that connect to "mona08" with PuTTY?
  • Enter "/group/online/dataflow/scripts/errorLog LHCb". Here is if you want to see what is going on in LHCb partition. For a different one replace LHCb for TDET or VELOA for instance.
  • You should see the error logger with 3 screens as in the screenshot. The top one prints the messages, the bottom left is reserved for the history and the bottom right is for the settings.
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrows.
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.
 
Changed:
<
<
>
>
 
Changed:
<
<

The Presenter

Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.
>
>

The Presenter

Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.
 
Changed:
<
<
Select "Tools" -> "PageEditor"
>
>
Select "Tools" -> "PageEditor"
 
Changed:
<
<
>
>
  In the Dialog box: disconect for the DB (histogram data base)

In the windows of the left, click in Cancel

Changed:
<
<
>
>
 
Changed:
<
<
Now you should see 2 new areas
in the right part of the Presenter Window.
One called "DIM Histogram Browser"
and one called "Histograms in Database"

Double click on the nodes name in the "DIM Histogram Browser" in this example "hltc03".
>
>
Now you should see 2 new areas
in the right part of the Presenter Window.
One called "DIM Histogram Browser"
and one called "Histograms in Database"

Double click on the nodes name in the "DIM Histogram Browser" in this example "hltc03".
 
Changed:
<
<
Select "HltGlobalMonitor" and check
"m_histoodinentry" and "m_histoodintype"
>
>
Select "HltGlobalMonitor" and check
"m_histoodinentry" and "m_histoodintype"
 
Changed:
<
<
Right click and choose "Add checked to Database"
>
>
Right click and choose "Add checked to Database"
 
Changed:
<
<
Now the selected data appears in the "Histograms in Database".

Select "Gaucho Job".
Check the data you are interested in.
Right click and select "Add checked histogram(s) to Page"
>
>
Now the selected data appears in the "Histograms in Database".

Select "Gaucho Job".
Check the data you are interested in.
Right click and select "Add checked histogram(s) to Page"
  Now your histograms should appear in the main area of the presenter. You can place them with your mouse. When you press the green "Play" button they'll start updating.
Changed:
<
<

Recompiling the HLT code in the pit

>
>

Recompiling the HLT code in the pit

 
  • The LHCb Moore at EFF the is started from the following script: /group/online/hlt/scripts/defaultfilter.sh (is a soft link to a script in the hlt area)
    • i.s: defaultfilter.sh -> /group/hlt/devel-20080821/Moore_v5r0/Hlt/Moore/v5r0/job/runMooreOnline_EFF.sh
  • This script runs Moore with an options file, there are two main options files at Hlt/Moore/v5r0/options
Line: 98 to 120
 
    • If some paths or version has been updated you need to do also:
      • > ./makePath.sh
Changed:
<
<

Testing Moore on lxplus

>
>

Testing Moore on lxplus

 
  • Temporally, you need to create your Moore_v5r1/cmt directory and locate in it the project.cmt file that you can find at $LHCb_release_area/MOORE/MOORE_v5r1/cmt
  • > getpack Hlt/Moore v5r1
  • setup the env: > setenvMoore v5r1 or >SetupProject Moore v5r1
Line: 109 to 132
 
  • >getpack Online/Presenter >cd Online/Presenter/v0r11/cmt >cmt config, source >setup.csh, gmake
  • set the lxplus node in which you are running Moore for the DIM server. > setenv DIM_DNS_NODE lxplus224
  • execute the presenter, in >Online/Presenter/slc4_amd64_gcc34
Changed:
<
<

Testing new code in the EFF (for experts) at TDET

>
>

Testing new code in the EFF (for experts) at TDET

 
  • Make your own develop directory where to locate your local copy of Moore
  • ask the Online people to make a defaultfilter_test.sh pointing to your Moore script and that the reserved subfarm for the HLT is using your defaultfilter_test.sh.
  • login into the hlt01 machine and execute the PVSS script to control the farm: /group/online/hlt/pvss/HLT_UI_DEN.sh
Line: 128 to 151
 
  • You can ssh to the subfarm, open the presenter and see the histograms
  • You can open errorLog TDET & and see the errors/warnings
  • When you are done, remember to give back the subfarm! go to FARM:TOP, and then mark remove, and refresh/do it click
Added:
>
>
<!-- /patternTopic-->

Show attachments (20)

<!-- END twistyPlugin-->
Hide attachments (20)
<!-- END twistyPlugin-->

I Attachment Action Size Date Who Comment
pdfpdf HltMuPlots.pdf manage 594.1K 04 Sep 2006 - 18:10 Main.leggerf Plots obtained with the new Hlt Muon checking code
pdfpdf Hltcalibration.pdf manage 785.2K 04 Sep 2006 - 18:08 Main.leggerf Proposal on how to calibrate the Hlt Muon Alley
txttxt MinutesbrainstormingJune14.txt manage 1.4K 09 Jul 2006 - 16:58 MiriamGandelman Minutes of June 14
pdfpdf Structure_and_guidelines.pdf manage 22.7K 16 Jun 2006 - 10:02 Main.hruiz Proposal of code structure and guidelines for the alleys
pdfpdf TriggerStreamInStripping.pdf manage 91.2K 23 Nov 2006 - 16:25 Main.dijkstra Trigger stream proposal (Tomasz)
docdoc \\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc manage 39.0K 21 Sep 2006 - 16:02 JoseHernando proposal to the HltSummary? class
txttxt hlthowto_conditions.txt manage 2.2K 14 Jun 2006 - 14:46 Main.hernando
txttxt trigger-monitoring-060714.txt manage 2.6K 19 Jul 2006 - 14:58 Main.dijkstra Minutes July 14
txttxt trigger-monitoring-060825.txt manage 3.2K 30 Aug 2006 - 15:34 Main.dijkstra Minutes August 25
txttxt trigger-monitoring-060922.txt manage 2.6K 03 Oct 2006 - 14:19 Main.dijkstra Minutes Sep 22.
txttxt trigger-monitoring-061020.txt manage 2.0K 26 Oct 2006 - 15:43 Main.dijkstra Minutes Oct 20, 2006.
txttxt trigger-monitoring-061117.txt manage 1.8K 23 Nov 2006 - 16:28 Main.dijkstra Minutes Nov 17, 2006
txttxt trigger-monitoring-070209.txt manage 2.5K 15 Feb 2007 - 11:57 Main.dijkstra Minutes Feb 9, 2007
txttxt trigger-monitoring-070302.txt manage 1.4K 07 Mar 2007 - 09:54 Main.dijkstra Minutes monitoring meeting March 2, 2007.
txttxt trigger-monitoring-070413.txt manage 2.2K 17 Apr 2007 - 15:30 Main.dijkstra Minutes April 13, 2007
txttxt trigger-monitoring-070511.txt manage 2.9K 29 May 2007 - 15:04 Main.dijkstra Minutes May 11, 2007
txttxt trigger-monitoring-070601.txt manage 3.4K 13 Jun 2007 - 18:16 Main.dijkstra Minutes June 1, 2007
txttxt trigger-monitoring-070629.txt manage 2.5K 03 Jul 2007 - 11:55 Main.dijkstra Minutes June 29, 2007
txttxt trigger-monitoring-may17-06.txt manage 2.3K 20 Jun 2006 - 15:20 Main.miriam Minutes May 17 meeting
txttxt trigger-monitoring.txt manage 2.5K 04 Jul 2006 - 17:19 Main.dijkstra Minutes June 30
<!-- END twistyPlugin-->
<!--//twikiAttachments-->
<!-- /patternContent-->

E dit|W YSIWYG|A ttach|P rintable|C lone|R aw View|Backlinks: We b, A l l Webs|H istory: r20 < r19 < r18 < r17 < r16|M ore topic actions

<!--/patternTopicActions-->

<!-- /patternMoved-->
<!-- /patternMainContents-->
<!-- /patternMain-->
<!-- /patternLeftBar-->
<!-- /patternFloatWrap-->

<!-- /patternOuter-->
<!-- /patternWrapper-->
| Powered by TWiki |

|
<!-- /patternTopBar-->
This site is powered by the TWiki collaboration platformCopyright & by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Ask a support question or Send feedback
<!-- /patternBottomBarContents-->
<!-- /patternBottomBar-->
<!-- /patternPage-->
<!-- /patternPageShadow-->
<!-- /patternScreen-->
 
Deleted:
<
<
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Oct 20, 2006." date="1161870232" name="trigger-monitoring-061020.txt" path="trigger-monitoring-061020.txt" size="2030" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Trigger stream proposal (Tomasz)" date="1164295504" name="TriggerStreamInStripping.pdf" path="TriggerStreamInStripping.pdf" size="93429" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Plots obtained with the new Hlt Muon checking code" date="1157386211" name="HltMuPlots.pdf" path="HltMuPlots.pdf" size="608372" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes August 25" date="1156944866" name="trigger-monitoring-060825.txt" path="trigger-monitoring-060825.txt" size="3289" user="Main.dijkstra" version="2"
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1150289218" name="hlthowto_conditions.txt" path="hlthowto_conditions.txt" size="2291" user="hernando" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes of June 14" date="1152457117" name="MinutesbrainstormingJune14.txt" path="MinutesbrainstormingJune14.txt" size="1402" user="Main.MiriamGandelman" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes June 30" date="1152026364" name="trigger-monitoring.txt" path="trigger-monitoring.txt" size="2574" user="Main.dijkstra" version="4"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Feb 9, 2007" date="1171537060" name="trigger-monitoring-070209.txt" path="trigger-monitoring-070209.txt" size="2582" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="proposal to the HltSummary class" date="1158847337" name="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" path="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" size="39936" user="Main.JoseHernando" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes May 17 meeting" date="1150809623" name="trigger-monitoring-may17-06.txt" path="trigger-monitoring-may17-06.txt" size="2345" user="miriam" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal of code structure and guidelines for the alleys" date="1150444954" name="Structure_and_guidelines.pdf" path="Structure_and_guidelines.pdf" size="23237" user="hruiz" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal on how to calibrate the Hlt Muon Alley" date="1157386085" name="Hltcalibration.pdf" path="Hltcalibration.pdf" size="804062" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes July 14" date="1153313915" name="trigger-monitoring-060714.txt" path="trigger-monitoring-060714.txt" size="2614" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070413.txt" attr="" comment="Minutes April 13, 2007" date="1176816617" name="trigger-monitoring-070413.txt" path="trigger-monitoring-070413.txt" size="2287" stream="trigger-monitoring-070413.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070511.txt" attr="" comment="Minutes May 11, 2007" date="1180443880" name="trigger-monitoring-070511.txt" path="trigger-monitoring-070511.txt" size="3000" stream="trigger-monitoring-070511.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
 
META FILEATTACHMENT attachment="trigger-monitoring-070629.txt" attr="" comment="Minutes June 29, 2007" date="1183456511" name="trigger-monitoring-070629.txt" path="trigger-monitoring-070629.txt" size="2547" stream="trigger-monitoring-070629.txt" user="Main.dijkstra" version="1"
Added:
>
>
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070511.txt" attr="" comment="Minutes May 11, 2007" date="1180443880" name="trigger-monitoring-070511.txt" path="trigger-monitoring-070511.txt" size="3000" stream="trigger-monitoring-070511.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070413.txt" attr="" comment="Minutes April 13, 2007" date="1176816617" name="trigger-monitoring-070413.txt" path="trigger-monitoring-070413.txt" size="2287" stream="trigger-monitoring-070413.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes July 14" date="1153313915" name="trigger-monitoring-060714.txt" path="trigger-monitoring-060714.txt" size="2614" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal on how to calibrate the Hlt Muon Alley" date="1157386085" name="Hltcalibration.pdf" path="Hltcalibration.pdf" size="804062" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal of code structure and guidelines for the alleys" date="1150444954" name="Structure_and_guidelines.pdf" path="Structure_and_guidelines.pdf" size="23237" user="hruiz" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes May 17 meeting" date="1150809623" name="trigger-monitoring-may17-06.txt" path="trigger-monitoring-may17-06.txt" size="2345" user="miriam" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="proposal to the HltSummary class" date="1158847337" name="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" path="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" size="39936" user="Main.JoseHernando" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Feb 9, 2007" date="1171537060" name="trigger-monitoring-070209.txt" path="trigger-monitoring-070209.txt" size="2582" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes June 30" date="1152026364" name="trigger-monitoring.txt" path="trigger-monitoring.txt" size="2574" user="Main.dijkstra" version="4"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes of June 14" date="1152457117" name="MinutesbrainstormingJune14.txt" path="MinutesbrainstormingJune14.txt" size="1402" user="Main.MiriamGandelman" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1150289218" name="hlthowto_conditions.txt" path="hlthowto_conditions.txt" size="2291" user="hernando" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes August 25" date="1156944866" name="trigger-monitoring-060825.txt" path="trigger-monitoring-060825.txt" size="3289" user="Main.dijkstra" version="2"
META FILEATTACHMENT attr="" autoattached="1" comment="Plots obtained with the new Hlt Muon checking code" date="1157386211" name="HltMuPlots.pdf" path="HltMuPlots.pdf" size="608372" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Trigger stream proposal (Tomasz)" date="1164295504" name="TriggerStreamInStripping.pdf" path="TriggerStreamInStripping.pdf" size="93429" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Oct 20, 2006." date="1161870232" name="trigger-monitoring-061020.txt" path="trigger-monitoring-061020.txt" size="2030" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"

Revision 202008-09-12 - BrunoSouzaDePaula

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 60 to 60
 

The Presenter

Changed:
<
<
Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/monobjectpresenter.sh"
on the command line.
You should see something like the screenshot.
>
>
Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.
 
Select "Tools" -> "PageEditor"

Revision 192008-09-08 - MiriamGandelman

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 81 to 81
  Now your histograms should appear in the main area of the presenter. You can place them with your mouse. When you press the green "Play" button they'll start updating.
Changed:
<
<

Recompailing the HLT code in the pit

>
>

Recompiling the HLT code in the pit

 
  • The LHCb Moore at EFF the is started from the following script: /group/online/hlt/scripts/defaultfilter.sh (is a soft link to a script in the hlt area)
    • i.s: defaultfilter.sh -> /group/hlt/devel-20080821/Moore_v5r0/Hlt/Moore/v5r0/job/runMooreOnline_EFF.sh
Changed:
<
<
  • This script runs Moore with an option file, there are two main option files at Hlt/Moore/v5r0/options
    • DEFAULT.opts and DEFAULT_TAE.opts (for Time Aligment Events
>
>
  • This script runs Moore with an options file, there are two main options files at Hlt/Moore/v5r0/options
    • DEFAULT.opts and DEFAULT_TAE.opts (for Time Alignment Events)
 
  • To recompile the code:
Changed:
<
<
    • before recompiling the code! if you do it in the directory in use by the EFF, it can affect the run. The precedure is make a temp directory, complit it there, test in TDET, and when sure that it works, recompile the directory in use.
>
>
    • before recompiling the code! if you do it in the directory in use by the EFF, it can affect the run. The procedure is: make a temp directory, compile it there, test in TDET, and when sure that it works, recompile the directory in use.
 
    • set the project environment:
    • please set the right CMTPROJECTPATH to the directory where Moore is located, for example:
Line: 99 to 99
 
      • > ./makePath.sh

Testing Moore on lxplus

Changed:
<
<
  • Temporally, you need to create yout Moore_v5r1/cmt directory and locate in it the project.cmt file that you can find at $LHCb_release_area/MOORE/MOORE_v5r1/cmt
>
>
  • Temporally, you need to create your Moore_v5r1/cmt directory and locate in it the project.cmt file that you can find at $LHCb_release_area/MOORE/MOORE_v5r1/cmt
 
  • > getpack Hlt/Moore v5r1
  • setup the env: > setenvMoore v5r1 or >SetupProject Moore v5r1
  • normal way: go to Hlt/Moore/v5r0/cmt, do cmt config, source setup.csh, cmt br make
Changed:
<
<
  • You need ro run the follosing script Hlt/Moore/v5r1/job/runMooreOnline.csh
>
>
  • You need to run the following script Hlt/Moore/v5r1/job/runMooreOnline.csh
 
  • To see the histogram you need to run the histogram presenter
  • You log in lxplus, and set the Online Project: >SetupProject Online v4r14 or >setenvOnline v4r14
  • >getpack Online/Presenter >cd Online/Presenter/v0r11/cmt >cmt config, source >setup.csh, gmake
Changed:
<
<
  • set the lxplus node in wich you are running Moore for the DIM server. > setenv DIM_DNS_NODE lxplus224
>
>
  • set the lxplus node in which you are running Moore for the DIM server. > setenv DIM_DNS_NODE lxplus224
 
  • execute the presenter, in >Online/Presenter/slc4_amd64_gcc34

Testing new code in the EFF (for experts) at TDET

  • Make your own develop directory where to locate your local copy of Moore
  • ask the Online people to make a defaultfilter_test.sh pointing to your Moore script and that the reserved subfarm for the HLT is using your defaultfilter_test.sh.
  • login into the hlt01 machine and execute the PVSS script to control the farm: /group/online/hlt/pvss/HLT_UI_DEN.sh
Changed:
<
<
  • go to lavel FSM, then + HLT, right-click FARM, then click view, it opens FARM:TOP window
>
>
  • go to level FSM, then + HLT, right-click FARM, then click view, it opens FARM:TOP window
 
  • login into dumdaq01 to execute the TDET script
  • Run PVSS script: /group/online/ecs/Shortcuts/TDET/TDDAQ_UI_DEN.sh
  • got to label FSM, then + in TDDAQ, right-click TDET, click view, opens TDET:TOP window
Line: 123 to 123
 
  • In State, now select: start run
  • If errors, try to recover, and configure again
  • Now in Active state, you can configure the run, clear in TFC control
Changed:
<
<
  • Set the triggers: radom, periodic, calibration apply and exit.
>
>
  • Set the triggers: random, periodic, calibration apply and exit.
 
  • Now click on go: it starts to send events to the TDET in the selected subfarm
  • You can ssh to the subfarm, open the presenter and see the histograms
  • You can open errorLog TDET & and see the errors/warnings

Revision 182008-09-05 - JoseHernando

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 88 to 88
 
    • DEFAULT.opts and DEFAULT_TAE.opts (for Time Aligment Events
  • To recompile the code:
    • before recompiling the code! if you do it in the directory in use by the EFF, it can affect the run. The precedure is make a temp directory, complit it there, test in TDET, and when sure that it works, recompile the directory in use.
Deleted:
<
<
 
    • set the project environment:
    • please set the right CMTPROJECTPATH to the directory where Moore is located, for example:
Line: 98 to 97
 
      • > source setup.sh
    • If some paths or version has been updated you need to do also:
      • > ./makePath.sh
Added:
>
>

Testing Moore on lxplus

  • Temporally, you need to create yout Moore_v5r1/cmt directory and locate in it the project.cmt file that you can find at $LHCb_release_area/MOORE/MOORE_v5r1/cmt
  • > getpack Hlt/Moore v5r1
  • setup the env: > setenvMoore v5r1 or >SetupProject Moore v5r1
  • normal way: go to Hlt/Moore/v5r0/cmt, do cmt config, source setup.csh, cmt br make
  • You need ro run the follosing script Hlt/Moore/v5r1/job/runMooreOnline.csh
  • To see the histogram you need to run the histogram presenter
  • You log in lxplus, and set the Online Project: >SetupProject Online v4r14 or >setenvOnline v4r14
  • >getpack Online/Presenter >cd Online/Presenter/v0r11/cmt >cmt config, source >setup.csh, gmake
  • set the lxplus node in wich you are running Moore for the DIM server. > setenv DIM_DNS_NODE lxplus224
  • execute the presenter, in >Online/Presenter/slc4_amd64_gcc34
 

Testing new code in the EFF (for experts) at TDET

  • Make your own develop directory where to locate your local copy of Moore
  • ask the Online people to make a defaultfilter_test.sh pointing to your Moore script and that the reserved subfarm for the HLT is using your defaultfilter_test.sh.
Line: 117 to 128
 
  • You can ssh to the subfarm, open the presenter and see the histograms
  • You can open errorLog TDET & and see the errors/warnings
  • When you are done, remember to give back the subfarm! go to FARM:TOP, and then mark remove, and refresh/do it click
Deleted:
<
<
META FILEATTACHMENT attachment="trigger-monitoring-070629.txt" attr="" comment="Minutes June 29, 2007" date="1183456511" name="trigger-monitoring-070629.txt" path="trigger-monitoring-070629.txt" size="2547" stream="trigger-monitoring-070629.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070511.txt" attr="" comment="Minutes May 11, 2007" date="1180443880" name="trigger-monitoring-070511.txt" path="trigger-monitoring-070511.txt" size="3000" stream="trigger-monitoring-070511.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070413.txt" attr="" comment="Minutes April 13, 2007" date="1176816617" name="trigger-monitoring-070413.txt" path="trigger-monitoring-070413.txt" size="2287" stream="trigger-monitoring-070413.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes July 14" date="1153313915" name="trigger-monitoring-060714.txt" path="trigger-monitoring-060714.txt" size="2614" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal on how to calibrate the Hlt Muon Alley" date="1157386085" name="Hltcalibration.pdf" path="Hltcalibration.pdf" size="804062" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal of code structure and guidelines for the alleys" date="1150444954" name="Structure_and_guidelines.pdf" path="Structure_and_guidelines.pdf" size="23237" user="hruiz" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes May 17 meeting" date="1150809623" name="trigger-monitoring-may17-06.txt" path="trigger-monitoring-may17-06.txt" size="2345" user="miriam" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="proposal to the HltSummary class" date="1158847337" name="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" path="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" size="39936" user="Main.JoseHernando" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Feb 9, 2007" date="1171537060" name="trigger-monitoring-070209.txt" path="trigger-monitoring-070209.txt" size="2582" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes June 30" date="1152026364" name="trigger-monitoring.txt" path="trigger-monitoring.txt" size="2574" user="Main.dijkstra" version="4"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes of June 14" date="1152457117" name="MinutesbrainstormingJune14.txt" path="MinutesbrainstormingJune14.txt" size="1402" user="Main.MiriamGandelman" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1150289218" name="hlthowto_conditions.txt" path="hlthowto_conditions.txt" size="2291" user="hernando" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes August 25" date="1156944866" name="trigger-monitoring-060825.txt" path="trigger-monitoring-060825.txt" size="3289" user="Main.dijkstra" version="2"
META FILEATTACHMENT attr="" autoattached="1" comment="Plots obtained with the new Hlt Muon checking code" date="1157386211" name="HltMuPlots.pdf" path="HltMuPlots.pdf" size="608372" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Trigger stream proposal (Tomasz)" date="1164295504" name="TriggerStreamInStripping.pdf" path="TriggerStreamInStripping.pdf" size="93429" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Oct 20, 2006." date="1161870232" name="trigger-monitoring-061020.txt" path="trigger-monitoring-061020.txt" size="2030" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
 
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"
Added:
>
>
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Oct 20, 2006." date="1161870232" name="trigger-monitoring-061020.txt" path="trigger-monitoring-061020.txt" size="2030" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Trigger stream proposal (Tomasz)" date="1164295504" name="TriggerStreamInStripping.pdf" path="TriggerStreamInStripping.pdf" size="93429" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Plots obtained with the new Hlt Muon checking code" date="1157386211" name="HltMuPlots.pdf" path="HltMuPlots.pdf" size="608372" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes August 25" date="1156944866" name="trigger-monitoring-060825.txt" path="trigger-monitoring-060825.txt" size="3289" user="Main.dijkstra" version="2"
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1150289218" name="hlthowto_conditions.txt" path="hlthowto_conditions.txt" size="2291" user="hernando" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes of June 14" date="1152457117" name="MinutesbrainstormingJune14.txt" path="MinutesbrainstormingJune14.txt" size="1402" user="Main.MiriamGandelman" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes June 30" date="1152026364" name="trigger-monitoring.txt" path="trigger-monitoring.txt" size="2574" user="Main.dijkstra" version="4"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Feb 9, 2007" date="1171537060" name="trigger-monitoring-070209.txt" path="trigger-monitoring-070209.txt" size="2582" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="proposal to the HltSummary class" date="1158847337" name="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" path="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" size="39936" user="Main.JoseHernando" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes May 17 meeting" date="1150809623" name="trigger-monitoring-may17-06.txt" path="trigger-monitoring-may17-06.txt" size="2345" user="miriam" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal of code structure and guidelines for the alleys" date="1150444954" name="Structure_and_guidelines.pdf" path="Structure_and_guidelines.pdf" size="23237" user="hruiz" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal on how to calibrate the Hlt Muon Alley" date="1157386085" name="Hltcalibration.pdf" path="Hltcalibration.pdf" size="804062" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes July 14" date="1153313915" name="trigger-monitoring-060714.txt" path="trigger-monitoring-060714.txt" size="2614" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070413.txt" attr="" comment="Minutes April 13, 2007" date="1176816617" name="trigger-monitoring-070413.txt" path="trigger-monitoring-070413.txt" size="2287" stream="trigger-monitoring-070413.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070511.txt" attr="" comment="Minutes May 11, 2007" date="1180443880" name="trigger-monitoring-070511.txt" path="trigger-monitoring-070511.txt" size="3000" stream="trigger-monitoring-070511.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070629.txt" attr="" comment="Minutes June 29, 2007" date="1183456511" name="trigger-monitoring-070629.txt" path="trigger-monitoring-070629.txt" size="2547" stream="trigger-monitoring-070629.txt" user="Main.dijkstra" version="1"

Revision 172008-09-04 - JoseHernando

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 60 to 60
 

The Presenter

Changed:
<
<
Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.
>
>
Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/monobjectpresenter.sh"
on the command line.
You should see something like the screenshot.
 
Select "Tools" -> "PageEditor"
Changed:
<
<
Change User to "HIST_WRITER"
>
>

In the Dialog box: disconect for the DB (histogram data base)

In the windows of the left, click in Cancel

 
Now you should see 2 new areas
in the right part of the Presenter Window.
One called "DIM Histogram Browser"
and one called "Histograms in Database"

Double click on the nodes name in the "DIM Histogram Browser" in this example "hltc03".
Line: 79 to 84
 

Recompailing the HLT code in the pit

  • The LHCb Moore at EFF the is started from the following script: /group/online/hlt/scripts/defaultfilter.sh (is a soft link to a script in the hlt area)
    • i.s: defaultfilter.sh -> /group/hlt/devel-20080821/Moore_v5r0/Hlt/Moore/v5r0/job/runMooreOnline_EFF.sh
Changed:
<
<
  • This script runs Moore with an option file, there are two main option files at HltSys/v*/options
    • DEFAULT.opts and DEFAULT_TAE.opts (for Time Aligment Events)
>
>
  • This script runs Moore with an option file, there are two main option files at Hlt/Moore/v5r0/options
    • DEFAULT.opts and DEFAULT_TAE.opts (for Time Aligment Events
 
  • To recompile the code:
Added:
>
>
    • before recompiling the code! if you do it in the directory in use by the EFF, it can affect the run. The precedure is make a temp directory, complit it there, test in TDET, and when sure that it works, recompile the directory in use.
 
Changed:
<
<
    • please set the right CMTPROJECTPATH to the directory where Moore set in the hlt directory, for example:
>
>
    • please set the right CMTPROJECTPATH to the directory where Moore is located, for example:
 
      • > export CMTPROJECTPATH=/group/hlt/devel-20080821:/sw/lib/lhcb:/sw/lib/lcg/external
Changed:
<
<
      • > go the the Moore package Moore_v5r0/Hlt/Moore/v5r0/cmt
>
>
    • > go the directory Moore_v5r0/Hlt/Moore/v5r0/cmt
 
      • > cmt config
      • > source setup.sh
      • If some paths or version has been updated you need to do also:
        • > ./makePath.sh
Changed:
<
<

>
>

Testing new code in the EFF (for experts) at TDET

  • Make your own develop directory where to locate your local copy of Moore
  • ask the Online people to make a defaultfilter_test.sh pointing to your Moore script and that the reserved subfarm for the HLT is using your defaultfilter_test.sh.
  • login into the hlt01 machine and execute the PVSS script to control the farm: /group/online/hlt/pvss/HLT_UI_DEN.sh
  • go to lavel FSM, then + HLT, right-click FARM, then click view, it opens FARM:TOP window
  • login into dumdaq01 to execute the TDET script
  • Run PVSS script: /group/online/ecs/Shortcuts/TDET/TDDAQ_UI_DEN.sh
  • got to label FSM, then + in TDDAQ, right-click TDET, click view, opens TDET:TOP window
  • go to FARM:TOP and take the subfarm reserved for the HLT, refresh/do it click
  • Now you need to take that subfarm quickly for TDET:TOP, click on the lock in the State label, only if the lock is open, otherwise it means that TDET is been used by someone else, click on take, and then the State goes to not allocated status, then click on it, and allocate it.
  • In State, now select: configure to start the run, it goes to ready state
  • In State, now select: start run
  • If errors, try to recover, and configure again
  • Now in Active state, you can configure the run, clear in TFC control
  • Set the triggers: radom, periodic, calibration apply and exit.
  • Now click on go: it starts to send events to the TDET in the selected subfarm
  • You can ssh to the subfarm, open the presenter and see the histograms
  • You can open errorLog TDET & and see the errors/warnings
  • When you are done, remember to give back the subfarm! go to FARM:TOP, and then mark remove, and refresh/do it click
 
Deleted:
<
<
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Oct 20, 2006." date="1161870232" name="trigger-monitoring-061020.txt" path="trigger-monitoring-061020.txt" size="2030" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Trigger stream proposal (Tomasz)" date="1164295504" name="TriggerStreamInStripping.pdf" path="TriggerStreamInStripping.pdf" size="93429" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Plots obtained with the new Hlt Muon checking code" date="1157386211" name="HltMuPlots.pdf" path="HltMuPlots.pdf" size="608372" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes August 25" date="1156944866" name="trigger-monitoring-060825.txt" path="trigger-monitoring-060825.txt" size="3289" user="Main.dijkstra" version="2"
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1150289218" name="hlthowto_conditions.txt" path="hlthowto_conditions.txt" size="2291" user="hernando" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes of June 14" date="1152457117" name="MinutesbrainstormingJune14.txt" path="MinutesbrainstormingJune14.txt" size="1402" user="Main.MiriamGandelman" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes June 30" date="1152026364" name="trigger-monitoring.txt" path="trigger-monitoring.txt" size="2574" user="Main.dijkstra" version="4"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Feb 9, 2007" date="1171537060" name="trigger-monitoring-070209.txt" path="trigger-monitoring-070209.txt" size="2582" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="proposal to the HltSummary class" date="1158847337" name="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" path="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" size="39936" user="Main.JoseHernando" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes May 17 meeting" date="1150809623" name="trigger-monitoring-may17-06.txt" path="trigger-monitoring-may17-06.txt" size="2345" user="miriam" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal of code structure and guidelines for the alleys" date="1150444954" name="Structure_and_guidelines.pdf" path="Structure_and_guidelines.pdf" size="23237" user="hruiz" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal on how to calibrate the Hlt Muon Alley" date="1157386085" name="Hltcalibration.pdf" path="Hltcalibration.pdf" size="804062" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes July 14" date="1153313915" name="trigger-monitoring-060714.txt" path="trigger-monitoring-060714.txt" size="2614" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070413.txt" attr="" comment="Minutes April 13, 2007" date="1176816617" name="trigger-monitoring-070413.txt" path="trigger-monitoring-070413.txt" size="2287" stream="trigger-monitoring-070413.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070511.txt" attr="" comment="Minutes May 11, 2007" date="1180443880" name="trigger-monitoring-070511.txt" path="trigger-monitoring-070511.txt" size="3000" stream="trigger-monitoring-070511.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
 
META FILEATTACHMENT attachment="trigger-monitoring-070629.txt" attr="" comment="Minutes June 29, 2007" date="1183456511" name="trigger-monitoring-070629.txt" path="trigger-monitoring-070629.txt" size="2547" stream="trigger-monitoring-070629.txt" user="Main.dijkstra" version="1"
Added:
>
>
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070511.txt" attr="" comment="Minutes May 11, 2007" date="1180443880" name="trigger-monitoring-070511.txt" path="trigger-monitoring-070511.txt" size="3000" stream="trigger-monitoring-070511.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070413.txt" attr="" comment="Minutes April 13, 2007" date="1176816617" name="trigger-monitoring-070413.txt" path="trigger-monitoring-070413.txt" size="2287" stream="trigger-monitoring-070413.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes July 14" date="1153313915" name="trigger-monitoring-060714.txt" path="trigger-monitoring-060714.txt" size="2614" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal on how to calibrate the Hlt Muon Alley" date="1157386085" name="Hltcalibration.pdf" path="Hltcalibration.pdf" size="804062" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal of code structure and guidelines for the alleys" date="1150444954" name="Structure_and_guidelines.pdf" path="Structure_and_guidelines.pdf" size="23237" user="hruiz" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes May 17 meeting" date="1150809623" name="trigger-monitoring-may17-06.txt" path="trigger-monitoring-may17-06.txt" size="2345" user="miriam" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="proposal to the HltSummary class" date="1158847337" name="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" path="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" size="39936" user="Main.JoseHernando" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Feb 9, 2007" date="1171537060" name="trigger-monitoring-070209.txt" path="trigger-monitoring-070209.txt" size="2582" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes June 30" date="1152026364" name="trigger-monitoring.txt" path="trigger-monitoring.txt" size="2574" user="Main.dijkstra" version="4"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes of June 14" date="1152457117" name="MinutesbrainstormingJune14.txt" path="MinutesbrainstormingJune14.txt" size="1402" user="Main.MiriamGandelman" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1150289218" name="hlthowto_conditions.txt" path="hlthowto_conditions.txt" size="2291" user="hernando" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes August 25" date="1156944866" name="trigger-monitoring-060825.txt" path="trigger-monitoring-060825.txt" size="3289" user="Main.dijkstra" version="2"
META FILEATTACHMENT attr="" autoattached="1" comment="Plots obtained with the new Hlt Muon checking code" date="1157386211" name="HltMuPlots.pdf" path="HltMuPlots.pdf" size="608372" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Trigger stream proposal (Tomasz)" date="1164295504" name="TriggerStreamInStripping.pdf" path="TriggerStreamInStripping.pdf" size="93429" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Oct 20, 2006." date="1161870232" name="trigger-monitoring-061020.txt" path="trigger-monitoring-061020.txt" size="2030" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"

Revision 162008-09-04 - JoseHernando

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Changed:
<
<

LHCb trigger: Informal Online Documentation

>
>

LHCb trigger: Informal Online Documentation

 
Changed:
<
<

Shift info

>
>

Shift info

 
Changed:
<
<

Actual Run Control Status via Web: http://lbstatus.cern.ch/

>
>

Actual Run Control Status via Web: http://lbstatus.cern.ch/

 
Changed:
<
<

Logging in the Online Cluster

>
>

Logging in the Online Cluster

 
  • To login into any machines from the pit you need an account on the Online Cluster (For HLT Piquets it is the hlt_shift Hans mailed).
  • The connection between the Online cluster and the rest of the world has to be done through the gateway (lbgw01.cern.ch if you are in lxplus or gw01.cern.ch if you are in the Online cluster).
  • To prevent heavy network traffic you should NOT connect remotely to the Online Cluster unless you have a good reason for that.
  • The computers you can work from in the Control Room work in a "First come first serve" system. So chose anyone that is free.
Changed:
<
<
  • As there are only Windows machines there you will need to export the display if you connect to any other machine. So starting Exceed is the first thing to do.
>
>
  • As there are only Windows machines there you will need to export the display if you connect to any other machine. So starting Exceed is the first thing to do.
 
Changed:
<
<
>
>
 
  • With Exceed opened you can connect to the machines with PuTTY.
Changed:
<
<
  • But to export the display you should go to the Putty window in Connection > SSH > X11 check the Enable X11 forwarding box and in the X display location type in the machine you are logged in (there is a label with the name in the screen. It is for example lb018w where only the numbers can change).
>
>
  • But to export the display you should go to the Putty window in Connection > SSH > X11 check the Enable X11 forwarding box and in the X display location type in the machine you are logged in (there is a label with the name in the screen. It is for example lb018w where only the numbers can change).
 
Changed:
<
<
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!
>
>
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!
 
Changed:
<
<

Computers Scheme

>
>

Computers Scheme

 
  • The EFF (Event Filter Farm) is where the HLT will run and at moment there are 50 subfarms installed.
  • Each subfarm is called hlta01, hltb10, hltc06 etc and has 4 nodes that are called hlta0101, hlta0102 and so on.
  • Each of these nodes have 8 cores which means each subfarm can and will run 32 HLT processes at the same time.
  • There are the machines from the monitoring farm (mona08 is the most used one).
Changed:
<
<
  • Whenever you want to compile something go to the plus machines to not make the EFF machines busy (just putty to plus).
>
>
  • Whenever you want to compile something go to the plus machines to not make the EFF machines busy (just putty to plus).
 
Changed:
<
<

HLT code in the pit

>
>

HLT code in the pit

 
  • The HLT that is installed in the Online Cluster is absolutely not what is released and that you all know. It is a much simpler one.
  • It has only 2 different alleys: a Random trigger alley (HltRandom) and a not Random trigger alley (HltPhysics).
  • The difference is based on the Trigger type defined in the Odin bank.
  • The trigger type contained in Odin is defined per event and can be: Cosmics, Physics, Auxiliary, Random, Periodic, Calibration, Time Aligned Events and are defined in $DAQEVENTROOT/Event/ODIN.h
  • The Random Trigger Alley is called when the type of trigger in Odin is Random (which is 3) and the Physics is called for all the other types.
Changed:
<
<
  • The Random Alley just pre scales events by a certain factor defined by who is running it and the Physics accepts all the events.
>
>
  • The Random Alley just pre scales events by a certain factor defined by who is running it and the Physics accepts all the events.
 
Changed:
<
<

The way the code runs

>
>

The way the code runs

 
  • Everything in the pit is controlled by PVSS.
  • This means that you have to run everything through PVSS panels. They control everything: High voltage, Data AQuisition, L0, HLT, Storage, Monitoring and so on.
  • You can chose what you want to run and set many properties in the PVSS panels that will make the option files that will be used for running for all the processes.
  • It is possible to run LHCb including as many detectors as one wants and it is also to possible to run a given subdetector in standalone mode (Each of this subdetectors or LHCb are called partitions).
Changed:
<
<
  • There is also the TDET partition that controls 5 test Tell1s that send raw banks in the same format as they come from LHCb. That is the main testing environment we have to see if things work in real data.
>
>
  • There is also the TDET partition that controls 5 test Tell1s that send raw banks in the same format as they come from LHCb. That is the main testing environment we have to see if things work in real data.

The Error Logger

  • To get the printouts of what is running, you need to open the errorLog
  • For that connect to "mona08" with PuTTY
  • Enter "/group/online/dataflow/scripts/errorLog LHCb". Here is if you want to see what is going on in LHCb partition. For a different one replace LHCb for TDET or VELOA for instance.
  • You should see the error logger with 3 screens as in the screenshot. The top one prints the messages, the bottom left is reserved for the history and the bottom right is for the settings.
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrows.
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.

 
Added:
>
>

The Presenter

Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.
 
Changed:
<
<

The Error Logger

  • To get the printouts of what is running, you need to open the errorLog
  • For that connect to "mona08" with PuTTY
  • Enter "/group/online/dataflow/scripts/errorLog LHCb". Here is if you want to see what is going on in LHCb partition. For a different one replace LHCb for TDET or VELOA for instance.
  • You should see the error logger with 3 screens as in the screenshot. The top one prints the messages, the bottom left is reserved for the history and the bottom right is for the settings.
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrows.
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.

The Presenter

Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.

Select "Tools" -> "PageEditor"

Change User to "HIST_WRITER"

Now you should see 2 new areas
in the right part of the Presenter Window.
One called "DIM Histogram Browser"
and one called "Histograms in Database"

Double click on the nodes name in the "DIM Histogram Browser" in this example "hltc03".

Select "HltGlobalMonitor" and check
"m_histoodinentry" and "m_histoodintype"

Right click and choose "Add checked to Database"

Now the selected data appears in the "Histograms in Database".

Select "Gaucho Job".
Check the data you are interested in.
Right click and select "Add checked histogram(s) to Page"
>
>
Select "Tools" -> "PageEditor"

Change User to "HIST_WRITER"

Now you should see 2 new areas
in the right part of the Presenter Window.
One called "DIM Histogram Browser"
and one called "Histograms in Database"

Double click on the nodes name in the "DIM Histogram Browser" in this example "hltc03".

Select "HltGlobalMonitor" and check
"m_histoodinentry" and "m_histoodintype"

Right click and choose "Add checked to Database"

Now the selected data appears in the "Histograms in Database".

Select "Gaucho Job".
Check the data you are interested in.
Right click and select "Add checked histogram(s) to Page"
  Now your histograms should appear in the main area of the presenter. You can place them with your mouse. When you press the green "Play" button they'll start updating.
Added:
>
>

Recompailing the HLT code in the pit

  • The LHCb Moore at EFF the is started from the following script: /group/online/hlt/scripts/defaultfilter.sh (is a soft link to a script in the hlt area)
    • i.s: defaultfilter.sh -> /group/hlt/devel-20080821/Moore_v5r0/Hlt/Moore/v5r0/job/runMooreOnline_EFF.sh
  • This script runs Moore with an option file, there are two main option files at HltSys/v*/options
    • DEFAULT.opts and DEFAULT_TAE.opts (for Time Aligment Events)
  • To recompile the code:
    • set the project environment:
    • please set the right CMTPROJECTPATH to the directory where Moore set in the hlt directory, for example:
      • > export CMTPROJECTPATH=/group/hlt/devel-20080821:/sw/lib/lhcb:/sw/lib/lcg/external
      • > go the the Moore package Moore_v5r0/Hlt/Moore/v5r0/cmt
      • > cmt config
      • > source setup.sh
      • If some paths or version has been updated you need to do also:
        • > ./makePath.sh

 
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"

Revision 152008-08-28 - HansDijkstra

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 11 to 11
 
Added:
>
>

Actual Run Control Status via Web: http://lbstatus.cern.ch/

 

Logging in the Online Cluster

  • To login into any machines from the pit you need an account on the Online Cluster (For HLT Piquets it is the hlt_shift Hans mailed).

Revision 142008-08-20 - BrunoSouzaDePaula

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 57 to 57
 

The Error Logger

Changed:
<
<
>
>
 
Changed:
<
<
Connect to "mona08" with PuTTY
Enter "/group/online/dataflow/scripts/errorLog LHCb"
You should see the error logger with 3 screens as in the screenshot

You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrows .
Tip: You may want to disable mona08 to reduce the messages.
>
>
  • To get the printouts of what is running, you need to open the errorLog
  • For that connect to "mona08" with PuTTY
  • Enter "/group/online/dataflow/scripts/errorLog LHCb". Here is if you want to see what is going on in LHCb partition. For a different one replace LHCb for TDET or VELOA for instance.
  • You should see the error logger with 3 screens as in the screenshot. The top one prints the messages, the bottom left is reserved for the history and the bottom right is for the settings.
  • You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrows.
  • Notice that this severity level is just a filter, if the program is printing only WARNINGs if you put the errorLog to DEBUG you won't get any DEBUG messages.
  • Tip: You may want to disable mona08 to reduce the messages.
 

Revision 132008-08-19 - StephanNies

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 94 to 94
 
Changed:
<
<
Change Password to "HIST_WRITER"
>
>
Change User to "HIST_WRITER"
 

Revision 122008-08-19 - StephanNies

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 63 to 63
 Connect to "mona08" with PuTTY
Enter "/group/online/dataflow/scripts/errorLog LHCb"
You should see the error logger with 3 screens as in the screenshot
Added:
>
>

You can choose the serverity level of messages in the small right lower window with tab or ctrl-arrows .
Tip: You may want to disable mona08 to reduce the messages.
 
Line: 102 to 105
 in the right part of the Presenter Window.
One called "DIM Histogram Browser"
and one called "Histograms in Database"
Added:
>
>

Double click on the nodes name in the "DIM Histogram Browser" in this example "hltc03".
 
Added:
>
>
Select "HltGlobalMonitor" and check
"m_histoodinentry" and "m_histoodintype"

Right click and choose "Add checked to Database"

Now the selected data appears in the "Histograms in Database".

Select "Gaucho Job".
Check the data you are interested in.
Right click and select "Add checked histogram(s) to Page"

Now your histograms should appear in the main area of the presenter. You can place them with your mouse. When you press the green "Play" button they'll start updating.

 
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"

Revision 112008-08-19 - StephanNies

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 17 to 17
 
  • The connection between the Online cluster and the rest of the world has to be done through the gateway (lbgw01.cern.ch if you are in lxplus or gw01.cern.ch if you are in the Online cluster).
  • To prevent heavy network traffic you should NOT connect remotely to the Online Cluster unless you have a good reason for that.
  • The computers you can work from in the Control Room work in a "First come first serve" system. So chose anyone that is free.
Changed:
<
<
  • As there are only Windows machines there you will need to export the display if you connect to any other machine. So starting Exceed is the first thing to do.
  • With Exceed opened you can connect to the machines with putty.
>
>
  • As there are only Windows machines there you will need to export the display if you connect to any other machine. So starting Exceed is the first thing to do.

  • With Exceed opened you can connect to the machines with PuTTY.
 
  • But to export the display you should go to the Putty window in Connection > SSH > X11 check the Enable X11 forwarding box and in the X display location type in the machine you are logged in (there is a label with the name in the screen. It is for example lb018w where only the numbers can change).
Changed:
<
<
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!
>
>
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!
 

Computers Scheme

  • The EFF (Event Filter Farm) is where the HLT will run and at moment there are 50 subfarms installed.

Revision 102008-08-19 - StephanNies

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 47 to 47
 
  • There is also the TDET partition that controls 5 test Tell1s that send raw banks in the same format as they come from LHCb. That is the main testing environment we have to see if things work in real data.
Added:
>
>

The Error Logger

Connect to "mona08" with PuTTY
Enter "/group/online/dataflow/scripts/errorLog LHCb"
You should see the error logger with 3 screens as in the screenshot

The Presenter

Connect to a node, for example "hltc03".
You can start the presenter by typing
"/group/online/presenter/presenter.sh"
on the command line.
You should see something like the screenshot.

Select "Tools" -> "PageEditor"

Change Password to "HIST_WRITER"

Now you should see 2 new areas
in the right part of the Presenter Window.
One called "DIM Histogram Browser"
and one called "Histograms in Database"
 
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"

Revision 92008-08-18 - BrunoSouzaDePaula

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->

Revision 82008-08-18 - BrunoSouzaDePaula

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 19 to 19
 
  • The computers you can work from in the Control Room work in a "First come first serve" system. So chose anyone that is free.
  • As there are only Windows machines there you will need to export the display if you connect to any other machine. So starting Exceed is the first thing to do.
  • With Exceed opened you can connect to the machines with putty.
Changed:
<
<
  • But to export the display you should go to the Putty window in Connection > SSH > X11 check the Enable X11 forwarding box and in the X display location type in the machine you are logged in (there is a label with the name in the screen. It is for example lb023w where only the numbers can change).
>
>
  • But to export the display you should go to the Putty window in Connection > SSH > X11 check the Enable X11 forwarding box and in the X display location type in the machine you are logged in (there is a label with the name in the screen. It is for example lb018w where only the numbers can change).
 
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!

Computers Scheme

Revision 72008-08-15 - HansDijkstra

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 9 to 9
 
Changed:
<
<
>
>
 

Logging in the Online Cluster

Revision 62008-08-15 - BrunoSouzaDePaula

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 45 to 45
 
  • It is possible to run LHCb including as many detectors as one wants and it is also to possible to run a given subdetector in standalone mode (Each of this subdetectors or LHCb are called partitions).
  • There is also the TDET partition that controls 5 test Tell1s that send raw banks in the same format as they come from LHCb. That is the main testing environment we have to see if things work in real data.
Deleted:
<
<
Some random links as a skeleton for later progress:
 
Deleted:
<
<
 
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"

Revision 52008-08-15 - HansDijkstra

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->

LHCb trigger: Informal Online Documentation


Added:
>
>

Shift info

 

Logging in the Online Cluster

  • To login into any machines from the pit you need an account on the Online Cluster (For HLT Piquets it is the hlt_shift Hans mailed).

Revision 42008-08-15 - BrunoSouzaDePaula

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Changed:
<
<

LHCb trigger: Oral online documentation

>
>

LHCb trigger: Informal Online Documentation

 

Revision 32008-08-14 - BrunoSouzaDePaula

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Changed:
<
<

LHCb trigger: Oral online documentation

>
>

LHCb trigger: Oral online documentation

 
Changed:
<
<

This is just a skeleton

HLT Pending Issues
>
>

Logging in the Online Cluster

  • To login into any machines from the pit you need an account on the Online Cluster (For HLT Piquets it is the hlt_shift Hans mailed).
  • The connection between the Online cluster and the rest of the world has to be done through the gateway (lbgw01.cern.ch if you are in lxplus or gw01.cern.ch if you are in the Online cluster).
  • To prevent heavy network traffic you should NOT connect remotely to the Online Cluster unless you have a good reason for that.
  • The computers you can work from in the Control Room work in a "First come first serve" system. So chose anyone that is free.
  • As there are only Windows machines there you will need to export the display if you connect to any other machine. So starting Exceed is the first thing to do.
  • With Exceed opened you can connect to the machines with putty.
  • But to export the display you should go to the Putty window in Connection > SSH > X11 check the Enable X11 forwarding box and in the X display location type in the machine you are logged in (there is a label with the name in the screen. It is for example lb023w where only the numbers can change).
  • You can save this configuration for further use if you do not want to go through this procedure every time you want to use putty!

Computers Scheme

  • The EFF (Event Filter Farm) is where the HLT will run and at moment there are 50 subfarms installed.
  • Each subfarm is called hlta01, hltb10, hltc06 etc and has 4 nodes that are called hlta0101, hlta0102 and so on.
  • Each of these nodes have 8 cores which means each subfarm can and will run 32 HLT processes at the same time.
  • There are the machines from the monitoring farm (mona08 is the most used one).
  • Whenever you want to compile something go to the plus machines to not make the EFF machines busy (just putty to plus).

HLT code in the pit

  • The HLT that is installed in the Online Cluster is absolutely not what is released and that you all know. It is a much simpler one.
  • It has only 2 different alleys: a Random trigger alley (HltRandom) and a not Random trigger alley (HltPhysics).
  • The difference is based on the Trigger type defined in the Odin bank.
  • The trigger type contained in Odin is defined per event and can be: Cosmics, Physics, Auxiliary, Random, Periodic, Calibration, Time Aligned Events and are defined in $DAQEVENTROOT/Event/ODIN.h
  • The Random Trigger Alley is called when the type of trigger in Odin is Random (which is 3) and the Physics is called for all the other types.
  • The Random Alley just pre scales events by a certain factor defined by who is running it and the Physics accepts all the events.

The way the code runs

  • Everything in the pit is controlled by PVSS.
  • This means that you have to run everything through PVSS panels. They control everything: High voltage, Data AQuisition, L0, HLT, Storage, Monitoring and so on.
  • You can chose what you want to run and set many properties in the PVSS panels that will make the option files that will be used for running for all the processes.
  • It is possible to run LHCb including as many detectors as one wants and it is also to possible to run a given subdetector in standalone mode (Each of this subdetectors or LHCb are called partitions).
  • There is also the TDET partition that controls 5 test Tell1s that send raw banks in the same format as they come from LHCb. That is the main testing environment we have to see if things work in real data.
  Some random links as a skeleton for later progress:

Revision 22008-08-14 - HugoRuiz

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
Added:
>
>
<!-- /ActionTrackerPlugin -->
 

LHCb trigger: Oral online documentation

Changed:
<
<


Blabla:

>
>

This is just a skeleton

 HLT Pending Issues
Changed:
<
<
Blabla
>
>
Some random links as a skeleton for later progress:
 

Revision 12008-07-20 - HugoRuiz

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

LHCb trigger: Oral online documentation



Blabla:

HLT Pending Issues

Blabla

META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Sep 22." date="1159877941" name="trigger-monitoring-060922.txt" path="trigger-monitoring-060922.txt" size="2657" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes monitoring meeting March 2, 2007." date="1173257659" name="trigger-monitoring-070302.txt" path="trigger-monitoring-070302.txt" size="1383" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Nov 17, 2006" date="1164295682" name="trigger-monitoring-061117.txt" path="trigger-monitoring-061117.txt" size="1844" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Oct 20, 2006." date="1161870232" name="trigger-monitoring-061020.txt" path="trigger-monitoring-061020.txt" size="2030" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Trigger stream proposal (Tomasz)" date="1164295504" name="TriggerStreamInStripping.pdf" path="TriggerStreamInStripping.pdf" size="93429" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Plots obtained with the new Hlt Muon checking code" date="1157386211" name="HltMuPlots.pdf" path="HltMuPlots.pdf" size="608372" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes August 25" date="1156944866" name="trigger-monitoring-060825.txt" path="trigger-monitoring-060825.txt" size="3289" user="Main.dijkstra" version="2"
META FILEATTACHMENT attr="" autoattached="1" comment="" date="1150289218" name="hlthowto_conditions.txt" path="hlthowto_conditions.txt" size="2291" user="hernando" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes of June 14" date="1152457117" name="MinutesbrainstormingJune14.txt" path="MinutesbrainstormingJune14.txt" size="1402" user="Main.MiriamGandelman" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes June 30" date="1152026364" name="trigger-monitoring.txt" path="trigger-monitoring.txt" size="2574" user="Main.dijkstra" version="4"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes Feb 9, 2007" date="1171537060" name="trigger-monitoring-070209.txt" path="trigger-monitoring-070209.txt" size="2582" user="Main.dijkstra" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="proposal to the HltSummary class" date="1158847337" name="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" path="\\CERNHOMEH.CERN.CH\Desktop_H\hernando\papers\HltSummary\HLT_summary_v2.doc" size="39936" user="Main.JoseHernando" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes May 17 meeting" date="1150809623" name="trigger-monitoring-may17-06.txt" path="trigger-monitoring-may17-06.txt" size="2345" user="miriam" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal of code structure and guidelines for the alleys" date="1150444954" name="Structure_and_guidelines.pdf" path="Structure_and_guidelines.pdf" size="23237" user="hruiz" version="1.1"
META FILEATTACHMENT attr="" autoattached="1" comment="Proposal on how to calibrate the Hlt Muon Alley" date="1157386085" name="Hltcalibration.pdf" path="Hltcalibration.pdf" size="804062" user="Main.leggerf" version="1"
META FILEATTACHMENT attr="" autoattached="1" comment="Minutes July 14" date="1153313915" name="trigger-monitoring-060714.txt" path="trigger-monitoring-060714.txt" size="2614" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070413.txt" attr="" comment="Minutes April 13, 2007" date="1176816617" name="trigger-monitoring-070413.txt" path="trigger-monitoring-070413.txt" size="2287" stream="trigger-monitoring-070413.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070511.txt" attr="" comment="Minutes May 11, 2007" date="1180443880" name="trigger-monitoring-070511.txt" path="trigger-monitoring-070511.txt" size="3000" stream="trigger-monitoring-070511.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070601.txt" attr="" comment="Minutes June 1, 2007" date="1181751413" name="trigger-monitoring-070601.txt" path="trigger-monitoring-070601.txt" size="3457" stream="trigger-monitoring-070601.txt" user="Main.dijkstra" version="1"
META FILEATTACHMENT attachment="trigger-monitoring-070629.txt" attr="" comment="Minutes June 29, 2007" date="1183456511" name="trigger-monitoring-070629.txt" path="trigger-monitoring-070629.txt" size="2547" stream="trigger-monitoring-070629.txt" user="Main.dijkstra" version="1"
 
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