-
Notifications
You must be signed in to change notification settings - Fork 31
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
Handle Situation where V1 Visium tissue_positions_list.csv
Has a Header
#146
Comments
Hi @jeffquinn-msk @inodb, thanks for reporting. Do you know any publicly available dataset that presents this structure? |
To reproduce I am taking the visium_1.3.0_io dataset from the sandbox and replacing the |
Btw, this issue reminds me of this one (Xenium), where data processed with an old version of Xenium Onboard Analysis is partly reprocessed with a recent version of SpaceRanger, creating confusion when parsing. Anyway, the case that you reported seems easy to address, I'll work on a fix now. |
Hi made a fix in the linked PR. Some details:
|
Fixes header bug Visium data #146
…header Fixes header bug Visium data scverse#146
I've been given a new dataset where the positions file is in the V1 location
spatial/tissue_positions_list.csv
, but it has a header. Really annoying I know. This ends up causing an exception in the Visium loader as the coordinates are loaded as string type bypandas
. You might see similar data eventually as well I'm guessing..Could we add something to the code to check for header in both locations? This is the function I wrote to deal with this:
The text was updated successfully, but these errors were encountered: