-
Notifications
You must be signed in to change notification settings - Fork 1
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
feat: floe labeling #347
feat: floe labeling #347
Conversation
- Update notebook
Check out this pull request on See visual diffs & provide feedback on Jupyter Notebooks. Powered by ReviewNB |
Codecov ReportAll modified lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## main #347 +/- ##
==========================================
- Coverage 91.84% 90.46% -1.39%
==========================================
Files 29 29
Lines 871 902 +31
==========================================
+ Hits 800 816 +16
- Misses 71 86 +15
☔ View full report in Codecov by Sentry. |
src/tracker/tracker.jl
Outdated
Tag floes in the `data.props` by assigning a unique `Floe_ID`` to each floe in each image using pair data in `pairs`. The ID is stored in the `Floe_ID` column of the `props` DataFrame in `data`. | ||
|
||
# Arguments | ||
- `data::Data`: the data structure containing the images and properties of the floes (output of `IFTPipeline.extractfeatures`). The `props` field of `data` is modified in-place. |
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.
- `data::Data`: the data structure containing the images and properties of the floes (output of `IFTPipeline.extractfeatures`). The `props` field of `data` is modified in-place. | |
- `floedata::Data`: the data structure containing the images and properties of the floes (output of `IFTPipeline.extractfeatures`). The `props` field of `data` is modified in-place. |
src/tracker/tracker.jl
Outdated
""" | ||
tagfloes!(floedata, pairs) | ||
|
||
Tag floes in the `data.props` by assigning a unique `Floe_ID`` to each floe in each image using pair data in `pairs`. The ID is stored in the `Floe_ID` column of the `props` DataFrame in `data`. |
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.
Tag floes in the `data.props` by assigning a unique `Floe_ID`` to each floe in each image using pair data in `pairs`. The ID is stored in the `Floe_ID` column of the `props` DataFrame in `data`. | |
Tag floes in the `data.props` by assigning a unique `Floe_ID` to each floe in each image using pair data in `pairs`. The ID is stored in the `Floe_ID` column of the `props` DataFrame in `data`. |
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.
This looks good so far. I just added a comment about updating the docstring so that the arguments match the names used in function itself.
src/tracker/tracker.jl
Outdated
- `data::Data`: the data structure containing the images and properties of the floes (output of `IFTPipeline.extractfeatures`). The `props` field of `data` is modified in-place. | ||
- `pairs`: the output of `pairfloes`. | ||
""" | ||
function tagfloes!(props, pairs) |
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.
Here the first arg is props
, but in the docstring it is floedata
. Maybe update the docstring so it is consistent?
Using a different implementation using early tagging and mappings for relabeling. |
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.
Everything looks good, reviewed in person during weekly sync meeting.
@danielmwatkins @ellenbuckley See
notebooks/track-floes/track-floes.ipynb
for a complete sample workflow with test data.TODO: Update
track
inhttps://github.com/WilhelmusLab/ice-floe-tracker-pipeline/blob/main/src/tracker.jl
so it does floe labeling.#339