Update LAMARR configuration for consistency
To match Gauss metrics RUN2 configuration.
Merge request reports
Activity
requested review from @adavis
@dpopov digging into the logs of the two options, I see that the following changes are present: (summarising)
old new BeamHCrossingAngle = -0.000105 (default: -0.0005200000000000001) BeamHCrossingAngle = -0.000395 (default: -0.0005200000000000001) BeamEmittance = 0.00445 (default: 0.0037) BeamEmittance = 0.00402 (default: 0.0037) InteractionPosition = [0.84, -0.18, -2.6] (default: [0.459, -0.015, 0.5]) InteractionPosition = [0.84, -0.18, -3.1] (default: [0.459, -0.015, 0.5]) BunchRMS = 63.07 (default: 82.03) BunchRMS = 53.034 (default: 82.03) TimingAuditor.TIMER INFO Generator 816.300 TimingAuditor.TIMER INFO Generator 752.600 Which is ~60 ms faster in the generation phase, so confirming that the fix is indeed correct. I notice that the pipeline failed, so this should be fixed then I believe this is good to merge.
mentioned in commit fcc5db32
Please register or sign in to reply