Skip to content

xenium fails on imported segmentation #308

@dcjones

Description

@dcjones

The xenium function assumes there are two masks corresponding to nuclear and cell boundaries, which is true of xenium segmentation, but this not necessarily true when 3rd party segmentation is imported using the xeniumranger import-segmentation tool.

Issue is here:

If not detecting this case automatically, there should be at least a function argument to point it to the correct mask index.

(See dcjones/proseg#75)

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions