Updated RICH PD properties based on measurements
Merge request reports
Activity
This contains all the known updates to-date on the RICH PD properties and readout time info. These include the updates provided by Edoardo and Giovanni from the Mapmt measurements. It also contains a new condition named LookupTable for applying the time gates during the readout simulation in Boole and the corresponding update is being made in the Detector, to be able to use this. This is mainly aimed at the sim10/run3-ideal branch for running Boole. (It is also aimed at sim10/run3-2023 branch and other simulation branches as appropriate).
Edited by Sajan Easoassigned to @clemenci
Resolved by Sajan Easo@seaso, I assume this is needed to have a better simulation for 2024. Is there a corresponding MR for SIMCOND? Also is this ideal or 2024?
- Last reply by Sajan Easo
added SIM 2023 SIM 2024 Simulation labels
The Boole will run OK even when the LookupTable is not present. The LookupTable is to apply a certain specfied time gate and when it is not present it will just run with using default time gate.
The Detector MR 581 is to read the data from the new condition introduced here. (BTW, there is no need to wait for that Detector update to be present for this MR,considering this update is just adding a condition in the conditionsDB. For more details on this topic, one may consult someone like @clemenci ).
In this context, I think this MR can go ahead and hence switching back to regular status.
mentioned in issue lhcb/Boole#24
added ready-to-merge label
added SIM Run3 label
-
Looking at lhcb/Detector!581 there is a change in the conditions used. Given that is also used for Run5, this should be also ported to sim11/run5-ideal.
Or should we have there an equivalent MR with ideal conditions? @jonrob, @seaso ?
added SIM Run5 label
Hello,
In the current situation, I think it is OK to port this also to sim11/run5-ideal as you mention.
This has to do with the fact that , this is the 'only' measured set of values for pmts and the associated CLARO-chip readout. It is best to use them in all branches where pmts are involved. I guess it is better than using the nominal values.
(The general long term plan for RUN4 is to replace the CLARO-chip with a new readout chip named FastRICH. For RUN5 the long term plan is to replace either some or all of the pmts with new types of photon detectors. However we are far away from having the all relevant information in databases and from developing all the software for them. Hence it is best to use the 'best known info' in all branches, until new data becomes available. In addition to this, in the RICH-DD4HEP software there are some provisions to use some default values instead of those from DB, if ever needed).
mentioned in commit a876bf40
mentioned in merge request lhcb/Detector!581