Speaks for itself - gets round issues with the TrigDecisionTool feature access

Tau Roi names have changed for the TauIso processing

```
git grep -l EDMDecodingVersion | xargs sed -i 's/EDMDecodingVersion/EDMVersion/g'
```

Roi was not correct, so tracks would not be retrieved.

FS tracking moniotring chains were added that are not being run in the menu.
This adds wildcarded chains to circumvent this

Mark Sutton authored 4 years ago and Adam Edward Barton committed 4 years ago

Changes to show the directory name for the timing plots on the plots themselves
to more easily be able to tell one histogram from another in the display

Also, introduces some additional performance plots for the muon isolation trackings

Mark Sutton authored 4 years ago and Frank Winklmeier committed 4 years ago

Instead of filling one set of histograms, the tool has beem mofified to
fill different monitoring histograms depending on the provided prefix

	modified:   Trigger/TrigMonitoring/TrigIDtrkMonitoring/python/TrigIDPhysValMonitoringConfig.py
	modified:   Trigger/TrigMonitoring/TrigIDtrkMonitoring/python/TrigIDtrkMonitoringConfig.py

The muon Roi were changed so now we can't find the tracks in the same Roi, this
adds chains for these additional Roi names to try to catch them all

Mark Sutton authored 4 years ago and Frank Winklmeier committed 4 years ago

Monitoring for the newly added Precision Tracking collections

The Muon trigger creates a new RoiDescriptor, HLT_Roi_L2SAMuon for use by
the ID Trigger tracking. ( see atlas/athena!31747 )

This change allows the ID Trigger moniotirng to use the new RoiDescriptor.

Before the change in !31747 the ID Trigger muon moniotring does not work,
so this change is fine to go in before !31747

Mark Sutton authored 5 years ago and Adam Edward Barton committed 5 years ago

The ID Trigger Track collections have been renamed using the new consistent
naming convention as discussed in the TGM of 2019-08-28 (https://indico.cern.ch/event/843886/)

https://indico.cern.ch/event/843886/contributions/3545029/attachments/1898633/3133218/sutt-idcollections-2019-08-28.pdf

This should include all the changes to the configuration of the ID Trigger
and the menu code for the signatures, including the signature monitoring.

The vertex collections still need to be renamed - this will be done in the
future once the track renaming is complete.

Update the chain configuration

 - print function

Also fix some tab/space inconsistencies.

Retrurn before configuting any of the Tier0 monitoing for the ID Trigger

Directory in initial request was wrong - this fixes it

Because some fool changed all the ID Track collection names without
actually consulting anyone, and didn;t really know what they were doing,
the monitoring broke. In addition the idperf chains upon which we rely
have not been implemented.

This attempts to add some monitoring for standard chains, using the new
track cllections. The new collections may not work, it may be that code
changes are needed to use the new TDT. If the monitoring does not work
because of the actual names themselves, then this won't be fixed since
we are in any case moving to a new naming convention, so will be fixed
during the Great Renaming.

The latest changes to 21.3 that should have been swept automatically failed to sweep because of an out of date file in master. So these changes just include the changes for the files from !23630 (merged)

In addition, there are a lot of other changes that appeared to already be there due to !23613 (merged) in the from !23630 (merged), but in the fresh checkout of master that I made just a minute ago, they still seem to be missing. As a consquence could this just be accepted -all these changes have already been reviewed and this request is simply to force the files to be updated since the automatic sweeps failed.

Update packages:TrigFastTrackFinder TrigL2SiTrackFinder TrigL2TRTSegFinder TrigT2BeamSpot TrigTRTHighTHitCounter TrigInDetAnalysis TrigInDetAnalysisExample TrigInDetAnalysisUser TrigInDetAnalysisUtils TrigInDetTruthAlgs TrigInDetEvent TrigInDetEventTPCnv TrigInDetPattRecoEvent TrigIDJpsiMonitoring TrigIDTPMonitor TrigIDtrkMonitoring IDScanHitFilter IDScanZFinder TrigIDUtils TrigInDetPattRecoTools TrigInDetRecoTools TrigInDetToolInterfaces TrigInDetTrackExtrapolator TrigInDetTrackFitter TrigInDetVxInJetTool TrigJPsiTools TrigOfflineDriftCircleTool TrigOnlineSpacePointTool TrigSiSpacePointTool TrigTRT_TrackExtensionTool TrigVertexFitter TrigVKalFitter TrigInDetTruthEvent TrigTruthEventAthenaPool TrigTruthEventTPCnv TrigInDetValidation TrigInDetValidationLight TrigInDetValidationWeb  from upstream/21.0-TrigMC to upstream/master via pseudo-merge


Former-commit-id: 9e323acc

Peter Onyisi authored 6 years ago and Vakhtang Tsulaia committed 6 years ago

Former-commit-id: d92d4bf0065df98232e7de86fe9f3216a0a02c63

Katherine Pachal authored 6 years ago and Atlas Nightlybuild committed 6 years ago

Sweeping !10962 from 21.1-dev to 21.1.
Fix the roi in the FTK bjet chains

See merge request atlas/athena!10999

(cherry picked from commit 6c5e9c0a [formerly 06231c037f1365b370510f977bee2190e4e5a12b])

9099dbec Merge branch '21.1-dev-ftkfix' into '21.1-dev'

Former-commit-id: b7cd5f1f

Katherine Pachal authored 6 years ago and Atlas Nightlybuild committed 6 years ago

Fix the roi in the FTK bjet chains

See merge request atlas/athena!10962

(cherry picked from commit 8fcd24cb [formerly a579121cd87f601914899619bd2a329ec4a66bb1])

494ef084 Fix the roi in the FTK bjet chains

Former-commit-id: 93e61b04

Katherine Pachal authored 6 years ago and Atlas Nightlybuild committed 6 years ago

Add analyses for FTK full scan chains to the Tier 0 analysis

See merge request atlas/athena!10854

(cherry picked from commit 0eb92fc2 [formerly 4130763dce5da6e000eed96e88b0ce649f015ad1])

eaa38891 Add analyses for FTK full scan chains to the Tier 0 analysis
ba8870d6 Add the FTK refitted fullscan collections to the Tier 0 analysis

Former-commit-id: a39e9866

This reverts commit cdf718bf [formerly 9d67f5b8].


Former-commit-id: 008b62d0

This reverts commit 9156e32a [formerly f73d17d3], reversing
changes made to 27d106d1 [formerly 8f2f5188].


Former-commit-id: 9d67f5b8

Imma Riu authored 7 years ago and Atlas Nightlybuild committed 7 years ago

Generalise chain patterns somewhat

See merge request !6349

Former-commit-id: 0e022ecb

This includes all the changes that have gone into either 21.0
or 21.1 but which somehow have not yet made it into the master
branch.

We do not want to make any changes to the code in this merge
request since we need the code to be consistent with 21.0 and
21.1. Any comments on the code should refer to the merge requests
in the other releases


Former-commit-id: 45fbeb94

	* TrigIDtrkMonitoring-00-02-75
	* bjet vtx monitoring

2016-11-26 sutt < sutt @ cern.ch >
	* TrigIDtrkMonitoring-00-02-74
	* changes for the bjet vertex monitoring

2016-11-23 sutt < sutt @ cern.ch >
	* TrigIDtrkMonitoring-00-02-73
	* fix stupid python indentation

2016-11-23 sutt < sutt @ cern.ch >
        * TrigIDtrkMonitoring-00-02-72
        * change Muon chain order

2016-11-22 sutt < sutt @ cern.ch >
        * TrigIDtrkMonitoring-00-02-71
        * fix bjet chains

2016-11-22 sutt < sutt @ cern.ch >
...
(Long ChangeLog diff - truncated)


Former-commit-id: 30265517

	* TrigIDtrkMonitoring-00-02-67
	* fix egamma chains


Former-commit-id: 23d7a478

	* TrigIDtrkMonitoring-00-02-66
	* add shifter chains for HI running

2016-10-10 sutt < sutt @ cern.ch >
	* TrigIDtrkMonitoring-00-02-65
	* remove redundent chains

2016-10-10 sutt < sutt @ cern.ch >
	* TrigIDtrkMonitoring-00-02-64
	* tau chains

2016-10-10 sutt < sutt @ cern.ch >
	* TrigIDtrkMonitoring-00-02-63
	* vertex chains

2016-10-10 sutt < sutt @ cern.ch >
	* TrigIDtrkMonitoring-00-02-62
	* vtx analyses

2016-10-07 sutt < sutt @ cern.ch >
...
(Long ChangeLog diff - truncated)


Former-commit-id: 9bdd052a

	* TrigIDtrkMonitoring-00-02-60
	* add vertex monitoring

2016-07-01 sutt < sutt @ cern.ch >
	* TrigIDtrkMonitoring-00-02-59
	* fix bjet chains

2016-07-01 sutt < sutt @ cern.ch >
	* TrigIDtrkMonitoring-00-02-58
	* update chains

2016-05-15 sutt < sutt @ cern.ch >
	* TrigIDtrkMonitoring-00-02-57
	* monitor non split bjet chain


Former-commit-id: f11b8d47

	* TrigIDtrkMonitoring-00-02-56
	* update Shifter tags

2016-05-04 sutt < sutt @ cern.ch >
	* TrigIDtrkMonitoring-00-02-55
	* fix chains

2016-05-04 sutt < sutt @ cern.ch >
	* TrigIDtrkMonitoring-00-02-54
	* update chains

2016-04-23 sutt < sutt @ cern.ch >
	* TrigIDtrkMonitoring-00-02-53
	* use only tau leading track

2016-04-20 sutt < sutt @ cern.ch >
	* TrigIDtrkMonitoring-00-02-52
	* add cmake lists


Former-commit-id: cb2a4ac2