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

Support for dax file input format #7

Open
pranathivemuri opened this issue Jan 20, 2022 · 3 comments
Open

Support for dax file input format #7

pranathivemuri opened this issue Jan 20, 2022 · 3 comments
Labels
enhancement New feature or request

Comments

@pranathivemuri
Copy link

pranathivemuri commented Jan 20, 2022

New feature

Hi @krokicki! Thanks for the very well-written repo. wondering if you would add support for dax file format images that are obtained from imaging rounds from MERFISH? It seems like the pipeline currently takes in .czi and .mvl files as input

Proposal

  1. Dax file support for stitching module

Usage scenario

It could be used for the analysis of MERFISH data

Suggest implementation

@pranathivemuri pranathivemuri added the enhancement New feature or request label Jan 20, 2022
@krokicki
Copy link
Member

Hi @pranathivemuri, thanks for the suggestion, we'll definitely take it into account for a future version.

@pranathivemuri
Copy link
Author

pranathivemuri commented Jan 31, 2022

Hi @krokicki thanks for your reply. If I were to implement it, would it require changing the first module i.e registration module to be compatible, or do other steps of the pipeline expect czi, mvl formats in any way? thanks in advance for your reply!

@krokicki
Copy link
Member

@pranathivemuri, it would only require a change to the stitching module, specifically the code here: https://github.com/saalfeldlab/stitching-spark and here: https://github.com/JaneliaSciComp/multifish/blob/master/workflows/stitching.nf
Once the data is ingested and stitched, the rest of the pipeline works from that stitched N5. You might want to create an issue over in that stitching-spark repo and ask those developers how difficult it would be to add dax support.

By the way, as a workaround, if you have a different stitching process you can use for your data, you could just find a way to convert your final data into N5 format, and place that into the expected locations (e.g. outputs/acq_name/stitching/export.n5), and then use --skip stitching to run the pipeline from that point forward.

There are many ways to convert data to N5 format. If you can get your data into a TIFF series, there are two Nextflow-based TIFF to n5 converters here:
https://github.com/JaneliaSciComp/nf-demos/blob/main/n5-tools-dask/tiff-to-n5.nf
https://github.com/JaneliaSciComp/nf-demos/blob/main/n5-tools-spark/tiff-to-n5.nf

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

2 participants