Difference between revisions of "CPP and NPP Readiness Review"
From GlueXWiki
(→Documentation for Review) |
|||
| Line 21: | Line 21: | ||
# [https://halldweb.jlab.org/doc-private/DocDB/ShowDocument?docid=4670 CPP Jeopardy Presentation PAC 48] September 24, 2020 | # [https://halldweb.jlab.org/doc-private/DocDB/ShowDocument?docid=4670 CPP Jeopardy Presentation PAC 48] September 24, 2020 | ||
# [https://halldweb.jlab.org/doc-private/DocDB/ShowDocument?docid=4527 CPP Jeopardy Update PAC 48] June 22, 2020 | # [https://halldweb.jlab.org/doc-private/DocDB/ShowDocument?docid=4527 CPP Jeopardy Update PAC 48] June 22, 2020 | ||
| − | |||
| − | |||
| − | |||
| − | |||
Revision as of 17:21, 24 November 2020
Preparations for the CPP and NPP Readiness Review
- Goal: Complete Readiness Review in time to schedule experiment in 2022
- Media:Coarse Acc Schedule 2021.pdf
Issues for the Readiness Review
- Budget
- Mechanical Design and Installation
- Trigger
- CPP Test and TOF Rates (Ilya)
- Running CPP and NPP together
Trigger
Discussion topics with Sasha
- CPP / NPP plan is to run multiple TOF configuration files + FCAL trigger with possibly a lower threshold.
- Confirm that no new firmware is needed for the TOF, i.e. modifications for TOF only need different configuration files
- We would like to run the TOF trigger with multiple configuration files plus the FCAL trigger
Documentation for Review
- CPP Jeopardy Presentation PAC 48 September 24, 2020
- CPP Jeopardy Update PAC 48 June 22, 2020
