-
Notifications
You must be signed in to change notification settings - Fork 58
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
Issue349 imtool3 d td #355
Conversation
blue button for help + help for trackpads
Great! Thanks @tanguyduval ! What's your thoughts on handling the conflicting files? It appears the y are too complex to view on GitHub. Should we just use the ones in this branch to overwrite the one in master? Or are the ones in master possibly modified from the base imtool3D ones, and overwriting them would result in missing features/lines of code neeed for your _td mods? |
# Conflicts: # External/imtool3D_td/imtool3D.m # External/imtool3D_td/imtool3D_3planes.m # External/imtool3D_td/imtool3D_nii_3planes.m # External/imtool3D_td/src/load_nii_datas.m
@mathieuboudreau I just did the merge. I used the new version and overwrote master with new versions of imtool3D. |
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.
This PR perfectly fixes #349. I went through the PR review checklist and everything pass fine.
Thanks a lot @tanguyduval !!
Purpose
solve #349
Approach
in nii_load.m, Apply use the scaling and convert to double automatically. If output takes more than 300Mb of memory consumption ask the user.
These changes were already done in dicm2nii and imtool3D. So I just updated these two External repo with their latest version.
Open Questions and Pre-Merge TODOs
Use github checklists. When solved, check the box and explain the answer.
Review that changed source files/lines are related to the pull request/issue
If any files/commits were accidentally included, cherry-pick them into another branch.
Review that changed source files/lines were not accidentally deleted
Fix appropriately if so.
Test new features or bug fix
If not implemented/resolved adequately, solve it or inform the developer by requesting changes in your review.
Preferably, set breakpoints in the locations that the code was changed and follow allong line by line to see if the code behaves as intended.
Manual GUI tests (general)
Specifications
Reviewer
@mathieuboudreau