-
Notifications
You must be signed in to change notification settings - Fork 0
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
Request for Loupe files #1
Comments
I found it hard to use the spatial data in GEO. I will glad if you share the Loupe files :) |
Hello, thanks for you message and your interest in analysing the data. Load a 10x Genomics Visium Spatial Experiment into a Seurat object LoupeR to Generate CLOUPE files from Seurat Objects Thanks! |
Seurat expects input in .h5 format, but your GEO series only provides unfiltered .mtx, making it difficult for me to use. I know this might be bothersome, but I would be immensely grateful if you could provide the original Seurat .rds format object or a standard h5 format file for generate a Seurat object. |
I am currently conducting a research project on endometriosis, and the spatial transcriptomic data presented in your article would be invaluable for my study. I was wondering if you would be willing to share the Loupe files from your analysis. Having access to these files would greatly enhance my understanding of your analytical processes and results, which would be incredibly helpful for my own research.
I assure you that the data will be kept strictly confidential and will only be used for research purposes. I will also make sure to properly cite your work in any resulting publications.
I would be immensely grateful if you could take the time to consider my request. If you are willing to share the data, please let me know, and I will promptly respond with details on how to securely transfer the files.
Thank you for your time and attention. I sincerely appreciate the significant contributions you and your team have made to the field of endometriosis research.
Best regards
The text was updated successfully, but these errors were encountered: