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

Custom cell segmentation #16

Open
vdsukhov opened this issue Jul 10, 2023 · 2 comments
Open

Custom cell segmentation #16

vdsukhov opened this issue Jul 10, 2023 · 2 comments

Comments

@vdsukhov
Copy link

Hello everyone!

I have the results of custom cell segmentation and I am able to export them in geojson format. After that, I would like to use them to update the vzg file by applying the vpt pipeline. Could you please assist me in doing so? Thank you!

@timwiggin
Copy link
Collaborator

Hi Vladimir! If you've exported the cell boundaries as a geojson file, you should be able to import them using vpt convert-geometry (documentation). There is more than one convention for representing cells in GeoJSON, convert-geometry supports the QuPath conventions (documentation). Your file may require some tweaks depending on how it was assembled.

Hope that helps!

@vdsukhov
Copy link
Author

vdsukhov commented Jul 28, 2023

Hi @timwiggin
Thank you! I finally found the time to check it. I'd like to provide a recap of the steps I performed, hoping it could be helpful to someone else.

Cell Segmentation: Initially, I used the stardist extension in QuPath to segment cells. Then, I exported the segmented cells in geojson format.

Updating the vzg File: To update the vzg file, I followed the following sequence of commands:

  1. convert-geometry: This command was used to create a new cell_boundaries parquet file.
  2. partition-transcripts: I utilized this command to generate the cell_by_gene.csv file.
  3. derive-entity-metadata: Next, I used this command to generate the cell_metadata.csv file.
  4. update-vzg: Finally, I ran this command to create/update the final vzg file.

If my steps make sense, then the issue can be considered closed.

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

2 participants