-
Notifications
You must be signed in to change notification settings - Fork 70
[2/2] label image target assignment #709
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
Conversation
@@ -5,7 +5,6 @@ numpy != 1.13.0 | |||
pandas >= 0.23.4 | |||
pycodestyle<2.4.0 | |||
pytest>=3.6.3 | |||
regional |
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.
Until a make target is in place to keep everything in sync, either a josh-ping on requirement changes or a modification of environment.yml
would be appreciated.
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.
Is there a way to automatically source the requirements in environment.yml
from a file?
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.
There is, but it likely changes the purpose of this. As it stands, the file reproduces what will be installed by using conda install -c bioconda starfish
. If it sources requirements, it will match (far better) the current source code. I haven't found a way for bioconda's meta.yaml to just re-use some existing definition. I can add the generation code for bioconda to spacetx/starfish
though. Thoughts on a make release
target?
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.
What do you envision in a make release
target?
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.
- run extended
check_requirements
to sync conda - bump version number
- commit, tag, push tag
- add
.dev
to version number, commit, and push to master - build package and push to pypi
- build docker and push to hub
- generate and push commit to bioconda-recipes (and potentially open a PR)
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.
migrated to #761
409cb0a
to
f4fe64d
Compare
Codecov Report
@@ Coverage Diff @@
## ajc-segmentation-modernization #709 +/- ##
==================================================================
- Coverage 86.25% 85.18% -1.07%
==================================================================
Files 123 115 -8
Lines 4445 3956 -489
==================================================================
- Hits 3834 3370 -464
+ Misses 611 586 -25
Continue to review full report at Codecov.
|
@@ -5,7 +5,6 @@ numpy != 1.13.0 | |||
pandas >= 0.23.4 | |||
pycodestyle<2.4.0 | |||
pytest>=3.6.3 | |||
regional |
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.
Is there a way to automatically source the requirements in environment.yml
from a file?
coordinates = r.coordinates | ||
return [make_dict(id_, verts) for id_, verts in enumerate(coordinates)] | ||
print(f"Writing label image to {args.output}") | ||
imsave(args.output, label_image) |
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 bit concerned that our output format for this stage is a numpy array...
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 believe an array is the field standard. We could wrap this up in an xarray. The image should have x, y, and z, as well as corresponding coordinates.
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 warrants discussion, but should be done in a follow-up PR. #724
4c73dc1
to
d8430bf
Compare
8d48ba3
to
ee99c02
Compare
Note: rename propagated to docs in #886 |
This PR:
TargetAssignment.Label
to do assignment using a label imagePointInPoly2D
regional
dependencyTesting plan:
ISS Image:
TargetAssignment.Label
TargetAssignment.Label
This identifies an obvious problem with our segmentation approach, but assignment appears to be working.
Test code, can be run at end of ISS notebook: