add OSEM step size rule #40
Closed
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
I wouldn't put this in the ISTA example. It certainly makes very little sense to have both OSEM-type step-size (i.e. preconditioner) and the "kappa^2" preconditioner. It would be a good candidate for SIRF-Contrib though. We could conceivably have some OSEM implementations there: hand-crafted, using SIRF, using CIL. By the way, I'm not sure if this should be a step-size or preconditioner. I guess with the current CIL code, there's little distinction anymore. |
casperdcl
force-pushed
the
main
branch
3 times, most recently
from
908c39a to
9900487
Compare
|
shall we close this then? |
|
Closing this as no intention to merge it. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Create and use the OSEM step size rule.