[ENH] Allow datman to handle linked XNAT sessions #358
Conversation
This file contains 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
- The manifest files linked from the source session were causing incorrect paths to be generated in the dashboard, causing metrics to appear as broken images. This is resolved now, by omitting them from the symlink name_map - Files that could not be traditionally exported directly from xnat (i.e. files that could only be exported with dcm2niix) were being missed when searching datman-style paths. This is fixed now, and all valid datman-style names with matching tags will be detected.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
datman.exporters.SharedExporterclass that finds and symlinks relevant files (i.e. those with the correctly configured tags) from the XNAT source session (b642855, 9584af8, 85b3d01, b61671f, d45703c)datman.exporters.DBExporterto mark shared scans with the correct source scan ID (7f8f8a7)datman.exporters.DBExporterbugs related to some scans missing on the first run ofdatman/bin/dm_xnat_extract.pywhen those scans first export only to bids (instead of the legacy nii folder) (09bb73f)datman.scan.Scanbug causing some scans to be missed because the .niftis property did not update after object creation (b4620a1)