-
Notifications
You must be signed in to change notification settings - Fork 59
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
Unrecognized zarr version for example dataset in tutorial #863
Comments
Thanks @keviny2 for reporting. There was a misconfiguration in the pipeline that we use to generate and upload the datasets and a dev version of the package was used. I now re-run the job that is converting and uploading the datasets, so in 1-2 hours you should be able to download the correct datasets. The format will be bumped at the next release of CC @berombau |
Great. Thanks @LucaMarconato ! |
I got the same error for another two example datasets, Visium dataset, Xenium dataset, can you kindly regenerated them as well? @LucaMarconato , Many thanks! BTW this package is fantastic! Thank you all for creating such an amazing tool! |
@stevenhuakui thanks for the kind feedback, and for reporting. You are right, those two datasets are from a notebook that I didn't re-run. Now when the conversion job will conclude, all the datasets should be consistent. |
Perfect! Thanks @LucaMarconato ! |
i get the same error, when use the The link to the example dataset (https://s3.embl.de/spatialdata/spatialdata-sandbox/mouse_liver.zip) |
@zhangj1115 thanks for reporting. The same problem reoccurred. It will be fixed in a few hours. I will make a release soon, which will address the issue at the root by providing a version of the library that is able to read the updated uploaded data. |
I get an error when I load the example
.zarr
as aSpatialData
object in the tutorial. The link to the example dataset (https://s3.embl.de/spatialdata/spatialdata-sandbox/mouse_liver.zip) uses an unrecognized Version 0.6-dev. Here is the last part of the stack trace:The text was updated successfully, but these errors were encountered: