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
Upload example of transforming raw MERFISH -> spaceTx formatted data #478
Conversation
@joshmoore -- take a look at the raw tiff files on s3. I suspect there's metadata in them that can be used to obviate my explicit map. also curious what you think! will work on an nd2 example shortly. |
Codecov Report
@@ Coverage Diff @@
## master #478 +/- ##
=======================================
Coverage 84.56% 84.56%
=======================================
Files 73 73
Lines 2812 2812
=======================================
Hits 2378 2378
Misses 434 434 Continue to review full report at Codecov.
|
i.e. if the input files had been named as above with the one extra file, the FOV writer would have generated the same output (assuming my code is correct, which I'll now verify...) You stopped at 16 (154 MB) of the 496 (71 GB) TIFFs to just get this working ASAP? (Or is something else going on? S3 didn't contain an XLS for cross-checking.)
I did some digging, @dganguli, but didn't find any metadata. Do you know anything about the provenance of these files? |
With the last commit on spacetx-fov-writer and ignoring file names and checksums, here's the diff:
|
@joshmoore You work fast. 😮 |
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.
Would love a bit of clarification on a comment, otherwise this looks good. Thanks @dganguli !
class MERFISHTile(FetchedTile): | ||
def __init__(self, file_path, hyb, ch): | ||
self.file_path = file_path | ||
# how to index tiles from indices into multi-page tiff |
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 want to make sure I'm clear on what this means:
# maps information on the acquisition channel and round to an index that identifies the correct page in the original multi-page tiff 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.
so each fov_00x.tiff loads into numpy as a 18X2048X2048 array. that first axis corresponds to some round and color channel. the map dictates how to index into that first axis based on the round/channel you want.
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.
16 rounds + dapi + ___ ?
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.
failed attempt at a membrane stain
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.
Thanks.
You guys have to sleep at some point! |
Says who? :-) |
I did some digging, @dganguli, but didn't find any metadata. Do you know anything about the provenance of these files? Really? Nothing fun embedded in the tiffs? I do not know anything about the provenance of these files. |
You stopped at 16 (154 MB) of the 496 (71 GB) TIFFs to just get this working ASAP? (Or is something else going on? S3 didn't contain an XLS for cross-checking.) Oops the 16 is a bug. Fixing. I'll also add the XLS to s3. |
@joshmoore : s3://czi.starfish.data.public/browse/raw/20180820/merfish_u2os/data_organization.xlsx is the xls file to check against. |
Cheers. |
My guess is going to be that the generating MATLAB script didn't store anything. For those following along, here's the contents of the spreadsheet:
|
With:
I was able to validate the output of this PR:
|
@dganguli @ttung : |
Remaining work includes: