Difference between revisions of "iRefScape plugin menu"

Latest revision as of 15:45, 6 July 2011

Search tools

Retrieve interactions for the selected nodes

To load all protein-protein interactions and complexes involving one or more selected nodes. This action is the same as performing a iteration=1 search using iRefScape for the selected nodes.

Expand one level

To load all protein-protein interactions and complexes involving at least one of the nodes in the current network. The behaviour is same as performing iteration=1 search using iRefScape for all the nodes.

Load interactions between neighbours

To complete the interactions between the currently loaded nodes. When a search & load operation is performed in iRefScape, the network returned contains all the proteins interacting with the query and the corresponding interactions. This does not return interactions between the neighbours of the query. This operation is the same as performing an iteration=0 search using iRefScape for all the nodes. This action has no effect for networks for which this operation has already been performed using the option presented at the end of the search.

Clear load history (Reload everything next time)

This will clear the iRefScape cache memory containing currently loaded nodes and edges. IRefScape keeps track of what is loaded to avoid reloading and thus increase efficiency. Therefore, if a search is performed twice,the network will not be re-loaded unless the user has requested that results be shown in a new view or they have selected this menu option. If the user wishes to reload the network then this option has to be used. When using other methods of expanding the network like “Expand one level” iRefScape handles the cache clearing automatically.

Reset node degree

This option resets the i.alive_degree of nodes. i.alive_degree provides how many nodes with a certain attribute type is connected to each node (set using filters).

Load user variables

Note

This section is being updated.

User variables can be attached to nodes and be browsed using the attribute browser. This file can not be used as a searchable index (can not be used as a search type). Please see section iRefScape user searchable index for details on searchable indices.

There are three ways to load own variables for the user.

Use the Cytoscape attribute loading feature (Cytoscape manual)
Use a use attribute file with iRefScape (described in this section)
Include the attribute with the batch search file. (Described in the section Attribute batch file.)

The iRefScape user attribute loader is provided as a complementing feature to the Cytoscape node attribute loading (Cytoscape manual). For most of the attribute loading operations the Cytoscape node attribute loader is sufficient and easier to use. However, when the iRefScape node attribute file is used, this can be used by using the menu entry iRefScape-> Search tools > Load user variables. In addition the file will be available for subsequent operations.

iRefScape user variable file format

The first line of the file provides instructions and this line is compulsory.

Example. 
#i.rog	New_attribute

The first line always starts with a hash ("#") and immediately followed by the iReFscape variable name. This iRefScape variable name is used to locate the nodes via the new attribute will be attached. Then a tab is used as a column separator, followed by the name of the user attribute name.This user attribute name should be unique( not already used). In the above example the user attribute to use is the i.rog and the user attribute name is "New_attribute".

From the second line onwards, the attributes with the mapping attribute are provided.

Example 
4399398	TENC1|UniProtKB:Q63HR2|

The first column provides the iRefScape attribute to use and the second column provides the user attribute. Multiple attributes should be separated with a pipe ("|"). The example line shown would locate the node with i.rog=4399398 and attach the "TENC1|UniProtKB:Q63HR2|" value to it with the attribute name "New_attribute"

Each column is separated by a TAB.
Each line ends with a new line character ("\n")
The file should be constructed using a plain text editor (e.g. Kate, notepad) and word processing software like Microsoft word should not be used to construct this file.
The file extension is ".txt"
Sample file "ONE__EXT__ROG_#Name_5_.iruv" can be found in the iRefScape installation directory (iRefIndex directory)
The file name should have the format _rog_USER_VARIABLE_NAME.iruv (The text in bold is supplied by the user. e.g., _rog_myAttribute.iruv ).

Sample file
#i.rog	New_name
4399398	TENC1|UniProtKB:Q63HR2|
452957	GFI1B|UniProtKB:Q5VTD9|
561552	TENC1|UniProtKB:Q63HR2-4|
534065	GFI1B_MOUSE|UniProtKB:O70237|

View tools

Toggle selected multi-edges

iRefScape creates multiple edges between nodes to represent multiple evidences. If an interaction between two proteins has evidence from both MINT and IntAct, there will be 2 edges; one for MINT and one for IntAct. Although this provides more information for the user, sometime the user may prefer to collapse these edges to a single edge to facilitate viewing. When this action is performed on a network, all but a randomly selected edge between each node is hidden. The edges which are hidden has the i.flag=1 and the one remaining has i.flag=0. Therefore, while this process is random by default, the user can control which edges to keep and which to hide by editing the i.flag edge attribute before using the toggle multi-edge option.

Zoom to selected

This action brings the selected node(s) to the centre of the screen and makes the nodes as large as possible given that all selected nodes are visible. This action can also be performed manually using Cytoscape's zoom tool.

