Nothing
bulkAnalyseR: Integrating multi-omics or external data"
In bulkAnalyseR: Interactive Shiny App for Bulk Sequencing Data
wzxhzdk:0
## Cis-regulatory integration
*bulkAnalyseR* enables the integration of information involving cis-regulatory elements. A reference expression matrix is chosen, which may or may not be the central expression matrix for one of the full modality panels. A GRN is created on this expression matrix (see [here](https://core-bioinformatics.github.io/bulkAnalyseR/articles/bulkAnalyseR.html) for more information about GRN inference). Elements in the GRN are compared against elements from a second table which are located in proximity (e.g. 1kb, user-defined parameter); the elements in proximity are used to augment the focal GRN.
As an example, we consider a subset of the mRNAseq and h3k4me3 ChIPseq data from an experiment included in [a 2019 paper by Yang et al](https://www.sciencedirect.com/science/article/pii/S2405471219301152). The preprocessed mRNAseq data is included in the *bulkAnalyseR* package and can be loaded by running:
wzxhzdk:1
wzxhzdk:2
We define a default full modality app for the RNAseq data with an additional column relating to cis-integration so we also need to define a metadata table for the RNAseq data (our reference expression matrix):
wzxhzdk:3
wzxhzdk:4
Our reference inputs for the RNAseq data have the following structure:
wzxhzdk:5
To identify elements in proximity to genes in this dataset, we also need a table with chromosome, start and stop coordinates for genes. The data needed for the integration step can be found [here](https://github.com/Core-Bioinformatics/bulkAnalyseR/tree/main/exampledata/Yang2019_ChIP).
wzxhzdk:6
For RNAseq, such a table can be produced from the reference gtf. We also need to supply the organism database, here "org.Mm.eg.db" (see [here](https://core-bioinformatics.github.io/bulkAnalyseR/articles/bulkAnalyseR.html) for more information).
Finally, we need information about the ChIPseq peak coordinates to compare against RNAseq gene coordinates. These can come, for example, from MACS2 peak calling output (narrowPeak files).
wzxhzdk:7
The two coordinate tables should always have this structure and chromosome names must match between tables.
To create the integration tab, we need to define the following tibble:
wzxhzdk:8
Note that in this table, the names of all tables should be enclosed in quotation marks.
To create the app itself, we use the same call to *generateShinyApp* as [here](https://core-bioinformatics.github.io/bulkAnalyseR/articles/bulkAnalyseR.html) but we add the *cis.integration* argument with this tibble.
wzxhzdk:9
The cis-integration tab will look like this:
wzxhzdk:10
We could instead create an app with two modality tabs, including the ChIPseq expression matrix and cis integration with each of the mRNAseq and ChIPseq as the reference expression matrix like follows:
wzxhzdk:11
An example app with cis-integration can be found [here](http://bioinf.stemcells.cam.ac.uk:3838/bulkAnalyseR/Yang2019_Integration/).
## Trans-regulatory elements
*bulkAnalyseR* also offers the opportunity to analyse multiple elements which are not related necessarily by proximity but by correlation. For this component, two expression matrices are required, on the same columns. A joint GRN is then calculated on the combined expression matrices and targets can be chosen from either table.
To show this functionality, we focus on the mRNA and miRNA data from [a 2021 paper by Li et al](https://www.tandfonline.com/doi/full/10.1080/21655979.2021.1899533). The data needed for this example can be found [here](https://github.com/Core-Bioinformatics/bulkAnalyseR/tree/main/exampledata/Li2021_miRNA_mRNA).
wzxhzdk:12
wzxhzdk:13
The trans integration tab for the Li 2021 data could look like:
wzxhzdk:14
An example app with trans-integration can be found [here](https://github.com/Core-Bioinformatics/bulkAnalyseR/tree/main/exampledata/Li2021_miRNA_mRNA).
## Custom integration
*bulkAnalyseR* further offers the option to include custom integration relating to your reference expression matrix. This could include known miRNA-mRNA target interations or known transcription factors.
To integration miRNA-mRNA target interaction information, you can use the following function to create a custom comparison table:
wzxhzdk:15
To view the available filtering options for Support Type and Experiments (validation type), run the function with the extra *print* arguments:
wzxhzdk:16
Any comparison table supplied for custom integration should have these 5 columns. Reference_ID and Reference_Name should match the reference expression matrix. The final Category column allows the selection of more specific category of integration information.
To define the full app, we again use the typical Yang 2019 call to *generateShinyApp* but add the *custom.integration* parameter.
wzxhzdk:17
The custom integration panel for the Yang 2019 data, combined with miRTarBase information looks like:
wzxhzdk:18
An example app with custom integration can be found [here](http://bioinf.stemcells.cam.ac.uk:3838/bulkAnalyseR/Yang2019_Integration/).
## Integrating enrichment information
*bulkAnalyseR* also facilitates the integration of miRNA and transcription factor information in the DE & enrichment GRN tab:
wzxhzdk:19
wzxhzdk:20
Try the bulkAnalyseR package in your browser
Any scripts or data that you put into this service are public.
bulkAnalyseR documentation built on Dec. 28, 2022, 2:04 a.m.
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
Embedding an R snippet on your website
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.
wzxhzdk:0
## Cis-regulatory integration
*bulkAnalyseR* enables the integration of information involving cis-regulatory elements. A reference expression matrix is chosen, which may or may not be the central expression matrix for one of the full modality panels. A GRN is created on this expression matrix (see [here](https://core-bioinformatics.github.io/bulkAnalyseR/articles/bulkAnalyseR.html) for more information about GRN inference). Elements in the GRN are compared against elements from a second table which are located in proximity (e.g. 1kb, user-defined parameter); the elements in proximity are used to augment the focal GRN.
As an example, we consider a subset of the mRNAseq and h3k4me3 ChIPseq data from an experiment included in [a 2019 paper by Yang et al](https://www.sciencedirect.com/science/article/pii/S2405471219301152). The preprocessed mRNAseq data is included in the *bulkAnalyseR* package and can be loaded by running:
wzxhzdk:1
wzxhzdk:2
We define a default full modality app for the RNAseq data with an additional column relating to cis-integration so we also need to define a metadata table for the RNAseq data (our reference expression matrix):
wzxhzdk:3
wzxhzdk:4
Our reference inputs for the RNAseq data have the following structure:
wzxhzdk:5
To identify elements in proximity to genes in this dataset, we also need a table with chromosome, start and stop coordinates for genes. The data needed for the integration step can be found [here](https://github.com/Core-Bioinformatics/bulkAnalyseR/tree/main/exampledata/Yang2019_ChIP).
wzxhzdk:6
For RNAseq, such a table can be produced from the reference gtf. We also need to supply the organism database, here "org.Mm.eg.db" (see [here](https://core-bioinformatics.github.io/bulkAnalyseR/articles/bulkAnalyseR.html) for more information).
Finally, we need information about the ChIPseq peak coordinates to compare against RNAseq gene coordinates. These can come, for example, from MACS2 peak calling output (narrowPeak files).
wzxhzdk:7
The two coordinate tables should always have this structure and chromosome names must match between tables.
To create the integration tab, we need to define the following tibble:
wzxhzdk:8
Note that in this table, the names of all tables should be enclosed in quotation marks.
To create the app itself, we use the same call to *generateShinyApp* as [here](https://core-bioinformatics.github.io/bulkAnalyseR/articles/bulkAnalyseR.html) but we add the *cis.integration* argument with this tibble.
wzxhzdk:9
The cis-integration tab will look like this:
wzxhzdk:10
We could instead create an app with two modality tabs, including the ChIPseq expression matrix and cis integration with each of the mRNAseq and ChIPseq as the reference expression matrix like follows:
wzxhzdk:11
An example app with cis-integration can be found [here](http://bioinf.stemcells.cam.ac.uk:3838/bulkAnalyseR/Yang2019_Integration/).
## Trans-regulatory elements
*bulkAnalyseR* also offers the opportunity to analyse multiple elements which are not related necessarily by proximity but by correlation. For this component, two expression matrices are required, on the same columns. A joint GRN is then calculated on the combined expression matrices and targets can be chosen from either table.
To show this functionality, we focus on the mRNA and miRNA data from [a 2021 paper by Li et al](https://www.tandfonline.com/doi/full/10.1080/21655979.2021.1899533). The data needed for this example can be found [here](https://github.com/Core-Bioinformatics/bulkAnalyseR/tree/main/exampledata/Li2021_miRNA_mRNA).
wzxhzdk:12
wzxhzdk:13
The trans integration tab for the Li 2021 data could look like:
wzxhzdk:14
An example app with trans-integration can be found [here](https://github.com/Core-Bioinformatics/bulkAnalyseR/tree/main/exampledata/Li2021_miRNA_mRNA).
## Custom integration
*bulkAnalyseR* further offers the option to include custom integration relating to your reference expression matrix. This could include known miRNA-mRNA target interations or known transcription factors.
To integration miRNA-mRNA target interaction information, you can use the following function to create a custom comparison table:
wzxhzdk:15
To view the available filtering options for Support Type and Experiments (validation type), run the function with the extra *print* arguments:
wzxhzdk:16
Any comparison table supplied for custom integration should have these 5 columns. Reference_ID and Reference_Name should match the reference expression matrix. The final Category column allows the selection of more specific category of integration information.
To define the full app, we again use the typical Yang 2019 call to *generateShinyApp* but add the *custom.integration* parameter.
wzxhzdk:17
The custom integration panel for the Yang 2019 data, combined with miRTarBase information looks like:
wzxhzdk:18
An example app with custom integration can be found [here](http://bioinf.stemcells.cam.ac.uk:3838/bulkAnalyseR/Yang2019_Integration/).
## Integrating enrichment information
*bulkAnalyseR* also facilitates the integration of miRNA and transcription factor information in the DE & enrichment GRN tab:
wzxhzdk:19
wzxhzdk:20
bulkAnalyseR documentation built on Dec. 28, 2022, 2:04 a.m.
Try the bulkAnalyseR package in your browser
Any scripts or data that you put into this service are public.
R Package Documentation
Browse R Packages
We want your feedback!
Note that we can't provide technical support on individual packages. You should contact the package authors for that.
Embedding an R snippet on your website
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.