-
Notifications
You must be signed in to change notification settings - Fork 23
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
Severe batch effect after denoising. #16
Comments
I think it might be because you trained STAGATE for each section individually. In this scenario, we recommend concatenating the spatial networks of different sections together and processing them with the same STAGATE model. For you question, we added two additional tutorials to introduce how STAGATE work for multiple sections (with or without batch effects). See https://stagate.readthedocs.io/en/latest/AT1.html and https://stagate.readthedocs.io/en/latest/AT2.html for details. By the way, recently, we extended our STAGATE to identify spatial domains on multiple sections, and designed a new algorithm STAligner, which may be online within a month. : ) |
Thanks for your reply~ And I am really looking forward to your new algorithm:) |
Hi, now I've solved the batch effect through your new tutorial:) |
In my opinion, the denoised results are only used to view gene expressions. Actually, like other denoising or imputation methods (like MAGIC or scVI), the return matrix of STAGATE is a dense matrix, which may lead the p-value of DE-analysis get lower, giving many false positives. |
Got your point, thanks~ |
Hi, I have tested SPAGATE-tensorflow on 2 replicates(2 slices) of one stage, but when I load the denoised count matrices into Seurat, I found severe batch effect than raw count matrices.
Can you give some advice on it?
The text was updated successfully, but these errors were encountered: