Case study: TSPAN14 xQTL and AD GWAS¶
This notebook documents the analysis of xQTL case study on a targeted gene, TSPAN14.
- Section 0: Sanity check
- Section 1: Fine-mapping for xQTL and GWAS
- Section 2: Multi-context colocalization with Bellenguez 2022
- Section 3: Refinement of colocalized loci with other AD GWAS
- Section 4: Assessment of multi-context xQTL effect sizes
- Section 5: Multi-context causal TWAS (including conventional TWAS and MR)
- Section 6: Context specific multi-gene fine-mapping
- Section 7: Epigenomic QTL and their target regions
- Section 8: Context focused validation in other xQTL data
- Section 9: Non-linear effects of xQTL
- Section 10: in silico functional studies in iPSC model
- Section 11: Functional annotations of selected loci
- Section 12: Candidate loci as trans-xQTL
Overview¶
FunGen-xQTL resource contains 67 xQTL contexts as well as 9 AD GWAS fine-mapped genome-wide. The overarching goal for case studies is to use these resource to raise questions and learn more about gene targets of interest.
Overall, a case study consists of the following aspects:
- Check the basic information of the gene
- Check the existing xQTL and integrative analysis results, roughly including
- Summary table for univariate fine-mapping
- Marginal association results
- Multi-gene and multi-context fine-mapping
- Multi-context colocalization with AD GWAS
- TWAS, MR and causal TWAS
- Integration with epigenetic QTL
- Quantile QTL
- Interaction QTL
- Validation:
- Additional xQTL data in FunGen-xQTL
- Additional AD GWAS data-set already generated by FunGen-xQTL
- In silico functional studies
- Additional iPSC data-sets
- Functional annotations of variants, particularly in relevant cellular contexts
- Creative thinking: generate hypothesis, search in literature, raise questions to discuss
Computing environment setup¶
Interactive analysis will be done on AWS cloud powered by MemVerge. Please contact Gao Wang to setup accounts for you to start the analysis.
Please follow instructions on https://wanggroup.org/productivity_tips/mmcloud-interactive to configure your computing environment. Here are some additional packages you need to install after the initial configuration, in order to perform these analysis:
micromamba install -n r_libs r-pecotmr
micromamba install -n r_libs r-bedmatrix
How to Use This Notebook¶
- Before you start: Load functions from
cb_plot.Randutilis.R, located at/data/interactive_analysis/rf2872/codes/. These functions and resources are packaged to streamline the analysis and ensure everything is as clean as possible. And also the codes for ColocBoost under path/data/colocalization/colocboost/R. - Inside of this notebook, use
sed -iorCtrl+Fto replace the geneTSPAN14with the gene you want to analyze. - For detailed analysis in some sections, please refer to the corresponding analysis notebooks as indicated. These companion notebooks are available under this same folder. The rest of the tasks can be completed with a few lines of code, as demonstrated in this notebook.
- Similarly for the companion notebooks you should also use the
sed -iorCtrl+Freplacing gene_name (TSPAN14 in this case) with the gene you want to investigate.
While using this notebook, you may need to generate three intermediate files from Sections 1 and 2, which will be useful for downstream analysis:
- a. Section 1:
- Fine-mapping contexts that indicate shared signals with AD,
TSPAN14_finemapping_contexts.rds. This can be used as input for Section 8 the multi-cohort validation step - A subset of the xQTL-AD table,
Fungen_xQTL_allQTL.overlapped.gwas.export.TSPAN14.rds. This can be used as input for Section 12.
- Fine-mapping contexts that indicate shared signals with AD,
- b. Section 2: A variant list showing colocalization in cohorts we analyzed with ColocBoost,
TSPAN14_colocboost_res.rds. this can be used as input for Sections 7, 9, 10, and 12.
Section 0: Sanity check¶
Check the basic information of the gene¶
- To gain a preliminary understanding of this gene’s expression—specifically, whether it is cell-specific—can help us quickly determine if our results are consistent with expectations.
Useful websites:
- check gene function, (immune) cell type specificity, tissue specifity, protein location: https://www.proteinatlas.org
- check gene position and structure: https://www.ncbi.nlm.nih.gov/gene/
- other collective information: https://www.genecards.org
Check the existing results which are inputs to this analysis¶
source('/data/interactive_analysis/rf2872/codes/cb_plot.R')
source('/data/interactive_analysis/rf2872/codes/utilis.R')
for(file in list.files("/data/colocalization/colocboost/R", pattern = ".R", full.names = T)){
source(file)
}
gene_name = 'TSPAN14'
dir.create(paste0('plots/', gene_name), recursive = T)
get basic target gene information
target_gene_info <- get_gene_info(gene_name = gene_name)
target_gene_info
- $gene_info
A data.table: 1 x 14 region_id #chr start end TSS LD_matrix_id LD_sumstats_id LD_sumstats_id_old TADB_index TADB_id gene_start gene_end sliding_windows gene_name <chr> <chr> <dbl> <dbl> <int> <chr> <chr> <chr> <chr> <chr> <int> <int> <chr> <chr> ENSG00000108219 chr10 79454165 84120000 80454165 chr10:79309511-80126158,chr10:80126158-82231647,chr10:82231647-83966001,chr10:83966001-85526873 10_79309511-80126158,10_80126158-82231647,10_82231647-83966001,10_83966001-85526873 10_79309511-80126158,10_80126158_82231647,10_82231647_83966001,10_83966001_85526873 TADB_849,TADB_850 chr10_76790791_81245367,chr10_78526508_85081995 80454166 80533124 chr10:74243567-81245367,chr10:75869601-85081995,chr10:76790791-88435035,chr10:78526508-91908553,chr10:83138420-94806272 TSPAN14 - $target_LD_ids
A matrix: 1 x 4 of type chr chr10:79309511-80126158 chr10:80126158-82231647 chr10:82231647-83966001 chr10:83966001-85526873 - $target_sums_ids
A matrix: 1 x 4 of type chr 10_79309511-80126158 10_80126158-82231647 10_82231647-83966001 10_83966001-85526873 - $gene_region
- 'chr10:79454165-84120000'
- $target_TAD_ids
A matrix: 1 x 2 of type chr chr10_76790791_81245367 chr10_78526508_85081995
gene_id = target_gene_info$gene_info$region_id
chrom = target_gene_info$gene_info$`#chr`
Take a quick look for the expression of target gene in ROSMAP bulk data, we don't want them to be too low
source('/data/interactive_analysis/rf2872/codes/utilis.R')
expression_in_rosmap_bulk(target_gene_info)
region_p
Bellenguez et al GWAS signals has many overlap with CS from other xQTL sources. This motivates us to look further. The figure above shows the ranges of CS to give us a loci level idea. Below, we show the variants in those CS, color-coding the variants that are shared between them in the same color. In particular, AD GWAS signals are also captured by a few xQTL data, although at this point we don't have formal statistical (colocalization) evidences for these observations yet.
pip_p
This is done using ColocBoost. The most updated version of ColocBoost results are under path
s3://statfungen/ftp_fgc_xqtl/analysis_result/ColocBoost/2024_9/
cb_res <- readRDS(paste0("/data/analysis_result/ColocBoost/2024_9/",gene_id,"_res.rds") )
#save colocboost results
cb_res_table <- get_cb_summary(cb_res)
saveRDS(cb_res_table, paste0(gene_name, "_colocboost_res.rds"))
cb <- plot_cb(cb_res = cb_res, cex.pheno = 1.5, x.phen = -0.2)
pdf('plots/TSPAN14/sec2.colocboost_res.pdf', width = 10, height = 5)
replayPlot(cb$p)
dev.off()
# colocalized variants
cb_res_table
| colocalized phenotypes | purity | # variants | highest VCP | colocalized index | colocalized variants | max_abs_z_variant | cset_id |
|---|---|---|---|---|---|---|---|
| <chr> | <dbl> | <dbl> | <dbl> | <chr> | <chr> | <chr> | <chr> |
| AC; AC_unproductive; DLPFC_unproductive | 1.0000000 | 1 | 0.9997845 | 7181 | chr10:80512871:TTTGTTGTTGTTGTTG:TTTG | chr10:80512871:TTTGTTGTTGTTGTTG:TTTG | coloc_sets:Y7_Y11_Y12:CS1 |
| Exc; DLPFC; AC; PCC; DLPFC_unproductive; PCC_unproductive; AD_Bellenguez_2022 | 0.9862626 | 10 | 0.1535453 | 7165; 7099; 7098; 7103; 7132; 7163; 7090; 7159; 7184; 7200 | chr10:80513323:T:C; chr10:80510092:C:G; chr10:80520381:T:G; chr10:80489996:G:A; chr10:80509855:A:G; chr10:80491788:C:A; chr10:80492013:G:A; chr10:80493945:C:A; chr10:80497814:T:C; chr10:80508189:A:C | chr10:80513323:T:C | coloc_sets:Y4_Y6_Y7_Y8_Y12_Y13_Y14:CS2 |
# effect sign for each coloc sets
get_effect_sign_csets(cb_res)
- $`coloc_sets:Y7_Y11_Y12:CS1`
A data.frame: 1 x 4 variants AC AC_unproductive DLPFC_unproductive <chr> <dbl> <dbl> <dbl> chr10:80512871:TTTGTTGTTGTTGTTG:TTTG chr10:80512871:TTTGTTGTTGTTGTTG:TTTG 13.08519 -8.534175 -12.50158 - $`coloc_sets:Y4_Y6_Y7_Y8_Y12_Y13_Y14:CS2`
A data.frame: 10 x 8 variants Exc DLPFC AC PCC DLPFC_unproductive PCC_unproductive AD_Bellenguez_2022 <chr> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> <dbl> chr10:80510092:C:G chr10:80510092:C:G 8.085155 7.515560 13.73716 12.91315 -12.27762 -8.827435 7.611650 chr10:80492013:G:A chr10:80492013:G:A 8.085155 7.512116 13.76660 12.87399 -12.26355 -8.706989 7.676471 chr10:80491788:C:A chr10:80491788:C:A 8.085155 7.512116 13.76660 12.87399 -12.26355 -8.706989 7.656863 chr10:80493945:C:A chr10:80493945:C:A 8.085155 7.512116 13.76660 12.87399 -12.26355 -8.706989 7.656863 chr10:80497814:T:C chr10:80497814:T:C 8.085155 7.512116 13.76660 12.87399 -12.26355 -8.706989 7.607843 chr10:80509855:A:G chr10:80509855:A:G 8.085155 7.495725 13.73716 12.91315 -12.16287 -8.827435 7.524272 chr10:80489996:G:A chr10:80489996:G:A 8.085155 7.519246 13.85109 12.85209 -12.06513 -8.847074 7.441176 chr10:80508189:A:C chr10:80508189:A:C 8.085155 7.471587 13.73716 12.91315 -12.11940 -8.827435 7.419048 chr10:80513323:T:C chr10:80513323:T:C 8.089445 7.646292 13.89353 13.08764 -12.67859 -8.730885 0.000000 chr10:80520381:T:G chr10:80520381:T:G 7.992847 7.579862 13.54425 13.02695 -12.60627 -8.521531 0.000000
# LD between coloc sets
get_between_purity_simple(cb_res, gene.name = gene_id, path = '/data/colocalization/QTL_data/eQTL/')
| coloc_csets_1 | coloc_csets_2 | min_abs_cor | max_abs_cor | median_abs_cor |
|---|---|---|---|---|
| coloc_sets:Y7_Y11_Y12:CS1 | coloc_sets:Y4_Y6_Y7_Y8_Y12_Y13_Y14:CS2 | 0.742992620641873 | 0.75877282132962 | 0.745705268852512 |
Here, different colors refer to different 95% Colocalization Sets (CoS, a metric developed in ColocBoost indicating that there is 95% probabilty that this CoS captures a colocalization event). We only included ROSMAP data for this particular ColocBoost analysis. In this case, we observe cell specific eQTL, bulk sQTL colocalization on ROSMAP data with AD as two separate CoS, suggesting two putative causal signals. We did not detect colocalization with pQTL of statistical significance although from Section 1 there are some overlap with pQTL signals in fine-mapping CS, the overlapped variants in CS have small PIP.
Section 3: Refinement of colocalized loci with other AD GWAS¶
Here we refine the colocalization with other AD GWAS to iron out any heterogeniety between studies (heterogeniety can come from many sources), to get additional candidate loci from these more heterogenous sources as candidates to study.
AD_cohorts <- c('AD_Jansen_2021', 'AD_Bellenguez_EADB_2022', 'AD_Bellenguez_EADI_2022',
'AD_Kunkle_Stage1_2019', 'AD_Wightman_Excluding23andMe_2021',
'AD_Wightman_ExcludingUKBand23andME_2021', 'AD_Wightman_Full_2021')
cb_ad <- plot_cb(cb_res = cb_res, cex.pheno = 1.5, x.phen = -0.2, add_gwas = TRUE, gene_id = gene_id, cohorts = AD_cohorts)
No pvalue cutoff. Extract all variants names.No pvalue cutoff. Extract all variants names.No pvalue cutoff. Extract all variants names.No pvalue cutoff. Extract all variants names.No pvalue cutoff. Extract all variants names.No pvalue cutoff. Extract all variants names.No pvalue cutoff. Extract all variants names.
pdf('plots/TSPAN14/sec3.colocboost_res_allad.pdf', width = 10, height = 5)
replayPlot(cb_ad$p)
dev.off()
Section 4: Assessment of multi-context xQTL effect sizes¶
Option 1: ColocBoost + MASH¶
Use colocboost variants and check for mash posterior contrast to see if the effect size are shared or specific or even opposite. Advantage is that colocboost result is AD GWAS informed; issue is that marginal posterior effects is not always the joint
Option 2: mvSuSiE¶
Use mvSuSiE multicontext fine-mapping results --- the bubble plot to check posterior effects. Issue is that we don't have this results yet, and this is limited to one cohort at a time, without information from AD.
We should go for option 1 by default and if we want to make claim about opposite effect size we double-check with mvSuSiE multicontext analysis.
The most updated version of cTWAS analysis are under path
s3://statfungen/ftp_fgc_xqtl/analysis_result/cTWAS/
TWAS results¶
We report TWAS from all contexts and methods from the pipeline. Here we will filter it down to the best performing methods and only keep contexts that are significant.
plot_TWAS_res(gene_id = gene_id)
MR results¶
This is only available for genes that are deemed significant in TWAS and have summary statistics available for effect size and standard errors in GWAS, in addition to z-scores --- current version does not support z-scores although we will soon also support z-scores in MR using MAF from reference panel.
cTWAS results¶
To be updated soon.
A quick analysis: using the xQTL-AD summary table (flatten table)¶
We extract from xQTL-AD summary table the variants to get other genes also have CS with the variants shared by target gene and AD.
multigene_flat <- get_multigene_multicontext_flatten('Fungen_xQTL_allQTL.overlapped.gwas.export.TSPAN14.rds', sQTL = 'no_MSBB')
multigene_flat
| gene_id | #chr | start | end | gene_name | contexts |
|---|---|---|---|---|---|
| <chr> | <chr> | <int> | <int> | <chr> | <chr> |
| ENSG00000108179 | chr10 | 79347468 | 79347469 | PPIF | MiGA_SVZ_eQTL |
| ENSG00000122359 | chr10 | 80205571 | 80205572 | ANXA11 | Knight_eQTL,BM_36_MSBB_eQTL,BM_44_MSBB_eQTL,MSBB_BM36_pQTL,Ast_DeJager_eQTL,Exc_DeJager_eQTL,DLPFC_DeJager_eQTL,PCC_DeJager_eQTL,AC_DeJager_eQTL,Ast_Kellis_eQTL,Exc_Kellis_eQTL,Ast_mega_eQTL,Exc_mega_eQTL,DLPFC_Bennett_pQTL,ROSMAP_DLPFC_sQTL |
| ENSG00000122378 | chr10 | 80407828 | 80407829 | PRXL2A | MiGA_GTS_eQTL,MiGA_SVZ_eQTL,ROSMAP_DLPFC_sQTL |
| ENSG00000133661 | chr10 | 79982613 | 79982614 | SFTPD | MiGA_GTS_eQTL,ROSMAP_AC_sQTL |
| ENSG00000133665 | chr10 | 80344744 | 80344745 | DYDC2 | MiGA_SVZ_eQTL,PCC_DeJager_eQTL |
| ENSG00000133678 | chr10 | 80078645 | 80078646 | TMEM254 | MiGA_SVZ_eQTL,MiGA_THA_eQTL,AC_DeJager_eQTL |
| ENSG00000138326 | chr10 | 78033759 | 78033760 | RPS24 | MiGA_THA_eQTL |
| ENSG00000148600 | chr10 | 84194536 | 84194537 | CDHR1 | ROSMAP_PCC_sQTL |
| ENSG00000185303 | chr10 | 79560406 | 79560407 | SFTPA2 | BM_44_MSBB_eQTL,PCC_DeJager_eQTL,AC_DeJager_eQTL |
| ENSG00000185737 | chr10 | 81875193 | 81875194 | NRG3 | Knight_eQTL,MiGA_SVZ_eQTL,ROSMAP_AC_sQTL,ROSMAP_PCC_sQTL |
| ENSG00000188199 | chr10 | 79703226 | 79703227 | NUTM2B | AC_DeJager_eQTL |
Other genes implicated are PROC and HS6ST1 in MiGA cohort which may share causal eQTL with TSPAN14. Further look into the data-set --- using these genes as targets and repeating what we did above for TSPAN14 --- might be needed to establish a more certain conclusion.
Alternatively, we may be able to apply a multi-gene statistical fine-mapping test on TSPAN14 region to find these genes, as you will see in the section below.
A statistically solid approach: mvSuSiE multi-gene analysis¶
This multi-gene fine-mapping analysis was done for each xQTL context separately. We will need to check the results for all contexts where this gene has an xQTL, in order to identify if there are other genes also sharing the same xQTL with this target gene. We included other genes in the same TAD window along with this gene, and extended it into a sliding window approach to include multiple TADs just in case. You need to check the sliding windows belongs to that gene (TSS) on analysis repo.
sliding_windows <- target_gene_info$gene_info$sliding_windows %>% strsplit(., ',') %>% unlist %>% as.character
sliding_windows
- 'chr10:74243567-81245367'
- 'chr10:75869601-85081995'
- 'chr10:76790791-88435035'
- 'chr10:78526508-91908553'
- 'chr10:83138420-94806272'
The most updated version of mvSuSiE multi-gene results are under path
s3://statfungen/ftp_fgc_xqtl/analysis_result/mvsusie_multi_gene_test/multi_gene/ Currently it is still WIP. You can revisit this later when we prompt you to. Here is an example for TSPAN14:
mnm_gene <- list()
for (window in sliding_windows) {
mnm_gene_tmp <- NULL
mnm_gene_tmp <- tryCatch(
readRDS(paste0('/data/analysis_result/mvsusie_multi_gene/multi_gene/ROSMAP_multi_gene.', window, '.mnm.rds')),
error = function(e) NULL
)
if (!is.null(mnm_gene_tmp)) {
if(target_gene_info$gene_info$region_id %in% mnm_gene_tmp$mvsusie_fitted$condition_names){
tryCatch({
p <- mvsusieR::mvsusie_plot(mnm_gene_tmp$mvsusie_fitted, sentinel_only = F, add_cs = T)
print(p) # This ensures the plot is displayed in JupyterLab
}, error = function(e) NULL)
} else {
message('There is mnm result for sliding window ',window,', but not include target gene ', gene_name, ' in CS')
}
mnm_gene <- append(mnm_gene, list(mnm_gene_tmp))
}
}
In this case, there is no statistical evidence for TSPAN14 sharing any of its xQTL with other genes in ROSMAP Microglia data we looked into; although we have not analyzed MiGA this way yet (which showed some potential signals from the quick analysis above).
Generate a crude plot to determined whether the story is interesting¶
This is a crude version of the case study plot which shows the fsusie Effect (colored line), the gene body (black arrow), the epi-QTL (large dots with the same color as the effects) and ADGWAS cs position (small red dots).
Only produce the refine plot if we can see either:
- There are sharing snp between epi-QTL and AD CS
- There are the AD CS located within one of the effect range
- The crude plot suggest something interesting
options(repr.plot.width = 40, repr.plot.height = 40)
ggplot() + theme_bw() + facet_grid(cs_coverage_0.95 + study + region ~ ., labeller = labeller(.rows = function(x) gsub("([_:,-])", "\n", x)), scale = "free_y") +
theme(text = element_text(size = 20), strip.text.y = element_text(size = 25, angle = 0.5)) +
# xlim(view_win) +
ylab("Estimated effect") +
# geom_line(data = haQTL_df %>% mutate(study = "haQTL effect") %>% filter(CS == 5),
# aes_string(y = "fun_plot", x = "x", col = "CS"), size = 4, col = "#00AEEF") +
geom_line(data = effect_of_interest ,
aes_string(y = "fun_plot", x = "x", col = "cs_coverage_0.95"), size = 2) +
geom_point(data = effect_of_interest ,
aes_string(y = "pip", x = "pos", col = "cs_coverage_0.95"), size = 10) +
theme(text = element_text(size = 40), strip.text.y = element_text(size = 15, angle = 0.5),
axis.text.x = element_text(size = 40), axis.title.x = element_text(size = 40)) +
xlab("Position") +
ylab("Estimated\neffect") +
geom_segment(arrow = arrow(length = unit(1, "cm")), aes(x = gene_start, xend = gene_end, y = 1, yend = 1), size = 6,
data = tar_gene_info$gene_info, alpha = 0.3) +
geom_text(aes(x = (gene_start + gene_end) / 2, y = 1 , label = gene_name), size = 10,
data = tar_gene_info$gene_info)+
geom_point(aes(x = pos, y = pip ) ,color = "red", data = flatten_table%>%filter( str_detect(study,"AD_") , cs_coverage_0.95 != 0 )%>%mutate(AD_study = study%>%str_replace_all("_","\n" ))%>%select(-study,-region,-cs_coverage_0.95) )
Section 8: Context focused validation in other xQTL data¶
see notebook
add fake version for now, so you don't have to refer to above link
Background: our "discovery set" is ROSMAP but we have additional "validation" sets including:
- STARNET
- MiGA
- KnightADRC
- MSBB
- metaBrain
- UKB pQTL
TODO:
- Get from Carlos WashU CSF based resource (pQTL and metabolomic QTL)
This section shows verification of findings from these data-sets. In principle we should check them through sections 1-6 more formally. In practice we will start with colocalization via colocboost --- since our study is genetics (variant and loci level) focused. We can selectively follow them up for potentially intereting validations. We therefore only demonstrate validation via colocboost as a starting point.
finempping_contexts <- readRDS(paste0(gene_name, '_finemapping_contexts.rds')) # from sec1
finempping_contexts <- get_norosmap_contexts(finempping_contexts)
cb_ad <- plot_cb(cb_res = cb_res, cex.pheno = 1.5, x.phen = -0.2, add_QTL = TRUE, cohorts = finempping_contexts, gene_id = gene_id)
No pvalue cutoff. Extract all variants names.No pvalue cutoff. Extract all variants names.
In conclusion from what's shown above, when we check the association signals in STARNET and MiGA on colocalization established from ROSMAP and AD GWAS, we see additional evidences.
APOE interaction¶
options(repr.plot.width=6, repr.plot.height=6)
ggplot(TSPAN14_int_res, aes(x = variant_id, y = qvalue_interaction)) +
geom_point(alpha = 0.7, size = 6) +
labs(title = "qvalue for TSPAN14 csets in interaction association nalysis",
x = "Gene Name",
y = "qvalue_interaction",
size = "qvalue_interaction") +
theme_minimal(base_size = 14) +
theme(panel.background = element_blank(),
panel.grid.major = element_line(color = "grey80"),
legend.position = NULL,
axis.text.x = element_text(angle = 45, hjust = 1)) + ylim(0,1)
# scale_color_manual(values = colorRampPalette(brewer.pal(8, "Set1"))(length(unique(flat_var$gene_name))))
ggsave('plots/TSPAN14/sec11.interaction_association_TSPAN14_lessPIP25.pdf', height = 5, width = 8)
In conclusion, there is no interaction QTL with APOE identified.
vars_p
apoe_p
Section 11: Functional annotations of selected loci¶
see notebook
TODO
- Touch base with Ryan on the snATAC annotations
- Run this by Pavel to see if there are additional comments on how we do this
FIXME
func_p
options(repr.plot.width=12, repr.plot.height=6)
if(!is.null(flat_var)){
ggplot(flat_var, aes(x = gene_name, y = pip, size = pip)) +
geom_point(alpha = 0.7) +
labs(title = paste0("PIP values for trans fine mapped Genes in ", gene_name ," csets with AD"),
x = "Gene Name",
y = "PIP",
size = "PIP",
color = "CS Coverage 0.95 Min Corr") +
theme_minimal(base_size = 14) +
theme(panel.background = element_blank(),
panel.grid.major = element_line(color = "grey80"),
legend.position = NULL,
axis.text.x = element_text(angle = 45, hjust = 1))
# scale_color_manual(values = colorRampPalette(brewer.pal(8, "Set1"))(length(unique(flat_var$gene_name))))
ggsave(paste0('plots/TSPAN14/sec12.trans_fine_mapping_',gene_name,'.pdf'), height = 5, width = 8)
} else{
message('There are no detectable trans signals for ', gene_name)
}
Creative thinking: generate hypothesis, search in literature, raise questions to discuss¶
You can now generate some preliminary hypotheses based on the above results. Next, you should search for evidence in the literature to support or refine these hypotheses and identify additional analyses needed to confirm them.