You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Hello,
I ran Baysor v0.7, and tried to import the segmentation results with xeniumranger 3.1 import-segmentation. I followed the steps explained in 10x website, and made sure the files format (geojson GeometryCollection) was correct. Each cell in the polygons.geojson have more than 4 vertices.
However, few cells have a different polygon shape after running xeniumranger import segmentation. Some cells end up having less than 4 vertices, which cause the python reader of the package I am using (spatialdata) to fail, because polygons needs to have at least 4 vertices. I am wondering if you know what could be the origin of this, maybe an issue the polygons.geojson file or in the segmentation.csv ?
Thank you very much !
The text was updated successfully, but these errors were encountered:
That is very curious. Is it possible for you to provide one of the problematic polygons? (e.g., one that had more than 4 vertices and which had less than 4 vertices in the outputs.)
One scenario that comes to mind where this could happen is if the polygon is actually 2D. For example, something like:
Hello,
I ran Baysor v0.7, and tried to import the segmentation results with xeniumranger 3.1 import-segmentation. I followed the steps explained in 10x website, and made sure the files format (geojson GeometryCollection) was correct. Each cell in the polygons.geojson have more than 4 vertices.
However, few cells have a different polygon shape after running xeniumranger import segmentation. Some cells end up having less than 4 vertices, which cause the python reader of the package I am using (spatialdata) to fail, because polygons needs to have at least 4 vertices. I am wondering if you know what could be the origin of this, maybe an issue the polygons.geojson file or in the segmentation.csv ?
Thank you very much !
The text was updated successfully, but these errors were encountered: