Differences between revisions 33 and 35 (spanning 2 versions)
Revision 33 as of 2013-12-11 06:05:19
Size: 13769
Comment:
Revision 35 as of 2013-12-12 01:01:50
Size: 12790
Comment:
Deletions are marked like this. Additions are marked like this.
Line 3: Line 3:
Interaction networks are useful as stand-alone models. However, they are most powerful for answering scientific questions when integrated with additional information. Cytoscape allows the user to add arbitrary node, edge and network information to Cytoscape as node/edge/network attributes. This could include, for example, annotation data on a gene or confidence values in a protein-protein interaction. These attributes can then be visualized in a user-defined way by setting up a mapping from data attributes to visual attributes (colors, shapes, and so on).  The section on [[Cytoscape_User_Manual/Visual_Styles| visual styles]] discusses this in greater detail. Interaction networks are useful as stand-alone models. However, they are most powerful for answering scientific questions when integrated with additional information. Cytoscape allows the user to add arbitrary node, edge and network information to Cytoscape as node/edge/network data columns. This could include, for example, annotation data on a gene or confidence values in a protein-protein interaction. These column data can then be visualized in a user-defined way by setting up a mapping from columns to network properties (colors, shapes, and so on). The section on [[Cytoscape_3/UserManual/Styles|Styles]] discusses this in greater detail.
Line 5: Line 5:
== Cytoscape Attribute File Format == == Cytoscape Data File Format ==
Line 7: Line 7:
Node and edge attribute files are simply formatted: a node attribute file begins with the name of the attribute on the first line (note that it cannot contain spaces). Each following line contains the name of the node, followed by an equals sign and the value of that attribute. Numbers and text strings are the most common attribute types. All values for a given attribute must have the same type. For example: Node and edge data files are simply formatted: a node data file begins with the name of the column on the first line (note that it cannot contain spaces). Each following line contains the name of the node, followed by an equals sign and the data value. Numbers and text strings are the most common data types. All values for a given column must have the same type. For example:
Line 15: Line 15:
An edge attribute file has much the same structure, except that the name of the edge is the source node name, followed by the interaction type in parentheses, followed by the target node name. Directionality counts, so switching the source and target will refer to a different (or perhaps non-existent) edge. The following is an example edge attributes file: An edge data file has much the same structure, except that the name of the edge is the source node name, followed by the interaction type in parentheses, followed by the target node name. Directionality counts, so switching the source and target will refer to a different (or perhaps non-existent) edge. The following is an example edge data file:
Line 23: Line 23:
Since Cytoscape treats edge attributes as directional, the second and third edge attribute values refer to two different edges (source and target are reversed, though the nodes involved are the same). Since Cytoscape treats edge data as directional, the second and third edge data values refer to two different edges (source and target are reversed, though the nodes involved are the same).
Line 25: Line 25:
Each attribute is stored in a separate file. Node and edge attribute files use the same format. Node attribute file names often use the suffix ".noa", while edge attribute file names use the suffix ".eda". Cytoscape recognizes these suffixes when browsing for attribute files. Each data column is stored in a separate file. Node and edge data files use the same format. Node data file names often use the suffix ".noa", while edge data file names use the suffix ".eda". Cytoscape recognizes these suffixes when browsing for data files.
Line 27: Line 27:
Node and edge attributes may be loaded at the command line using the –n and –e options or via the File → Import menu. Node and edge data may be loaded at the command line using the –n and –e options or via the '''File → Import''' menu.
Line 29: Line 29:
When expression data is loaded using an expression matrix, it is automatically loaded as node attribute data unless explicitly specified otherwise. When expression data is loaded using an expression matrix, it is automatically loaded as node data unless explicitly specified otherwise.
Line 31: Line 31:
Node and edge attributes are attached to nodes and edges, and so are independent of networks. Attributes for a given node or edge will be applied to all copies of that node or edge in all loaded network files, regardless of whether the attribute file or network file is imported first. Node and edge data columns are attached to nodes and edges, and so are independent of networks. Data values for a given node or edge will be applied to all copies of that node or edge in all loaded network files, regardless of whether the data file or network file is imported first.
Line 33: Line 33:
Note: In order to import network attributes in Cytoscape 2.4, please go to File → Import → Attribute from Table (text/MS Excel)... or encode them in an XGMML network file (see [[Cytoscape_User_Manual/Network_Formats|Supported File Formats]] for more details).
Line 36: Line 35:
Every attribute file has one header line that gives the name of the attribute, and optionally some additional meta-information about that attribute. The format is as follows: Every data file has one header line that gives the name of the data column, and optionally some additional meta-information about that data column. The format is as follows:
Line 39: Line 38:
attributeName (class=JavaClassName) columnName (class=JavaClassName)
Line 41: Line 40:
The first field is always the attribute name: it cannot contain spaces. If present, the class field defines the name of the class of the attribute values. For example, java.lang.String or String for Strings, java.lang.Double or Double for floating point values, java.lang.Integer or Integer for integer values, etc. If the value is actually a list of values, the class should be the type of the objects in the list.  If no class is specified in the header line, Cytoscape will attempt to guess the type from the first value. If the first value contains numbers in a floating point format, Cytoscape will assume java.lang.Double; if the first value contains only numbers with no decimal point, Cytoscape will assume java.lang.Integer; otherwise Cytoscape will assume java.lang.String. Note that the first value can lead Cytoscape astray: for example, The first field is always the column name: it cannot contain spaces. If present, the class field defines the name of the class of the data values. For example, java.lang.String or String for Strings, java.lang.Double or Double for floating point values, java.lang.Integer or Integer for integer values, etc. If the value is actually a list of values, the class should be the type of the objects in the list. If no class is specified in the header line, Cytoscape will attempt to guess the type from the first value. If the first value contains numbers in a floating point format, Cytoscape will assume java.lang.Double; if the first value contains only numbers with no decimal point, Cytoscape will assume java.lang.Integer; otherwise Cytoscape will assume java.lang.String. Note that the first value can lead Cytoscape astray: for example,
Line 44: Line 43:
floatingPointAttribute floatingPointDataColumn
Line 52: Line 51:
floatingPointAttribute (class=Double) floatingPointDataColumn (class=Double)
Line 60: Line 59:
floatingPointAttribute floatingPointDataColumn
Line 65: Line 64:
Every line past the first line identifies the name of an object (a node in a node attribute file or an edge in a edge attribute file) along with the String representation of the attribute value. The delimiter is always an equals sign; whitespace (spaces and/or tabs) before and after the equals sign is ignored. This means that your names and values can contain whitespace, but object names cannot contain an equals sign and no guarantees are made concerning leading or trailing whitespace. Object names must be the Node ID or Edge ID as seen in the left-most column of the attribute browser if the attribute is to map to anything.  These names must be reproduced exactly, including case, or they will not match. Every line past the first line identifies the name of an object (a node in a node data file or an edge in a edge data file) along with the String representation of the data value. The delimiter is always an equals sign; whitespace (spaces and/or tabs) before and after the equals sign is ignored. This means that your names and values can contain whitespace, but object names cannot contain an equals sign and no guarantees are made concerning leading or trailing whitespace. Object names must be the Node ID or Edge ID as seen in the left-most column of the Table Panel if the data column is to map to anything. These names must be reproduced exactly, including case, or they will not match.
Line 77: Line 76:
Note that tabs are not allowed in edge names.  Tabs can be used to separate the edge name from the "=" delimiter, but not within the edge name itself. Also note that this format is different from the specification of interactions in the SIF file format. To be explicit: a SIF entry for the previous interaction would look like Note that tabs are not allowed in edge names. Tabs can be used to separate the edge name from the "=" delimiter, but not within the edge name itself. Also note that this format is different from the specification of interactions in the SIF file format. To be explicit: a SIF entry for the previous interaction would look like
Line 90: Line 89:
listAttributeName (class=java.lang.String) listDataColumnName (class=java.lang.String)
Line 95: Line 94:
This example shows an attribute whose value is defined as a list of text strings. The first object has three strings, and thus three elements in its list, while the second object has a list with only one element. In the case of a list every attribute value uses list syntax (i.e. parentheses), and each element is of the same class. Again, the class will be inferred if it is not specified in the header line. Lists are not supported by the visual mapper and so can’t be mapped to visual attributes. This example shows a data column whose value is defined as a list of text strings. The first object has three strings, and thus three elements in its list, while the second object has a list with only one element. In the case of a list every data value uses list syntax (i.e. parentheses), and each element is of the same class. Again, the class will be inferred if it is not specified in the header line. Lists are not supported by Styles and so can’t be mapped to network properties.
Line 99: Line 98:
Sometimes it is desirable to for attributes to include linebreaks, such as node labels that extend over two lines. You can acomplish by inserting {{{\n}}} into the attribute value.  For example: Sometimes it is desirable to for data values to include linebreaks, such as node labels that extend over two lines. You can accomplish by inserting {{{\n}}} into the data value. For example:
Line 102: Line 101:
newlineAttr newlineDataColumn
Line 107: Line 106:
== Import Attribute Table Files == == Import Data Table Files ==
Line 109: Line 108:
As of Cytoscape 2.4, importing delimited text and MS Excel attribute data tables is now supported.  Using this functionality, users can now easily import data that isn't formatted into Cytoscape node or edge attribute file formats (as described above). As of Cytoscape 2.4, importing delimited text and MS Excel attribute data tables is now supported. Using this functionality, users can now easily import data that isn't formatted into Cytoscape node or edge data file formats (as described above).
Line 111: Line 110:
{{attachment:attribute_table_import_main.png}}

'''''Sample Attribute Table 1'''''
'''''Sample Data Table 1'''''
Line 119: Line 116:
The attribute table file should contain a primary key column and at least one attribute column. The maximum number of attribute columns is unlimited. The ''Alias'' column is an optional feature, as is using the first row of data as attribute names. Alternatively, you can specify each attribute name from the File → Import → Attribute from Table (text/MS Excel)... user interface. The data table file should contain a primary key column and at least one data column. The maximum number of data columns is unlimited. The '''Alias''' column is an optional feature, as is using the first row of data as column names. Alternatively, you can specify each column name from the '''File → Import → Attribute from Table (text/MS Excel)...''' user interface.
Line 122: Line 119:
The user interface of the "Import Attributes from Table" window is similar to that of the "Import Network from Table" window.
   
 1. Select File → Import → Attribute from Table (text/MS Excel)...
 1. Select one of the attribute types from the Attributes radio buttons. Cytoscape can import node, edge, and network attributes.
 1. Select a data file. To load a local file, click on the Select File button and choose a data file. This can be either a text or Excel (.xls) file. To load a remote file, type the source URL directly into the text box. To show a preview of the remote file, click the Reload button on the Show Text File Import Options panel.
 1. (Optional) If the table is not properly delimited in the preview panel, change the delimiter in the Text File Import Options panel. The default delimiter is the tab. This step is not necessary for Excel Workbooks.
 1. By default, the first column is designated as the primary key. Change the key column if necessary.
  {{attachment:attribute_table_import_primary_key.png}}
 1. Click the Import button.
  {{attachment:ImportColumnsFromTable.png}}
 
 1. Select '''File → Import → Table → File...'''.
 1. Select a data file. The file can be either a text or Excel (.xls) file.
 1. In the '''Target Table Data''' section, choose where to import the data to. You can choose an existing network collection, a specific network only, or you can choose to import the data to an '''Unassigned Table''' (described below).
 1. Depending on what you choose in the '''Where to import Table Data''' drop-down, you will need to select a network collection or specific network. You will also need to select '''Importing Type''', that is whether the data is node, edge or network table columns.
 1. If the table is not properly delimited in the preview panel, change the delimiter in the '''Show Text File Import Options''' panel. The default delimiter is tab. This step is not necessary for Excel Workbooks.
 1. By default, the first column is designated as the primary key. Change the key column if necessary.
 1. Click '''OK''' to import.
Line 133: Line 130:
==== Mapping Key Attributes to the primary key ====
Formerly, Cytoscape only supported mapping between node/edge IDs and the primary keys in attribute files.  With the introduction of Cytoscape 2.4, this limitation has been removed, and now both IDs and attributes with primitive data types (string, boolean, floating point, and integer) can be selected as the Key Attribute using the dropdown list provided. Complex attributes such as lists are not supported.
/*
Is this still relevant?
==== Annotation File to Table
Mapping ====
Formerly, Cytoscape only supported mapping between node/edge IDs and the primary keys in data files. With the introduction of Cytoscape 2.4, this limitation has been removed, and now both IDs and data columns with primitive data types (string, boolean, floating point, and integer) can be selected as the Key Attribute using the dropdown list provided. Complex attributes such as lists are not supported.
Line 139: Line 138:
Cytoscape uses a simple mechanism to manage aliases of objects.   Both nodes and edges can have aliases.  If an attribute is loaded as an alias, it is treated as a special attribute called "alias". This will be used when mapping attributes. If the primary key and key attribute for an object do not match, Cytoscape will search for a match between aliases and the key attribute. To define an alias column in the attribute table, just click on the checkboxes to the left of the column name while importing. Cytoscape uses a simple mechanism to manage aliases of objects. Both nodes and edges can have aliases. If an attribute is loaded as an alias, it is treated as a special attribute called "alias". This will be used when mapping attributes. If the primary key and key attribute for an object do not match, Cytoscape will search for a match between aliases and the key attribute. To define an alias column in the attribute table, just click on the checkboxes to the left of the column name while importing.
Line 142: Line 141:
*/
Line 143: Line 143:
==== Text File Import Options ====
For more detail on these options, please see the "Import Free-Format Table Files" section of the user manual in the [[Cytoscape_User_Manual/Creating_Networks|Creating Networks]] chapter.

=== Attribute Browser ===
=== Table Panel ===
Line 149: Line 146:
When Cytoscape is started, the Attribute Browser appears in the bottom !CytoPanel. This browser can be hidden and restored using the F5 key or the View → Show/Hide attribute browser menu option. Like other !CytoPanels, the browser can be undocked by pressing the little icon in the browser’s top right corner. When Cytoscape is started, the Table Panel appears in the bottom right of the main Cytoscape window. This browser can be hidden and restored using the F5 key or the '''View → Show/Hide Table Panel''' menu option. Like other Panels, the browser can be undocked by pressing the little icon in the top right corner.
Line 151: Line 148:
To swap between displaying node, edge, and network attributes use the tabs on the bottom of the panel labeled "Node Attribute Browser", "Edge Attribute Browser", and "Network Attribute Browser". The attribute browser displays attributes belonging to selected nodes and/or edges and the currently selected network. To populate the browser with rows (as pictured above), simply select nodes and/or edges in a loaded network. By default, only the ID of nodes and edges is shown. To display more than just the ID, click the Select Attributes {{attachment:attributes_select_icon.png}} button and choose the attributes that are to be displayed (select various attributes by clicking on them, and then click elsewhere on the screen to close the attribute list). Each attribute chosen will result in one column in the attribute browser. To swap between displaying node, edge, and network Data Tables use the tabs on the bottom of the Table Panel. The Table Panel displays columns belonging to selected nodes and/or edges and the currently selected network. To populate the panel with rows (as pictured above), simply select nodes and/or edges in a loaded network. By default, only the ID of nodes and edges is shown. To display more than just the ID, click the '''Show Column''' {{attachment:attributes_select_icon.png}} button and choose the columns that are to be displayed (select various columns by clicking on them, and then click elsewhere on the screen to close the column list).
Line 153: Line 150:
Most attribute values can be edited by double-clicking an attribute cell (only the ID cannot be edited). Newline characters can be inserted into String attributes either by pressing ''Enter'' or by typing "\n".  Once finished editing, click outside of the editing cell in the Attribute Browser or press ''Shift-Enter'' to save your edits.  Pressing ''Esc'' while editing will undo any changes. Most column values can be edited by double-clicking the cell (only the ID cannot be edited). Newline characters can be inserted into String columns either by pressing '''Enter''' or by typing "\n". Once finished editing, click outside of the editing cell in the Table Panel or press '''Shift-Enter''' to save your edits. Pressing '''Esc''' while editing will undo any changes.
Line 155: Line 152:
Attribute rows in the browser can be sorted alphabetically by specific attribute by clicking on a column heading. A new attribute can be created using the Create New Attribute {{attachment:attributes_new_icon.png}} button, and must be one of four types – integer, string, real number (floating point), or boolean. Attributes can be deleted using the Delete Attributes {{attachment:attributes_delete_icon.png}} button. '''NOTE: Deleting attributes removes them from Cytoscape, not just the attribute browser!''' To remove attributes from the browser without deleting them, simply unselect the attribute using the Select Attributes {{attachment:attributes_select_icon.png}} button. Rows in the panel can be sorted alphabetically by specific column by clicking on a column heading. A new column can be created using the '''Create New column''' {{attachment:attributes_new_icon.png}} button, and must be one of four types – integer, string, real number (floating point), or boolean. Columns can be deleted using the '''Delete Columns...''' {{attachment:attributes_delete_icon.png}} button. '''NOTE: Deleting columns removes them from Cytoscape, not just the Table Panel!''' To remove columns from the panel without deleting them, simply unselect the column using the '''Select Columns''' {{attachment:attributes_select_icon.png}} button.

Interaction networks are useful as stand-alone models. However, they are most powerful for answering scientific questions when integrated with additional information. Cytoscape allows the user to add arbitrary node, edge and network information to Cytoscape as node/edge/network data columns. This could include, for example, annotation data on a gene or confidence values in a protein-protein interaction. These column data can then be visualized in a user-defined way by setting up a mapping from columns to network properties (colors, shapes, and so on). The section on Styles discusses this in greater detail.

Cytoscape Data File Format

Node and edge data files are simply formatted: a node data file begins with the name of the column on the first line (note that it cannot contain spaces). Each following line contains the name of the node, followed by an equals sign and the data value. Numbers and text strings are the most common data types. All values for a given column must have the same type. For example:

FunctionalCategory
YAL001C = metabolism
YAR002W = apoptosis
YBL007C = ribosome

An edge data file has much the same structure, except that the name of the edge is the source node name, followed by the interaction type in parentheses, followed by the target node name. Directionality counts, so switching the source and target will refer to a different (or perhaps non-existent) edge. The following is an example edge data file:

InteractionStrength
YAL001C (pp) YBR043W = 0.82
YMR022W (pd) YDL112C = 0.441
YDL112C (pd) YMR022W = 0.9013

Since Cytoscape treats edge data as directional, the second and third edge data values refer to two different edges (source and target are reversed, though the nodes involved are the same).

Each data column is stored in a separate file. Node and edge data files use the same format. Node data file names often use the suffix ".noa", while edge data file names use the suffix ".eda". Cytoscape recognizes these suffixes when browsing for data files.

Node and edge data may be loaded at the command line using the –n and –e options or via the File → Import menu.

When expression data is loaded using an expression matrix, it is automatically loaded as node data unless explicitly specified otherwise.

Node and edge data columns are attached to nodes and edges, and so are independent of networks. Data values for a given node or edge will be applied to all copies of that node or edge in all loaded network files, regardless of whether the data file or network file is imported first.

Detailed file format (Advanced users)

Every data file has one header line that gives the name of the data column, and optionally some additional meta-information about that data column. The format is as follows:

columnName (class=JavaClassName)

The first field is always the column name: it cannot contain spaces. If present, the class field defines the name of the class of the data values. For example, java.lang.String or String for Strings, java.lang.Double or Double for floating point values, java.lang.Integer or Integer for integer values, etc. If the value is actually a list of values, the class should be the type of the objects in the list. If no class is specified in the header line, Cytoscape will attempt to guess the type from the first value. If the first value contains numbers in a floating point format, Cytoscape will assume java.lang.Double; if the first value contains only numbers with no decimal point, Cytoscape will assume java.lang.Integer; otherwise Cytoscape will assume java.lang.String. Note that the first value can lead Cytoscape astray: for example,

floatingPointDataColumn
firstName = 1
secondName = 2.5

In this case, the first value will make Cytoscape think the values should be integers, when in fact they should be floating point numbers. It's safest to explicitly specify the value type to prevent confusion. A better format would be:

floatingPointDataColumn (class=Double)
firstName = 1
secondName = 2.5

or

floatingPointDataColumn 
firstName = 1.0
secondName = 2.5

Every line past the first line identifies the name of an object (a node in a node data file or an edge in a edge data file) along with the String representation of the data value. The delimiter is always an equals sign; whitespace (spaces and/or tabs) before and after the equals sign is ignored. This means that your names and values can contain whitespace, but object names cannot contain an equals sign and no guarantees are made concerning leading or trailing whitespace. Object names must be the Node ID or Edge ID as seen in the left-most column of the Table Panel if the data column is to map to anything. These names must be reproduced exactly, including case, or they will not match.

Edge names are all of the form:

sourceName (edgeType) targetName

Specifically, that is

sourceName space openParen edgeType closeParen space targetName

Note that tabs are not allowed in edge names. Tabs can be used to separate the edge name from the "=" delimiter, but not within the edge name itself. Also note that this format is different from the specification of interactions in the SIF file format. To be explicit: a SIF entry for the previous interaction would look like

sourceName edgeType targetName

or

sourceName whiteSpace edgeType whiteSpace targetName

To specify lists of values, use the following syntax:

listDataColumnName (class=java.lang.String)
firstObjectName = (firstValue::secondValue::thirdValue)
secondObjectName = (onlyOneValue)

This example shows a data column whose value is defined as a list of text strings. The first object has three strings, and thus three elements in its list, while the second object has a list with only one element. In the case of a list every data value uses list syntax (i.e. parentheses), and each element is of the same class. Again, the class will be inferred if it is not specified in the header line. Lists are not supported by Styles and so can’t be mapped to network properties.

Newline Feature

Sometimes it is desirable to for data values to include linebreaks, such as node labels that extend over two lines. You can accomplish by inserting \n into the data value. For example:

newlineDataColumn
YJL157C = This is a long\nline for a label.

Import Data Table Files

As of Cytoscape 2.4, importing delimited text and MS Excel attribute data tables is now supported. Using this functionality, users can now easily import data that isn't formatted into Cytoscape node or edge data file formats (as described above).

Sample Data Table 1

Object Key

Alias

SGD ID

AAC3

YBR085W|ANC3

S000000289

AAT2

YLR027C|ASP5

S000004017

BIK1

YCL029C|ARM5|PAC14

S000000534

The data table file should contain a primary key column and at least one data column. The maximum number of data columns is unlimited. The Alias column is an optional feature, as is using the first row of data as column names. Alternatively, you can specify each column name from the File → Import → Attribute from Table (text/MS Excel)... user interface.

Basic Operation

  • ImportColumnsFromTable.png

  1. Select File → Import → Table → File....

  2. Select a data file. The file can be either a text or Excel (.xls) file.
  3. In the Target Table Data section, choose where to import the data to. You can choose an existing network collection, a specific network only, or you can choose to import the data to an Unassigned Table (described below).

  4. Depending on what you choose in the Where to import Table Data drop-down, you will need to select a network collection or specific network. You will also need to select Importing Type, that is whether the data is node, edge or network table columns.

  5. If the table is not properly delimited in the preview panel, change the delimiter in the Show Text File Import Options panel. The default delimiter is tab. This step is not necessary for Excel Workbooks.

  6. By default, the first column is designated as the primary key. Change the key column if necessary.
  7. Click OK to import.

Advanced Options

Annotation File to Table Mapping

Formerly, Cytoscape only supported mapping between node/edge IDs and the primary keys in data files. With the introduction of Cytoscape 2.4, this limitation has been removed, and now both IDs and data columns with primitive data types (string, boolean, floating point, and integer) can be selected as the Key Attribute using the dropdown list provided. Complex attributes such as lists are not supported.

attribute_table_import_keyattr.png

Aliases

Cytoscape uses a simple mechanism to manage aliases of objects. Both nodes and edges can have aliases. If an attribute is loaded as an alias, it is treated as a special attribute called "alias". This will be used when mapping attributes. If the primary key and key attribute for an object do not match, Cytoscape will search for a match between aliases and the key attribute. To define an alias column in the attribute table, just click on the checkboxes to the left of the column name while importing.

attribute_table_import_alias.png */

Table Panel

attribute_browser26.png

When Cytoscape is started, the Table Panel appears in the bottom right of the main Cytoscape window. This browser can be hidden and restored using the F5 key or the View → Show/Hide Table Panel menu option. Like other Panels, the browser can be undocked by pressing the little icon in the top right corner.

To swap between displaying node, edge, and network Data Tables use the tabs on the bottom of the Table Panel. The Table Panel displays columns belonging to selected nodes and/or edges and the currently selected network. To populate the panel with rows (as pictured above), simply select nodes and/or edges in a loaded network. By default, only the ID of nodes and edges is shown. To display more than just the ID, click the Show Column attributes_select_icon.png button and choose the columns that are to be displayed (select various columns by clicking on them, and then click elsewhere on the screen to close the column list).

Most column values can be edited by double-clicking the cell (only the ID cannot be edited). Newline characters can be inserted into String columns either by pressing Enter or by typing "\n". Once finished editing, click outside of the editing cell in the Table Panel or press Shift-Enter to save your edits. Pressing Esc while editing will undo any changes.

Rows in the panel can be sorted alphabetically by specific column by clicking on a column heading. A new column can be created using the Create New column attributes_new_icon.png button, and must be one of four types – integer, string, real number (floating point), or boolean. Columns can be deleted using the Delete Columns... attributes_delete_icon.png button. NOTE: Deleting columns removes them from Cytoscape, not just the Table Panel! To remove columns from the panel without deleting them, simply unselect the column using the Select Columns attributes_select_icon.png button.

The right-click menu on the Attribute Browser has several functions, such as exporting attribute information to spreadsheet applications. For example, use the right-click menu to Select All and then Copy the data, and then paste it into a spreadsheet application. Each attribute browser panel also has a button for importing new attributes: attributes_import_icon.png .

The Node Attribute Browser panel has additional buttons for loading Gene Expression attribute matrices ( attributes_gene_expr_icon.png ) as node attributes.

Attribute Batch Editor

attribute_editor26.png The Attribute Browser has an Attribute Batch Editor. This enables you to set and modify attribute values for selected nodes or edges of a specified attribute at once. For example, if you want to create a new attribute called Modules and set module names for each group of selected nodes, you can use Set command from this editor.

Cytoscape_3/UserManual/Columns (last edited 2016-04-26 22:15:22 by server2)

Funding for Cytoscape is provided by a federal grant from the U.S. National Institute of General Medical Sciences (NIGMS) of the Na tional Institutes of Health (NIH) under award number GM070743-01. Corporate funding is provided through a contract from Unilever PLC.

MoinMoin Appliance - Powered by TurnKey Linux