-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add transformation (world-to-voxel) #5
Conversation
Codecov Report
Additional details and impacted files@@ Coverage Diff @@
## main #5 +/- ##
=========================================
Coverage 100.00% 100.00%
=========================================
Files 3 6 +3
Lines 83 133 +50
=========================================
+ Hits 83 133 +50
|
- added hypothesis['numpy'] to create numpy arrays for strategies - add world2voxel function - add error checks for invalid combinations - add test cases - simplified padding (from original) to apply to just a single voxel
fac0999
to
f5f2465
Compare
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.
Fundamentally this looks good, just want to nail down the spec for the transformation function a little and improve some of the testing
55ede7d
to
eb765a5
Compare
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.
A couple of little things related to the test
91088c8
to
b4c6070
Compare
- generate values to draw from and compose affine transform with for scaling, rotation and translation components - permutate though scaling, rotation, and translation matrices to give more variance in the affine - also add transforms as a component to codecov - quality fixes - rename codecov components to reflect paths
Proposed changes
Probably the last "small" PR, adding in the transformation from world to voxel coordinates. The affine matrix had to separately constructed by the values generated (to create a valid matrix).
Note: I updated the
codecov
component names to reflect the paths of the files / modules, should be updated in the next PR if it does not show up in this one.Types of changes
What types of changes does your code introduce? Put an
x
in the boxes that applyChecklist
Put an
x
in the boxes that apply. You can also fill these out after creating the PR. If you are unsure about any of the choices, don't hesitate to ask!poe quality
taskNotes
All PRs will undergo the unit testing before being reviewed. You may be requested to explain or make additional changes before the PR is accepted.