-
Notifications
You must be signed in to change notification settings - Fork 26
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
[c++] Push-down spatial metadata in the MultiscaleImage
class from Python to C++
#3622
Conversation
Write the coordinate space metadata and spatial encoding version metadata for the `MultiscaleImage` in the C++ layer instead of the Python layer.
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.
Neat! :)
SPATIAL_ENCODING_VERSION_VAL.c_str(), | ||
true); | ||
|
||
// Set coordinate space metadata. |
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.
// Set coordinate space metadata. | |
// Set coordinat-space metadata. |
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.
I don't think coordinate space should be hyphenated.
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #3622 +/- ##
==========================================
+ Coverage 86.26% 86.28% +0.01%
==========================================
Files 55 55
Lines 6378 6378
==========================================
+ Hits 5502 5503 +1
+ Misses 876 875 -1
Flags with carried forward coverage won't be shown. Click here to find out more.
|
Co-authored-by: John Kerl <[email protected]>
Issue and/or context: sc-62102
Changes:
Write the
MultiscaleImage
coordinate-space metadata and spatial-encoding metadata in the C++ layer instead of in Python. This leaves theMultiscaleImageMetadata
properties to be addressed in a future PR.