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

Better encoding of what's imaged in each channel #375

Open
vreuter opened this issue Nov 20, 2024 · 1 comment
Open

Better encoding of what's imaged in each channel #375

vreuter opened this issue Nov 20, 2024 · 1 comment
Assignees
Milestone

Comments

@vreuter
Copy link
Collaborator

vreuter commented Nov 20, 2024

Right now, the parameters config file has hooks for specifying which channel's nuclei and which channel is FISH. But with #337 , we'd like a way to encode what's imaged in each channel in a more flexible way.

@vreuter vreuter added enhancement New feature or request brainstorming labels Nov 20, 2024
@vreuter
Copy link
Collaborator Author

vreuter commented Nov 20, 2024

Here's a snippet from ZARR metadata (.zattrs)...

    "metadata": {
        "channel_0": {
            "emissionLambdaNm": 450.5,
            "excitationLambdaNm": 365.0,
            "name": "DAPI"
        },
        "channel_1": {
            "emissionLambdaNm": 630.0,
            "excitationLambdaNm": 561.0,
            "name": "Red"
        },
       ...

So, the user could map channel index (0, 1, etc.) to a biological entity like "nucleus" or "fiducials", or could perhaps map "DAPI", "Red", etc. to those values. Need to think on this. Indices may be simpler since o/w the user would need to know what was captured and stored in the raw Nikon (or other camera) format.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants