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

What are the actual controls for the CRISPR plates? #96

Open
timtreis opened this issue Jan 31, 2024 · 5 comments
Open

What are the actual controls for the CRISPR plates? #96

timtreis opened this issue Jan 31, 2024 · 5 comments
Labels
cpg0016 faq Document this issue in an FAQ

Comments

@timtreis
Copy link

Hey everyone, we're trying to compare data across "perturbation-universes". For this, we're having a deeper look into the controls in the CRISPR plates.

Their layout is, for example, like this:
image

Chandrasekaran et al. states that:

image

By deduction, that'd mean that no-guide is DMSO. However, DMSO would be a bad control for CRISPR, since the guide RNAs, unlike drugs, are not dissolved in it but rather some transfection agent. Were these acquired to stay comparable to the other drug plates?

@yugeji

@yugeji
Copy link

yugeji commented Jan 31, 2024

Also from the paper:
image

@gewirtz
Copy link

gewirtz commented Mar 16, 2024

So to be very explicit-- are the no-guide and non-target (EXCLUDING DMSO) both used as the negative controls for the CRISPR plates?

@niranjchandrasekaran
Copy link
Contributor

Hi all, I apologize for the delayed response. The paragraph shared by @yugeji is correct. I should update the text shared by @timtreis (thank you for catching that!).

We use both no-guide and non-targeting guide wells as negative control in our analyses (we don't use DMSO).

Please let me know if you have other questions.

@shntnu shntnu added cpg0016 faq Document this issue in an FAQ labels Apr 3, 2024
@yugeji
Copy link

yugeji commented Apr 4, 2024

Okay, so to summarize, each CRISPR plate should contain:

  • 8 compounds which are positive controls also appearing in the compound plates (x4)
  • 10x no-guide (aka, absolutely no treatment)
  • 10x non-targeting guides
  • 8x DMSO
  • 4x PLK1

Given this, would it be possible to share an updated layout @niranjchandrasekaran ? The reason we brought this up is because we absolutely could not find anything labeled "DMSO" on the CRISPR plates.

Thanks very much in advance!

@niranjchandrasekaran
Copy link
Contributor

Hi @yugeji, if you use both compounds.csv.gz and crispr.csv.gz, along with well.csv.gz (all in the metadata folder), you will find the poscon compounds and DMSO wells. For example, when the run the following

well_df = pd.read_csv('metadata/well.csv.gz')
compound_df = pd.read_csv('metadata/compound.csv.gz')
crispr_df = pd.read_csv('metadata/crispr.csv.gz')

merged_df = (
    well_df.query("Metadata_Plate == 'CP-CC9-R1-03'")
    .merge(crispr_df, on="Metadata_JCP2022", how="left")
    .query(
        "Metadata_Symbol=='PLK1' or Metadata_NCBI_Gene_ID.isna()"
    )
    .merge(compound_df, on="Metadata_JCP2022", how="left")
    .assign(
        perturbation_id=lambda x: np.where(
            x.Metadata_Symbol.notna(), x.Metadata_Symbol, x.Metadata_InChIKey
        )
    )
)

merged_df.perturbation_id.value_counts()

I get

no-guide                       11
non-targeting                  10
IAZDPXIOMUYVGZ-UHFFFAOYSA-N     8
SRVFFFJZQVENJC-UHFFFAOYSA-N     4
PLK1                            4
IHLVSLOZUHKNMQ-UHFFFAOYSA-N     4
IVUGFMLRJOCGAS-UHFFFAOYSA-N     4
OINGHOPGNMYCAB-UHFFFAOYSA-N     4
GJFCONYVAUNLKB-UHFFFAOYSA-N     4
LOUPRKONTZGTKE-UHFFFAOYSA-N     4
KPBNHDGDUADAGP-UHFFFAOYSA-N     4
CQKBSRPVZZLCJE-UHFFFAOYSA-N     4
Name: perturbation_id, dtype: int64

IAZDPXIOMUYVGZ-UHFFFAOYSA-N is DMSO while the other InChIKey correspond to the 8 compounds poscons.

I should note that the number of wells in your comment is for the “median” plate. Some plates have more number of wells.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cpg0016 faq Document this issue in an FAQ
Projects
None yet
Development

No branches or pull requests

5 participants