Cross checks on beam position in XY and SIMCOND tag in Run3
About expected-2023
Beam position in Beam6800GeV-md100-expected-2023-nu1.4.py:
Gauss().InteractionPosition = [ 1.092*SystemOfUnits.mm,
0.474*SystemOfUnits.mm,
0.0*SystemOfUnits.mm ]
- Condition DB: sim-20230626-vc-md100 (Velo partially closed at +- 23.5mm)
Beam position in PbPb-Beam2680GeV-md100-expected-2023-fix1.py:
Gauss().InteractionPosition = [ 1.092*SystemOfUnits.mm,
0.474*SystemOfUnits.mm,
0.0*SystemOfUnits.mm ]
- Condition DB: sim-20230626-vc-md100 (Velo partially closed at +- 23.5mm)
About realistic-2023:
Beam position in Beam6800GeV-md100-2023-nu1.6.py:
Gauss().InteractionPosition = [ 1.29*SystemOfUnits.mm,
0.57*SystemOfUnits.mm,
7.8*SystemOfUnits.mm ]
- Condition DB: lhcb-conddb/SIMCOND!222 (merged)
Beam position in PbPb-Beam2680GeV-md100-2023-fix1.py:
Gauss().InteractionPosition = [ 1.143*SystemOfUnits.mm,
0.649*SystemOfUnits.mm,
5.535*SystemOfUnits.mm ]
- Condition DB: To be added?
About expected-2024:
Beam position in Beam6800GeV-md100-expected-2024-nu7.6.py:
Gauss().InteractionPosition = [ 1.092*SystemOfUnits.mm,
0.474*SystemOfUnits.mm,
0.0*SystemOfUnits.mm ]
- Condition DB: sim-20231017-vc-md100 (Velo closed)
Beam position in expected-2024 PbPb:
To be decided
- Condition DB: To be added?
Edited by Qiuchan Lu