-
Notifications
You must be signed in to change notification settings - Fork 68
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
Allow for intensity tables with labeled axes #1181
Conversation
6c2d2d2
to
608812d
Compare
Codecov Report
@@ Coverage Diff @@
## master #1181 +/- ##
==========================================
- Coverage 88.52% 88.29% -0.23%
==========================================
Files 133 134 +1
Lines 4976 5008 +32
==========================================
+ Hits 4405 4422 +17
- Misses 571 586 +15
Continue to review full report at Codecov.
|
e7c8dbd
to
a2f6818
Compare
3de5f0e
to
fe6b3bf
Compare
a2f6818
to
f449151
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.
Great change, thanks. See one question below.
2c3b2f8
to
cad0b89
Compare
ymin = crop_y | ||
xmin = crop_x | ||
zmax = image_stack.shape['z'] - crop_z | ||
zmax = image_stack.axis_labels(Axes.ZPLANE)[-crop_z - 1] |
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.
-crop_z - 1 this is weird, what value is this?
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.
So this is to allow for cropping from the maximum zlayer. crop_z=0 => zmax=-1 (i.e., last plane). crop_z=1 => zmax=-2 (i.e., second to last plane).
097ebde
to
c7328da
Compare
a74f9ae
to
4062d6f
Compare
8d3311a
to
74be1d7
Compare
Currently, we use the offset of r/c/z to label the axes on the intensity table. We should instead be using the axes labels from the ImageStack. This PR makes that change in three key areas: 1. `IntensityTable.empty_intensity_table` now accepts the labels for the axes. 2. `IntensityTable.from_spot_data` now accepts the labels for the axes and verifies that the number of labels matches the intensity data. 3. `IntensityTable.from_image_stack` reads the labels for the zplane axes and assigns them correctly. Test plan: Add a test that instantiates a labeled ImageStack and derives an IntensityTable from it. Also ran `make test && make -j run-notebooks`. Depends on #1178 Fixes #1168
74be1d7
to
bd6e533
Compare
Currently, we use the offset of r/c/z to label the axes on the intensity table. We should instead be using the axes labels from the ImageStack. This PR makes that change in three key areas:
IntensityTable.empty_intensity_table
now accepts the labels for the axes.IntensityTable.from_spot_data
now accepts the labels for the axes and verifies that the number of labels matches the intensity data.IntensityTable.from_image_stack
reads the labels for the zplane axes and assigns them correctly.Test plan: Add a test that instantiates a labeled ImageStack and derives an IntensityTable from it. Also ran
make test && make -j run-notebooks
.Depends on #1178
Fixes #1168