Open
Conversation
Add a new Python example that illustrate the full reconstruction workflow, from the GATE simulation until the final FDK reconstruction.
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Add a new Python example that illustrate the full reconstruction workflow, from the GATE simulation until the final FDK reconstruction.
This is the sibling PR of OpenGATE/opengate#895. I think it should be merged after OpenGATE/opengate#895 (maybe even after it makes it to a GATE release?).
Perhaps now would be a good time to add the mechanisms to execute examples during the CI, like it is done in RTK. @axel-grc would that be a lot of work? Would you have time to have a look into it? It would probably be much faster for your to do it than for me.
Also, do we want to add the source code directly into the documentation, as it is done in RTK?
Final question, do we want the same example implemented in bash? Could be useful in the documentation.