Difference: LHCbTrigger (1 vs. 122)

Revision 1222018-11-02 - AlexPearce

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 13 to 13
 
  • Conferences: See the presentation section of the HLT WG database. For presentations before 2016, see this page. Approved HLT plots for conferences are on this page.
  • Documentation: See the lhcb-note section of the HLT WG database. There is also a page listing commissioning notes in preparation.
  • Deadlines: Jump to this section of the current page.
Added:
>
>
 

Planning

Revision 1212018-08-22 - MichaelWilkinson

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

General information

  • Meetings: We have our weekly trigger meeting on Friday afternoon at 15:00 in 2-R-30. See the indico listing.
Changed:
<
<
>
>
 
Changed:
<
<
  • Conferences: See the presentation section of the HLT WG database. For presentations before 2016, see this page. Approved HLT plots for conferences are on this page.
  • Documentation: See the lhcb-note section of the HLT WG database. There is also a page listing commissioning notes in preparation.
>
>
  • Conferences: See the presentation section of the HLT WG database. For presentations before 2016, see this page. Approved HLT plots for conferences are on this page.
  • Documentation: See the lhcb-note section of the HLT WG database. There is also a page listing commissioning notes in preparation.
 
  • Deadlines: Jump to this section of the current page.

Planning

Changed:
<
<
>
>
 
Line: 30 to 30
  It is expected that anybody developing HLT code, including Hlt2 line authors, should keep an eye on these automatic tests, and report any issues.
Nightly qmtests Look here under lhcb-head (Moore and MooreOnline). In order to run all tests, you can do: make test ARGS ="-j 12"
Changed:
<
<
Throughput tests with a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
HLT rates See these instructions to use the Moore_RateTest script yourself.
Tests are run on a daily basis within the lhcbpr framework, using 30k L0 filtered events from the TestFileDB.
Tests are run on samples corresponding to a few different L0 TCKs, and on different nightly build slots.
The results are published here. See also gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.
>
>
Throughput tests with a farm node Pick the latest entry from here Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
HLT rates See these instructions to use the Moore_RateTest script yourself.
Tests are run on a daily basis within the lhcbpr framework, using 30k L0 filtered events from the TestFileDB.
Tests are run on samples corresponding to a few different L0 TCKs, and on different nightly build slots.
The results are published here. See also gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.
 

Developing Hlt2 lines

Changed:
<
<
2018 startup deadlines: presentation of new lines to be included in 2018 is February 2nd. Deadline for committing new lines will be ~6 weeks later (March 16th, subject to changes in the LHC schedule).

If you wish to introduce a new Hlt2 line, or retune an existing one, please follow the steps listed in the table below.
The aim is to have a turnaround time of a few weeks for a new or updated Hlt2 line to enter the data taking. This means there are no specific dead lines and we try to be as flexible as possible.
>
>
2018 startup deadlines: presentation of new lines to be included in 2018 is February 2nd. Deadline for committing new lines will be ~6 weeks later (March 16th, subject to changes in the LHC schedule).

If you wish to introduce a new Hlt2 line, or retune an existing one, please follow the steps listed in the table below.
The aim is to have a turnaround time of a few weeks for a new or updated Hlt2 line to enter the data taking. This means there are no specific dead lines and we try to be as flexible as possible.
 This turnaround time does not apply at the beginning of a year when potentially many new lines are added at once.
1 Contact your WG liason Discuss with them any questions you have on the following steps
2 Determine the signal rate in the LHCb acceptance This should be without any selection or reconstruction cuts (so you don't need MC)
Line: 48 to 49
 
7 Create an LBHLT JIRA task See for example LBHLT-124
8 Write your trigger line Follow these instructions.
9 Instrument your line with at least one monitoring histogram detailed instructions here.
Changed:
<
<
10 Measure the rates of your line(s) Using with at least 50000 HLT1 accepted events. A dataset is provided in the TestFileDB and there is an example on how to process it with the Moore_RateTest on this page.
>
>
10 Measure the rates of your line(s) Using with at least 50000 HLT1 accepted events. A dataset is provided in the TestFileDB and there is an example on how to process it with the Moore_RateTest on this page.
 
11 Measure the efficiency of your lines(s) Again using the standard Moore_RateTest script, with juggled signal MC, or data, where possible.
12 Estimate the purity of your line(s) For rare/forbidden/unobserved modes, it is suggested to use e.g. the current world's best limit (cross section x) BF, or if there is no limit, you should use a limit that would be considered "interesting".
13 Independence test Run the Moore_RateTest script without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
Line: 75 to 76
 

Level-0

  • TCKs: All released ones as listed here. See also slide-9.
  • Bandwidth division: More details on this page
Changed:
<
<
  • Testing L0 TCKs: See these instructions to run L0App and print the rates.
  • Software: See this page on the L0App application, and these details on L0Muon emulation.
>
>
  • Testing L0 TCKs: See these instructions to run L0App and print the rates.
  • Software: See this page on the L0App application, and these details on L0Muon emulation.
 

Trigger performance studies

  • Timing Studies: Checking the impact of increasing the number of Kalman iterations on Hlt execution time
Line: 88 to 89
 
  • GPU Studies: Studies of running (part of) HLT1 on GPUs

Physics working group specific pages

Changed:
<
<
>
>
 

About the HLT

Added:
>
>
 
  • HltLine -- Basic Structural Unit of the HLT
Changed:
<
<
>
>
 
Changed:
<
<
  • PrivateTCK -- Using a private TCK for running on MC with special settings (deprecated)
  • whichTCK -- How to find out which TCK was used for a given dataset
  • seeTCK -- How to see if a given TCK exists in the software
>
>
  • PrivateTCK -- Using a private TCK for running on MC with special settings (deprecated)
  • whichTCK -- How to find out which TCK was used for a given dataset
  • seeTCK -- How to see if a given TCK exists in the software
 
Line: 107 to 109
 
Changed:
<
<
>
>
 
Changed:
<
<
  • LHCbTCK: Pages describing the complete (L0+HLT) procedure for modifying an existing TCK
>
>
  • LHCbTCK: Pages describing the complete (L0+HLT) procedure for modifying an existing TCK
 

Revision 1202018-03-13 - DorotheaVomBruch

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

Upgrade Trigger development

Added:
>
>
  • GPU Studies: Studies of running (part of) HLT1 on GPUs
 

Physics working group specific pages

Revision 1192018-02-27 - PatrickSKoppenburg

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

General information

Changed:
<
<
  • Meetings: We have our weekly HLT operations meeting on Friday afternoon at 15:00 in 2-R-30. See the indico listing.
>
>
  • Meetings: We have our weekly trigger meeting on Friday afternoon at 15:00 in 2-R-30. See the indico listing.
 

Revision 1182018-01-25 - RosenMatev

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 31 to 31
 It is expected that anybody developing HLT code, including Hlt2 line authors, should keep an eye on these automatic tests, and report any issues.
Nightly qmtests Look here under lhcb-head (Moore and MooreOnline). In order to run all tests, you can do: make test ARGS ="-j 12"
Throughput tests with a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
Changed:
<
<
HLT rates See these instructions to use the Moore_RateTest script yourself.
Tests are run on a daily basis within the lhcbpr framework, using 30k L0 filtered events from the TestFileDB.
Tests are run on samples corresponding to a few different L0 TCKs, and on different nightly build slots.
The results are published here.
with a nice summary here. See also LBCORE-970, gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
>
>
HLT rates See these instructions to use the Moore_RateTest script yourself.
Tests are run on a daily basis within the lhcbpr framework, using 30k L0 filtered events from the TestFileDB.
Tests are run on samples corresponding to a few different L0 TCKs, and on different nightly build slots.
The results are published here. See also gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
 
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.

Developing Hlt2 lines

Revision 1172018-01-17 - ConorFitzpatrick

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 31 to 31
 It is expected that anybody developing HLT code, including Hlt2 line authors, should keep an eye on these automatic tests, and report any issues.
Nightly qmtests Look here under lhcb-head (Moore and MooreOnline). In order to run all tests, you can do: make test ARGS ="-j 12"
Throughput tests with a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
Changed:
<
<
HLT rates See these instructions to use the Moore_RateTest script yourself.
Tests are run on a daily basis within the lhcbpr framework, using 30k L0 filtered events from the TestFileDB.
Tests are run on samples corresponding to a few different L0 TCKs, and on different nightly build slots.
The results are published here.
The default should be 2016-patches and 0x160B. Results here. See also LBCORE-970, gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
>
>
HLT rates See these instructions to use the Moore_RateTest script yourself.
Tests are run on a daily basis within the lhcbpr framework, using 30k L0 filtered events from the TestFileDB.
Tests are run on samples corresponding to a few different L0 TCKs, and on different nightly build slots.
The results are published here.
with a nice summary here. See also LBCORE-970, gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
 
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.

Developing Hlt2 lines

Revision 1162018-01-10 - ConorFitzpatrick

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

General information

Changed:
<
<
  • Meetings: We have our weekly HLT operations meeting on Friday afternoon at 15:00 in 2-R-30. See the indigo listing.
>
>
  • Meetings: We have our weekly HLT operations meeting on Friday afternoon at 15:00 in 2-R-30. See the indico listing.
 
Changed:
<
<
  • Documentation: See the lhcb-note section of the HLT WG database. There is also a page listing 2015 commissioning notes in preparation.
>
>
  • Documentation: See the lhcb-note section of the HLT WG database. There is also a page listing commissioning notes in preparation.
 
  • Deadlines: Jump to this section of the current page.

Planning

Changed:
<
<
>
>
 
Deleted:
<
<
 
Added:
>
>
 

Information for Hlt Piquets and WG liaisons

The HLT piquets should refer to the HLT Piquet Guide

Revision 1152017-12-11 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 54 to 54
 
13 Independence test Run the Moore_RateTest script without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
14 Tuning knobs We need to see the purity and efficiency as a function of rate for a tunable parameter (a cut you're happy to tighten or at worst a prescale)
15 Second HLT ops presentation It should include the results of all of the above steps. The deadline for this presentation for new lines for the 2018 startup is March 16th.
Changed:
<
<
16 Merge request Can happen before the second presentation. Mark as WIP if still work in progress.
>
>
16 Merge request Can happen before the second presentation. Mark as WIP if still work in progress. The target should be 2018-patches
 
17 Create JIRA subtask for new TCK  
18 Check the next nightly tests  
19 Release manager accepts merge request  

Revision 1142017-12-01 - RosenMatev

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 35 to 35
 
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.

Developing Hlt2 lines

Added:
>
>
2018 startup deadlines: presentation of new lines to be included in 2018 is February 2nd. Deadline for committing new lines will be ~6 weeks later (March 16th, subject to changes in the LHC schedule).

 If you wish to introduce a new Hlt2 line, or retune an existing one, please follow the steps listed in the table below.
The aim is to have a turnaround time of a few weeks for a new or updated Hlt2 line to enter the data taking. This means there are no specific dead lines and we try to be as flexible as possible.
This turnaround time does not apply at the beginning of a year when potentially many new lines are added at once.
Line: 43 to 44
 
3 Carefully consider need for Turbo(++) or FULL Please keep your liaison involved
4 Get signal MC Request or make sure you have already a small signal MC sample with raw banks
5 Read the general guidelines Make sure you are prepared to follow these instructions, if not speak with your liason.
Changed:
<
<
6 First HLT ops presentation After completing the above steps present on the general plan for the new line and tell us your signal rate For new lines intended for the 2017 startup, this must be done by the 24th Feb.
>
>
6 First HLT ops presentation After completing the above steps present on the general plan for the new line and tell us your signal rate For new lines intended for the 2018 startup, this must be done by Feb 2nd.
 
7 Create an LBHLT JIRA task See for example LBHLT-124
8 Write your trigger line Follow these instructions.
9 Instrument your line with at least one monitoring histogram detailed instructions here.
Line: 52 to 53
 
12 Estimate the purity of your line(s) For rare/forbidden/unobserved modes, it is suggested to use e.g. the current world's best limit (cross section x) BF, or if there is no limit, you should use a limit that would be considered "interesting".
13 Independence test Run the Moore_RateTest script without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
14 Tuning knobs We need to see the purity and efficiency as a function of rate for a tunable parameter (a cut you're happy to tighten or at worst a prescale)
Changed:
<
<
15 Second HLT ops presentation It should include the results of all of the above steps. The deadline for this presentation for new lines for the 2017 startup is the 30th March.
>
>
15 Second HLT ops presentation It should include the results of all of the above steps. The deadline for this presentation for new lines for the 2018 startup is March 16th.
 
16 Merge request Can happen before the second presentation. Mark as WIP if still work in progress.
17 Create JIRA subtask for new TCK  
18 Check the next nightly tests  

Revision 1132017-09-18 - RoelAaij

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

HLT Monitoring

Added:
>
>
 

Level-0

  • TCKs: All released ones as listed here. See also slide-9.

Revision 1122017-08-11 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 57 to 57
 
17 Create JIRA subtask for new TCK  
18 Check the next nightly tests  
19 Release manager accepts merge request  
Changed:
<
<
20 HLT piquet to prepare new HLT2 TCK  
21 PPG/OPG sign off for deployment  
22 TCK deployment  
23 Validation of data Line authors are expected to look at the monitoring histograms for the lines, and at the output data, and report back to HLT ops within 1-2 weeks of first data with the new TCK.
>
>
20 Update Tesla configuration In case a new Turbo or TurCal line is updated, the Tesla production step needs to be updated to know about the new line, otherwise the productions will crash. The HLT should inform the production team about this change in advance.
21 HLT piquet to prepare new HLT2 TCK  
22 PPG/OPG sign off for deployment  
23 TCK deployment  
24 Validation of data Line authors are expected to look at the monitoring histograms for the lines, and at the output data, and report back to HLT ops within 1-2 weeks of first data with the new TCK.
 

The Tesla project

Revision 1112017-08-11 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 53 to 53
 
13 Independence test Run the Moore_RateTest script without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
14 Tuning knobs We need to see the purity and efficiency as a function of rate for a tunable parameter (a cut you're happy to tighten or at worst a prescale)
15 Second HLT ops presentation It should include the results of all of the above steps. The deadline for this presentation for new lines for the 2017 startup is the 30th March.
Changed:
<
<
16 Merge request to master Can happen before the second presentation. Mark as WIP if still work in progress.
>
>
16 Merge request Can happen before the second presentation. Mark as WIP if still work in progress.
 
17 Create JIRA subtask for new TCK  
18 Check the next nightly tests  
19 Release manager accepts merge request  

Revision 1102017-07-26 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 35 to 35
 
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.

Developing Hlt2 lines

Deleted:
<
<
The deadlines for 2017 data taking are: 24th February 2017 presentation in the Hlt Ops meeting, 30th March 2017 merge request of a functioning line.
 If you wish to introduce a new Hlt2 line, or retune an existing one, please follow the steps listed in the table below.
Changed:
<
<
The aim is to have a turnaround time of a few weeks for a new or updated Hlt2 line to enter the data taking.
>
>
The aim is to have a turnaround time of a few weeks for a new or updated Hlt2 line to enter the data taking. This means there are no specific dead lines and we try to be as flexible as possible.
 This turnaround time does not apply at the beginning of a year when potentially many new lines are added at once.
1 Contact your WG liason Discuss with them any questions you have on the following steps
2 Determine the signal rate in the LHCb acceptance This should be without any selection or reconstruction cuts (so you don't need MC)

Revision 1092017-05-25 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 97 to 97
 
  • PrivateTCK -- Using a private TCK for running on MC with special settings (deprecated)
  • whichTCK -- How to find out which TCK was used for a given dataset
  • seeTCK -- How to see if a given TCK exists in the software
Changed:
<
<
>
>
  • Update TCK -- How to change algorithm properties and make a new TCK based on an existing one
  • updateL0TCK - Updating the L0 part of a TCK
 

Revision 1082017-05-05 - ConorFitzpatrick

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 17 to 17
 
  • Deadlines: Jump to this section of the current page.

Planning

Changed:
<
<
>
>
 

Revision 1072017-05-01 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 92 to 92
 
Changed:
<
<
  • PrivateTCK -- Using a private TCK for running on MC with special settings
>
>
 
  • whichTCK -- How to find out which TCK was used for a given dataset
  • seeTCK -- How to see if a given TCK exists in the software
  • newTCK -- How to make a new TCK based on an existing one

Revision 1062017-04-05 - RoelAaij

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 46 to 46
 
6 First HLT ops presentation After completing the above steps present on the general plan for the new line and tell us your signal rate For new lines intended for the 2017 startup, this must be done by the 24th Feb.
7 Create an LBHLT JIRA task See for example LBHLT-124
8 Write your trigger line Follow these instructions.
Changed:
<
<
9 Instrument your line with at least one monitoring histogram detailed instructions to follow.
>
>
9 Instrument your line with at least one monitoring histogram detailed instructions here.
 
10 Measure the rates of your line(s) Using with at least 50000 HLT1 accepted events. A dataset is provided in the TestFileDB and there is an example on how to process it with the Moore_RateTest on this page.
11 Measure the efficiency of your lines(s) Again using the standard Moore_RateTest script, with juggled signal MC, or data, where possible.
12 Estimate the purity of your line(s) For rare/forbidden/unobserved modes, it is suggested to use e.g. the current world's best limit (cross section x) BF, or if there is no limit, you should use a limit that would be considered "interesting".

Revision 1052017-03-30 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 53 to 53
 
13 Independence test Run the Moore_RateTest script without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
14 Tuning knobs We need to see the purity and efficiency as a function of rate for a tunable parameter (a cut you're happy to tighten or at worst a prescale)
15 Second HLT ops presentation It should include the results of all of the above steps. The deadline for this presentation for new lines for the 2017 startup is the 30th March.
Changed:
<
<
16 Merge request to master After approval in the HLT ops meeting.
>
>
16 Merge request to master Can happen before the second presentation. Mark as WIP if still work in progress.
 
17 Create JIRA subtask for new TCK  
18 Check the next nightly tests  
19 Release manager accepts merge request  

Revision 1042017-02-23 - ConorFitzpatrick

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 38 to 38
 If you wish to introduce a new Hlt2 line, or retune an existing one, please follow the steps listed in the table below.
The aim is to have a turnaround time of a few weeks for a new or updated Hlt2 line to enter the data taking.
This turnaround time does not apply at the beginning of a year when potentially many new lines are added at once.
Changed:
<
<
1 Discuss with your WG liaison And read these instructions.
2 Carefully consider need for Turbo(++) or FULL Please keep your liaison involved
3 First HLT ops presentation On the general plan for the new line. For new lines intended for the 2017 startup, this must be done by the 24th Feb.
4 Create an LBHLT JIRA task  
5 Tuning knobs We need to see rates, purities and efficiencies for at least 3 working points.
6 Measure the rates of your line(s) Using with at least 50000 HLT1 accepted events. A dataset is provided in the TestFileDB and there is an example on how to process it with the Moore_RateTest on this page.
7 Measure the efficiency of your lines(s) Again using the standard Moore_RateTest script, with juggled signal MC, or data, where possible.
If MC sample unavailable, we can approve, conditional on seeing the test within a few weeks
Good arguments need to be made if you think that a MC based efficiency measurement is inappropriate for your use case.
8 Estimate the purity of your line(s) For rare/forbidden/unobserved modes, it is suggested to use e.g. the current world's best limit (cross section x) BF, or if there is no limit, you should use a limit that would be considered "interesting".
9 Independence test Run the same rate test without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
10 Second HLT ops presentation It should include the results of all of the above steps. The deadline for this presentation for new lines for the 2017 startup is the 30th March.
11 Merge request to master After approval in the HLT ops meeting.
12 Create JIRA subtask for new TCK  
13 Check the next nightly tests  
14 Release manager accepts merge request  
15 HLT piquet to prepare new HLT2 TCK  
16 PPG/OPG sign off for deployment  
17 TCK deployment  
18 Validation of data Line authors are expected to look at the monitoring histograms for the lines, and at the output data, and report back to HLT ops within 1-2 weeks of first data with the new TCK.
>
>
1 Contact your WG liason Discuss with them any questions you have on the following steps
2 Determine the signal rate in the LHCb acceptance This should be without any selection or reconstruction cuts (so you don't need MC)
3 Carefully consider need for Turbo(++) or FULL Please keep your liaison involved
4 Get signal MC Request or make sure you have already a small signal MC sample with raw banks
5 Read the general guidelines Make sure you are prepared to follow these instructions, if not speak with your liason.
6 First HLT ops presentation After completing the above steps present on the general plan for the new line and tell us your signal rate For new lines intended for the 2017 startup, this must be done by the 24th Feb.
7 Create an LBHLT JIRA task See for example LBHLT-124
8 Write your trigger line Follow these instructions.
9 Instrument your line with at least one monitoring histogram detailed instructions to follow.
10 Measure the rates of your line(s) Using with at least 50000 HLT1 accepted events. A dataset is provided in the TestFileDB and there is an example on how to process it with the Moore_RateTest on this page.
11 Measure the efficiency of your lines(s) Again using the standard Moore_RateTest script, with juggled signal MC, or data, where possible.
12 Estimate the purity of your line(s) For rare/forbidden/unobserved modes, it is suggested to use e.g. the current world's best limit (cross section x) BF, or if there is no limit, you should use a limit that would be considered "interesting".
13 Independence test Run the Moore_RateTest script without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
14 Tuning knobs We need to see the purity and efficiency as a function of rate for a tunable parameter (a cut you're happy to tighten or at worst a prescale)
15 Second HLT ops presentation It should include the results of all of the above steps. The deadline for this presentation for new lines for the 2017 startup is the 30th March.
16 Merge request to master After approval in the HLT ops meeting.
17 Create JIRA subtask for new TCK  
18 Check the next nightly tests  
19 Release manager accepts merge request  
20 HLT piquet to prepare new HLT2 TCK  
21 PPG/OPG sign off for deployment  
22 TCK deployment  
23 Validation of data Line authors are expected to look at the monitoring histograms for the lines, and at the output data, and report back to HLT ops within 1-2 weeks of first data with the new TCK.
 

The Tesla project

Revision 1032017-02-23 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 42 to 42
 
2 Carefully consider need for Turbo(++) or FULL Please keep your liaison involved
3 First HLT ops presentation On the general plan for the new line. For new lines intended for the 2017 startup, this must be done by the 24th Feb.
4 Create an LBHLT JIRA task  
Changed:
<
<
5 Measure the rates of your line(s) Using with at least 50000 HLT1 accepted events. A dataset is provided in the TestFileDB and there is an example on how to process it with the Moore_RateTest on this page.
6 Measure the efficiency of your lines(s) Again using the standard Moore_RateTest script, with juggled signal MC, or data, where possible.
If MC sample unavailable, we can approve, conditional on seeing the test within a few weeks
Good arguments need to be made if you think that a MC based efficiency measurement is inappropriate for your use case.
7 Tuning knobs We need to see rates and efficiencies for at least 3 working points.
8 Independence test Run the same rate test without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
9 Second HLT ops presentation It should include the results of all of the above steps. The deadline for this presentation for new lines for the 2017 startup is the 30th March.
10 Merge request to master After approval in the HLT ops meeting.
11 Create JIRA subtask for new TCK  
12 Check the next nightly tests  
13 Release manager accepts merge request  
14 HLT piquet to prepare new HLT2 TCK  
15 PPG/OPG sign off for deployment  
16 TCK deployment  
17 Validation of data Line authors are expected to look at the monitoring histograms for the lines, and at the output data, and report back to HLT ops within 1-2 weeks of first data with the new TCK.
>
>
5 Tuning knobs We need to see rates, purities and efficiencies for at least 3 working points.
6 Measure the rates of your line(s) Using with at least 50000 HLT1 accepted events. A dataset is provided in the TestFileDB and there is an example on how to process it with the Moore_RateTest on this page.
7 Measure the efficiency of your lines(s) Again using the standard Moore_RateTest script, with juggled signal MC, or data, where possible.
If MC sample unavailable, we can approve, conditional on seeing the test within a few weeks
Good arguments need to be made if you think that a MC based efficiency measurement is inappropriate for your use case.
8 Estimate the purity of your line(s) For rare/forbidden/unobserved modes, it is suggested to use e.g. the current world's best limit (cross section x) BF, or if there is no limit, you should use a limit that would be considered "interesting".
9 Independence test Run the same rate test without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
10 Second HLT ops presentation It should include the results of all of the above steps. The deadline for this presentation for new lines for the 2017 startup is the 30th March.
11 Merge request to master After approval in the HLT ops meeting.
12 Create JIRA subtask for new TCK  
13 Check the next nightly tests  
14 Release manager accepts merge request  
15 HLT piquet to prepare new HLT2 TCK  
16 PPG/OPG sign off for deployment  
17 TCK deployment  
18 Validation of data Line authors are expected to look at the monitoring histograms for the lines, and at the output data, and report back to HLT ops within 1-2 weeks of first data with the new TCK.
 

The Tesla project

Revision 1022017-02-22 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 42 to 42
 
2 Carefully consider need for Turbo(++) or FULL Please keep your liaison involved
3 First HLT ops presentation On the general plan for the new line. For new lines intended for the 2017 startup, this must be done by the 24th Feb.
4 Create an LBHLT JIRA task  
Changed:
<
<
5 Measure the rates of your line(s) Using with at least 50000 HLT1 accepted events. Please follow these instructions to use the standard Moore_RateTest script.
>
>
5 Measure the rates of your line(s) Using with at least 50000 HLT1 accepted events. A dataset is provided in the TestFileDB and there is an example on how to process it with the Moore_RateTest on this page.
 
6 Measure the efficiency of your lines(s) Again using the standard Moore_RateTest script, with juggled signal MC, or data, where possible.
If MC sample unavailable, we can approve, conditional on seeing the test within a few weeks
Good arguments need to be made if you think that a MC based efficiency measurement is inappropriate for your use case.
7 Tuning knobs We need to see rates and efficiencies for at least 3 working points.
8 Independence test Run the same rate test without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.

Revision 1012017-02-22 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 46 to 46
 
6 Measure the efficiency of your lines(s) Again using the standard Moore_RateTest script, with juggled signal MC, or data, where possible.
If MC sample unavailable, we can approve, conditional on seeing the test within a few weeks
Good arguments need to be made if you think that a MC based efficiency measurement is inappropriate for your use case.
7 Tuning knobs We need to see rates and efficiencies for at least 3 working points.
8 Independence test Run the same rate test without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
Changed:
<
<
9 Second HLT ops presentation That includes: link to LBHLT JIRA task; very brief physics case; case for Turbo(++) or FULL; rates and efficiencies for at least 3 working points; evidence of independence test success. The deadline for this presentation for new lines for the 2017 startup is the 30th March.
>
>
9 Second HLT ops presentation It should include the results of all of the above steps. The deadline for this presentation for new lines for the 2017 startup is the 30th March.
 
10 Merge request to master After approval in the HLT ops meeting.
11 Create JIRA subtask for new TCK  
12 Check the next nightly tests  

Revision 1002017-02-20 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 40 to 40
 This turnaround time does not apply at the beginning of a year when potentially many new lines are added at once.
1 Discuss with your WG liaison And read these instructions.
2 Carefully consider need for Turbo(++) or FULL Please keep your liaison involved
Changed:
<
<
3 Create an LBHLT JIRA task  
4 Measure the rates of your line(s) Using with at least 50000 HLT1 accepted events. Please follow these instructions to use the standard Moore_RateTest script.
5 Measure the efficiency of your lines(s) Again using the standard Moore_RateTest script, with juggled signal MC, or data, where possible.
If MC sample unavailable, we can approve, conditional on seeing the test within a few weeks
Good arguments need to be made if you think that a MC based efficiency measurement is inappropriate for your use case.
>
>
3 First HLT ops presentation On the general plan for the new line. For new lines intended for the 2017 startup, this must be done by the 24th Feb.
4 Create an LBHLT JIRA task  
5 Measure the rates of your line(s) Using with at least 50000 HLT1 accepted events. Please follow these instructions to use the standard Moore_RateTest script.
6 Measure the efficiency of your lines(s) Again using the standard Moore_RateTest script, with juggled signal MC, or data, where possible.
If MC sample unavailable, we can approve, conditional on seeing the test within a few weeks
Good arguments need to be made if you think that a MC based efficiency measurement is inappropriate for your use case.
 
7 Tuning knobs We need to see rates and efficiencies for at least 3 working points.
8 Independence test Run the same rate test without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
Changed:
<
<
9 HLT ops presentation That includes: link to LBHLT JIRA task; very brief physics case; case for Turbo(++) or FULL; rates and efficiencies for at least 3 working points; evidence of independence test success.
>
>
9 Second HLT ops presentation That includes: link to LBHLT JIRA task; very brief physics case; case for Turbo(++) or FULL; rates and efficiencies for at least 3 working points; evidence of independence test success. The deadline for this presentation for new lines for the 2017 startup is the 30th March.
 
10 Merge request to master After approval in the HLT ops meeting.
11 Create JIRA subtask for new TCK  
12 Check the next nightly tests  

Revision 992017-02-16 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 17 to 17
 
  • Deadlines: Jump to this section of the current page.

Planning

Changed:
<
<
>
>
 

Revision 982017-01-23 - MikaVesterinen

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

Old pages

Changed:
<
<
A list of historic, and probably obsolete, pages on the LHCbTrigger is here.
>
>
A list of historic, and probably obsolete, pages on the LHCbTrigger is here.
 
META FILEATTACHMENT attachment="LHCb_Split_Trigger_Plot.key.pdf" attr="" comment="" date="1380027116" name="LHCb_Split_Trigger_Plot.key.pdf" path="LHCb_Split_Trigger_Plot.key.pdf" size="19957" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Deferred_Trigger_Plot.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Deferred_Trigger_Plot.key.pdf" path="LHCb_Deferred_Trigger_Plot.key.pdf" size="20230" user="gligorov" version="1"

Revision 972017-01-18 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 38 to 38
 If you wish to introduce a new Hlt2 line, or retune an existing one, please follow the steps listed in the table below.
The aim is to have a turnaround time of a few weeks for a new or updated Hlt2 line to enter the data taking.
This turnaround time does not apply at the beginning of a year when potentially many new lines are added at once.
Changed:
<
<
1 Discuss with your WG liaison And read these instructions and use the recommended datasets
>
>
1 Discuss with your WG liaison And read these instructions.
 
2 Carefully consider need for Turbo(++) or FULL Please keep your liaison involved
3 Create an LBHLT JIRA task  
4 Measure the rates of your line(s) Using with at least 50000 HLT1 accepted events. Please follow these instructions to use the standard Moore_RateTest script.

Revision 962017-01-18 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 14 to 14
 
Added:
>
>
  • Deadlines: Jump to this section of the current page.
 

Planning

Changed:
<
<
  • Tasks: Lists (in need of organisation and review) from 2015-2016 YETS,
>
>
 

Information for Hlt Piquets and WG liaisons

Line: 27 to 28
 

Moore testing

It is expected that anybody developing HLT code, including Hlt2 line authors, should keep an eye on these automatic tests, and report any issues.
Added:
>
>
Nightly qmtests Look here under lhcb-head (Moore and MooreOnline). In order to run all tests, you can do: make test ARGS ="-j 12"
Throughput tests with a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
 
HLT rates See these instructions to use the Moore_RateTest script yourself.
Tests are run on a daily basis within the lhcbpr framework, using 30k L0 filtered events from the TestFileDB.
Tests are run on samples corresponding to a few different L0 TCKs, and on different nightly build slots.
The results are published here.
The default should be 2016-patches and 0x160B. Results here. See also LBCORE-970, gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
Deleted:
<
<
Nightlies Look here under lhcb-head (Moore and MooreOnline). In order to run all tests, you can do: make test ARGS ="-j 12"
 
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.
Deleted:
<
<
Throughput tests with a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
 

Developing Hlt2 lines

Changed:
<
<
The deadlines for 2017 data taking are: 24th February 2017 presentation in the Hlt Ops meeting, 30th March 2017 merge request of a functioning line. If you wish to introduce a new Hlt2 line, or retune an existing one, please discuss with your WG liaison and follow these instructions, with the recommended datasets. Before creating a merge request, you should give a presentation at a Friday afternoon HLT ops meeting, containing all of the following:
The use case We don't need a physics seminar, just a quick summary
Turbo, Turbo++ or FULL? And why
Measurement of the rates Using Moore_RateTest with at least 50000 HLT1 accepted events
Measurement of the efficiency Using Moore_RateTest with juggled signal MC, or data, where possible.
If MC sample unavailable, we can approve, conditional on seeing the test within a few weeks
Good arguments need to be made if you think that a MC based efficiency measurement is inappropriate for your use case.
Rate and efficiency Measurements should be repeated for at least 3 working points.
Independence test Run the same rate test without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
If the line is approved based on this presentation, we will recommend a TCK JIRA task to which this line should be associated.
The line author is then required to:
  • Create a JIRA sub task (associated to the main TCK JIRA task) with all log files attached and presentation linked.
  • A gitlab merge request (to master) is made and the code is reviewed
  • Check the nightly tests the next day as they will already pick up your changes before the merge request is accepted.
Once the request is accepted, the HLT piquet will prepare a new HLT2 TCK which will be advertised to the lists
  • The next step is for the line author to check the new HLT2 TCK diff.
The new TCK will be signed off at the next OPG and PPG (silently, if there isn't one that week), and then deployed at the pit.
  • It is expected that the line author reports within 1-2 weeks on the validation of their line with real data.

The aim is to have a turnaround time of a few weeks for a new or updated Hlt2 line to enter the data taking. This turnaround time does not apply at the beginning of a year when potentially many new lines are added at once.

>
>
The deadlines for 2017 data taking are: 24th February 2017 presentation in the Hlt Ops meeting, 30th March 2017 merge request of a functioning line.
If you wish to introduce a new Hlt2 line, or retune an existing one, please follow the steps listed in the table below.
The aim is to have a turnaround time of a few weeks for a new or updated Hlt2 line to enter the data taking.
This turnaround time does not apply at the beginning of a year when potentially many new lines are added at once.
1 Discuss with your WG liaison And read these instructions and use the recommended datasets
2 Carefully consider need for Turbo(++) or FULL Please keep your liaison involved
3 Create an LBHLT JIRA task  
4 Measure the rates of your line(s) Using with at least 50000 HLT1 accepted events. Please follow these instructions to use the standard Moore_RateTest script.
5 Measure the efficiency of your lines(s) Again using the standard Moore_RateTest script, with juggled signal MC, or data, where possible.
If MC sample unavailable, we can approve, conditional on seeing the test within a few weeks
Good arguments need to be made if you think that a MC based efficiency measurement is inappropriate for your use case.
7 Tuning knobs We need to see rates and efficiencies for at least 3 working points.
8 Independence test Run the same rate test without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
9 HLT ops presentation That includes: link to LBHLT JIRA task; very brief physics case; case for Turbo(++) or FULL; rates and efficiencies for at least 3 working points; evidence of independence test success.
10 Merge request to master After approval in the HLT ops meeting.
11 Create JIRA subtask for new TCK  
12 Check the next nightly tests  
13 Release manager accepts merge request  
14 HLT piquet to prepare new HLT2 TCK  
15 PPG/OPG sign off for deployment  
16 TCK deployment  
17 Validation of data Line authors are expected to look at the monitoring histograms for the lines, and at the output data, and report back to HLT ops within 1-2 weeks of first data with the new TCK.
 

The Tesla project

Revision 952017-01-18 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 16 to 16
 
  • Documentation: See the lhcb-note section of the HLT WG database. There is also a page listing 2015 commissioning notes in preparation.

Planning

Added:
>
>
 
Changed:
<
<
>
>
 

Information for Hlt Piquets and WG liaisons

The HLT piquets should refer to the HLT Piquet Guide
Line: 26 to 27
 

Moore testing

It is expected that anybody developing HLT code, including Hlt2 line authors, should keep an eye on these automatic tests, and report any issues.
Changed:
<
<
Tests Description
HLT rates See these instructions to use the Moore_RateTest script yourself.
Tests are run on a daily basis within the lhcbpr framework, using 30k L0 filtered events from the TestFileDB.
Tests are run on samples corresponding to a few different L0 TCKs, and on different nightly build slots.
The results are published here.
The default should be 2016-patches and 0x160B. Results here. See also LBCORE-970, gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
Nightlies Look here under lhcb-head (Moore and MooreOnline). In order to run all tests, you can do: make test ARGS ="-j 12"
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.
Throughput tests with a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
>
>
HLT rates See these instructions to use the Moore_RateTest script yourself.
Tests are run on a daily basis within the lhcbpr framework, using 30k L0 filtered events from the TestFileDB.
Tests are run on samples corresponding to a few different L0 TCKs, and on different nightly build slots.
The results are published here.
The default should be 2016-patches and 0x160B. Results here. See also LBCORE-970, gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
Nightlies Look here under lhcb-head (Moore and MooreOnline). In order to run all tests, you can do: make test ARGS ="-j 12"
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.
Throughput tests with a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
 

Developing Hlt2 lines

Changed:
<
<
>
>
The deadlines for 2017 data taking are: 24th February 2017 presentation in the Hlt Ops meeting, 30th March 2017 merge request of a functioning line.
 If you wish to introduce a new Hlt2 line, or retune an existing one, please discuss with your WG liaison and follow these instructions, with the recommended datasets. Before creating a merge request, you should give a presentation at a Friday afternoon HLT ops meeting, containing all of the following:
Line: 55 to 55
  The aim is to have a turnaround time of a few weeks for a new or updated Hlt2 line to enter the data taking. This turnaround time does not apply at the beginning of a year when potentially many new lines are added at once.
Changed:
<
<
The deadlines for 2017 data taking are: 24th February 2017 presentation in the Hlt Ops meeting, 30th March 2017 merge request of a functioning line.
>
>
 

The Tesla project

Line: 118 to 118
 

Old pages

Changed:
<
<
>
>
A list of historic, and probably obsolete, pages on the LHCbTrigger is here.
 
META FILEATTACHMENT attachment="LHCb_Split_Trigger_Plot.key.pdf" attr="" comment="" date="1380027116" name="LHCb_Split_Trigger_Plot.key.pdf" path="LHCb_Split_Trigger_Plot.key.pdf" size="19957" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Deferred_Trigger_Plot.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Deferred_Trigger_Plot.key.pdf" path="LHCb_Deferred_Trigger_Plot.key.pdf" size="20230" user="gligorov" version="1"

Revision 942017-01-13 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 46 to 46
 If the line is approved based on this presentation, we will recommend a TCK JIRA task to which this line should be associated.
The line author is then required to:
  • Create a JIRA sub task (associated to the main TCK JIRA task) with all log files attached and presentation linked.
Changed:
<
<
  • A gitlab merge request (to 2016-patches) is made and the code is reviewed
>
>
  • A gitlab merge request (to master) is made and the code is reviewed
 
  • Check the nightly tests the next day as they will already pick up your changes before the merge request is accepted.
Once the request is accepted, the HLT piquet will prepare a new HLT2 TCK which will be advertised to the lists
  • The next step is for the line author to check the new HLT2 TCK diff.
The new TCK will be signed off at the next OPG and PPG (silently, if there isn't one that week), and then deployed at the pit.
  • It is expected that the line author reports within 1-2 weeks on the validation of their line with real data.
Changed:
<
<
All of the above is written in this document.
>
>
The aim is to have a turnaround time of a few weeks for a new or updated Hlt2 line to enter the data taking. This turnaround time does not apply at the beginning of a year when potentially many new lines are added at once.

The deadlines for 2017 data taking are: 24th February 2017 presentation in the Hlt Ops meeting, 30th March 2017 merge request of a functioning line.

 

The Tesla project

Revision 932016-11-29 - MarcoCattaneo

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

Planning

Changed:
<
<
>
>
 

Information for Hlt Piquets and WG liaisons

The HLT piquets should refer to the HLT Piquet Guide

Revision 922016-11-18 - MikaVesterinen

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

Upgrade Trigger development

Added:
>
>

Physics working group specific pages

 

About the HLT

Revision 912016-09-01 - MikaVesterinen

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

General information

Changed:
<
<
>
>
 
  • Conferences: See the presentation section of the HLT WG database. For presentations before 2016, see this page. Approved HLT plots for conferences are on this page.
  • Documentation: See the lhcb-note section of the HLT WG database. There is also a page listing 2015 commissioning notes in preparation.

Revision 902016-08-17 - MikaVesterinen

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

General information

  • Meetings: We have our weekly HLT operations meeting on Friday afternoon at 15:00 in 2-R-30. See the indigo listing.
Changed:
<
<
>
>
 

Revision 892016-07-28 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 28 to 28
 
HLT rates See these instructions to use the Moore_RateTest script yourself.
Tests are run on a daily basis within the lhcbpr framework, using 30k L0 filtered events from the TestFileDB.
Tests are run on samples corresponding to a few different L0 TCKs, and on different nightly build slots.
The results are published here.
The default should be 2016-patches and 0x160B. Results here. See also LBCORE-970, gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
Nightlies Look here under lhcb-head (Moore and MooreOnline). In order to run all tests, you can do: make test ARGS ="-j 12"
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.
Changed:
<
<
Timing tests on a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
>
>
Throughput tests with a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
 

Developing Hlt2 lines

Revision 882016-07-28 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 25 to 25
  It is expected that anybody developing HLT code, including Hlt2 line authors, should keep an eye on these automatic tests, and report any issues.
Tests Description
Changed:
<
<
HLT rates See these instructions to use the Moore_RateTest script yourself.
Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
>
>
HLT rates See these instructions to use the Moore_RateTest script yourself.
Tests are run on a daily basis within the lhcbpr framework, using 30k L0 filtered events from the TestFileDB.
Tests are run on samples corresponding to a few different L0 TCKs, and on different nightly build slots.
The results are published here.
The default should be 2016-patches and 0x160B. Results here. See also LBCORE-970, gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
 
Nightlies Look here under lhcb-head (Moore and MooreOnline). In order to run all tests, you can do: make test ARGS ="-j 12"
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.
Timing tests on a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.

Revision 872016-07-26 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 10 to 10
 
Changed:
<
<
>
>
  • Conferences: See the presentation section of the HLT WG database. For presentations before 2016, see this page. Approved HLT plots for conferences are on this page.
 
  • Documentation: See the lhcb-note section of the HLT WG database. There is also a page listing 2015 commissioning notes in preparation.

Planning

Revision 862016-07-22 - SaschaStahl

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 40 to 40
 
Measurement of the rates Using Moore_RateTest with at least 50000 HLT1 accepted events
Measurement of the efficiency Using Moore_RateTest with juggled signal MC, or data, where possible.
If MC sample unavailable, we can approve, conditional on seeing the test within a few weeks
Good arguments need to be made if you think that a MC based efficiency measurement is inappropriate for your use case.
Rate and efficiency Measurements should be repeated for at least 3 working points.
Changed:
<
<
Independence test Run the same rate test without your line included and use the ntuple to check that all lines give the same decisions in all events.
>
>
Independence test Run the same rate test without your line included and use the logfiles (and ntuples) to check that all other lines give the same inclusive rate.
 If the line is approved based on this presentation, we will recommend a TCK JIRA task to which this line should be associated.
The line author is then required to:
  • Create a JIRA sub task (associated to the main TCK JIRA task) with all log files attached and presentation linked.

Revision 852016-07-19 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 26 to 26
 It is expected that anybody developing HLT code, including Hlt2 line authors, should keep an eye on these automatic tests, and report any issues.
Tests Description
HLT rates See these instructions to use the Moore_RateTest script yourself.
Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
Changed:
<
<
Nightlies Look here under lhcb-head (Moore and MooreOnline)
>
>
Nightlies Look here under lhcb-head (Moore and MooreOnline). In order to run all tests, you can do: make test ARGS ="-j 12"
 
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.
Timing tests on a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.

Revision 842016-06-01 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 30 to 30
 
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.
Timing tests on a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
Changed:
<
<

Hlt line development guide

>
>

Developing Hlt2 lines

  If you wish to introduce a new Hlt2 line, or retune an existing one, please discuss with your WG liaison and follow these instructions, with the recommended datasets.
Line: 50 to 50
 
  • The next step is for the line author to check the new HLT2 TCK diff.
The new TCK will be signed off at the next OPG and PPG (silently, if there isn't one that week), and then deployed at the pit.
  • It is expected that the line author reports within 1-2 weeks on the validation of their line with real data.
Added:
>
>
All of the above is written in this document.
 

The Tesla project

Revision 832016-05-30 - MikaVesterinen

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

General information

Changed:
<
<
  • Meetings: We have our weekly HLT operations meeting on Friday afternoon's at 15:00 in 2-R-30. See the indigo listing.
>
>
  • Meetings: We have our weekly HLT operations meeting on Friday afternoon at 15:00 in 2-R-30. See the indigo listing.
 
Line: 30 to 30
 
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.
Timing tests on a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
Added:
>
>

Hlt line development guide

If you wish to introduce a new Hlt2 line, or retune an existing one, please discuss with your WG liaison and follow these instructions, with the recommended datasets. Before creating a merge request, you should give a presentation at a Friday afternoon HLT ops meeting, containing all of the following:

The use case We don't need a physics seminar, just a quick summary
Turbo, Turbo++ or FULL? And why
Measurement of the rates Using Moore_RateTest with at least 50000 HLT1 accepted events
Measurement of the efficiency Using Moore_RateTest with juggled signal MC, or data, where possible.
If MC sample unavailable, we can approve, conditional on seeing the test within a few weeks
Good arguments need to be made if you think that a MC based efficiency measurement is inappropriate for your use case.
Rate and efficiency Measurements should be repeated for at least 3 working points.
Independence test Run the same rate test without your line included and use the ntuple to check that all lines give the same decisions in all events.
If the line is approved based on this presentation, we will recommend a TCK JIRA task to which this line should be associated.
The line author is then required to:
  • Create a JIRA sub task (associated to the main TCK JIRA task) with all log files attached and presentation linked.
  • A gitlab merge request (to 2016-patches) is made and the code is reviewed
  • Check the nightly tests the next day as they will already pick up your changes before the merge request is accepted.
Once the request is accepted, the HLT piquet will prepare a new HLT2 TCK which will be advertised to the lists
  • The next step is for the line author to check the new HLT2 TCK diff.
The new TCK will be signed off at the next OPG and PPG (silently, if there isn't one that week), and then deployed at the pit.
  • It is expected that the line author reports within 1-2 weeks on the validation of their line with real data.
 

The Tesla project

Changed:
<
<

Hlt line development guide

Hlt2 line developers should follow these instructions, with the recommended datasets. It is required that line authors run the following tests before creating merge requests
>
>
 

HLT Monitoring

Level-0

Changed:
<
<
A table of L0 TCKs with their thresholds and integrated luminosities can be found in slide 9 of this talk by Matt Kenzie. There is also a full listing of L0 TCKs here.
>
>
  • TCKs: All released ones as listed here. See also slide-9.
  • Bandwidth division: More details on this page
  • Testing L0 TCKs: See these instructions to run L0App and print the rates.
  • Software: See this page on the L0App application, and these details on L0Muon emulation.
 

Trigger performance studies

  • Timing Studies: Checking the impact of increasing the number of Kalman iterations on Hlt execution time

Revision 822016-05-27 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 14 to 14
 
  • Documentation: See the lhcb-note section of the HLT WG database. There is also a page listing 2015 commissioning notes in preparation.

Planning

Changed:
<
<
>
>
 
Deleted:
<
<
 

Information for Hlt Piquets and WG liaisons

The HLT piquets should refer to the HLT Piquet Guide
Line: 24 to 21
 

Information for Hlt Piquets and WG liaisons

The HLT piquets should refer to the HLT Piquet Guide
Deleted:
<
<
 

Moore testing

Changed:
<
<
The following table gives an overview of the automatic tests that are run. MooreRateTestExamples
>
>
It is expected that anybody developing HLT code, including Hlt2 line authors, should keep an eye on these automatic tests, and report any issues.
 
Tests Description
Changed:
<
<
HLT rates Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
 lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
 lb-run --nightly-cvmfs --nightly lhcb-2016-patches Thu Moore/2016-patches python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
The test runs over 30k events by default to run over more events specify the --evtmax option.
>
>
HLT rates See these instructions to use the Moore_RateTest script yourself.
Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
The test runs over 30k events by default to run over more events specify the --evtmax option.
 
Nightlies Look here under lhcb-head (Moore and MooreOnline)
Changed:
<
<
Hlt1 independence test Under MooreOnline in the nightlies
>
>
Hlt1 independence test Under MooreOnline in the nightlies
There is some older documentation here.
 
Timing tests on a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.

The Tesla project

Line: 42 to 37
 

Hlt line development guide

Hlt2 line developers should follow these instructions, with the recommended datasets. It is required that line authors run the following tests before creating merge requests
Changed:
<
<
>
>
 

HLT Monitoring

Changed:
<
<
>
>
 

Level-0

A table of L0 TCKs with their thresholds and integrated luminosities can be found in slide 9 of this talk by Matt Kenzie.
Line: 60 to 54
 
  • Timing Studies: Checking the impact of increasing the number of Kalman iterations on Hlt execution time
  • Hlt2Rates: Rates of Hlt2 lines
  • HltCorrelations: Correlations of L0, Hlt and Stripping lines
Deleted:
<
<
 

Upgrade Trigger development

Line: 97 to 90
 
Added:
>
>
 

Old pages

Revision 812016-05-27 - MikaVesterinen

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

General information

Changed:
<
<
>
>
 

Planning

Line: 27 to 26
 

Moore testing

Added:
>
>
 The following table gives an overview of the automatic tests that are run.
Added:
>
>
MooreRateTestExamples
 
Tests Description
HLT rates Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
 lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
 lb-run --nightly-cvmfs --nightly lhcb-2016-patches Thu Moore/2016-patches python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
The test runs over 30k events by default to run over more events specify the --evtmax option.
Nightlies Look here under lhcb-head (Moore and MooreOnline)
Hlt1 independence test Under MooreOnline in the nightlies
Timing tests on a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
Added:
>
>

The Tesla project

 
Added:
>
>

Hlt line development guide

Hlt2 line developers should follow these instructions, with the recommended datasets. It is required that line authors run the following tests before creating merge requests
 
Added:
>
>

HLT Monitoring

 
Changed:
<
<

Conferences

>
>

Level-0

A table of L0 TCKs with their thresholds and integrated luminosities can be found in slide 9 of this talk by Matt Kenzie. There is also a full listing of L0 TCKs here.
 
Changed:
<
<

Documentation

>
>

Trigger performance studies

 
Changed:
<
<

The Tesla project

>
>

Upgrade Trigger development

 

About the HLT

Added:
>
>
 
  • TCKs -- Trigger Configuration Keys
  • MCTCKs -- How to make an 'MC' version of a TCK
  • PrivateTCK -- Using a private TCK for running on MC with special settings
Line: 81 to 98
 
Deleted:
<
<

Developing Hlt lines and testing of Moore

  • DataSets -- Data sets for trigger studies, including 2016 commissioning
  • Hlt2Lines -- Development guide for new Hlt2 lines

HLT Monitoring

Level-0

A table of L0 TCKs with their thresholds and integrated luminosities can be found in slide 9 of this talk by Matt Kenzie. There is also a full listing of L0 TCKs here.

Trigger performance studies

Upgrade Trigger development

 

Old pages

Revision 802016-05-20 - MikaVesterinen

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

Moore testing

The following table gives an overview of the automatic tests that are run.
Tests Description
Changed:
<
<
HLT rates Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
 lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
 lb-run --nightly-cvmfs --nightly lhcb-2016-patches Thu Moore/2016-patches python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
The test runs over 30k events by default to run over more events specify the -n #events option.
>
>
HLT rates Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
 lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
 lb-run --nightly-cvmfs --nightly lhcb-2016-patches Thu Moore/2016-patches python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
The test runs over 30k events by default to run over more events specify the --evtmax option.
 
Nightlies Look here under lhcb-head (Moore and MooreOnline)
Hlt1 independence test Under MooreOnline in the nightlies
Timing tests on a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.

Revision 792016-05-20 - SaschaStahl

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

Moore testing

The following table gives an overview of the automatic tests that are run.
Tests Description
Changed:
<
<
HLT rates Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
 lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
 lb-run --nightly-cvmfs --nightly lhcb-2016-patches Thu Moore/2016-patches python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
>
>
HLT rates Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
 lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
 lb-run --nightly-cvmfs --nightly lhcb-2016-patches Thu Moore/2016-patches python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
The test runs over 30k events by default to run over more events specify the -n #events option.
 
Nightlies Look here under lhcb-head (Moore and MooreOnline)
Hlt1 independence test Under MooreOnline in the nightlies
Timing tests on a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.

Revision 782016-05-19 - MikaVesterinen

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

Moore testing

The following table gives an overview of the automatic tests that are run.
Tests Description
Changed:
<
<
HLT rates Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
 lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
 lb-run --nightly-cvmfs --nightly <DAY> Moore 2016-patches python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
>
>
HLT rates Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
 lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
 lb-run --nightly-cvmfs --nightly lhcb-2016-patches Thu Moore/2016-patches python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
 
Nightlies Look here under lhcb-head (Moore and MooreOnline)
Hlt1 independence test Under MooreOnline in the nightlies
Timing tests on a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.

Revision 772016-05-18 - LaurentDufour

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

Moore testing

The following table gives an overview of the automatic tests that are run.
Tests Description
Changed:
<
<
HLT rates Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
 lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py 
 lb-run --nightly-cvmfs --nightly <DAY> Moore 2016-patches python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py 
>
>
HLT rates Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
 lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
 lb-run --nightly-cvmfs --nightly <DAY> Moore 2016-patches python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py' 
 
Nightlies Look here under lhcb-head (Moore and MooreOnline)
Hlt1 independence test Under MooreOnline in the nightlies
Timing tests on a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.

Revision 762016-05-16 - MikaVesterinen

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

Moore testing

The following table gives an overview of the automatic tests that are run.
Changed:
<
<
HLT rates Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons See also LBCORE-970, gitlab-repo, and these slides.
Nightlies Look here under lhcb-head (Moore and MooreOnline)  
Hlt1 independence test Under MooreOnline in the nightlies
Timing tests on a farm node Pick the latest entry from here See also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
The Moore_RateTest script can be run directly from a nightly or release build like
<!-- SyntaxHighlightingPlugin -->
lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py'
lb-run Moore v25r1 python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py'
   
<!-- end SyntaxHighlightingPlugin -->
>
>
Tests Description
HLT rates Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons
See also LBCORE-970, gitlab-repo, and these slides.
 lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py 
 lb-run --nightly-cvmfs --nightly <DAY> Moore 2016-patches python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py 
Nightlies Look here under lhcb-head (Moore and MooreOnline)
Hlt1 independence test Under MooreOnline in the nightlies
Timing tests on a farm node Pick the latest entry from here
Seee also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
 

Revision 752016-05-14 - MikaVesterinen

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

About the HLT

Changed:
<
<
>
>
 
  • HltLine -- Basic Structural Unit of the HLT
  • TCKs -- Trigger Configuration Keys
  • MCTCKs -- How to make an 'MC' version of a TCK

Revision 742016-05-04 - MikaVesterinen

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

General information

Added:
>
>
 

Planning

Line: 28 to 28
 

Moore testing

The following table gives an overview of the automatic tests that are run.
Changed:
<
<
HLT rates Pick the lastest entry from here for the default configuration, or here for all configuratons See also LBCORE-970, gitlab-repo, and these slides.
>
>
HLT rates Pick the lastest entry from here (0x1606) for the default configuration, or here for all configuratons See also LBCORE-970, gitlab-repo, and these slides.
 
Nightlies Look here under lhcb-head (Moore and MooreOnline)  
Hlt1 independence test Under MooreOnline in the nightlies
Timing tests on a farm node Pick the latest entry from here See also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.

Revision 732016-04-28 - MikaVesterinen

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

General information

  • We have our weekly HLT operations meeting on Friday afternoon's at 15:00 in 2-R-30. See the indigo listing.
  • List of WG liaisons.

Revision 722016-04-28 - MikaVesterinen

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

Documentation

Deleted:
<
<
 

The Tesla project

Line: 87 to 86
 

Developing Hlt lines and testing of Moore

  • DataSets -- Data sets for trigger studies, including 2016 commissioning
Changed:
<
<

Developing Hlt2 lines:

>
>
  • Hlt2Lines -- Development guide for new Hlt2 lines
 

HLT Monitoring

Revision 712016-04-26 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 30 to 30
 
HLT rates Pick the lastest entry from here for the default configuration, or here for all configuratons See also LBCORE-970, gitlab-repo, and these slides.
Nightlies Look here under lhcb-head (Moore and MooreOnline)  
Hlt1 independence test Under MooreOnline in the nightlies
Changed:
<
<
Timing tests on a farm node Pick the latest entry from here See also LBCORE-1007
>
>
Timing tests on a farm node Pick the latest entry from here See also LBCORE-1007, and these instructions to test Moore in the online environment on a dedicated node.
  The Moore_RateTest script can be run directly from a nightly or release build like
<!-- SyntaxHighlightingPlugin -->
lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py'
lb-run Moore v25r1 python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py'
   
<!-- end SyntaxHighlightingPlugin -->
Changed:
<
<
>
>
 

Conferences

Line: 122 to 119
 
Added:
>
>
 
META FILEATTACHMENT attachment="LHCb_Split_Trigger_Plot.key.pdf" attr="" comment="" date="1380027116" name="LHCb_Split_Trigger_Plot.key.pdf" path="LHCb_Split_Trigger_Plot.key.pdf" size="19957" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Deferred_Trigger_Plot.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Deferred_Trigger_Plot.key.pdf" path="LHCb_Deferred_Trigger_Plot.key.pdf" size="20230" user="gligorov" version="1"

Revision 702016-04-26 - MikaVesterinen

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

Information for Hlt Piquets and WG liaisons

The HLT piquets should refer to the HLT Piquet Guide
Changed:
<
<
>
>
 

Moore testing

The following table gives an overview of the automatic tests that are run.
Line: 116 to 116
 

Old pages

Added:
>
>
 

Revision 692016-04-22 - MikaVesterinen

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

Information for Hlt Piquets and WG liaisons

Changed:
<
<
>
>
The HLT piquets should refer to the HLT Piquet Guide
 
Added:
>
>

Moore testing

The following table gives an overview of the automatic tests that are run.
HLT rates Pick the lastest entry from here for the default configuration, or here for all configuratons See also LBCORE-970, gitlab-repo, and these slides.
Nightlies Look here under lhcb-head (Moore and MooreOnline)  
Hlt1 independence test Under MooreOnline in the nightlies
Timing tests on a farm node Pick the latest entry from here See also LBCORE-1007
The Moore_RateTest script can be run directly from a nightly or release build like
<!-- SyntaxHighlightingPlugin -->
lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py'
lb-run Moore v25r1 python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py'
   
<!-- end SyntaxHighlightingPlugin -->
 

Conferences

Line: 77 to 94
 

Developing Hlt2 lines:

Deleted:
<
<

Moore testing

The following table gives an overview of the automatic tests that are run.
HLT rates Pick the lastest entry from here for the default configuration, or here for all configuratons See also LBCORE-970, gitlab-repo, and these slides.
Nightlies Look here under lhcb-head (Moore and MooreOnline)  
Hlt1 independence test Under MooreOnline in the nightlies
Timing tests on a farm node Pick the latest entry from here See also LBCORE-1007
The Moore_RateTest script can be run directly from a nightly or release build like
<!-- SyntaxHighlightingPlugin -->
lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py'
lb-run Moore v25r1 python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py'
   
<!-- end SyntaxHighlightingPlugin -->
 

HLT Monitoring

Revision 682016-04-22 - MikaVesterinen

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

Information for Hlt Piquets and WG liaisons

Deleted:
<
<
 
Deleted:
<
<
 

Conferences

Revision 672016-04-20 - MikaVesterinen

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

Moore testing

The following table gives an overview of the automatic tests that are run.
Changed:
<
<
HLT rates Pick the lastest entry from here for the default configuration, or here for all configuratons See also LBCORE-970 and gitlab-repo
>
>
HLT rates Pick the lastest entry from here for the default configuration, or here for all configuratons See also LBCORE-970, gitlab-repo, and these slides.
 
Nightlies Look here under lhcb-head (Moore and MooreOnline)  
Hlt1 independence test Under MooreOnline in the nightlies
Timing tests on a farm node Pick the latest entry from here See also LBCORE-1007
Changed:
<
<
>
>
The Moore_RateTest script can be run directly from a nightly or release build like
<!-- SyntaxHighlightingPlugin -->
lb-run --nightly lhcb-head <DAY> Moore HEAD python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py'
lb-run Moore v25r1 python '$PRCONFIGROOT/python/MooreTests/Moore_RateTest.py'
   
<!-- end SyntaxHighlightingPlugin -->
 

Revision 662016-04-20 - MikaVesterinen

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

Conferences

Line: 93 to 91
  single node.
Added:
>
>
 

HLT Monitoring

Line: 115 to 114
 

Old pages

Changed:
<
<
>
>
 

Revision 652016-04-10 - MikaVesterinen

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

Planning

Revision 642016-04-10 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 10 to 10
 
  • We have our weekly HLT operations meeting on Friday afternoon's at 15:00 in 2-R-30. See the indigo listing.
  • List of WG liaisons.
  • The HLT WG database
Added:
>
>
  • See the "operations" twiki.
 

Planning

Revision 632016-04-07 - MikaVesterinen

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

Conferences

Deleted:
<
<
 

Revision 622016-04-07 - MikaVesterinen

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

Conferences

Added:
>
>
 

Revision 612016-04-04 - MikaVesterinen

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

Moore testing

The following table gives an overview of the automatic tests that are run.
Changed:
<
<
HLT rates Pick the lastest entry from here See also LBCORE-970 and gitlab-repo
>
>
HLT rates Pick the lastest entry from here for the default configuration, or here for all configuratons See also LBCORE-970 and gitlab-repo
 
Nightlies Look here under lhcb-head (Moore and MooreOnline)  
Hlt1 independence test Under MooreOnline in the nightlies
Timing tests on a farm node Pick the latest entry from here See also LBCORE-1007

Revision 602016-04-04 - SeanBenson

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

The Tesla project

Added:
>
>
 

About the HLT

Revision 592016-03-30 - MikaVesterinen

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

Moore testing

Changed:
<
<
>
>
The following table gives an overview of the automatic tests that are run.
HLT rates Pick the lastest entry from here See also LBCORE-970 and gitlab-repo
Nightlies Look here under lhcb-head (Moore and MooreOnline)  
Hlt1 independence test Under MooreOnline in the nightlies
Timing tests on a farm node Pick the latest entry from here See also LBCORE-1007
 

Revision 582016-03-08 - MikaVesterinen

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

Documentation

Changed:
<
<
>
>
 

The Tesla project

Revision 572016-02-26 - MikaVesterinen

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

General information

  • We have our weekly HLT operations meeting on Friday afternoon's at 15:00 in 2-R-30. See the indigo listing.
  • List of WG liaisons.
Added:
>
>
 

Planning

Revision 562016-02-11 - MikaVesterinen

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 11 to 11
 
  • List of WG liaisons.

Planning

Added:
>
>
 

Revision 552016-01-24 - SaschaStahl

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

Developing and testing Hlt lines

>
>

Developing Hlt lines and testing of Moore

 
  • DataSets -- Data sets for trigger studies, including 2016 commissioning
Added:
>
>
 

Developing Hlt2 lines:

Line: 76 to 77
 

Developing Hlt2 lines:

Changed:
<
<

Moore testing

>
>

Moore testing

 

Revision 542016-01-19 - SaschaStahl

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

Developing Hlt lines

>
>

Developing and testing Hlt lines

 
  • DataSets -- Data sets for trigger studies, including 2016 commissioning
Changed:
<
<

Developing Hlt2 lines:

>
>

Developing Hlt2 lines:

 

Moore testing

Revision 532016-01-14 - MikaVesterinen

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

Level-0

Added:
>
>
A table of L0 TCKs with their thresholds and integrated luminosities can be found in slide 9 of this talk by Matt Kenzie. There is also a full listing of L0 TCKs here.
 
  • The bandwidth division Is detailed on this page
  • Instructions to get run L0 and get the rates: L0RatesForHLTPage
Deleted:
<
<
 

Revision 522016-01-07 - MikaVesterinen

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

Developing Hlt lines

  • DataSets -- Data sets for trigger studies, including 2016 commissioning
Changed:
<
<

Developing Hlt2 lines:

>
>

Developing Hlt2 lines:

 
Deleted:
<
<
 
Changed:
<
<

Testing Moore Online - Performing a timing test

>
>

Moore testing

 

Revision 512016-01-07 - SaschaStahl

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

Developing Hlt2 lines with the new Template:

>
>

Developing Hlt lines

  • DataSets -- Data sets for trigger studies, including 2016 commissioning

Developing Hlt2 lines:

 
Changed:
<
<

Testing Moore Online - Performing a timing test

>
>

Testing Moore Online - Performing a timing test

 
  • MooreOnlineOffline -- Testing Moore and its timing in the Online environment on a single node.
Deleted:
<
<
  • DataSets: Data sets for trigger studies, including 2016 commissioning
 

Revision 502015-12-17 - SaschaStahl

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

Testing Moore Online - Performing a timing test

  • MooreOnlineOffline -- Testing Moore and its timing in the Online environment on a single node.
Added:
>
>
  • DataSets: Data sets for trigger studies, including 2016 commissioning
 

Revision 492015-12-14 - MikaVesterinen

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

Trigger performance studies

  • Timing Studies: Checking the impact of increasing the number of Kalman iterations on Hlt execution time

Revision 482015-12-14 - MikaVesterinen

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

About the HLT

Changed:
<
<
>
>
 
  • HltLine -- Basic Structural Unit of the HLT
  • TCKs -- Trigger Configuration Keys
  • MCTCKs -- How to make an 'MC' version of a TCK
Line: 66 to 66
 
  • MuFromFill: How to find out the value of mu in given data for a given run/fill
  • DataSets: Data sets for trigger studies
  • RawEventJuggler: Moving around the raw event for processing, A description of the framework in place for moving around the raw event.
Deleted:
<
<
  • L0App: Emulating L0 on real or simulated data
 
Line: 86 to 85
 

HLT Monitoring

Changed:
<
<

The BandWidth division

  • Is detailed on this page
>
>

Level-0

  • The bandwidth division Is detailed on this page
 
Changed:
<
<
>
>
 

Trigger performance studies

  • Timing Studies: Checking the impact of increasing the number of Kalman iterations on Hlt execution time

Revision 472015-12-11 - MikaVesterinen

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

Documentation

Added:
>
>
 

The Tesla project

Revision 462015-12-09 - MikaVesterinen

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

Revision 452015-12-09 - SaschaStahl

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

Testing Moore Online

>
>

Testing Moore Online - Performing a timing test

  single node.

Revision 442015-11-29 - MikaVesterinen

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

About the HLT

Added:
>
>
 
  • HltLine -- Basic Structural Unit of the HLT
  • TCKs -- Trigger Configuration Keys
  • MCTCKs -- How to make an 'MC' version of a TCK

Revision 432015-10-22 - MikaVesterinen

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

Documentation

 

The Tesla project

Revision 422015-10-12 - MikaVesterinen

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

Conferences

Revision 412015-09-30 - MikaVesterinen

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

Conferences

Revision 402015-09-24 - MikaVesterinen

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

Information for Hlt Piquets and WG liaisons

Revision 392015-09-09 - PatrickOwen

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

Conferences

Revision 382015-08-25 - ConorFitzpatrick

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

Upgrade Trigger development

 

Old pages

Revision 372015-08-23 - MikaVesterinen

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

The BandWidth division

Changed:
<
<
Is detailed on this page
>
>
 

Trigger performance studies

  • Timing Studies: Checking the impact of increasing the number of Kalman iterations on Hlt execution time

Revision 362015-08-06 - MikaVesterinen

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

Weekly HLT ops meetings

  • On Friday afternoon's at 15:00 in 2-R-30. Listed on indico
>
>

General information

  • We have our weekly HLT operations meeting on Friday afternoon's at 15:00 in 2-R-30. See the indigo listing.
  • List of WG liaisons.
 

Planning

Deleted:
<
<
  • List of WG liaisons (inc trigger) link
 
Deleted:
<
<
 
Changed:
<
<

Information for Hlt Piquets

>
>

Information for Hlt Piquets and WG liaisons

 
Deleted:
<
<
 
  • If you need an emergency release of HltTCK or another package, contact Albert Puig [albertDOTpuigATepflDOTch]
Added:
>
>
 

Conferences

Line: 64 to 62
 
Changed:
<
<

Instructions for WG liaisons

>
>
 

Developing Hlt2 lines with the new Template:

Revision 352015-07-30 - MikaVesterinen

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

Information for Hlt Piquets

Revision 342015-07-23 - MikaVesterinen

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

Instructions for WG liaisons

 

Developing Hlt2 lines with the new Template:

Revision 332015-07-13 - VladimirGligorov

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 21 to 21
 
Added:
>
>
  • If you need an emergency release of HltTCK or another package, contact Albert Puig [albertDOTpuigATepflDOTch]
 

Conferences

Revision 322015-07-13 - VladimirGligorov

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 10 to 10
 
  • On Friday afternoon's at 15:00 in 2-R-30. Listed on indico

Planning

Changed:
<
<
>
>
 

Revision 312015-07-12 - VladimirGligorov

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

Planning

Added:
>
>
 
Added:
>
>

Information for Hlt Piquets

 

Conferences

Line: 41 to 48
 
Added:
>
>
 

Developing Hlt2 lines with the new Template:

Line: 58 to 78
 

The BandWidth division

Is detailed on this page
Deleted:
<
<

Instructions

 

Trigger performance studies

  • Timing Studies: Checking the impact of increasing the number of Kalman iterations on Hlt execution time
  • Hlt2Rates: Rates of Hlt2 lines
  • HltCorrelations: Correlations of L0, Hlt and Stripping lines
Deleted:
<
<
 
Deleted:
<
<

Hlt Piquet Guide

 

Old pages

Added:
>
>
 
META FILEATTACHMENT attachment="LHCb_Split_Trigger_Plot.key.pdf" attr="" comment="" date="1380027116" name="LHCb_Split_Trigger_Plot.key.pdf" path="LHCb_Split_Trigger_Plot.key.pdf" size="19957" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Deferred_Trigger_Plot.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Deferred_Trigger_Plot.key.pdf" path="LHCb_Deferred_Trigger_Plot.key.pdf" size="20230" user="gligorov" version="1"

Revision 292015-06-24 - MikaVesterinen

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

Old pages

Added:
>
>
 

Revision 282015-06-23 - MikaVesterinen

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

HLT Monitoring

Revision 272015-06-09 - MikaVesterinen

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

Testing Moore Online

Added:
>
>
 

HLT Monitoring

Revision 262015-06-07 - RoelAaij

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

Hlt Piquet Guide

Added:
>
>
 

Revision 252015-06-04 - MikaVesterinen

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

Hlt Piquet Guide

Added:
>
>
 

Revision 242015-06-01 - MikaVesterinen

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

Revision 232015-06-01 - VladimirGligorov

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

Conferences

Added:
>
>
 

The Tesla project

Revision 222015-04-23 - VladimirGligorov

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 30 to 30
 
  • whichTCK -- How to find out which TCK was used for a given dataset
  • seeTCK -- How to see if a given TCK exists in the software
  • newTCK -- How to make a new TCK based on an existing one
Deleted:
<
<
 
Line: 83 to 82
 
Added:
>
>
 

Revision 202015-02-23 - MikaVesterinen

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

Developing Hlt2 lines with the new Template:

Added:
>
>
 

Testing Moore Online

Revision 192015-02-11 - RoelAaij

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

Developing Hlt2 lines with the new Template:

 

Testing Moore Online

Revision 182015-02-03 - RoelAaij

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

Testing Moore Online

 

HLT Monitoring

Revision 172015-02-02 - RoelAaij

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

HLT Monitoring

 

The BandWidth division

Is detailed on this page

Revision 162015-01-16 - MikaVesterinen

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

Conferences

Revision 152015-01-07 - MikaVesterinen

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

Planning

Added:
>
>
 
  • List of WG liaisons (inc trigger) link

Conferences

Revision 142014-12-15 - MikaVesterinen

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

LHCb trigger twiki pages

Changed:
<
<
Please choose one of the following links:
>
>

Weekly HLT ops meetings

  • On Friday afternoon's at 15:00 in 2-R-30. Listed on indico

Planning

Conferences

 
Changed:
<
<
>
>

The Tesla project

 
Deleted:
<
<
 
Changed:
<
<

Further information

  • Hlt operations meetings on indico
  • List of WG liaisons (inc trigger) link
>
>

About the HLT

The BandWidth division

Is detailed on this page

Instructions

Trigger performance studies

Hlt Piquet Guide

 
Added:
>
>

Old pages

 
Added:
>
>
 
META FILEATTACHMENT attachment="LHCb_Split_Trigger_Plot.key.pdf" attr="" comment="" date="1380027116" name="LHCb_Split_Trigger_Plot.key.pdf" path="LHCb_Split_Trigger_Plot.key.pdf" size="19957" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Deferred_Trigger_Plot.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Deferred_Trigger_Plot.key.pdf" path="LHCb_Deferred_Trigger_Plot.key.pdf" size="20230" user="gligorov" version="1"

Revision 132014-11-26 - PatrickSKoppenburg

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

Further information

Changed:
<
<
  • Hlt operations meetings on indigo
  • List of WG liasons (inc trigger) link
>
>
  • Hlt operations meetings on indico
  • List of WG liaisons (inc trigger) link
 

Revision 122014-11-08 - MikaVesterinen

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

Further information

  • Hlt operations meetings on indigo
  • List of WG liasons (inc trigger) link
 

META FILEATTACHMENT attachment="LHCb_Split_Trigger_Plot.key.pdf" attr="" comment="" date="1380027116" name="LHCb_Split_Trigger_Plot.key.pdf" path="LHCb_Split_Trigger_Plot.key.pdf" size="19957" user="gligorov" version="1"

Revision 112014-09-24 - VladimirGligorov

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

Revision 102014-02-10 - VladimirGligorov

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 15 to 15
 
META FILEATTACHMENT attachment="LHCb_Split_Trigger_Plot.key.pdf" attr="" comment="" date="1380027116" name="LHCb_Split_Trigger_Plot.key.pdf" path="LHCb_Split_Trigger_Plot.key.pdf" size="19957" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Deferred_Trigger_Plot.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Deferred_Trigger_Plot.key.pdf" path="LHCb_Deferred_Trigger_Plot.key.pdf" size="20230" user="gligorov" version="1"
Deleted:
<
<
META FILEATTACHMENT attachment="LHCb_Upgrade_Trigger_Plot.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Upgrade_Trigger_Plot.key.pdf" path="LHCb_Upgrade_Trigger_Plot.key.pdf" size="20762" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" path="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" size="20504" user="gligorov" version="1"
 
META FILEATTACHMENT attachment="chepPosterNeubert.tar.gzip" attr="" comment="Sources for the poster on HLT Architecture beyond LS1 presented at CHEP2013" date="1381841623" name="chepPosterNeubert.tar.gzip" path="chepPosterNeubert.tar.gzip" size="2799928" user="sneubert" version="1"
META FILEATTACHMENT attachment="LHCb_2012_Deferred_Trigger_Plot.pdf" attr="" comment="" date="1382520336" name="LHCb_2012_Deferred_Trigger_Plot.pdf" path="LHCb_2012_Deferred_Trigger_Plot.pdf" size="19615" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_2012_Deferred_Trigger_Plot.001.png" attr="" comment="" date="1382521526" name="LHCb_2012_Deferred_Trigger_Plot.001.png" path="LHCb_2012_Deferred_Trigger_Plot.001.png" size="92208" user="gligorov" version="1"

Revision 92013-10-23 - SebastianNeubert

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 11 to 11
 
Changed:
<
<
>
>
 
META FILEATTACHMENT attachment="LHCb_Split_Trigger_Plot.key.pdf" attr="" comment="" date="1380027116" name="LHCb_Split_Trigger_Plot.key.pdf" path="LHCb_Split_Trigger_Plot.key.pdf" size="19957" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Deferred_Trigger_Plot.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Deferred_Trigger_Plot.key.pdf" path="LHCb_Deferred_Trigger_Plot.key.pdf" size="20230" user="gligorov" version="1"

Revision 82013-10-23 - VladimirGligorov

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 6 to 6
  Please choose one of the following links:
Added:
>
>
 
Line: 18 to 19
 
META FILEATTACHMENT attachment="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" path="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" size="20504" user="gligorov" version="1"
META FILEATTACHMENT attachment="chepPosterNeubert.tar.gzip" attr="" comment="Sources for the poster on HLT Architecture beyond LS1 presented at CHEP2013" date="1381841623" name="chepPosterNeubert.tar.gzip" path="chepPosterNeubert.tar.gzip" size="2799928" user="sneubert" version="1"
META FILEATTACHMENT attachment="LHCb_2012_Deferred_Trigger_Plot.pdf" attr="" comment="" date="1382520336" name="LHCb_2012_Deferred_Trigger_Plot.pdf" path="LHCb_2012_Deferred_Trigger_Plot.pdf" size="19615" user="gligorov" version="1"
Added:
>
>
META FILEATTACHMENT attachment="LHCb_2012_Deferred_Trigger_Plot.001.png" attr="" comment="" date="1382521526" name="LHCb_2012_Deferred_Trigger_Plot.001.png" path="LHCb_2012_Deferred_Trigger_Plot.001.png" size="92208" user="gligorov" version="1"

Revision 72013-10-23 - VladimirGligorov

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

LHCb trigger twiki pages

Deleted:
<
<
img08b3531ea0bca1106da7e65a6650d882.png
Structure of the LHCb trigger in 2012 datataking, without deferral of L0 events.
imge797f2eee20fb6afddf4370b9075eb33.png
Structure of the LHCb trigger in 2012 datataking, with deferral of L0 events.
 Please choose one of the following links:

Revision 62013-10-23 - VladimirGligorov

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 32 to 32
 
META FILEATTACHMENT attachment="LHCb_Upgrade_Trigger_Plot.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Upgrade_Trigger_Plot.key.pdf" path="LHCb_Upgrade_Trigger_Plot.key.pdf" size="20762" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" path="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" size="20504" user="gligorov" version="1"
META FILEATTACHMENT attachment="chepPosterNeubert.tar.gzip" attr="" comment="Sources for the poster on HLT Architecture beyond LS1 presented at CHEP2013" date="1381841623" name="chepPosterNeubert.tar.gzip" path="chepPosterNeubert.tar.gzip" size="2799928" user="sneubert" version="1"
Added:
>
>
META FILEATTACHMENT attachment="LHCb_2012_Deferred_Trigger_Plot.pdf" attr="" comment="" date="1382520336" name="LHCb_2012_Deferred_Trigger_Plot.pdf" path="LHCb_2012_Deferred_Trigger_Plot.pdf" size="19615" user="gligorov" version="1"

Revision 52013-10-15 - SebastianNeubert

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 25 to 25
 
Added:
>
>
 
META FILEATTACHMENT attachment="LHCb_Split_Trigger_Plot.key.pdf" attr="" comment="" date="1380027116" name="LHCb_Split_Trigger_Plot.key.pdf" path="LHCb_Split_Trigger_Plot.key.pdf" size="19957" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Deferred_Trigger_Plot.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Deferred_Trigger_Plot.key.pdf" path="LHCb_Deferred_Trigger_Plot.key.pdf" size="20230" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Upgrade_Trigger_Plot.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Upgrade_Trigger_Plot.key.pdf" path="LHCb_Upgrade_Trigger_Plot.key.pdf" size="20762" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" path="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" size="20504" user="gligorov" version="1"
Added:
>
>
META FILEATTACHMENT attachment="chepPosterNeubert.tar.gzip" attr="" comment="Sources for the poster on HLT Architecture beyond LS1 presented at CHEP2013" date="1381841623" name="chepPosterNeubert.tar.gzip" path="chepPosterNeubert.tar.gzip" size="2799928" user="sneubert" version="1"

Revision 42013-09-24 - VladimirGligorov

Line: 1 to 1
 
META TOPICPARENT name="LHCbTrigger"
<!-- /ActionTrackerPlugin -->
Line: 24 to 24
 
Added:
>
>
META FILEATTACHMENT attachment="LHCb_Split_Trigger_Plot.key.pdf" attr="" comment="" date="1380027116" name="LHCb_Split_Trigger_Plot.key.pdf" path="LHCb_Split_Trigger_Plot.key.pdf" size="19957" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Deferred_Trigger_Plot.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Deferred_Trigger_Plot.key.pdf" path="LHCb_Deferred_Trigger_Plot.key.pdf" size="20230" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Upgrade_Trigger_Plot.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Upgrade_Trigger_Plot.key.pdf" path="LHCb_Upgrade_Trigger_Plot.key.pdf" size="20762" user="gligorov" version="1"
META FILEATTACHMENT attachment="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" attr="" comment="" date="1380027135" name="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" path="LHCb_Upgrade_Trigger_Plot_WHLTDetails.key.pdf" size="20504" user="gligorov" version="1"

Revision 32013-09-06 - VladimirGligorov

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

LHCb trigger twiki pages

Added:
>
>
img08b3531ea0bca1106da7e65a6650d882.png
Structure of the LHCb trigger in 2012 datataking, without deferral of L0 events.
imge797f2eee20fb6afddf4370b9075eb33.png
Structure of the LHCb trigger in 2012 datataking, with deferral of L0 events.
 Please choose one of the following links:
Added:
>
>
 

Revision 22013-09-03 - MikaVesterinen

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

LHCb trigger twiki pages

Line: 7 to 7
 Please choose one of the following links:
Added:
>
>

Revision 12013-06-10 - ConorFitzpatrick

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

LHCb trigger twiki pages

Please choose one of the following links:

 
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