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

ROOT detector offset #837

Closed
KrisThielemans opened this issue Mar 2, 2021 · 2 comments
Closed

ROOT detector offset #837

KrisThielemans opened this issue Mar 2, 2021 · 2 comments

Comments

@KrisThielemans
Copy link
Collaborator

we currently have a keyword for changing the offset such that the first GATE crystal can be "rotated" to another crystal, such that the new (STIR) zero-th crystal is in the "vertical" position. It was introduced by @NikEfth as otherwise our images come out rotated. See here for an example https://github.com/UCL/STIR-GATE-Connection/blob/acf08710e2046d5d26831f7cb7dcd50e550be989/ExampleScanners/D690/root_header_template.hroot#L57

Example code where it is used is at

crystal1 -= half_block;
crystal2 -= half_block;
// Add offset
crystal1 += offset_dets;
crystal2 += offset_dets;

There are various problems with this:

  • as far as I can see half_block is not initialised. This is probably a bug that I introduced in InputStreamFromROOTFile changes for virtual crystals #617 (although it could be older). It is for instance here but this constructor was not used (and disabled in InputStreamFromROOTFile changes for virtual crystals #617). It might mean that most of the time it will be set to zero but it wouldn't be guaranteed.
  • the offset probably makes sense to very few STIR users
  • it creates trouble with find_ML_normfactors3D we believe (found by @francescaleek). The symmetry-code there will assume that a block starts at crystal 0, but that's not guaranteed as the user can put in any number. This then creates trouble in the estimated norm factors.

Ideally we resolve this after merging #181 (apologies that this hasn't been done yet!), by introducing a new keyword corresponding to an angle of the GATE "module" or so.

@robbietuk
Copy link
Collaborator

What steps are needed now that #181 has been merged?

@KrisThielemans
Copy link
Collaborator Author

half_block addressed in #1012. See also #938 for remaining discussions

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

2 participants