knitr::opts_chunk$set(echo=TRUE);

MultiEnrichMap notes

This document is intended to track the workflow steps involved in a typical MultiEnrichMap workflow. It also includes some details about custom column headers and how and where in the workflow they are handled.

Starting requirements

The starting data should include results from gene set enrichment analysis, in the form of a data.frame, an enrichResult object, or another class from which a data.frame can be coerced.

Each enrichment result is provided in its own data.frame or similar class.

Import from data.frame to enrichResult

enrichDF2enrichResult() converts a single data.frame to enrichResult.

Important arguments to enrichDF2enrichResult()

Optional arguments to enrichDF2enrichResult()

Notes

This function returns enrichResult object, with close approximation to the data produced in the clusterProfiler package, but not identical. For example, the pathway genes will not be fully correct without supplying the GmtT data upfront, since the GmtT data will contain the full set of pathway genes for all pathways.

Running multiEnrichMap()

To run multiEnrichMap() one must supply a list of enrichment results, either in the form of data.frame or enrichResult objects.

Steps carried out by multiEnrichMap()

Output from multiEnrichMap()

Output is returned as a list with the following items:



jmw86069/jamenrich documentation built on Feb. 3, 2024, 12:40 p.m.