-
Notifications
You must be signed in to change notification settings - Fork 579
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
Test case failure with test_visium_default not having any visible data points #2048
Comments
How are you building the package and running the tests? Are you working with a clone of the repo? |
I downloaded the github source archive at the 1.8.2 tag. The build process applies a few patches viewable here. One is a small change to some R code, and the other is I marked several more tests as needs internet because the Debian builds in an environment without network access and those ultimately tried to download something. (And it's really unclear if we can legally redistributed the 10x pbmc3k dataset.) The Debian build file is (here)[https://salsa.debian.org/med-team/python-scanpy/-/blob/master/debian/rules] though mostly it lets you see what tests I was skipping because of missing dependencies. Also if I set a color like in_tissue, or array_row the data shows up. I can paste the full build log if you'd like but this is the dependencies installed and the environment variables.
|
I can get the data by skipping the spatial plot. If I run this in a fresh IPython session I get the attached plot.
If I call scanpy.pl.spatial before I call pyplot.scatter I get the black plot, so it's probably some default isn't right. |
Hello, I was trying to build a Debian package for scanpy 1.8.2, and unsurprisingly ran into problems with the plot tests. Most of the problems were just slight plot layout differences, but the test_embedding_plots::test_visium_default test ends up generating a blank plot.
I can get something where the dots are visible by setting a color, but the color bar doesn't match the default.
I also tried add_outline=True which got me closer but is still not right, and still pretty hard to see.
I tried adjusting the marker size but didn't get very far. do you have any guesses what might be wrong?
Thanks
anndata 0.7.5+ds
scanpy 1.8.2
sinfo 0.3.1
PIL 8.3.2
anndata 0.7.5+ds
asciitree NA
beta_ufunc NA
binom_ufunc NA
cycler 0.10.0
cython_runtime NA
dateutil 2.8.1
fasteners NA
h5py 3.3.0
igraph 0.9.6
joblib 0.17.0
kiwisolver 1.3.2
leidenalg 0.8.8
llvmlite 0.35.0
matplotlib 3.3.4
monotonic NA
mpl_toolkits NA
natsort 7.1.0
nbinom_ufunc NA
numba 0.52.0
numcodecs 0.8.1+ds
numexpr 2.7.3
numpy 1.19.5
packaging 21.0
pandas 1.1.5
pkg_resources NA
pyexpat NA
pyparsing 2.4.7
pytoml NA
pytz 2021.3
scanpy 1.8.2
scipy 1.7.1
setuptools_scm NA
sinfo 0.3.1
sitecustomize NA
six 1.16.0
sklearn 0.23.2
tables 3.6.1
texttable 1.6.3
zarr 2.10.2+ds
Python 3.9.8 (main, Nov 7 2021, 15:47:09) [GCC 11.2.0]
Linux-5.14.0-2-amd64-x86_64-with-glibc2.32
4 logical CPU cores
Session information updated at 2021-11-10 22:03
The text was updated successfully, but these errors were encountered: