-
Notifications
You must be signed in to change notification settings - Fork 4
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
Hexagonal spatial bins #3
Comments
Thank you @lambdamoses for a great question/suggestion! Since we observed consistent SVG results with rotation-based permutations (rotate the x,y coordinates of the dataset prior to applying SEraster), we believe using a hexagonal grid rather than a square grid would not significantly affect the SVG results. We would love to know if there is a case in which a hexagonal grid offers an advantage over a square grid! If you would like to further explore, we implemented the This feature was added in the following commit. We are currently working on |
This feature was added in the following commit. Since |
For SFE, we've added functionalities to deal with smFISH transcript spot geometries. I think when those are available, the spatial binning should use the transcript spots rather than the cell coordinates, because transcript spots are not uniformly distributed within cells. Also, I'm debating what to do with Visium spot and cell polygons that sit at the boundary of two spatial bins during spatial binning when transcript spots are not available. Maybe assume uniform distribution and distribute the UMI or transcript spot counts proportionally with the area of overlap. I have long had the idea of adding general spatial binning or aggregation with any kind of geometry (including but not limited to spatial grids) to the SFE package itself. If you implement it in your package, then I'll simply suggest your package in SFE. |
I saw your paper on bioRxiv. Just wondering, what if you use a hexagonal grid rather than a square grid? How would it affect the SVG results?
The text was updated successfully, but these errors were encountered: