You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hi,
This isn't an "issue" per se. I thought it would potentially be very useful if the QCReport output included the z-scores that are calculated internally as part of SliceChecker and InterlaceChecker for deciding if a frame should be excluded. That way, one can quickly see how close a given frame was to exclusion, and more readily calibrate an appropriate set of thresholds to use for a given set of data.
So, I've implemented the changes necessary in the SliceChecker and InterlaceChecker code to store those z-scores while they are computed, and then later output them into the QCReport.
I'm not familiar with how to formally use GitHub for this sort of thing, so I haven't forked the code and created a pull request. But I'm mentioning this because if a DTIPrep developer is interested in incorporating these features, I'm more than happy to share the code.
cheers,
-Mike H.
The text was updated successfully, but these errors were encountered:
That's great, thanks for the edits. How did you get the code, I assume via "git clone"? simply commit and push the code back to the repository where we can approve it and it will be included in the repository.
Alternatively, just send the modified code to me or Juan.
Hello Mike,
This aritcle explains the procedure to fork a repository, modify the code and submit a pull request.
It is the preferred way. You will appear as a contributor to DTIPprep.
Let me know if you have any questions.
Best,
Juan
Hi,
This isn't an "issue" per se. I thought it would potentially be very useful if the QCReport output included the z-scores that are calculated internally as part of SliceChecker and InterlaceChecker for deciding if a frame should be excluded. That way, one can quickly see how close a given frame was to exclusion, and more readily calibrate an appropriate set of thresholds to use for a given set of data.
So, I've implemented the changes necessary in the SliceChecker and InterlaceChecker code to store those z-scores while they are computed, and then later output them into the QCReport.
I'm not familiar with how to formally use GitHub for this sort of thing, so I haven't forked the code and created a pull request. But I'm mentioning this because if a DTIPrep developer is interested in incorporating these features, I'm more than happy to share the code.
cheers,
-Mike H.
The text was updated successfully, but these errors were encountered: