-
Notifications
You must be signed in to change notification settings - Fork 174
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Brainbrowser not working after fixing paths in violation tables #4347
Brainbrowser not working after fixing paths in violation tables #4347
Conversation
… after the update to the violation tables
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.
Works great!
@ridz1208 As we discussed, I added the flag Critical to release so that this PR makes it to 20.3 along with the MRI one linked in the description. Thanks! |
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.
not tested. just reviewed
… tables (aces#4347) The paths stored in the 3 violation tables (MRICandidateErrors, mri_violations_log and mri_protocol_violated_scans) were wrong and a tool script has been provided on the LORIS-MRI side to correct the paths to the MINC files so that they are valid paths. Due to the bad paths being present in those tables, brainbrowser was hacked on the LORIS side to be able to display the images. Now that the paths are corrected, this hack can be removed which also simplifies the code.
Brief summary of changes
The paths stored in the 3 violation tables (
MRICandidateErrors
,mri_violations_log
andmri_protocol_violated_scans
) were wrong and a tool script has been provided on the LORIS-MRI side to correct the paths to the MINC files so that they are valid paths.Due to the bad paths being present in those tables, brainbrowser was hacked on the LORIS side to be able to display the images. Now that the paths are corrected, this hack can be removed which also simplifies the code.
This PR goes with aces/Loris-MRI#403 on the LORIS-MRI side where more details can be found regarding the bad paths stored in the violation tables.
This resolves issue...
Caveat for existing projects
Make sure to run the tool script called
cleanup_paths_of_violation_tables.pl
on the LORIS-MRI side in order to update the MINC location in the violation tables.To test this change...