Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
MLEstimateComponentBasedNormalisation refactor #1499
base: master
Are you sure you want to change the base?
MLEstimateComponentBasedNormalisation refactor #1499
Changes from 13 commits
3035db8
bc58f39
0dca08e
9fed40f
2579f81
5d89071
86f6a82
880e530
dd711b1
2bcdc80
0fa8455
90ea81b
f0c788b
e5e2cc7
8adb620
9ff77fe
5c1a0f7
a114d14
b0e05c9
1d6ca9b
0aae32e
ca1140c
2935b99
3c11502
7c18bc7
42340f2
f424ca8
a5f4b91
1eefeff
dcee251
63f8560
3d7e9ff
55e5f1a
55897ee
cbe81ec
fd194fc
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
I believe this is the cleanest way to implement all these changes. Here is a use case from my cpp program.
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.
I acknowledge #1498 (comment), however this does work and provides an alternative allocation of the data.
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.
I'd rather do it the other way around I'm afraid. Your way is very different from anything else in STIR.
I very much prefer to let
MLEstimateComponentBasedNormalisation
have ashared_ptr<BinNormalisationPETFromComponents> normalisation_sptr
member, which we can get viaget_output()
(returning ashared_ptr<const BinNorm...>
). TheMLEstimateComponentBasedNormalisation::get_efficiencies()
would then just forward tonormalisation_sptr->get_efficiencies()
(note that I wouldn't let those returnshared_ptr
then, but references). Any reason not to do it this way?