Before running the gDR pipeline, it is essential to annotate the data properly with drug and cell line information. This document outlines the process of data annotation and the requirements for the annotation files.
gDR uses two sources of annotation: drug annotation and cell line annotation. These annotations are added to a data table before running the pipeline. The scripts for adding data annotation are located in R/add_annotation.R
, which contains two functions: add_CellLine_annotation
and add_Drug_annotation
. It is recommended to run the cleanup_metadata
function, which adds annotations and performs some data cleaning.
Both drug and cell line annotation files are stored in gDRtestData/inst/annotation_data
. There are two files:
cell_lines.csv
drugs.csv
Users can edit these files to add their own annotations. After updating, it is required to reinstall gDRtestData
to use the new annotations.
Alternatively, users can use other annotation files stored outside of this package. For this purpose, it is necessary to set two environmental variables:
GDR_CELLLINE_ANNOTATION
: Represents the path to the cell line annotation CSV file.GDR_DRUG_ANNOTATION
: Represents the path to the drug annotation CSV file.Sys.setenv(GDR_CELLLINE_ANNOTATION = "some/path/to/cell_line_annotation.csv")
Sys.setenv(GDR_DRUG_ANNOTATION = "some/path/to/drug_annotation.csv")
NOTE: gDR annotation can be sourced from different locations. Setting environmental variables with paths for annotation has the highest priority and will be used as the first source of annotation, even if other sources are available. To clarify, if both the environmental variables and the internal annotation databases are set, gDR will prioritize the environmental variables for annotation.
To turn off the usage of external paths for data annotation, please set these two environmental variables to empty.
Sys.setenv(GDR_CELLLINE_ANNOTATION = "")
Sys.setenv(GDR_DRUG_ANNOTATION = "")
gDR has specific requirements for the annotation files to properly annotate the data.
The obligatory fields for drug annotation are:
gnumber
: Represents the ID of the drug.drug_name
: Represents the name of the drug.drug_moa
: Represents the drug mechanism of action.The obligatory fields for cell line annotation are:
cell_line_identifier
: Represents the cell line ID.cell_line_name
: Represents the name of the cell line.primary_tissue
: Represents the primary tissue of the cell line.doubling_time
: Represents the doubling time of the cell line in hours.parental_identifier
: Represents the name of the parental cell line.subtype
: Represents the subtype of the cell line.If some information is not known for the cell line or drug, the corresponding field should be left empty or NA. Nonetheless, since the fill parameter is consistently specified in the annotation function, the default value of ‘unknown’ can be altered by the user.
To illustrate, here’s an example of how to create a data.table
with the required fields for drug and cell line annotation:
# Example of creating a data.table with required fields for drug annotation
drug_annotation <- data.table(
gnumber = c("G1", "G2", "G3"),
drug_name = c("Drug A", "Drug B", "Drug C"),
drug_moa = c("MOA A", "MOA B", "MOA C")
)
# Example of creating a data.table with required fields for cell line annotation
cell_line_annotation <- data.table(
cell_line_identifier = c("Cell_Line_1", "Cell_Line_2", "Cell_Line_3"),
cell_line_name = c("Cell Line 1", "Cell Line 2", "Cell Line 3"),
primary_tissue = c("Tissue A", "Tissue B", "Tissue C"),
doubling_time = c(24, 30, 28),
parental_identifier = c("Parental 1", "Parental 2", "Parental 3"),
subtype = NA
)
For users within Genentech/Roche, we recommend utilizing our internal annotation databases. We provide the gDRinternal
package specifically for internal users, which includes functions for managing internal annotation data. If you are an internal user, you can install the gDRinternal
package, and gDRcore
will automatically utilize this package as a source of data annotation.
Proper annotation of drug and cell line data is crucial for running the gDR pipeline effectively. By adhering to the annotation requirements and following the outlined process, users can ensure accurate and reliable results from the pipeline.
sessionInfo()
#> R version 4.4.0 beta (2024-04-15 r86425)
#> Platform: x86_64-pc-linux-gnu
#> Running under: Ubuntu 22.04.4 LTS
#>
#> Matrix products: default
#> BLAS: /home/biocbuild/bbs-3.19-bioc/R/lib/libRblas.so
#> LAPACK: /usr/lib/x86_64-linux-gnu/lapack/liblapack.so.3.10.0
#>
#> locale:
#> [1] LC_CTYPE=en_US.UTF-8 LC_NUMERIC=C
#> [3] LC_TIME=en_US.UTF-8 LC_COLLATE=en_US.UTF-8
#> [5] LC_MONETARY=en_US.UTF-8 LC_MESSAGES=en_US.UTF-8
#> [7] LC_PAPER=en_US.UTF-8 LC_NAME=C
#> [9] LC_ADDRESS=C LC_TELEPHONE=C
#> [11] LC_MEASUREMENT=en_US.UTF-8 LC_IDENTIFICATION=C
#>
#> time zone: America/New_York
#> tzcode source: system (glibc)
#>
#> attached base packages:
#> [1] stats graphics grDevices utils datasets methods base
#>
#> other attached packages:
#> [1] BiocStyle_2.32.0
#>
#> loaded via a namespace (and not attached):
#> [1] digest_0.6.35 R6_2.5.1 bookdown_0.39
#> [4] fastmap_1.1.1 xfun_0.43 cachem_1.0.8
#> [7] knitr_1.46 htmltools_0.5.8.1 rmarkdown_2.26
#> [10] lifecycle_1.0.4 cli_3.6.2 sass_0.4.9
#> [13] jquerylib_0.1.4 compiler_4.4.0 tools_4.4.0
#> [16] evaluate_0.23 bslib_0.7.0 yaml_2.3.8
#> [19] BiocManager_1.30.22 jsonlite_1.8.8 rlang_1.1.3