-
Notifications
You must be signed in to change notification settings - Fork 95
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
Allow TOF mashing in SSRB #1464
Conversation
src/utilities/SSRB.cxx: formatting of help doc-string
This looks good to me, but weirdly enough it seems like we broke |
This results in shorter code, but also consistent. There was a "problem" in the previous version that the TOF bin was actually used as tang_pos_num when determining get_m() (but it didn't create a problem as currently get_m() in independent of both).
even if do_norm=1, we should not normalise with the number of TOF bins. This is because the projectors will take the width of the TOF bin properly into account. (In contrast, for "span", they don't).
add a few arguments and configurable environment variables to be able to modify the output of the simulation
Using the cache has very little impact on run-time for a single forward projection, but affects memory a lot. This is especially important for TOF.
I had to undo the normalisation for "num_mashed_tof_bins". The projectors are set-up such that the total number of counts remains the same independent of number of TOF bins/width etc (i.e. the same as non-TOF). Therefore, when mashing TOF bins and setting I've now added a test to check all this via reconstruction. This should be good to go. Let's see how the tests are doing. |
When using a single int as argument, the old style version is actually not used anymore due to the overload with the verbosity presumably. So use boost::format
span=2, max_rd=2 is unexpected, and leads to a bug in FBP3DRP etc. Changing to the expected case of max_rd=3 for now.
Changes in this pull request
Testing performed
Related issues
Checklist before requesting a review
documentation/release_XXX.md
has been updated with any functionality change (if applicable)