-
Notifications
You must be signed in to change notification settings - Fork 456
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
Angle and CobbAngle tool: set default 1 for rowPixelSpacing and columnPixelSpacing #1229
Conversation
…e angle and cobbangle tool
Codecov Report
@@ Coverage Diff @@
## master #1229 +/- ##
==========================================
+ Coverage 18.71% 19.03% +0.32%
==========================================
Files 286 286
Lines 8583 8584 +1
Branches 1459 1459
==========================================
+ Hits 1606 1634 +28
+ Misses 5784 5759 -25
+ Partials 1193 1191 -2
Continue to review full report at Codecov.
|
@JamesAPetts, this doesn't change labeling from |
Any idea when this will be merged? Or is it blocked by the codeclimate issue? |
So, all checks have now passed. When could we expect the merge? |
@dannyrb some info on this? |
@JamesAPetts can we have some update on this? |
Appreciate your patience on this one. I'll merge, but may revert if someone comes forward and forces the non-square pixel argument. We may eventually want this behavior as an optional flag that can be sit when cornerstone.init() is called. |
🎉 This PR is included in version 4.15.2 🎉 The release is available on: Your semantic-release bot 📦🚀 |
@dannyrb Thank you very much! :) |
Only added in the Angle and CobbAngle tool: rowPixelSpacing and columnPixelSpacing default to 1
What kind of change does this PR introduce? (Bug fix, feature, docs update, ...)
Bug fix
What is the current behavior? (You can also link to an open issue here)
When there are no pixel spacing data of the image, the values of the angle measurements are not able to be calculated, since the getPixelSpacing function returns null for the rowPixelSpacing and columnPixelSpacing values.
What is the new behavior (if this is a feature change)?
Value 1 is used in the angle value calculation if the rowPixelSpacing and/or columnPixelSpacing values are null.
Does this PR introduce a breaking change? (What changes might users need to make in their application due to this PR?)
No.
Other information:
Default value 1 is added since in the past every tool had it, but due to some refactoring (in which the getPixelSpacing function was created), this scenario was left out.