Skip to content
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

discordance between BestCall and probabilities #16

Open
LongpanUPC opened this issue Feb 1, 2023 · 2 comments
Open

discordance between BestCall and probabilities #16

LongpanUPC opened this issue Feb 1, 2023 · 2 comments

Comments

@LongpanUPC
Copy link

Hi,
a very good tool helps us classify tumors into different immune subtypes!
I run this function and get the results. in the results table, I found there are some discordances between BestCall and probabilities of belonging to each subtype. For instance, in this sample, bestcall indicates C3 subclass but C4 has higher probability. So I don't know which result I need to keep?
image

and here is the summary infomation in the series. 18 samples have these inconsistent information
image
image

Thanks in advance!

@Gibbsdavidl
Copy link
Collaborator

Gibbsdavidl commented Feb 1, 2023

Hi there,

Thanks for writing. The "best call" comes from a classifier that's trained on the C1-C6 scores, and sometimes doesn't agree with the maximum of the scores. There's a figure describing the classifier here (figure 2): https://www.biorxiv.org/content/10.1101/2020.01.17.910950v1

I would stay with BestCall.
-dave

@LongpanUPC
Copy link
Author

Hi there,

Thanks for writing. The "best call" comes from a classifier that's trained on the C1-C6 scores, and sometimes doesn't agree with the maximum of the scores. There's a figure describing the classifier here (figure 2): https://www.biorxiv.org/content/10.1101/2020.01.17.910950v1

I would stay with BestCall. -dave

thank you very much!

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

2 participants