matrixCtrl2Server: Shiny module server functions to control matrix view
In avucoh/DIVE: Data Integration and Visual Exploration

matrixCtrl2Server

R Documentation

Shiny module server functions to control matrix view

Description

Create a matrix view that can be visualized with appropriate plotting modules

Usage

matrixCtrl2Server(
  id,
  M = NULL,
  N = NULL,
  P = NULL,
  cutoffP = 0.05,
  cdata = NULL,
  metafilter = reactive({ }),
  newdata = reactive({ }),
  filtervals = NULL
)

Arguments

`id`	Character ID for specifying namespace, see `shiny::NS`.
`M`	A data matrix, e.g. a correlation matrix, which must have row and column names.
`N`	A matrix of the same dimensions as 'M' to be used as a filter layer, e.g. sample size.
`P`	A matrix of the same dimensions as 'M' to be used as a filter layer, e.g. p-values.
`cutoffP`	A cutoff value for 'P' to be used as default for filtering.
`cdata`	The data used for generating the matrix, necessary for allowing user-uploaded data to be integrated into mutable 'M'.
`metafilter`	Optional reactive data (table) where first column contains rows to be selected and metadata attributes as additional columns.
`newdata`	Optional reactive data (table) such as a user upload passed in by the `dataUploadServer` module or from some other component, and which is suitable for merging with cdata to calculate a new 'M'.
`filtervals`	Optional reactive object for storing filter values that need to be communicated to other modules.

Details

The module can integrate several types of interactions that control the view of a matrix. It handles recalculation of the view and passes on the data to be visualized with matrixMainServer or matrixAsNetworkServer. The base UI implements drop-down selection for basic subsetting of matrix indices and threshold-type filters, and integrates with other modules providing new data input or specialized selection interface. For example, for some data a map widget might provide a better selection interface than a simple drop-down, thus the map widget module could be implemented separately and its result communicated as metafilter.