Skip to content
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

Conversation

cmadjar
Copy link
Collaborator

@cmadjar cmadjar commented Feb 18, 2019

Brief summary of changes

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.

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...

  • make sure to run the tool provided on the LORIS-MRI side to update the violation tables and then try clicking on an image link in the MRI violation module to see if the image gets displayed

@cmadjar cmadjar added Add to Release Notes PR change should be highlighted in Release notes (important security, features and bugfixes) Bug PR or issue introducing/requiring bug fixes (not mutually exclusive with the Feature label) Caveat for Existing Projects PR contains changes that might impact the code or accepted practices of current active projects Document at Release PR adds or changes a feature such that the wiki (or other documentation) must be updated [branch] minor labels Feb 18, 2019
Copy link

@thomasbeaudry thomasbeaudry left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Works great!

@cmadjar cmadjar assigned driusan and unassigned thomasbeaudry Mar 1, 2019
@cmadjar cmadjar added the Critical to release PR or issue is key for the release to which it has been assigned label Mar 1, 2019
@cmadjar
Copy link
Collaborator Author

cmadjar commented Mar 1, 2019

@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!

Copy link
Contributor

@PapillonMcGill PapillonMcGill left a 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

@driusan driusan merged commit 6dffc76 into aces:minor Mar 4, 2019
@ridz1208 ridz1208 added this to the 20.3.0 milestone Mar 14, 2019
kchatpar pushed a commit to kchatpar/Loris that referenced this pull request Apr 15, 2019
… 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.
@cmadjar cmadjar deleted the fix_mri_violations_with_updated_location_in_violation_tables branch September 24, 2021 19:10
# for free to join this conversation on GitHub. Already have an account? # to comment
Labels
Add to Release Notes PR change should be highlighted in Release notes (important security, features and bugfixes) Bug PR or issue introducing/requiring bug fixes (not mutually exclusive with the Feature label) Caveat for Existing Projects PR contains changes that might impact the code or accepted practices of current active projects Critical to release PR or issue is key for the release to which it has been assigned Document at Release PR adds or changes a feature such that the wiki (or other documentation) must be updated
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants