-
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
SRT2D repository: SRT 2D PET and SPECT algorithms #1420
Conversation
Changes to use initial SSRB and arc-correction
…rom file - symmetry used" This reverts commit b32bb29.
Corrected the 2 mistakes in the Codacy report
Correction of the 8 (potentially minor) mistakes of the Codacy report
Correcting Codacy error
simulate_PET_data_for_tests.sh is now simulate_data_for_tests.sh
Dear Professor @KrisThielemans , -Thank you so much for Build and ctest!!! Unfortunately it won't run now, because I just realized I did not change the name simulate_PET_data_for_tests.sh to simulate_data_for_tests.sh also in run_scatter.sh file... I will now do the change. I am really sorry. -The current comment in SPECT parallelization is: -I renamed .sh manually because this option exists on the web interface, and it should be equivalent to the git option. I think the problem I recall with the name change, was that it was expected that simulate_PET_data_for_tests.sh should exist in SRT2D repository since it existed in master. In such a case could the solution be to rename the file in master first? -To run STIR, i had been cloning locally on my pc the current STIR version, and I then created the SRT etc files. These files I then uploaded to SRT2D Github. I am looking forward to your reply. I am really sorry for all the trouble. THANK YOU WHOLEHEARTEDLY FOR YOUR PATIENCE AND YOUR INVALUABLE HELP!!! |
simulate_PET_data_for_tests.sh is now simulate_data_for_tests.sh
no, let's leave it
All worked ok. (whatever happens on
You should clone your repo (not UCL/STIR) and checkout the SRT2D branch before making any changes. But anyway, I'm happy to do this at the very end. |
Dear Professsor @KrisThielemans, -Thank you wholeheartedly for your help with the SPECT data! I will wait for the Build and ctest you have set running (thank you!) to finish, and then I can make the changes for SRT2DSPECT code, i.e. 'attenuation filename' to 'attenuation projection filename' and add the comments. Or should I wait to get your reply on my questions for the SPECT conversation, so that the tests will run again after all changes are finalized? I am looking forward to your reply. I am really sorry for all the trouble. THANK YOU WHOLEHEARTEDLY FOR ALL YOUR INVALUABLE HELP!!! |
Dear Professor @KrisThielemans, ALL tests are succesful (I run locally Build and ctest), except for pre-commit.yml. I am looking forward to your comments. THANK YOU WHOLEHEARTEDLY FOR ALL YOU INVALUABLE HELP!!! |
As Codacy did not run, I changed a space for the tests to rerun
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.
excellent. I will run the pre-commit
now. Please don't push to the branch anymore, unless I ask you to.
… used (UCL#1519) use the time frame information (where available) for the listmode data to set the frame definition for the output of LmToProjData if all events are used, issuing a warning otherwise --------- Co-authored-by: Kris Thielemans <[email protected]>
Changes in this pull request
2 new analytic reconstruction algorithms SRT 2D PET in the src→ analytic → SRT2D folder and SRT 2D SPECT in the src→ analytic → SRT2DSPECT folder of my SRT2D repository.
[In 2016 in SRT2D folder had been uploaded the prior versions of both these two codes: these old versions do not work with the current STIR version (as there had been pointer etc changes in STIR in between). Also the new versions of the 2 algorithms are improved, e.g. the old SRT2DSPECT run only for uniform data, whereas the new one doesn’t have such restriction.]
Testing performed
Related issues
Checklist before requesting a review
documentation/release_XXX.md
has been updated with any functionality change (if applicable)