Skip to content

Conversation

@fhagemann
Copy link

Changing MSubModuleChargeTransport all at once became kind of chaotic, so I will be splitting my PR into smaller PRs, which should make it way easier to review and to collect feedback for the individual steps.

In this PR, I'm replacing the hard-coded values for strip pitches, detector width, number of strips etc. by the numbers obtained from MModule::m_Geometry, which I had to pass down to MSubModuleChargeTransport.

I will mark the parts of the codes where I have questions/comments after opening the PR.

@zoglauer
Copy link
Collaborator

zoglauer commented Dec 9, 2025

I think this is OK for now.
We have to come up with a plan how to handle, especially name, all the 16 detectors in their holders. In the past we had a file with all the parameters, and had a python script to generate our 12 detectors. Maybe think if we should do something similar.

@fhagemann
Copy link
Author

Can we merge this PR or should I add a TODO somewhere first and/or open an issue about this?

@zoglauer
Copy link
Collaborator

zoglauer commented Dec 9, 2025

It's this:
#77

@zoglauer zoglauer merged commit 871077b into cositools:develop/em Dec 9, 2025
ckierans pushed a commit to ckierans/nuclearizer that referenced this pull request Dec 10, 2025
* Set the geometry in SMEX DEE SubModules
* Read detector dimensions from the geometry
* Read detector radius from geometry
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants