Recapitulation of the discussion during the East Area meeting

At the end, the discussion turned to the H2/H4 schedule. BH noted there could be a small error in the visualization of the schedule (NA63 should not be present), which will be fixed. NC suggested meeting for this discussion on Monday next week and he will review the draft schedule over the weekend. All present agreed to hold this meeting on 27 February 2023. Note: After the meeting, an earlier time slot was identified, proposing Friday, Feb 24, 16:30. 

BH noted that there is a standing issue that requires input from ML, which is the request from NA64e to run at the very beginning. This is incompatible with the test beam time for GIF++, which is important for the LHC experiments. NA64 cannot be in the beam while GIF does this test. JB noted that ideally this should be checked soon, since ML will be on holiday next week. NC+JB promised to follow up on this with ML. BH noted that as soon as GIF++ stops, NA64 can start. 

NC noted that combining ATLAS ZDC and NA64 does not work. BH noted that she allotted to LHCb one slot where they do not have the highest purity and one where they do. For ATLAS ZDC there is then only one slot. NC added that the high energy electrons go to H4, so if this is what would be needed for ATLAS ZDC, then this should be scheduled there. BH mentioned that in the worst case, she may have to cut some time from NA64 and/or NA61. BH promised to check with ATLAS ZDC what energy electrons they need.  BH asked if the above issue implied ALICE PHOS would have the same problem. JB filled in that ALICE PHOS requests 1-100 GeV/c with 1% resolution, which NC responded this should be fine, with up to 75% purity. JB suggested tagging with the XCETs could help bridge the gap. 

Minutes of this meeting

Discussion draft schedule H2/H4 (24 February 2023).

Present: D. Banerjee (DB),  J. Bernhard (JB), N. Charitonidis (NC), M. van Dijk (MvD), S. Girod (SG), B. Holzer (BH), L. Nevay (LN), B. Rae (BR).

• NA64 needs to be in the zone from the beginning to install and calibrate.
• RD51 can run in parallel (in PPE134) with access to PPE144 possible
• All experiments in H2 in parallel with NA64-e in H4 can get electrons < 120 GeV. CMS HF fine as they are in the beginning, and NA64-e can prepare. Hadrons only possible > 100 GeV when NA64-e is running. 
• If NA64-e starts earlier, CALICE cannot get high energy electrons, only < 120 GeV/c will be possible. 
• ATLAS ZDC cannot run parallel to NA64 for high energy electrons, high energy hadrons possible. A solution would be that NA64 takes a week break and someone moves in front of them to accommodate the requests. 
• ALICE PHOS 1 – 100 GeV electrons is ok, higher momenta will have lower purity. 
• NA61 with RD51 and GIF++ ok.
• CMS HGCAL no high energy electrons > 150 GeV/c. They can have up to 120 GeV/c and hadrons > 100 GeV/c.
• CMS ZDC same as CMS HGCAL which is ok for their request.
• CMS ECAL, if they remain in parallel with NA61, they will have less purity than usual and will have to do offline cuts. 
• HIKE FASER half of the week favoring one and the other favoring other. Conflicting requests but ok with co-ordination. 
• LHCB and GIF++, RD51 ok.
• CMS HGCAL with NA65 hadrons and muons challenging for CMS HGCAL. While NA65 is preparing HGCAL can take hadrons and muons. Then electrons are ok with NA65. 
• With CMS HGCAL GIF++ would be better. Maybe NA65 does not need three weeks.
• If NP04 does not come (to be confirmed after the next SPSC) NA65 would be better in H2 (faster and better beam conditions). 
• NA61 in parallel with NA65 - if NA61 needs low energy hadrons change will be needed in the middle of NA65. Hadrons > 120 GeV ok. 
• NP04 with CMS HGCAL ok. If NP04 needs negative polarity hadrons (-80 secondary to whatever in tertiary)  this is compatible with NA61, but not the case with 
• NA61 always takes positive. 
• Overall, the only major issue is the ATLAS- ZDC request.