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

Comparing Multiple Clones to Clone A and E #53

Open
gwaybio opened this issue Mar 11, 2020 · 0 comments
Open

Comparing Multiple Clones to Clone A and E #53

gwaybio opened this issue Mar 11, 2020 · 0 comments
Labels
Discussion and Notes Documenting ideas/discussions

Comments

@gwaybio
Copy link
Member

gwaybio commented Mar 11, 2020

Previously, @mekelley and @ayberman sequenced Clones A and E and observed PSMB5 mutations (see #49 (comment)).

One goal is to determine if any of the four resistant clones (BZ001, BZ002, BZ003, and BZ004) also harbors a PSMB5 mutation based on a signature of morphology. The initial approach was to see where clone A and clone E clustered in comparison to each of the four "groups" we previously observed in #25. However, those groups appear to be artifactual - see #51.

An additional wrinkle in comparing the six clones, is that there appears to be batch effects between the batches analyzed. We do not observe substantial batch effect between BZ001, BZ002, BZ003, and BZ004 clones which were measured across 3 different batches (which totaled 5 different plates) (see #48). We also do not observe substantial batch effects between the two different batches (2 total plates) that measured clone A and clone E (batch 1 and 2). See below, which was added in #52

merged_umap_clone_ae

However, we do observe batch effects when combining the two groups of data (also added in #52):

clone_compare_batch_effect

Note that we can visually inspect for batch effects in this reduced dimension space (UMAP). It is not a great way to detect batch effects, but usually when we see batches cluster separately, especially when they both contain wild-type parental profiles, it hints towards a batch effect.

The current normalization procedure calculates z-scores for all samples. We can explore if alternative normalization procedures overcomes this batch effect.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Discussion and Notes Documenting ideas/discussions
Projects
None yet
Development

No branches or pull requests

1 participant