-
Notifications
You must be signed in to change notification settings - Fork 47
dRICH tiled aerogel; First attempt #840
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
There are a few different possibilities to tile the aerogel (considering the material loss at construction level) and to minimize aerogel material production. |
88ab284
to
f1f7673
Compare
Looks good, I linked this PR to close #166. I'll leave the code review to @wdconinc. One question: will this need any change in EICrecon's |
Hi @c-dilks, I tested the whole chain, and it goes through without complains. I guess because, still we have one layer of 4 cm aerogel. |
(but you might get more reviews when the overlap checks succeed) |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Please fix overlap checks. You can test it locally using checkOverlaps -c ${DETECTOR_PATH}/epic_craterlake.xml
and/or scripts/checkOverlaps.py -c ${DETECTOR_PATH}/epic_craterlake.xml
.
// aerogel placement and surface properties | ||
// TODO [low-priority]: define skin properties for aerogel and filter | ||
// FIXME: radiatorPitch might not be working correctly (not yet used) | ||
/* |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
No commented code is to be stored in the public repo, please just remove the block.
@@ -318,26 +379,29 @@ static Ref_t createDetector(Detector& desc, xml::Handle_t handle, SensitiveDetec | |||
radiatorRmax + | |||
snoutDelta * (aerogelThickness + airgapThickness + filterThickness) / snoutLength); | |||
|
|||
Volume aerogelVol(detName + "_aerogel", aerogelSolid, aerogelMat); | |||
//Volume aerogelVol(detName + "_aerogel", aerogelSolid, aerogelMat); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Same here and elsewhere.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hi @veprbl Dimtry, yes I know. I wanted to put this draft PR in order to make sure our young collaborators, work directly on a branch that is under radar of the software experts. As it will be part of their PhD studies. But, my impression is, they haven't yet managed to get an dev-access.
Hence I think I will take care of the overlap and other issues.
Briefly, what does this PR introduce?
The dRICH aerogel so far has been a disk, which is unrealistic. We are tiling the aerogel, and adding carbon fiber ribs. This has consequences in terms of detector acceptance and efficiency. This PR makes a very preliminary version to tile the aerogel as a cone segment. The right shape and dimension has not yet been finalized. This draft PR aims to work with collaborators (Luisa and Rohit), for performing further test, improving coding styles and remove the hardcoded parameters and make the nesting as much as possible user-tunable.
What kind of change does this PR introduce?
Before dRICH aerogel was a single disk, now we are tiling the aerogel (with realistic shapes and dimensions) .
Please check if this PR fulfills the following:
At this moment this is not a final version. The right aerogel tile shape and choices are yet to be finalized and acceptanceXefficiency studies are to be performed. It will remain as a draft PR for the time being. Once the right shape and dimensions are finalized, we will create a final PR.
Does this PR introduce breaking changes? What changes might users need to make to their code?
No
Does this PR change default behavior?
No