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

[Bug] sopa-v1.0.14 errors on Xenium v2 + multimodal cell segmentation data but not dapi-only data #80

Closed
sooheelee opened this issue Jun 8, 2024 · 8 comments

Comments

@sooheelee
Copy link

sooheelee commented Jun 8, 2024

Bonjour. This is my first time running sopa. I found both sopa-v1.0.14 and v1.0.13 errors on Xenium v2 pipeline data that includes multimodal cell segmentation stains but not on v2 pipeline data that uses only DAPI. The error is

ValueError: cannot reindex or align along dimension 'c' because of conflicting dimension sizes: {16, 4}

Full stack-trace: sopa-1.0.14-read-error-20240607.txt

Using the DAPI-only v2 data succeeds and gives the stdout:

SpatialData object with:
├── Images
│     └── 'morphology_focus': MultiscaleSpatialImage[cyx] (1, 3553, 5791), (1, 1776, 2895), (1, 888, 1447), (1, 444, 723), (1, 222, 361)
└── Points
      └── 'transcripts': DataFrame with shape: (<Delayed>, 11) (3D points)
with coordinate systems:
▸ 'global', with elements:
        morphology_focus (Images), transcripts (Points)

Both data sets are public, small and at https://www.10xgenomics.com/support/software/xenium-onboard-analysis/latest/resources/xenium-example-data.

Command was sopa read Xenium_V1_human_Lung_2fov_outs --technology xenium --sdata-path sopa for the latter.

Given the discussion in #68, expected read function to work. May be I am missing something? Thanks in advance for your help.

  • OS: macOS Ventura 13.6.3
  • Python 3.9.13
@quentinblampey
Copy link
Collaborator

quentinblampey commented Jun 9, 2024

Hello @sooheelee, thanks for the detailed issue. I'm aware of this issue, and it has been fixed in spatialdata-io, but I'm waiting for a release of spatialdata-io with a specific PR (scverse/spatialdata-io#151) to update sopa. It should come in one or a few weeks, I'll let you know!

@sooheelee
Copy link
Author

Thank you.

@littleju777
Copy link

Hi, I also met the same issue with multimodal cell segmentation data. I noticed that the tutorials were mostly wrote for Xenium with DAPI data, do you find methods work perfectly with multimodal data? Maybe using Xenium results + baysor would be better for Xenium V2.0 data. Do you have any updates? Thank you!

@quentinblampey
Copy link
Collaborator

Hi @littleju777, I haven't checked the multimodal segmentation yet. But indeed it may be better to use the Xenium results as a prior for Baysor, I will try to add this!

@littleju777
Copy link

Hi @littleju777, I haven't checked the multimodal segmentation yet. But indeed it may be better to use the Xenium results as a prior for Baysor, I will try to add this!

Thank you!

@quentinblampey
Copy link
Collaborator

Hi @sooheelee, I released sopa==1.1.1, which should fix this. Can you try and let me know?

And @littleju777 you can now use the multimodal segmentation as a prior for baysor. I provided a baysor config for snakemake, or you can also look at the FAQ here if you prefer using the CLI/API.

@littleju777
Copy link

Hi @sooheelee, I released sopa==1.1.1, which should fix this. Can you try and let me know?

And @littleju777 you can now use the multimodal segmentation as a prior for baysor. I provided a baysor config for snakemake, or you can also look at the FAQ here if you prefer using the CLI/API.

Thank you for the amazing work!

@quentinblampey
Copy link
Collaborator

You're welcome! I'm closing the issue, feel free to re-open if needed

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

No branches or pull requests

3 participants