Skip to content
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

why not use tan(angle) ? #389

Open
danieljeans opened this issue Sep 12, 2024 · 2 comments
Open

why not use tan(angle) ? #389

danieljeans opened this issue Sep 12, 2024 · 2 comments

Comments

@danieljeans
Copy link
Contributor

danieljeans commented Sep 12, 2024

Hi,

<zplane z="-InnerTracker_half_length" rmin="ITEnvelopeClearanceConeHalfAngle * ConeBeamPipe_zmax" rmax="InnerTracker_outer_radius" />

wouldn't it be more geometrically-correct to use

rmin="tan ( ITEnvelopeClearanceConeHalfAngle ) * ConeBeamPipe_zmax"

rather than

rmin="ITEnvelopeClearanceConeHalfAngle * ConeBeamPipe_zmax"
? (the difference is <3 mm in this case, but for ease of understanding the code...)

Similar construction in few other places, too.

@andresailer
Copy link
Contributor

Hi @danieljeans ,

You are correct, and as long as there are no overlaps I don't care about the precise dimensions of the envelope there. But you know #369 (comment) ...

So it depends how those inner tracker endcap inner radii were calculated and a few mm difference there could be painful...

@Zehvogel
Copy link
Contributor

This also confused me before (but I was also not aware of tan() being possible in the xml...). We should probably improve this at some point.

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

No branches or pull requests

3 participants