Difference: TriggerTisTos (1 vs. 52)

Revision 522012-04-19 - TomaszSkwarnicki

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

TriggerTisTos tool

Changed:
<
<
Some parts of documentation below is not up to date and will be improved. Please see presentation at Trigger & Stripping meeting on Nov 1, 2010 for the most recent report on TisTos software. If you are using Stripping MicroDSTs please also read StrippingMDSTsTisTos page.
>
>
Some parts of documentation below are not up to date. Please see presentation at Trigger & Stripping meeting on Nov 1, 2010 for the most recent report on TisTos software. If you are using Stripping MicroDSTs please also read StrippingMDSTsTisTos page.
  TriggerTisTos tool classifies triggers (L0 or Hlt) as TIS (Trigger Independent of Signal) or TOS (Trigger On Signal) with respect to user defined signal (e.g. B candidate).

Revision 512011-11-04 - TomaszSkwarnicki

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

TriggerTisTos tool

Some parts of documentation below is not up to date and will be improved. Please see presentation at Trigger & Stripping meeting on Nov 1, 2010 for the most recent

Changed:
<
<
report on TisTos software. If you are using Stripping MicroDSTs please also read StrippingDSTsTisTos page.
>
>
report on TisTos software. If you are using Stripping MicroDSTs please also read StrippingMDSTsTisTos page.
  TriggerTisTos tool classifies triggers (L0 or Hlt) as TIS (Trigger Independent of Signal) or TOS (Trigger On Signal) with respect to user defined signal (e.g. B candidate).

Revision 502011-11-01 - TomaszSkwarnicki

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

TriggerTisTos tool

Some parts of documentation below is not up to date and will be improved. Please see presentation at Trigger & Stripping meeting on Nov 1, 2010 for the most recent

Changed:
<
<
report on TisTos software. If you are using Stripping12 MicroDSTs please also read MicroDSTTisTos page.
>
>
report on TisTos software. If you are using Stripping MicroDSTs please also read StrippingDSTsTisTos page.
  TriggerTisTos tool classifies triggers (L0 or Hlt) as TIS (Trigger Independent of Signal) or TOS (Trigger On Signal) with respect to user defined signal (e.g. B candidate).
Line: 48 to 48
 

Comments to various DaVinci releases

Added:
>
>
  • DaVinci v29r0,v29r1

New set-up is needed for Stripping 17 MDSTs - see StrippingMDSTsTisTos page.

 
  • DaVinci v28r2p2 and similar

New 2011 DiMuon trigger is not yet supported in these releases. "getpack Phys/TisTosTobbing r122889" to make it work.

Line: 122 to 126
 DaVinci().HltType = 'Hlt1+Hlt2' ## pick one of 'Hlt1', 'Hlt2', or 'Hlt1+Hlt2'
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, last update 5 May 2011
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, last update 1 Nov 2011
 \ No newline at end of file

Revision 492011-05-05 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 48 to 48
 

Comments to various DaVinci releases

Added:
>
>
  • DaVinci v28r2p2 and similar

New 2011 DiMuon trigger is not yet supported in these releases. "getpack Phys/TisTosTobbing r122889" to make it work.

 
  • DaVinci v26r3p2

No known problems.

Line: 118 to 122
 DaVinci().HltType = 'Hlt1+Hlt2' ## pick one of 'Hlt1', 'Hlt2', or 'Hlt1+Hlt2'
Changed:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, last update 1 Dec 2010
>
>
-- TomaszSkwarnicki - 11 Oct 2007, last update 5 May 2011
 \ No newline at end of file

Revision 482010-12-01 - TomaszSkwarnicki

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

TriggerTisTos tool

Deleted:
<
<
Up to date information can be found in the recent presentation at Trigger & Stripping meeting on Nov 1, 2010.
 Some parts of documentation below is not up to date and will be improved.
Added:
>
>
Please see presentation at Trigger & Stripping meeting on Nov 1, 2010 for the most recent report on TisTos software. If you are using Stripping12 MicroDSTs please also read MicroDSTTisTos page.
  TriggerTisTos tool classifies triggers (L0 or Hlt) as TIS (Trigger Independent of Signal) or TOS (Trigger On Signal) with respect to user defined signal (e.g. B candidate).
Line: 37 to 37
 
Changed:
<
<
>
>

Links to related pages

 

Comments to various DaVinci releases

Added:
>
>
  • DaVinci v26r3p2

No known problems.

 
  • DaVinci v26r3
Changed:
<
<
Contains support for TisTossing schemes on MDSTs. Slight change in L0 TisTos of Muon triggers (use Trig/L0/MuonBCSU instead of Trig/L0/MuonCtrl).
>
>
Contains support for TisTossing schemes on MDSTs. Slight change in L0 TisTos of Muon triggers (use Trig/L0/MuonBCSU instead of Trig/L0/MuonCtrl).
 Fixes the bugs outlined below. However, it does contain bug for L0 trigger - see L0TriggerTisTos twiki.
Line: 109 to 118
 DaVinci().HltType = 'Hlt1+Hlt2' ## pick one of 'Hlt1', 'Hlt2', or 'Hlt1+Hlt2'
Deleted:
<
<

Links to related pages

-- TomaszSkwarnicki - 11 Oct 2007, last update 19 Nov 2010

 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, last update 1 Dec 2010

Revision 472010-11-18 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 48 to 48
 Contains support for TisTossing schemes on MDSTs. Slight change in L0 TisTos of Muon triggers (use Trig/L0/MuonBCSU instead of Trig/L0/MuonCtrl). Fixes the bugs outlined below.
Added:
>
>
However, it does contain bug for L0 trigger - see L0TriggerTisTos twiki.
 
  • DaVinci v26r1,r2,r2p1
Line: 115 to 116
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, last update 11 Nov 2010
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, last update 19 Nov 2010
 \ No newline at end of file

Revision 462010-11-11 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 110 to 110
 

Links to related pages

Changed:
<
<
>
>
 
Changed:
<
<
>
>
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, last update 1 Nov 2010
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, last update 11 Nov 2010
 \ No newline at end of file

Revision 452010-11-10 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 47 to 47
  Contains support for TisTossing schemes on MDSTs. Slight change in L0 TisTos of Muon triggers (use Trig/L0/MuonBCSU instead of Trig/L0/MuonCtrl).
Changed:
<
<
Fixes the bug outlined below.
>
>
Fixes the bugs outlined below.
 
  • DaVinci v26r1,r2,r2p1
Changed:
<
<
Results for "Hlt1.*Decision" wrong for most of 2010 data because of Hlt1L0.*Muon.*Decision (applies to all previous versions too).
>
>
Results for "Hlt1.*Decision" wrong for most of 2010 data because of Hlt1L0.*Muon.*Decision (applies to all previous versions too).
 See slide 19 in presentation at Trigger & Stripping meeting on Nov 1, 2010.
Added:
>
>
If you re-run L0+HLT triggers (using 1Track Hlt1 scheme) in DaVinci you must add:
        from Configurables import L0Conf
        L0Conf().FullL0MuonDecoding = True
        L0Conf().EnableL0DecodingOnDemand = True
otherwise your results for muons will be inaccurate and for hadrons completely wrong.
 
  • DaVinci v25r7

Revision 432010-11-01 - TomaszSkwarnicki

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

TriggerTisTos tool

Added:
>
>
Up to date information can be found in the recent presentation at Trigger & Stripping meeting on Nov 1, 2010. Some parts of documentation below is not up to date and will be improved.
 TriggerTisTos tool classifies triggers (L0 or Hlt) as TIS (Trigger Independent of Signal) or TOS (Trigger On Signal) with respect to user defined signal (e.g. B candidate). It can also be used to access summaries of candidates selected by the Trigger algorithms and saved in Raw Data.
Line: 23 to 27
  See Doxygen documentation of the DaVinci project. Make sure to follow link also to ITriggerSelectionTisTos from which ITriggerTisTos inherits.
  • More extensive documentation with code examples can be found in various presentations (use the first one listed for the most recent one, though even this version is a bit obsolete):
Added:
>
>
 
Line: 37 to 42
 

Comments to various DaVinci releases

Added:
>
>
  • DaVinci v26r3

Contains support for TisTossing schemes on MDSTs. Slight change in L0 TisTos of Muon triggers (use Trig/L0/MuonBCSU instead of Trig/L0/MuonCtrl). Fixes the bug outlined below.

  • DaVinci v26r1,r2,r2p1

Results for "Hlt1.*Decision" wrong for most of 2010 data because of Hlt1L0.*Muon.*Decision (applies to all previous versions too). See slide 19 in presentation at Trigger & Stripping meeting on Nov 1, 2010.

 
  • DaVinci v25r7

Major rewrite of the code (Phys/TisTosTobbing v5r0; Phys/DaVinciInterfaces v2r5).

Line: 95 to 112
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, last update 24 June 2010
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, last update 1 Nov 2010

Revision 422010-08-04 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 37 to 37
 

Comments to various DaVinci releases

Changed:
<
<
  • DaVinci HEAD in nightlies since 20100722:
>
>
  • DaVinci v25r7
 
Changed:
<
<
Major rewrite of the code (to be v5r0, at present tskwarni_20100721; use together with Phys/DaVinciInterfaces of the same tag).
>
>
Major rewrite of the code (Phys/TisTosTobbing v5r0; Phys/DaVinciInterfaces v2r5).
 More information will be provided. matchedTOSxxx methods were retired from the interface. Muon hit TOS threshold lowered from 0.7 to 0.6.
Changed:
<
<
A lots of new methods to provide new functionality (the old methods will still work as well).
>
>
A lots of new methods to provide new functionality (the old methods will still work as well). See also TisTosParticleTagger.
 
  • DaVinci v25r6

Revision 412010-07-24 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 14 to 14
  If you are interested in Tis/Tossing L0 trigger, please refer to L0TriggerTisTos twiki.
Added:
>
>
There in now TisTosParticleTagger which can be used to set-up filtering of Particles with respect to TisTos criteria, or to filter Events. Please refer to separate page for documentation.
 

Documentation

  • The user interface of the tool is defined in ITriggerTisTos.h which contains also some documentation.

Revision 402010-07-21 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 19 to 19
 
  • The user interface of the tool is defined in ITriggerTisTos.h which contains also some documentation. See Doxygen documentation of the DaVinci project. Make sure to follow link also to ITriggerSelectionTisTos from which ITriggerTisTos inherits.
Changed:
<
<
  • More extensive documentation with code examples can be found in various presentations (use the first one listed for the most recent one):
>
>
  • More extensive documentation with code examples can be found in various presentations (use the first one listed for the most recent one, though even this version is a bit obsolete):
 
Line: 34 to 34
 

Comments to various DaVinci releases

Added:
>
>
  • DaVinci HEAD in nightlies since 20100722:
 
Added:
>
>
Major rewrite of the code (to be v5r0, at present tskwarni_20100721; use together with Phys/DaVinciInterfaces of the same tag). More information will be provided. matchedTOSxxx methods were retired from the interface. Muon hit TOS threshold lowered from 0.7 to 0.6. A lots of new methods to provide new functionality (the old methods will still work as well).

  • DaVinci v25r6

No known problems. This version includes L0TriggerTisTos tool.

 
  • DaVinci v25r5.

Revision 392010-06-24 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 8 to 8
  There is also TESTisTos tool which can be used to classify selections saved in TES, stripping decision in particular.
Added:
>
>
If you are using TupleToolTISTOS for your Tis/Tos info, you may want to read How Do I configure TupleToolTrigger and TupleToolTISTOS? page. TupleToolTISTOS in DecayTreeTuple is an additional layer of software which calls TriggerTisTos tool described here.

If you are interested in Tis/Tossing L0 trigger, please refer to L0TriggerTisTos twiki.

 

Documentation

  • The user interface of the tool is defined in ITriggerTisTos.h which contains also some documentation. See Doxygen documentation of the DaVinci project. Make sure to follow link also to ITriggerSelectionTisTos from which ITriggerTisTos inherits.
Changed:
<
<
  • More extensive documentation with code examples can be found in various presentations:
>
>
  • More extensive documentation with code examples can be found in various presentations (use the first one listed for the most recent one):
 
Line: 28 to 34
 

Comments to various DaVinci releases

Added:
>
>

  • DaVinci v25r5.

No known problems. However, this and all earlier versions do not let you Tis/Tos L0 trigger to good accuracy (particularly L0DiMuon is affected). Please refer to L0TriggerTisTos info.

 
  • DaVinci v24r5p1

No known problems.

Line: 60 to 74
 

Links to related pages

Added:
>
>
 
Line: 69 to 84
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, last update 19 Oct 2009
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, last update 24 June 2010

Revision 382009-12-05 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 6 to 6
 with respect to user defined signal (e.g. B candidate). It can also be used to access summaries of candidates selected by the Trigger algorithms and saved in Raw Data.
Added:
>
>
There is also TESTisTos tool which can be used to classify selections saved in TES, stripping decision in particular.
 

Documentation

  • The user interface of the tool is defined in ITriggerTisTos.h which contains also some documentation.
Line: 24 to 26
 
Changed:
<
<

Warnings for users

>
>

Comments to various DaVinci releases

 
  • DaVinci v24r5p1

Revision 372009-12-03 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 26 to 26
 

Warnings for users

Added:
>
>
  • DaVinci v24r5p1

No known problems.

 
  • DaVinci v24r4

To work on slc5 platform you need to getpack Phys/TisTosTobbing v3r6 or higher (get a head version if this tag is not available yet) otherwise jobs can sometimes crash on the first event processed by the tool. slc4 platform appears to be fine.

Revision 362009-11-05 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 28 to 28
 
  • DaVinci v24r4
Changed:
<
<
No known problems.
>
>
To work on slc5 platform you need to getpack Phys/TisTosTobbing v3r6 or higher (get a head version if this tag is not available yet) otherwise jobs can sometimes crash on the first event processed by the tool. slc4 platform appears to be fine.
  There was a change in the tool catalog of known trigger names. In the previous version all names registered with HltANNSvc were considered valid trigger names, which in practice meant that there were a lot of spurious triggers in Hlt1 part. Now the trigger names are restricted to those appearing in HltDecReports which ensures that only executed triggers are known to the tool. Intermediate trigger selection names are restricted to those saved in HltSelReports. A consequence of these changes is that the list of known trigger names can vary from MC event to MC event (e.g. if L0 failed and Hlt was not excuted, there will be no known trigger names). Real data event all passed Hlt, thus the trigger list will not vary for the same TCK, however list of intermediate selection names can still vary from event to event depending which ones were saved in HltSelReports. The tool no longer complains if the user asked for a trigger selection which is not found (the warning can be reactivated via a property of the tool); the tool will silently return default values (decision=false; tis=false; tos=false).

Revision 352009-11-04 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 26 to 26
 

Warnings for users

Added:
>
>
  • DaVinci v24r4

No known problems.

There was a change in the tool catalog of known trigger names. In the previous version all names registered with HltANNSvc were considered valid trigger names, which in practice meant that there were a lot of spurious triggers in Hlt1 part. Now the trigger names are restricted to those appearing in HltDecReports which ensures that only executed triggers are known to the tool. Intermediate trigger selection names are restricted to those saved in HltSelReports. A consequence of these changes is that the list of known trigger names can vary from MC event to MC event (e.g. if L0 failed and Hlt was not excuted, there will be no known trigger names). Real data event all passed Hlt, thus the trigger list will not vary for the same TCK, however list of intermediate selection names can still vary from event to event depending which ones were saved in HltSelReports. The tool no longer complains if the user asked for a trigger selection which is not found (the warning can be reactivated via a property of the tool); the tool will silently return default values (decision=false; tis=false; tos=false).

 
  • DaVinci v24r3p1, v24r2p2

Revision 332009-10-20 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 27 to 27
 

Warnings for users

Changed:
<
<
  • DaVinci v24r3p2
>
>
  • DaVinci v24r3p1, v24r2p2
 
Changed:
<
<
No known problems.

  • DaVinci v24r3p1

Do not use this version. There are problems in Calo code in this version which cause crashes sometimes in Tis/Tos software.

>
>
Do not use these version. There are problems in Calo code which cause crashes sometimes in Tis/Tos software.
 
  • DaVinci v24r2

Revision 322009-10-19 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 26 to 26
 

Warnings for users

Added:
>
>
  • DaVinci v24r3p2

No known problems.

 
  • DaVinci v24r3p1
Changed:
<
<
There are problems when using TupleToolTISTOS in DecayTreeTuple (jobs occasionally crash). This is not undertood yet.
>
>
Do not use this version. There are problems in Calo code in this version which cause crashes sometimes in Tis/Tos software.
 
  • DaVinci v24r2
Line: 56 to 61
 
Changed:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, last update 13 Oct 2009
>
>
-- TomaszSkwarnicki - 11 Oct 2007, last update 19 Oct 2009
 \ No newline at end of file

Revision 312009-10-13 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 26 to 26
 

Warnings for users

Added:
>
>
  • DaVinci v24r3p1

There are problems when using TupleToolTISTOS in DecayTreeTuple (jobs occasionally crash). This is not undertood yet.

 
  • DaVinci v24r2

IMPORTANT! From this version now on, wild character matching in the trigger specifications passed to the tool is handled by regex (see e.g. Regular Expression Tutorial). This provides for more functionality. Users must change their code to replace any occurrence of '*' by '.*' (for example 'Hlt1*Decision' must be replaced by 'Hlt1.*Decision').

Line: 52 to 56
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, last update 9 Sep 2009
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, last update 13 Oct 2009

Revision 302009-10-02 - PatrickSKoppenburg

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

TriggerTisTos tool

Line: 41 to 41
 DaVinci().HltType = 'Hlt1+Hlt2' ## pick one of 'Hlt1', 'Hlt2', or 'Hlt1+Hlt2'
Deleted:
<
<
  • DaVinci v22r0p2

This re-release of v22r0 includes TisTosTobbing v3r2 and properly fixed TupleToolTISTOS. Re-running of MuonID for DC06 data is integraded into DaVinci() configurable, therefore users will no longer need to do it by themselves. Do not Tis/Tos Hl1Global, Hlt2Global in this version - use Hlt1*Decision and Hlt2*Decision instead.

  • All versions prior to DaVinci v22r0p2

When you analyze older DC06 DSTs in versions v22r0 and eariler you need to rerun MuonID in DaVinci for proper TisTossing of muon triggers . The tool will issue warnings ("No offline muon tracks at Rec/Track/Muon thus, muon hits will be ignored on trigger tracks.") but it will not crush if you don’t (results for Hlt1 and Hlt2 triggers will be reasonable, but not for L0 triggers). See Rerunning MuonID in DaVinci for more info.

  • DaVinci v22r0

You must getpack Phys/TisTosTobbing v3r2 and compile it in your area, otherwise tis/tos results for Hlt1*Decision will be wrong (no problems with Hlt2). This will also allow you to tis/tos L0 trigger decisions again, however, calling sequence is different than before and using L0*Decision no longer works.

I have updated python code example to illustrate how to tis/tos L0 trigger in this version. C++ code example is still old and needs updating.

If you are relying on TupleToolTISTOS, you will need to get the TupleToolTISTOS.cpp from head version of DecayTreeTuple, while keeping the rest of this library the same as in the official release.

Options to run trigger simulations on DC06 data:

from Gaudi.Configuration import *
from Configurables import DaVinci
DaVinci().ReplaceL0BanksWithEmulated = True ## enable if you want to rerun L0
#DaVinci().Hlt2IgnoreHlt1Decision = True    ## enable if you want Hlt2 irrespective of Hlt1
DaVinci().HltType = 'Hlt1+Hlt2'             ## pick one of 'Hlt1', 'Hlt2', or 'Hlt1+Hlt2'

See also the following posting about the bug related to ReplaceL0BanksWithEmulated option.

> -----Original Message-----
> From: Patrick Koppenburg [mailto:Patrick.Koppenburg@cern.ch]
> Sent: Tuesday, February 10, 2009 8:23 AM
> To: lhcb-davinci
> Subject: L0 trouble in DaVinci v22r0p2
> 
> Hi all,
> 
> Yesterday at t-rec Leandro reported about problems when re-running L0 in
> DaVinci v22r0p2. i.e. with
> 
> DaVinci().ReplaceL0BanksWithEmulated = True    # Redo L0
> 
> The symptom is that L0 actually runs after Hlt, which is nonsense of
> course and makes the Hlt1 decision incorrect.
> The problem is being investigated and so far we have a patch that works.
> At then of options add this:
> 
> def doMyChanges():
>     topalg = ApplicationMgr().TopAlg
>     topalg.remove("GaudiSequencer/L0DUBankSwap")
>     topalg.insert(1,"GaudiSequencer/L0DUBankSwap")
>     ApplicationMgr().TopAlg = topalg
> 
> appendPostConfigAction(doMyChanges)
> 
> this will put L0 at the beginning of TopAlgs instead of the end. Note
> that if you do not re-run L0 then it might cause an error. Sorry about
> the trouble. Please report any problem.
> 
> Cheers
> 
> Patrick
>

  • DaVinci v21r0

No way to TIS/TOS L0 trigger decision in this version (some L0XXXDecision still exist, but some are missing).

Options to run trigger simulations on DC06 data - same as in v20r3.

Three major changes: * ITriggerTisTos interface has changed. Users must eliminate ITriggerTisTos::kAllTriggers option in all calls to the tool. * Default tool now uses HltSelReports (persistent info). * New methods available which let users access HltObjectSummaries of candidates selected by trigger algorithms and saved in the Raw Data.

See Hlt Data and Usage, Dec. 11, 2008, LHCb Software Week for more information.

  • DaVinci v20r3

No major problems, but you must use Phys/TisTosTobbing v2r8 to protect yourself against crushes at DaVinci finalization.

Options to run trigger simulations on DC06 data:

from HltConf.Configuration import *
HltConf().replaceL0BanksWithEmulated = True
HltConf().hltType = 'Hlt1+Hlt2'
HltConf().applyConf()

  • DaVinci v20r2

No major problems, but you must use Phys/TisTosTobbing v2r8 to protect yourself against crushes at DaVinci finalization.

Options to run trigger simulations on DC06 data:

#include "$L0DUROOT/options/ReplaceL0DUBankWithEmulated.opts"
#include "$HLTCONFROOT/options/Hlt1.opts"
#include "$HLTCONFROOT/options/Hlt2.opts"

  • DaVinci v20r1

No major problems, but you must use Phys/TisTosTobbing v2r8 to protect yourself against crushes at DaVinci finalization.

Options to run trigger simulations on DC06 data:

#include "$L0DUROOT/options/L0DUBankSwap.opts"
#include "$L0DUROOT/options/DefaultTCK.opts"
#include "$HLTSYSROOT/options/Hlt1.opts"
#include "$HLTSYSROOT/options/Hlt2.opts"

  • DaVinci v20r0

No major problems, but you must use Phys/TisTosTobbing v2r8 to protect yourself against crushes at DaVinci finalization.

New Hlt1PhotonDiTrackDecision trigger is missing from $HLTSYSROOT/HltInit.opts. If you care about this trigger use your own version of HltInit.opts in which this entry has been added.

The trigger names have changed (already in DaVinci v19r14). Rename all L0TriggerXXX to L0XXXDecision (use “L0*Decision” for global L0 decision). Hlt2 triggers now have names Hlt2SelXXXDecision (use “Hlt2*Decision” for global Hlt2 decision). Hlt1 triggers also follow Hlt1XXXDecision pattern but “*” will still work if kAlleyExitsOnly flag is set (default!).

Options to run trigger simulations on DC06 data:

#include "$L0DUROOT/options/L0DUBankSwap.opts"
#include "$L0DUROOT/options/DefaultTCK.opts"
#include "$HLTSYSROOT/options/HltInit.opts"
#include "$HLTSYSROOT/options/Hlt1.opts"
#include "$HLTSYSROOT/options/Hlt2.opts"

  • DaVinci v19r14

Do not use this version because of crushes in calo code.

  • DaVinci v19r13

There are many problems with the tool functionality in DaVinci v19r13. To fix this release you must use Phys/TisTosTobbing v2r5 (e.g. do starting in your DaVinci_v19r13/ area: getpack Phys/TisTosTobbing v2r5; cd Phys/TisTosTobbing; mv v2r5 v2r4; cd v2r4/cmt; cmt config; gmake).

Options to run trigger simulations on DC06 data:

#include "$HLTSYSROOT/options/L0.opts"
#include "$HLTSYSROOT/options/HltInit.opts"
#include "$HLTSYSROOT/options/Hlt1.opts"
#include "$HLTSYSROOT/options/Hlt2.opts"

  • DaVinci v19r10 – v19r12

There was a problem with TisTossing L0 Muon triggers when LHCb::Track was passed as signal in all version before DaVinci v19r13. Passing Track is not a standard approach and therefore normal users should not worry about this (no problem when passing signal as LHCb::Particle).

  • DaVinci v19r9

In DaVinci v19r9 alley exit selections and L0 triggers are not recognized properly and therefore use of wild character in specifying triggers may lead to wrong results (using explicit lists of triggers works fine). This problem was fixed in DaVinci v19r10.

  • DaVinci v19v5-v19r8

No known problems, but no or limited python support.

  • DaVinci v19r4

See special instructions for use with DaVinci v19r4. The tool is not compatibile with the earlier DaVinci versions.

 

Links to related pages

Revision 292009-09-10 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 26 to 26
 

Warnings for users

Changed:
<
<
  • DaVinci v22r1, v22r2, v22r3, v23r0p, v23r1
>
>
  • DaVinci v24r2

IMPORTANT! From this version now on, wild character matching in the trigger specifications passed to the tool is handled by regex (see e.g. Regular Expression Tutorial). This provides for more functionality. Users must change their code to replace any occurrence of '*' by '.*' (for example 'Hlt1*Decision' must be replaced by 'Hlt1.*Decision').

  • DaVinci v22r1, v22r2, v22r3, v23r0p, v23r1, v24r1
  No known problems. Options to run trigger simulations on DC06 data:
Line: 228 to 232
 
Changed:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, last update 11 Jun 2009
>
>
-- TomaszSkwarnicki - 11 Oct 2007, last update 9 Sep 2009

Revision 282009-06-12 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 12 to 12
  See Doxygen documentation of the DaVinci project. Make sure to follow link also to ITriggerSelectionTisTos from which ITriggerTisTos inherits.
  • More extensive documentation with code examples can be found in various presentations:
Added:
>
>
 
Line: 25 to 26
 

Warnings for users

Changed:
<
<
  • DaVinci v22r1, v22r2, v22r3
>
>
  • DaVinci v22r1, v22r2, v22r3, v23r0p, v23r1
  No known problems. Options to run trigger simulations on DC06 data:
Line: 227 to 228
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, last update 19 Mar 2009
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, last update 11 Jun 2009

Revision 272009-04-17 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 25 to 25
 

Warnings for users

Changed:
<
<
  • DaVinci v22r1
>
>
  • DaVinci v22r1, v22r2, v22r3
  No known problems. Options to run trigger simulations on DC06 data:

Revision 262009-04-13 - StephanNies

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

TriggerTisTos tool

Revision 252009-03-19 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 12 to 12
  See Doxygen documentation of the DaVinci project. Make sure to follow link also to ITriggerSelectionTisTos from which ITriggerTisTos inherits.
  • More extensive documentation with code examples can be found in various presentations:
Added:
>
>
 
Line: 24 to 25
 

Warnings for users

Added:
>
>
  • DaVinci v22r1

No known problems. Options to run trigger simulations on DC06 data:

from Gaudi.Configuration import *
from Configurables import DaVinci
DaVinci().ReplaceL0BanksWithEmulated = True ## enable if you want to rerun L0
DaVinci().HltType = 'Hlt1+Hlt2'             ## pick one of 'Hlt1', 'Hlt2', or 'Hlt1+Hlt2'
 
  • DaVinci v22r0p2

This re-release of v22r0 includes TisTosTobbing v3r2 and properly fixed TupleToolTISTOS.

Line: 214 to 227
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, last update 29 Jan 2009
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, last update 19 Mar 2009

Revision 242009-02-19 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 57 to 57
 DaVinci().HltType = 'Hlt1+Hlt2' ## pick one of 'Hlt1', 'Hlt2', or 'Hlt1+Hlt2'
Added:
>
>
See also the following posting about the bug related to ReplaceL0BanksWithEmulated option.
> -----Original Message-----
> From: Patrick Koppenburg [mailto:Patrick.Koppenburg@cern.ch]
> Sent: Tuesday, February 10, 2009 8:23 AM
> To: lhcb-davinci
> Subject: L0 trouble in DaVinci v22r0p2
> 
> Hi all,
> 
> Yesterday at t-rec Leandro reported about problems when re-running L0 in
> DaVinci v22r0p2. i.e. with
> 
> DaVinci().ReplaceL0BanksWithEmulated = True    # Redo L0
> 
> The symptom is that L0 actually runs after Hlt, which is nonsense of
> course and makes the Hlt1 decision incorrect.
> The problem is being investigated and so far we have a patch that works.
> At then of options add this:
> 
> def doMyChanges():
>     topalg = ApplicationMgr().TopAlg
>     topalg.remove("GaudiSequencer/L0DUBankSwap")
>     topalg.insert(1,"GaudiSequencer/L0DUBankSwap")
>     ApplicationMgr().TopAlg = topalg
> 
> appendPostConfigAction(doMyChanges)
> 
> this will put L0 at the beginning of TopAlgs instead of the end. Note
> that if you do not re-run L0 then it might cause an error. Sorry about
> the trouble. Please report any problem.
> 
> Cheers
> 
> Patrick
>

 
  • DaVinci v21r0

No way to TIS/TOS L0 trigger decision in this version (some L0XXXDecision still exist, but some are missing).

Revision 232009-01-29 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 24 to 24
 

Warnings for users

Changed:
<
<
  • DaVinci v22r0p2 (in preparation)
>
>
  • DaVinci v22r0p2
 
Changed:
<
<
This re-release of v22r0 includes TisTosTobbing v3r2.
>
>
This re-release of v22r0 includes TisTosTobbing v3r2 and properly fixed TupleToolTISTOS.
 Re-running of MuonID for DC06 data is integraded into DaVinci() configurable, therefore users will no longer need to do it by themselves. Do not Tis/Tos Hl1Global, Hlt2Global in this version - use Hlt1*Decision and Hlt2*Decision instead.

  • All versions prior to DaVinci v22r0p2
Changed:
<
<
When you analyze older DC06 DSTs (often the case) you need to rerun MuonID in DaVinci for proper TisTossing of muon triggers .
>
>
When you analyze older DC06 DSTs in versions v22r0 and eariler you need to rerun MuonID in DaVinci for proper TisTossing of muon triggers .
 The tool will issue warnings ("No offline muon tracks at Rec/Track/Muon thus, muon hits will be ignored on trigger tracks.") but it will not crush if you don’t (results for Hlt1 and Hlt2 triggers will be reasonable, but not for L0 triggers). See Rerunning MuonID in DaVinci for more info.
Line: 175 to 175
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008, 15 July 2008, 8 Aug 2008, 31 Aug 2008, 15 Sep 2008, 30 Oct 2008, 20 Jan 2009
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, last update 29 Jan 2009
 \ No newline at end of file

Revision 222009-01-26 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 24 to 24
 

Warnings for users

Changed:
<
<
  • All versions
>
>
  • DaVinci v22r0p2 (in preparation)

This re-release of v22r0 includes TisTosTobbing v3r2. Re-running of MuonID for DC06 data is integraded into DaVinci() configurable, therefore users will no longer need to do it by themselves. Do not Tis/Tos Hl1Global, Hlt2Global in this version - use Hlt1*Decision and Hlt2*Decision instead.

  • All versions prior to DaVinci v22r0p2
  When you analyze older DC06 DSTs (often the case) you need to rerun MuonID in DaVinci for proper TisTossing of muon triggers . The tool will issue warnings ("No offline muon tracks at Rec/Track/Muon thus, muon hits will be ignored on trigger tracks.")

Revision 212009-01-20 - TomaszSkwarnicki

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

TriggerTisTos tool

TriggerTisTos tool classifies triggers (L0 or Hlt) as TIS (Trigger Independent of Signal) or TOS (Trigger On Signal) with respect to user defined signal (e.g. B candidate).

Added:
>
>
It can also be used to access summaries of candidates selected by the Trigger algorithms and saved in Raw Data.
 

Documentation

Line: 11 to 12
  See Doxygen documentation of the DaVinci project. Make sure to follow link also to ITriggerSelectionTisTos from which ITriggerTisTos inherits.
  • More extensive documentation with code examples can be found in various presentations:
Added:
>
>
 
Line: 29 to 31
 but it will not crush if you don’t (results for Hlt1 and Hlt2 triggers will be reasonable, but not for L0 triggers). See Rerunning MuonID in DaVinci for more info.
Changed:
<
<
There was a problem with TisTossing L0 Muon triggers when LHCb::Track was passed as signal in all version before DaVinci v19r13. Passing Track is not a standard approach and therefore normal users should not worry about this (no problem when passing signal as LHCb::Particle).
>
>
  • DaVinci v22r0

You must getpack Phys/TisTosTobbing v3r2 and compile it in your area, otherwise tis/tos results for Hlt1*Decision will be wrong (no problems with Hlt2). This will also allow you to tis/tos L0 trigger decisions again, however, calling sequence is different than before and using L0*Decision no longer works.

I have updated python code example to illustrate how to tis/tos L0 trigger in this version. C++ code example is still old and needs updating.

If you are relying on TupleToolTISTOS, you will need to get the TupleToolTISTOS.cpp from head version of DecayTreeTuple, while keeping the rest of this library the same as in the official release.

Options to run trigger simulations on DC06 data:

from Gaudi.Configuration import *
from Configurables import DaVinci
DaVinci().ReplaceL0BanksWithEmulated = True ## enable if you want to rerun L0
#DaVinci().Hlt2IgnoreHlt1Decision = True    ## enable if you want Hlt2 irrespective of Hlt1
DaVinci().HltType = 'Hlt1+Hlt2'             ## pick one of 'Hlt1', 'Hlt2', or 'Hlt1+Hlt2'

  • DaVinci v21r0
 
Changed:
<
<
  • DaVinci v20r4 (in development)
>
>
No way to TIS/TOS L0 trigger decision in this version (some L0XXXDecision still exist, but some are missing).
 
Changed:
<
<
Two major changes: 1) ITriggerTisTos interface has changed. Users must eliminate ITriggerTisTos::kAllTriggers option in all calls to the tool. 2) Default tool now uses HltSelReports (persistent info). Old tool version still available as TriggerTisTosHS, but it will eliminated soon. More details about the changes will posted later.
>
>
Options to run trigger simulations on DC06 data - same as in v20r3.

Three major changes: * ITriggerTisTos interface has changed. Users must eliminate ITriggerTisTos::kAllTriggers option in all calls to the tool. * Default tool now uses HltSelReports (persistent info). * New methods available which let users access HltObjectSummaries of candidates selected by trigger algorithms and saved in the Raw Data.

See Hlt Data and Usage, Dec. 11, 2008, LHCb Software Week for more information.

 
  • DaVinci v20r3
Line: 112 to 141
 
  • DaVinci v19r10 – v19r12
Changed:
<
<
No known problems.
>
>
There was a problem with TisTossing L0 Muon triggers when LHCb::Track was passed as signal in all version before DaVinci v19r13. Passing Track is not a standard approach and therefore normal users should not worry about this (no problem when passing signal as LHCb::Particle).
 
  • DaVinci v19r9
Line: 140 to 169
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008, 15 July 2008, 8 Aug 2008, 31 Aug 2008, 15 Sep 2008, 30 Oct 2008
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008, 15 July 2008, 8 Aug 2008, 31 Aug 2008, 15 Sep 2008, 30 Oct 2008, 20 Jan 2009

Revision 202008-11-14 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 31 to 31
  There was a problem with TisTossing L0 Muon triggers when LHCb::Track was passed as signal in all version before DaVinci v19r13. Passing Track is not a standard approach and therefore normal users should not worry about this (no problem when passing signal as LHCb::Particle).
Added:
>
>
  • DaVinci v20r4 (in development)

Two major changes: 1) ITriggerTisTos interface has changed. Users must eliminate ITriggerTisTos::kAllTriggers option in all calls to the tool. 2) Default tool now uses HltSelReports (persistent info). Old tool version still available as TriggerTisTosHS, but it will eliminated soon. More details about the changes will posted later.

 
  • DaVinci v20r3

No major problems, but you must use Phys/TisTosTobbing v2r8 to protect yourself against crushes at DaVinci finalization.

Revision 192008-11-03 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 11 to 11
  See Doxygen documentation of the DaVinci project. Make sure to follow link also to ITriggerSelectionTisTos from which ITriggerTisTos inherits.
  • More extensive documentation with code examples can be found in various presentations:
Changed:
<
<
>
>
 

Revision 182008-10-30 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 33 to 33
 
  • DaVinci v20r3
Changed:
<
<
No known problems.
>
>
No major problems, but you must use Phys/TisTosTobbing v2r8 to protect yourself against crushes at DaVinci finalization.
  Options to run trigger simulations on DC06 data:
Line: 45 to 45
 
  • DaVinci v20r2
Changed:
<
<
No known problems.
>
>
No major problems, but you must use Phys/TisTosTobbing v2r8 to protect yourself against crushes at DaVinci finalization.
  Options to run trigger simulations on DC06 data:
Line: 57 to 57
 
  • DaVinci v20r1
Changed:
<
<
No known problems.
>
>
No major problems, but you must use Phys/TisTosTobbing v2r8 to protect yourself against crushes at DaVinci finalization.
  Options to run trigger simulations on DC06 data:
Line: 70 to 70
 
  • DaVinci v20r0
Changed:
<
<
Generally works fine.
>
>
No major problems, but you must use Phys/TisTosTobbing v2r8 to protect yourself against crushes at DaVinci finalization.
  New Hlt1PhotonDiTrackDecision trigger is missing from $HLTSYSROOT/HltInit.opts. If you care about this trigger use your own version of HltInit.opts in which this entry has been added.
Line: 136 to 136
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008, 15 July 2008, 8 Aug 2008, 31 Aug 2008, 15 Sep 2008
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008, 15 July 2008, 8 Aug 2008, 31 Aug 2008, 15 Sep 2008, 30 Oct 2008
 \ No newline at end of file

Revision 172008-10-08 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 31 to 31
  There was a problem with TisTossing L0 Muon triggers when LHCb::Track was passed as signal in all version before DaVinci v19r13. Passing Track is not a standard approach and therefore normal users should not worry about this (no problem when passing signal as LHCb::Particle).
Added:
>
>
  • DaVinci v20r3

No known problems.

Options to run trigger simulations on DC06 data:

from HltConf.Configuration import *
HltConf().replaceL0BanksWithEmulated = True
HltConf().hltType = 'Hlt1+Hlt2'
HltConf().applyConf()
 
  • DaVinci v20r2

Revision 162008-10-07 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 117 to 117
 

Links to related pages

Changed:
<
<
>
>
 
Added:
>
>
 

Revision 152008-09-19 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 31 to 31
  There was a problem with TisTossing L0 Muon triggers when LHCb::Track was passed as signal in all version before DaVinci v19r13. Passing Track is not a standard approach and therefore normal users should not worry about this (no problem when passing signal as LHCb::Particle).
Added:
>
>
  • DaVinci v20r2

No known problems.

Options to run trigger simulations on DC06 data:

#include "$L0DUROOT/options/ReplaceL0DUBankWithEmulated.opts"
#include "$HLTCONFROOT/options/Hlt1.opts"
#include "$HLTCONFROOT/options/Hlt2.opts"
 
  • DaVinci v20r1

No known problems.

Revision 142008-09-15 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 11 to 11
  See Doxygen documentation of the DaVinci project. Make sure to follow link also to ITriggerSelectionTisTos from which ITriggerTisTos inherits.
  • More extensive documentation with code examples can be found in various presentations:
Added:
>
>
 
Changed:
<
<
>
>
 

Warnings for users

Line: 51 to 54
 Rename all L0TriggerXXX to L0XXXDecision (use “L0*Decision” for global L0 decision). Hlt2 triggers now have names Hlt2SelXXXDecision (use “Hlt2*Decision” for global Hlt2 decision). Hlt1 triggers also follow Hlt1XXXDecision pattern but “*” will still work if kAlleyExitsOnly flag is set (default!).
Deleted:
<
<
Sample codes linked to this page have not been yet updated to this change.
  Options to run trigger simulations on DC06 data:
Line: 109 to 111
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008, 15 July 2008, 8 Aug 2008, 31 Aug 2008
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008, 15 July 2008, 8 Aug 2008, 31 Aug 2008, 15 Sep 2008

Revision 132008-08-31 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 28 to 28
  There was a problem with TisTossing L0 Muon triggers when LHCb::Track was passed as signal in all version before DaVinci v19r13. Passing Track is not a standard approach and therefore normal users should not worry about this (no problem when passing signal as LHCb::Particle).
Added:
>
>
  • DaVinci v20r1

No known problems.

Options to run trigger simulations on DC06 data:

#include "$L0DUROOT/options/L0DUBankSwap.opts"
#include "$L0DUROOT/options/DefaultTCK.opts"
#include "$HLTSYSROOT/options/Hlt1.opts"
#include "$HLTSYSROOT/options/Hlt2.opts"
 
  • DaVinci v20r0

Generally works fine.

Line: 40 to 53
 Hlt1 triggers also follow Hlt1XXXDecision pattern but “*” will still work if kAlleyExitsOnly flag is set (default!). Sample codes linked to this page have not been yet updated to this change.
Added:
>
>
Options to run trigger simulations on DC06 data:
#include "$L0DUROOT/options/L0DUBankSwap.opts"
#include "$L0DUROOT/options/DefaultTCK.opts"
#include "$HLTSYSROOT/options/HltInit.opts"
#include "$HLTSYSROOT/options/Hlt1.opts"
#include "$HLTSYSROOT/options/Hlt2.opts"
 
  • DaVinci v19r14
Line: 49 to 71
  There are many problems with the tool functionality in DaVinci v19r13. To fix this release you must use Phys/TisTosTobbing v2r5 (e.g. do starting in your DaVinci_v19r13/ area: getpack Phys/TisTosTobbing v2r5; cd Phys/TisTosTobbing; mv v2r5 v2r4; cd v2r4/cmt; cmt config; gmake).
Added:
>
>
Options to run trigger simulations on DC06 data:
#include "$HLTSYSROOT/options/L0.opts"
#include "$HLTSYSROOT/options/HltInit.opts"
#include "$HLTSYSROOT/options/Hlt1.opts"
#include "$HLTSYSROOT/options/Hlt2.opts"
 
  • DaVinci v19r10 – v19r12

No known problems.

Line: 79 to 110
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008, 15 July 2008, 8 Aug 2008
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008, 15 July 2008, 8 Aug 2008, 31 Aug 2008
 \ No newline at end of file

Revision 122008-08-08 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 28 to 28
  There was a problem with TisTossing L0 Muon triggers when LHCb::Track was passed as signal in all version before DaVinci v19r13. Passing Track is not a standard approach and therefore normal users should not worry about this (no problem when passing signal as LHCb::Particle).
Changed:
<
<
  • DaVinci v19r14
>
>
  • DaVinci v20r0

Generally works fine.

 
Changed:
<
<
The execution crushes in the TriggerTisTos tool in calo related code. Do not use this version until proper fix is found.
>
>
New Hlt1PhotonDiTrackDecision trigger is missing from $HLTSYSROOT/HltInit.opts. If you care about this trigger use your own version of HltInit.opts in which this entry has been added.
 
Changed:
<
<
The trigger names have changed in this version.
>
>
The trigger names have changed (already in DaVinci v19r14).
 Rename all L0TriggerXXX to L0XXXDecision (use “L0*Decision” for global L0 decision). Hlt2 triggers now have names Hlt2SelXXXDecision (use “Hlt2*Decision” for global Hlt2 decision). Hlt1 triggers also follow Hlt1XXXDecision pattern but “*” will still work if kAlleyExitsOnly flag is set (default!). Sample codes linked to this page have not been yet updated to this change.
Added:
>
>
  • DaVinci v19r14

Do not use this version because of crushes in calo code.

 
  • DaVinci v19r13

There are many problems with the tool functionality in DaVinci v19r13. To fix this release you must use Phys/TisTosTobbing v2r5 (e.g. do starting in your DaVinci_v19r13/ area: getpack Phys/TisTosTobbing v2r5; cd Phys/TisTosTobbing; mv v2r5 v2r4; cd v2r4/cmt; cmt config; gmake).

Line: 72 to 79
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008, 15 July 2008
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008, 15 July 2008, 8 Aug 2008
 \ No newline at end of file

Revision 112008-08-07 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 21 to 21
 
  • All versions
Changed:
<
<
If you analyze older DC06 DSTs (often the case) you need to rerun MuonID in DaVinci for proper TisTossing of muon triggers . The tool will issue warnings but it will not crush if you don’t (results for Hlt1 and Hlt2 triggers will be reasonable, but not for L0 triggers).
>
>
When you analyze older DC06 DSTs (often the case) you need to rerun MuonID in DaVinci for proper TisTossing of muon triggers . The tool will issue warnings ("No offline muon tracks at Rec/Track/Muon thus, muon hits will be ignored on trigger tracks.") but it will not crush if you don’t (results for Hlt1 and Hlt2 triggers will be reasonable, but not for L0 triggers).
 See Rerunning MuonID in DaVinci for more info.

There was a problem with TisTossing L0 Muon triggers when LHCb::Track was passed as signal in all version before DaVinci v19r13. Passing Track is not a standard approach and therefore normal users should not worry about this (no problem when passing signal as LHCb::Particle).

Revision 102008-07-22 - TomaszSkwarnicki

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

TriggerTisTos tool

TriggerTisTos tool classifies triggers (L0 or Hlt) as TIS (Trigger Independent of Signal) or TOS (Trigger On Signal) with respect to user defined signal (e.g. B candidate).

Added:
>
>

Documentation

 

Warnings for users

  • All versions
Line: 47 to 59
 The tool is not compatibile with the earlier DaVinci versions.
Deleted:
<
<

Documentation

 

Links to related pages

Revision 92008-07-15 - TomaszSkwarnicki

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

TriggerTisTos tool

TriggerTisTos tool classifies triggers (L0 or Hlt) as TIS (Trigger Independent of Signal) or TOS (Trigger On Signal) with respect to user defined signal (e.g. B candidate).

Changed:
<
<

Compatibility

>
>

Warnings for users

 
Changed:
<
<
The tool was first released with DaVinci v19r5 (Hlt v1r9). See special instructions for use with DaVinci v19r4. The tool is not compatibile with the earlier DaVinci versions. First version with python support is in DaVinci v19r9.
>
>
  • All versions
 
Changed:
<
<
In DaVinci v19r9 alley exit selections and L0 triggers are not recognized properly and therefore use of wild character in specifying triggers may lead to wrong results (using explicit lists of triggers works fine). This problem was fixed in DaVinci v19r10.
>
>
If you analyze older DC06 DSTs (often the case) you need to rerun MuonID in DaVinci for proper TisTossing of muon triggers . The tool will issue warnings but it will not crush if you don’t (results for Hlt1 and Hlt2 triggers will be reasonable, but not for L0 triggers). See Rerunning MuonID in DaVinci for more info.

There was a problem with TisTossing L0 Muon triggers when LHCb::Track was passed as signal in all version before DaVinci v19r13. Passing Track is not a standard approach and therefore normal users should not worry about this (no problem when passing signal as LHCb::Particle).

  • DaVinci v19r14

The execution crushes in the TriggerTisTos tool in calo related code. Do not use this version until proper fix is found.

The trigger names have changed in this version. Rename all L0TriggerXXX to L0XXXDecision (use “L0*Decision” for global L0 decision). Hlt2 triggers now have names Hlt2SelXXXDecision (use “Hlt2*Decision” for global Hlt2 decision). Hlt1 triggers also follow Hlt1XXXDecision pattern but “*” will still work if kAlleyExitsOnly flag is set (default!). Sample codes linked to this page have not been yet updated to this change.

  • DaVinci v19r13
  There are many problems with the tool functionality in DaVinci v19r13. To fix this release you must use Phys/TisTosTobbing v2r5 (e.g. do starting in your DaVinci_v19r13/ area: getpack Phys/TisTosTobbing v2r5; cd Phys/TisTosTobbing; mv v2r5 v2r4; cd v2r4/cmt; cmt config; gmake).
Changed:
<
<
There was a problem with TisTossing L0 Muon triggers when LHCb::Track was passed as signal (no problem when passing it as LHCb::Particle) in all version before DaVinci v19r13.
>
>
  • DaVinci v19r10 – v19r12

No known problems.

  • DaVinci v19r9

In DaVinci v19r9 alley exit selections and L0 triggers are not recognized properly and therefore use of wild character in specifying triggers may lead to wrong results (using explicit lists of triggers works fine). This problem was fixed in DaVinci v19r10.

  • DaVinci v19v5-v19r8

No known problems, but no or limited python support.

  • DaVinci v19r4

See special instructions for use with DaVinci v19r4. The tool is not compatibile with the earlier DaVinci versions.

 

Documentation

Line: 40 to 69
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008, 15 July 2008

Revision 82008-07-09 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 7 to 7
 

Compatibility

Changed:
<
<
The tool was first released with DaVinci v19r5 (Hlt v1r9). See special instructions for use with DaVinci v19r4. The tool is not compatibile with the earlier DaVinci versions. First version with python support is in DaVinci v19r9.
>
>
The tool was first released with DaVinci v19r5 (Hlt v1r9). See special instructions for use with DaVinci v19r4. The tool is not compatibile with the earlier DaVinci versions. First version with python support is in DaVinci v19r9.
 
Changed:
<
<
In DaVinci v19r9 alley exit selections and L0 triggers are not recognized properly and therefore use of wild character in specifying triggers may lead to wrong results (using explicit lists of triggers works fine). This problem was fixed in DaVinci v19r10.
>
>
In DaVinci v19r9 alley exit selections and L0 triggers are not recognized properly and therefore use of wild character in specifying triggers may lead to wrong results (using explicit lists of triggers works fine). This problem was fixed in DaVinci v19r10.
 
Changed:
<
<
There are many problems with the tool functionality in DaVinci v19r13. To fix this release you must use Phys/TisTosTobbing v2r5 (e.g. do starting in your DaVinci_v19r13/ area: getpack Phys/TisTosTobbing v2r5; cd Phys/TisTosTobbing; mv v2r5 v2r4; cd v2r4/cmt; cmt config; gmake).
>
>
There are many problems with the tool functionality in DaVinci v19r13. To fix this release you must use Phys/TisTosTobbing v2r5 (e.g. do starting in your DaVinci_v19r13/ area: getpack Phys/TisTosTobbing v2r5; cd Phys/TisTosTobbing; mv v2r5 v2r4; cd v2r4/cmt; cmt config; gmake).

There was a problem with TisTossing L0 Muon triggers when LHCb::Track was passed as signal (no problem when passing it as LHCb::Particle) in all version before DaVinci v19r13.

 

Documentation

Revision 72008-06-18 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 10 to 10
 The tool was first released with DaVinci v19r5 (Hlt v1r9). See special instructions for use with DaVinci v19r4. The tool is not compatibile with the earlier DaVinci versions.
Changed:
<
<
First version with python support is in DaVinci v19r9.
>
>
First version with python support is in DaVinci v19r9.
  In DaVinci v19r9 alley exit selections and L0 triggers are not recognized properly and therefore use of wild character in specifying triggers may lead to wrong results (using explicit lists of triggers works fine). This problem was fixed in DaVinci v19r10.
Line: 22 to 22
  See Doxygen documentation of the DaVinci project. Make sure to follow link also to ITriggerSelectionTisTos from which ITriggerTisTos inherits.
  • More extensive documentation with code examples can be found in various presentations:
Added:
>
>
 
Line: 37 to 38
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008, 18 Jun 2008
 \ No newline at end of file

Revision 62008-06-18 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 10 to 10
 The tool was first released with DaVinci v19r5 (Hlt v1r9). See special instructions for use with DaVinci v19r4. The tool is not compatibile with the earlier DaVinci versions.
Added:
>
>
First version with python support is in DaVinci v19r9.
  In DaVinci v19r9 alley exit selections and L0 triggers are not recognized properly and therefore use of wild character in specifying triggers may lead to wrong results (using explicit lists of triggers works fine). This problem was fixed in DaVinci v19r10.
Added:
>
>
There are many problems with the tool functionality in DaVinci v19r13. To fix this release you must use Phys/TisTosTobbing v2r5 (e.g. do starting in your DaVinci_v19r13/ area: getpack Phys/TisTosTobbing v2r5; cd Phys/TisTosTobbing; mv v2r5 v2r4; cd v2r4/cmt; cmt config; gmake).
 

Documentation

  • The user interface of the tool is defined in ITriggerTisTos.h which contains also some documentation.

Revision 52008-02-13 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 11 to 11
 See special instructions for use with DaVinci v19r4. The tool is not compatibile with the earlier DaVinci versions.
Added:
>
>
In DaVinci v19r9 alley exit selections and L0 triggers are not recognized properly and therefore use of wild character in specifying triggers may lead to wrong results (using explicit lists of triggers works fine). This problem was fixed in DaVinci v19r10.
 

Documentation

  • The user interface of the tool is defined in ITriggerTisTos.h which contains also some documentation.
Line: 32 to 34
 
Deleted:
<
<
-- TomaszSkwarnicki - 11 Oct 2007
 \ No newline at end of file
Added:
>
>
-- TomaszSkwarnicki - 11 Oct 2007, 13 Feb 2008

Revision 42008-01-23 - JoseHernando

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

TriggerTisTos tool

Revision 32007-10-29 - StephenWotton

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

TriggerTisTos tool

Revision 22007-10-11 - TomaszSkwarnicki

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

TriggerTisTos tool

Line: 23 to 23
 

Links to related pages

Added:
>
>
 
Line: 31 to 32
 
Changed:
<
<
-- TomaszSkwarnicki - 01 Oct 2007
>
>
-- TomaszSkwarnicki - 11 Oct 2007

Revision 12007-10-01 - TomaszSkwarnicki

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

TriggerTisTos tool

TriggerTisTos tool classifies triggers (L0 or Hlt) as TIS (Trigger Independent of Signal) or TOS (Trigger On Signal) with respect to user defined signal (e.g. B candidate).

Compatibility

The tool was first released with DaVinci v19r5 (Hlt v1r9). See special instructions for use with DaVinci v19r4. The tool is not compatibile with the earlier DaVinci versions.

Documentation

Links to related pages

-- TomaszSkwarnicki - 01 Oct 2007

 
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