-
Notifications
You must be signed in to change notification settings - Fork 5
Fix/cohort extractor output paths #1506
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
Conversation
for more information, see https://pre-commit.ci
Codecov ReportPatch coverage:
Additional details and impacted files@@ Coverage Diff @@
## master #1506 +/- ##
=======================================
Coverage 67.87% 67.88%
=======================================
Files 185 185
Lines 6544 6546 +2
=======================================
+ Hits 4442 4444 +2
Misses 2102 2102
Help us with your feedback. Take ten seconds to tell us how you rate us. Have a feature suggestion? Share it here. ☔ View full report in Codecov by Sentry. |
rkm
left a comment
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.
Looks great - just need to change the name of the news file to match the PR (not the issue number)
|
@darshad-github feel free to hit the big green "merge" button! 😄 |
Proposed Changes
This pull request fixes an issue spotted when running a test extraction. The problem occurs when UIDs present in the PACS data that are used to generate the extraction output paths
<StudyInstanceUID>/<SeriesInstanceUID>/...start with a dot. This indicates a hidden directory in Linux causing some directories to appear "missing" from the extraction output unless hidden files are shown.To fix this issue, the leading periods are now removed when generating the output path in the DefaultProjectPathResolver class. Additionally, a new test case has been added to the DefaultProjectPathResolverTest class to ensure that hidden directories are handled correctly.
Types of changes
What types of changes does your code introduce? Tick all that apply.
[skip ci]Checklist
By opening this PR, I confirm that I have:
Issues
If relevant, tag any issues that are expected to be resolved with this PR. E.g.: