# 1 Version Information

R version: 4.1.0

Bioconductor version: 3.13

Cytoscape: 3.8.2

Cy3D (Cytoscape app): 1.1.3

KEGGscape (Cytoscape app): 0.9.1

# 2 Introduction

Visualization of Trans-omic networks helps biological interpretation by illustrating pathways where the signals are transmitted (Gehlenborg et al., 2010).

To characterize signals that go across multiple omic layers, Yugi and colleagues have proposed a method for network visualization (Yugi et al., 2014) by stacking multiple 2D pathways in a 3D space.

The 3D network visualization was realized by VANTED (Rohn et al., 2012). However, the visualization relies on time-consuming manual operation. Here we propose transomics2cytoscape, an R package that automatically creates 3D network visualization in combination with Cytoscape (Shannon, 2003), Cy3D App, and Cytoscape Automation (Otasek et al., 2019).

## 2.1 Installation

This package requires Cytoscape to be installed and you need to run Cytoscape before running the following R code.

``BiocManager::install("transomics2cytoscape")``

# 3 Workflow

There is 2 functions `create3Dnetwork` and `createTransomicEdges` in transomics2cytoscape. Below is a diagram of the transomics2cytoscape workflow.

`create3Dnetwork` has 3 arguments.

The 1st one is a directory path where you put the network files to be layered in 3D space. The 2nd one is a file path of TSV for the Z-axis layout of the network files (called “Layer definition file”). The last one is a file path of XML used to style Cytoscape.

For example,

``suid <- create3Dnetwork(networkDataDir, networkLayers, stylexml)``

`createTransomicEdges` has 2 arguments.

The 1st one is the SUID of the network created by `create3Dnetwork`. The 2nd one is a file path of TSV for the transomic interactions (called “Transomic interaction file”).

For example,

``suid <- createTransomicEdges(suid, layer1to2)``

## 3.1 Input files

### 3.1.1 (Any number of) network files to be layered in 3D space

Files that Cytoscape can import. You need to put these files in the directory of the 1st argument of `create3Dnetwork`. You don’t need to put files for the KEGG pathway. For KEGG pathway, you can import the network just by writing the KEGG pathway ID in the “Layer definition file” described later.

### 3.1.2 Layer definition file

“Layer definition file” is a TSV file for the Z-axis layout of the network files.

A file that defines network layer index and the Z-height of the network in 3D space. The format is as follows.

``````layer1  rno04910    2400
layer2  rno01100    1500
layer3  rno01100    1``````

The 1st column is the network layer index. This information is added to the node table column `LAYER_INDEX`.

The 2nd column is the KEGG pathway ID or the network file name in the directory of the 1st argument of `create3Dnetwork`. You don’t need to prepare a network file for the KEGG pathway. You can import the KEGG pathway simply by writing the KEGG pathway ID. The last column is the Z-height of the network.

### 3.1.3 A style file of Cytoscape

A Cytoscape style file. For more information about Cytoscape style file, see the Cytoscape user manual. Note that you can only use style properties that are supported by Cy3D.

### 3.1.4 Trans-omic interaction file

“Trans-omic interaction file” is a TSV file that defines the edges that connect the different network layers. The format is as follows.