Select last iRefScape selection

This action shows the last selection performed by an iRefScape operation. This features does not record user selections or selections made by using Cytoscape tools (e.g filters).

Select nodes with different taxid than query node

Some interactions may involve proteins from multiple species. An interaction may truly occur between proteins from two species (e.g. an interaction between a Human protein and a virus protein). In other cases, this may be an artefact of how data was entered by the source database.

Select between nodes

This option highlights (selects) nodes interacting with at least two nodes that have been pre-selected by the user. The node attribute i.alive_degree will be recalculated to reflect the degree of each node with respect to this pre-selection.

Show spoke-represented complexes

Some complexes are represented as a set of binary interactions by some sources. This action attempts to highlight such complexes as a single unit by attaching them all to a single pseudonode.

Grouping

Reset group

This action clears any groups created for a pairwise comparison or presentation of nodes.

Set group=1 for selection

This adds the selected nodes to the first group of nodes in a comparison operation.

Set group=2 for selection

This adds the selected nodes to the second group of nodes in a comparison operation.

Create comparison table

With two groups defined using the above operations, this action causes a table to be displayed showing the first group of nodes across the top of the table (as column headings) and the second group of nodes down the side of the table (as row headings). In the body of the table, each cell situated in a particular location (defined in terms of a particular column and row) represents one or more nodes that connect the node featured in the heading for the cell's column with the node featured in the heading for the cell's row.

Hide/Un-hide

Hide selected nodes

This action hides the selected nodes. This operation is performed in a independent thread and more efficient than hiding using Cytoscape's 'hide node' utility for large networks.

Hide nodes (except pseudonodes)

This action hides all select nodes which represent proteins. This will not hide pseudonodes representing a complex, a collapsed area or a collapsed hub.

Hide nodes not selected

Hides all nodes which are not currently selected

Hide nodes not selected (except pseudonodes)

Hides all nodes which are not currently selected and that represent proteins. This will not hide pseudonodes representing a complex, a collapsed area or a collapsed hub.

Un-hide all

Un-hides all nodes which are hidden by the user.

Safe mode

This option is only available when using Java 1.5 and will not appear for Java 1.6 or newer. Selecting this will un-dock the iRefScape window and handles errors and exceptions thrown due to bugs in Java 1.5. When this mode is activated not all graphic features will be available.

All iRefIndex Pages

Follow this link for a listing of all iRefIndex related pages (archived and current).

@@ Line 2: / Line 2: @@
 ===Retrieve interactions for the selected nodes===
-To load all protein-protein interactions and complexes involving one or more selected nodes. This action is the same as performing a iteration=1 search using iRefScape for the selected nodes.
+To load all protein-protein interactions and complexes involving one or more '''selected nodes'''. This action is the same as performing a iteration=1 search using iRefScape for the selected nodes.
 ===Expand one level===
@@ Line 8: / Line 8: @@
 ===Load interactions between neighbours===
-To complete the interactions between the currently loaded nodes. When a search & load operation is performed in iRefScape the network retuned contains all the proteins interacting with the query and the corresponding interactions. This does not return interactions between the neighbours of the query. This operation is same as performing a iteration=0 search using iRefScape for all the nodes.
+To complete the interactions between the currently loaded nodes. When a search & load operation is performed in iRefScape, the network returned contains all the proteins interacting with the query and the corresponding interactions. This does not return interactions between the neighbours of the query. This operation is the same as performing an iteration=0 search using iRefScape for all the nodes.
 This action has no effect for networks for which this operation has already been performed using the option presented at the end of the search.
 ===Clear load history (Reload everything next time)===
-This will clear the iRefScape cache memory containing currently loaded nodes and edges. IRefScape keep track of what is loaded to avoid reloading and thus increase efficiency. Therefore, if a search is performed twice without requesting to make a new view  or selecting this menu option the network will not be re-loaded. If the user wishes to reload the network then this option has to be used. When using other methods of expanding network like “Expand one level” iRefScape handles the cache clearing automatically.
+This will clear the iRefScape cache memory containing currently loaded nodes and edges. IRefScape keeps track of what is loaded to avoid reloading and thus increase efficiency. Therefore, if a search is performed twice,the network will not be re-loaded unless the user has requested that results be shown in a new view or they have selected this menu option.  If the user wishes to reload the network then this option has to be used. When using other methods of expanding the network like “Expand one level” iRefScape handles the cache clearing automatically.
 ===Reset node degree===
 This option resets the i.alive_degree of nodes.  i.alive_degree provides how many nodes with a certain attribute type is connected to each node (set using filters).
