Skip to content
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

Rework physical coordinate calculation for max_proj #1353

Merged
merged 10 commits into from
May 23, 2019

Conversation

ttung
Copy link
Collaborator

@ttung ttung commented May 15, 2019

This is based on top of #1352 and #1291. The most likely path for this to get merged is for #1352 (and its supporting PRs) to land, rebase #1291 on top of master, and merging this all in.

@ttung ttung requested a review from shanaxel42 May 15, 2019 08:38
@ttung ttung force-pushed the tonytung-max-proj-coords branch from b7d02f9 to 8a9eb81 Compare May 15, 2019 08:38
@codecov-io
Copy link

codecov-io commented May 15, 2019

Codecov Report

Merging #1353 into master will increase coverage by 0.01%.
The diff coverage is 100%.

Impacted file tree graph

@@            Coverage Diff            @@
##           master   #1353      +/-   ##
=========================================
+ Coverage   89.19%   89.2%   +0.01%     
=========================================
  Files         148     148              
  Lines        5368    5374       +6     
=========================================
+ Hits         4788    4794       +6     
  Misses        580     580
Impacted Files Coverage Δ
starfish/core/imagestack/imagestack.py 94.06% <100%> (+0.1%) ⬆️

Continue to review full report at Codecov.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 8af3e83...ebd6b99. Read the comment docs.

@ttung ttung force-pushed the tonytung-max-proj-coords branch 2 times, most recently from 7c80afe to 753d5dc Compare May 15, 2019 20:36
@ttung ttung force-pushed the tonytung-max-proj-coords-base branch from 39c5fb0 to 25548ab Compare May 15, 2019 20:38
@ttung ttung force-pushed the tonytung-max-proj-coords branch 2 times, most recently from 1234dbb to 65e59eb Compare May 15, 2019 23:53
@ttung ttung force-pushed the tonytung-max-proj-coords-base branch from 3c72c4f to 9de6573 Compare May 15, 2019 23:54
@ttung ttung force-pushed the tonytung-max-proj-coords branch 2 times, most recently from 2068103 to 691c9a1 Compare May 16, 2019 18:42
@ttung ttung force-pushed the tonytung-max-proj-coords-base branch from 4f72039 to e31b3ba Compare May 20, 2019 21:42
@ttung ttung force-pushed the tonytung-max-proj-coords branch 3 times, most recently from ee3ac61 to bc7b6b1 Compare May 21, 2019 18:35
Tony Tung added 3 commits May 23, 2019 11:14
This is based on top of #1352 and #1291.  The most likely path for this to get merged is for #1352 (and its supporting PRs) to land, rebase #1291 on top of master, and merging this all in.
@ttung ttung force-pushed the tonytung-max-proj-coords branch from bc7b6b1 to ebd6b99 Compare May 23, 2019 18:14
@ttung ttung changed the base branch from tonytung-max-proj-coords-base to master May 23, 2019 18:16
@ttung
Copy link
Collaborator Author

ttung commented May 23, 2019

Now that #1352 has landed, I'm rebasing this on master. It should contain all the contents of #1291 and the current #1353.

@ttung ttung merged commit 6a86c67 into master May 23, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants