-
Notifications
You must be signed in to change notification settings - Fork 5
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
Bugs discovery for single-cell level spatialDM #25
Comments
There is a following-up question for this step: It seems that there still exists errors and warnings for this step. Moreover, for running a spatial datasetsw ith 4,000 cells and 150,000 genes, cellphonedb is obviously faster than spatialDM (10 mins vs 16 hours), which is not consistent with the efficiency plot shown in the readme file. Are there any approaches to acclecrate spatialDM? Thanks. |
sdm.weight_matrix(adata, l=120, cutoff=0.2, single_cell=False) # weight_matrix by rbf kernel Also, I found that the parallel parameter ‘nproc=8’ can significantly reduce the processing time. |
Hi, I met same problem here even if I tried both l=120 or l=1200. I think there is lack of information for us to choose a good initial value of l and cutoff. Moreover, I need to set single_cell=True because I am handling single-cell data (like MERFISH). Also I tried to set nproc = 8, the time usage is the same as nproc =1. |
@HelloWorldLTY
is caused by applying numpy methods on csr_matrix. The following code should solve it:
|
I've been trying with VisiumHD data which now can have from 150k to 650k + spots (barcodes) so I think at this stage SpatialDM isn't quite compatible with single-cell level resolution for spatial data unfortunately |
try proposed fix according to StatBiomed#25 (comment)
Hi, I met a bug when inferring cci in image-based spatial data:
Could you please take a look? Thanks.
The text was updated successfully, but these errors were encountered: