Skip to content

Cell cycle scoring aproach #728

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

Closed
Xcubitor opened this issue Aug 22, 2018 · 4 comments
Closed

Cell cycle scoring aproach #728

Xcubitor opened this issue Aug 22, 2018 · 4 comments

Comments

@Xcubitor
Copy link

Hello,

I was wondering how the cell cycle scoring command operates. Meaning, that are the steps that are undertaken in order to come up with the scores for each cell?

thanks :-)

@orrzor
Copy link

orrzor commented Aug 23, 2018

@Xcubitor
Copy link
Author

Thanks orrzor :-) I did but the vignette doesn't really explain how the data from the gene sets is pulled together and how the scores are computed.

@satijalab
Copy link
Collaborator

As we say in the vignette, the scores are computed using an algorithm developed by Itay Tirosh, when he was a postdoc in the Regev Lab (Science et al., 2016). The gene sets are also taken from his work.

You can read the methods section of https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4944528/ to see how the scoring works, but essentially- the method scores cells based on the expression of each gene in a signature set - after controlling for the expected expression of genes with similar abundance.

@ChelseaCHENX
Copy link

Does the Seurat object need to be normalized and scaled before applying cell cycle scoring? If not, would this function automatically do normalization/scaling?

yuhanH added a commit that referenced this issue Mar 29, 2023

Verified

This commit was created on GitHub.com and signed with GitHub’s verified signature. The key has expired.
Feat/s5 transfer anchors
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants