Adding varying chi2 flag and using chi2 for new eta regions

We have new fit constants for the new region definitions. They are uploaded to /eos/atlas/atlascerngroupdisk/data-art/grid-input/PhaseIIUpgrade/EFTracking/ATLAS-P2-RUN4-03-00-00/banks_5L/v0.21/ For the ones that work, all but the last 4 eta bins, we have fit chi2 cut values for the first stage. These are subject to change if we need to make an update for the first stage chi2 cut. However, they are ok for now and should work if we turn on the varying chi2 flag that I wrote in here. The function uses the eta bin definition to find the corresponding chi2 cut based on the new region number.

Best regards, Osip

added EFTracking label

requested review from @jahreda and @brosser

added 1 commit

• 4d0cca13 - Replace FPGATrackSimAnalysisConfig.py

Compare with previous version

added 1 commit

• 53012bcb - Edit FPGATrackSimAnalysisConfig.py

Compare with previous version

marked this merge request as ready

This merge request affects 1 package:

• Trigger/EFTracking/FPGATrackSim/FPGATrackSimConfTools

This merge request affects 2 files:

• Trigger/EFTracking/FPGATrackSim/FPGATrackSimConfTools/python/FPGATrackSimAnalysisConfig.py
• Trigger/EFTracking/FPGATrackSim/FPGATrackSimConfTools/python/FPGATrackSimConfigFlags.py

added Trigger main review-pending-level-1 labels

CI Result SUCCESS (hash 53012bcb)

	Athena
externals
cmake
make
tests

Full details available on this CI monitor view. Check the JIRA CI status board for known problems
Athena: number of compilation errors 0, warnings 0
For experts only: Jenkins output (remote access info)

added review-approved label and removed review-pending-level-1 label

merged

mentioned in commit 2024009a

mentioned in merge request !78982 (merged)