[DEE] Update AnalyzeEvent in MSubModuleChargeTransport
#85
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This is a first PR to replace the dummy code in
MSubModuleChargeTransport::AnalyzeEvent.I will open this as a draft PR, there are still a lot of magic numbers in there (bias voltage, temperature, initial charge cloud size, cross-talk parameters), but this is mainly to collect feedback on my current implementation while moving forward and improving this in comparison with data.
Some mathematical background:
The linear charge density of an event at a given position and depth can be approximated by Eq. (7) in https://doi.org/10.1016/j.nima.2023.168310. To get to the actual charge/energy, we need to integrate the linear charge density from the left edge of the strip to the right edge of the strip:
The idea is then to calculate the energy for the main strip and it's direct neighbors.
Here is a plot of what is happening in the code:
The implementation of cross-talk is based on the parameterization that we obtained from simulations (for now just for one detector and implemented as magic numbers). This currently seems to underestimate the cross-talk on the HV side and overestimate the cross-talk on the LV side.
