Where should `sc.datasets` put data?
See original GitHub issueI’m adding that expression atlas downloader now (#489), and wondering where the files should go.
pbmc68k_reduced
and toggleswitch
put the datasets relative to where scanpy is installed (via __file__
). All other functions place the data relative to where the python process was started.
While I like not storing the same files all over a filesystem, I’m not sure in the scanpy
installation directory is the right place to be storing data.
Thoughts?
Issue Analytics
- State:
- Created 4 years ago
- Comments:26 (25 by maintainers)
Top Results From Across the Web
Where should `sc.datasets` put data? · Issue #558 - GitHub
Hi Isaac, I have a related question: does your expression atlas downloader also store the coordinate and all the meta data?
Read more >scanpy_03_integration
First need to load the QC filtered dataset and create individual adata objects per batch. ... As the stored AnnData object contains scaled...
Read more >Import spatial data in AnnData and Squidpy - Read the Docs
This tutorial shows how to store spatial datasets in anndata.AnnData . ... In this tutorial, we will showcase how spatial data are stored...
Read more >Online update of scvi-tools models with query datasets
It could have also been the case that only some of the protein data was missing, in which case we would add zeros...
Read more >How to load GEO datasets for analysis using Scanpy / Scvi ...
I have a question about data export from GEO to scanpy object. ... So I want to ask how can I transformGSE81608 dataset...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
The scanpy install directory is super wrong, as it’s not writable for many people.
There’s exactly one correct way of determining a global place for cache* files like this:
appdirs.user_cache_dir(...)
Alex and me talked in the past and decided for a visible directory in the working directory. I’d be up for changing it to
user_cache_dir(…)
for the data.*the data are cache files since reexccuting their function after deleting the files will redownload them without loss of information.
All good, thank you for your work!