-==Load user variables==
+===Load user variables===
-Users can load there own variables for proteins which are mapped to a ROGID. The file should follow the format given below;
-#Should be a plain text file with exactly two columns and each line ending with a new line character (pressing enter).
-#First column should contain the ROGID
-#Second column should contain the user attribute/variable.
-#The file name should have the format _rog_#USER_VARIABLE_NAME.iruv (The text between # and the .iruv will be variable name)
-<pre>
+{{Note|
-e.g
+This section is being updated.
-#rog	USER_VARIABLE
+}}
-j4H4IZH/ecTvEDjCel+eLTCmFyE9606	1
-j4H4IZH/ecTvEDjCel+eLTCmFyE9606	1
-q6/pRFyay7gQ6bb2rzvKYgfkeaE9606	2
-sODZSppCsuEgRmhSHp3UjwOf2M9606	3
-obze7v7i2yTIIcJjd7laIriNFg89606	4
-Ty0OLkmhoUPjUuLQQv5ykN057oM9606	5
-bhW4sEt1YhYwHnHCyDNV3vvThs9606	6
-Al8M+JdB4H+QnwITh8KcicdI2x49606	6
-rkL/SGL1Enj6KoFkPbbcoJ5vKJE9606	6
-</pre>
+User variables can be attached to nodes and be browsed using the attribute browser. This file can not be used as a searchable index (can not be used as a search type). Please see section [[#iRefScape_user_searchable_index|iRefScape user searchable index]] for details on searchable indices.
+There are three ways to load own variables for the user.
+#Use the  Cytoscape attribute loading feature ([http://cytoscape.org/manual/Cytoscape2_8Manual.html#Node%20and%20Edge%20Attributes Cytoscape manual])
+#Use a use attribute file with iRefScape (described in this section)
+#Include the attribute with the batch search file. (Described in the section [[#Attribute_batch_file|Attribute batch file]].)
+The iRefScape user attribute loader is provided as a complementing feature to the Cytoscape node attribute loading ([http://cytoscape.org/manual/Cytoscape2_8Manual.html#Node%20and%20Edge%20Attributes Cytoscape manual]). For most of the attribute loading operations the Cytoscape node attribute loader is sufficient and easier to use. However, when the iRefScape node attribute file is used, this can be used by using the menu entry iRefScape-> Search tools > Load user variables. In addition the file will be available for subsequent operations.
+====iRefScape user variable file format====
+The first line of the file provides instructions and this line is compulsory.
+ Example.
+ #i.rog	New_attribute
+The first line always starts with a hash ("#") and immediately followed by the iReFscape  variable name. This iRefScape variable name is used to locate the nodes via the new attribute will be attached. Then a tab is used as a column separator, followed by the name of the user attribute name.This user attribute name should be unique( not already used). In the above example the user attribute to use is the i.rog and the user attribute name is "New_attribute".
+From the second line onwards, the attributes with the mapping attribute are provided.
+ Example
+ 4399398	TENC1|UniProtKB:Q63HR2|
+The first column provides the iRefScape attribute to use and the second column provides the user attribute. Multiple attributes should be separated with a pipe ("|"). The example line shown would locate the node with i.rog=4399398 and attach the "TENC1|UniProtKB:Q63HR2|" value to it with the attribute name "New_attribute"
+*Each column is separated by a TAB.
+*Each line ends with a new line character ("\n")
+*The file should be constructed using a plain text editor (e.g. Kate, notepad) and word processing software like Microsoft word should not be used to construct this file.
+* The file extension is ".txt"
+* Sample file "ONE__EXT__ROG_#Name_5_.iruv" can be found in the iRefScape installation directory (iRefIndex directory)
+*The file name should have the format _rog_'''USER_VARIABLE_NAME'''.iruv (The text in bold is supplied by the user.  e.g., _rog_myAttribute.iruv ).
+ Sample file
+ #i.rog	New_name
+ 4399398	TENC1|UniProtKB:Q63HR2|
+	GFI1B|UniProtKB:Q5VTD9|
+	TENC1|UniProtKB:Q63HR2-4|
+	GFI1B_MOUSE|UniProtKB:O70237|
 ==View tools==
 ===Toggle selected multi-edges===
-iRefScape creates multiple edges between nodes to represent multiple evidences (if the same interaction a between two proteins represented by two nodes appears in MINT and IntAct there will be 2 edges, one for MINT and one for IntAct). Although this provides more information for the user, sometime the user may prefer to collapse this edges to a single edge to ease the observation. When this action is performed on a network all but a randomly selected edge between each node is hidden. The edges which are hidden has the i.flag=1 and the once remain has i.flag=0. Therefore, all this process is random by default the user can control which edges to remain and which to hid by using the i.flag edge attribute,
+iRefScape creates multiple edges between nodes to represent multiple evidences. If an interaction between two proteins has evidence from both MINT and IntAct, there will be 2 edges; one for MINT and one for IntAct. Although this provides more information for the user, sometime the user may prefer to collapse these edges to a single edge to facilitate viewing. When this action is performed on a network, all but a randomly selected edge between each node is hidden. The edges which are hidden has the i.flag=1 and the one remaining has i.flag=0. Therefore, while this process is random by default, the user can control which edges to keep and which to hide by editing the i.flag edge attribute before using the '''toggle multi-edge''' option.
 ===Zoom to selected===
-This action brings the selected node/nodes to the centre of the screen and make the nodes large as possible given that all selected nodes are visible. This action could also be performed using Cytoscapes zoom option.
+This action brings the '''selected node(s)''' to the centre of the screen and makes the nodes as large as possible given that all selected nodes are visible. This action can also be performed manually using Cytoscape's zoom tool.
 ===Select last iRefScape selection===
-This action show the last selection operation performed by an iRefScape operation. This features do not record mouse selection of selection by other means than iRefScape selection operations (e.g filters)
+This action shows the last selection '''performed by an iRefScape operation'''. This features does not record user selections or selections made by using Cytoscape tools (e.g filters).
 ===Select nodes with different taxid than query node===
-Some interactions may involve proteins from multiple species. This may be due to that the interaction is really between proteins of two specises (e.g. an interaction between a Human protein and a virus protein), or may be because the proteins selected to demonstrate the interaction exists as from different species in the protein databases.
+Some interactions may involve proteins from multiple species. An interaction may truly occur between proteins from two species (e.g. an interaction between a Human protein and a virus protein).  In other cases, this may be an artefact of how data was entered by the source database.
 ===Select between nodes===
-This option highlights (selects) nodes interacting with at least two selected nodes by the user.
+This option highlights (selects) nodes interacting with at least two nodes that have been pre-selected by the user.  The node attribute '''i.alive_degree''' will be recalculated to reflect the degree of each node with respect to this pre-selection.
 ===Show spoke-represented complexes===
 Some complexes are represented as a set of binary interactions by some sources. This action attempts to highlight such complexes as a single unit by attaching them all to a single pseudonode.
+== Grouping ==
+=== Reset group ===
+This action clears any groups created for a pairwise comparison or presentation of nodes.
+=== Set group=1 for selection ===
+This adds the selected nodes to the first group of nodes in a comparison operation.
+=== Set group=2 for selection ===
+This adds the selected nodes to the second group of nodes in a comparison operation.
+=== Create comparison table ===
+With two groups defined using the above operations, this action causes a table to be displayed showing the first group of nodes across the top of the table (as column headings) and the second group of nodes down the side of the table (as row headings). In the body of the table, each cell situated in a particular location (defined in terms of a particular column and row) represents one or more nodes that connect the node featured in the heading for the cell's column with the node featured in the heading for the cell's row.
 ==Hide/Un-hide==
 ===Hide selected nodes===
-This action hides the selected nodes. When this action activated the nodes which are selected (manually or by a filter) are hidden from the view. This operation is performed in a independent thread and more efficient than hiding using Cytoscape node hide for large networks.
+This action hides the selected nodes. This operation is performed in a independent thread and more efficient than hiding using Cytoscape's 'hide node' utility for large networks.
 ===Hide nodes (except pseudonodes)===
-This action hides all select nodes which represent proteins. This will not hide pseudonodes representing a complex, a collapsed area or a hub bi-parse.
+This action hides all select nodes which represent proteins. This will not hide pseudonodes representing a complex, a collapsed area or a collapsed hub.
 ===Hide nodes not selected===
 Hides all nodes which are not currently selected
 ===Hide nodes not selected (except pseudonodes)===
-Hides all nodes which are not currently selected and that represent proteins. This will not hide pseudonodes representing a complex, a collapsed area or a hub bi-parse.
+Hides all nodes which are not currently selected and that represent proteins. This will not hide pseudonodes representing a complex, a collapsed area or a collapsed hub.
 ===Un-hide all===
@@ Line 79: / Line 111: @@
 ==Safe mode==
-This option is only available when using JAVA 1.5 and will not appear for Java 1.6 or never. Selecting this will un-dock the iRefScape window and handles errors and exceptions thrown due to bugs in JAVA 1.5. When this mode is activated not all graphic features will be available.
+This option is only available when using Java 1.5 and will not appear for Java 1.6 or newer. Selecting this will un-dock the iRefScape window and handles errors and exceptions thrown due to bugs in Java 1.5. When this mode is activated not all graphic features will be available.
+== All iRefIndex Pages ==
+Follow this link for a listing of all iRefIndex related pages (archived and current).
+[[Category:iRefIndex]]

Anonymous

Search