-
Notifications
You must be signed in to change notification settings - Fork 33
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
Gene set scores correlate w/ cell content #86
Comments
You're correct - the I see you're using a Seurat object as input - what preprocessing steps had you run so far on that object? Are all the genes present, or has it been filtered yet? I think this might be related to the |
Hey David--sorry about the delay. Just had a change to revisit this. Here are some details to help explore this further So yes, I started with a seurat object comprising a "pure" population of cancer cells with the goal of using Vision for scoring and calculating autocorrelation. Given the purity of the population, I reasoned that I would expect meaningful genes to be detected in at least 5% of cells, so increased the Previous run with
Now re-running with default
Doesn't seem to improve the issue. Looked at the distribution of the scores: And then the relationship between mean score and how much the signature correlated with UMI (thinking that maybe it was only when scores were low or something) In case you want to look at this specific example, I've uploaded this Seurat object and the hallmark gene set to a Google Drive you can access here
|
Hi there. Thanks for the work on this package! I love the incorporation of autocorrelation.
I've been looking into the scores produced by Vision (seurat object as input) and have found that that scores correlate fairly well with total UMI counts.
I noticed that my signatures were all correlating with each other, so I checked their correlation with total UMI per cell and found that many correlate well
And this seems to be a related to the total size of the signature:
I only mention this because I believe the default
sig_norm_method
is supposed to deal with thisThe text was updated successfully, but these errors were encountered: