Cytoscape App Store - XlinkCyNET

Details
Release History

Categories: 3d visualization, annotation, automation, data visualization, graph analysis, import, interaction database, molecular structure, network analysis, network generation, online data import, PPI-network, visualization

**XlinkCyNET** is an open-source Java plugin that generates residue-to-residue connections provided by XL-MS in protein interaction networks. Importantly, it provides an interactive interface for the exploration of cross-links and offers various options to display protein domains. Moreover, XlinkCyNET is integrated to ___PyMOL___, allowing to visualize all identified cross-links in the protein structure. The app works well in complex networks containing thousands of proteins. A [video](https://www.youtube.com/embed/uLuJ7RlFb3I?rel=0&showinfo=0) demonstrating how the application works can be found on the [software website](https://www.theliulab.com/software/xlinkcynet). A detailed [tutorial](http://dx.doi.org/10.21203/rs.3.pex-1172/v1), which explains step by step the functionality of all parameters is available at *Protocol Exchange*. ***Please cite our paper:*** Lima, DB, *et al.*, **[“XlinkCyNET: A Cytoscape Application for Visualization of Protein Interaction Networks Based on Cross-Linking Mass Spectrometry Identifications”](https://doi.org/10.1021/acs.jproteome.0c00957)**, Journal of Proteome Research (20): 1943–1950, 2021. ###Features ↪ Visualize protein-protein interaction network based on cross-linking mass spectrometry data ↪ Apply a residue-to-residue layout to a Cytoscape interaction network ↪ Annotate protein domains to all nodes in the network ↪ Map cross-links on high-resolution structures through PyMOL ↪ *AlphaFold* is possible to be used to retrieve protein structures. <hr/> ###Input file The input file must have the following columns, which should be assigned to the correct column type in Cytoscape. *Required columns:* `gene_a` → represents the node name: *source node (Local)*, `gene_b` → represents the node name: *target node (Local)*, `protein_a` → represents the Uniprot protein accession number of protein a in the following format: db|Unique_Identifier|Entry_Name: *Source Node Attribute (Shared)*, `protein_b` → represents the Uniprot protein accession number of protein b in the following format: db|Unique_Identifier|Entry_Name: *Target Node Attribute (Shared)*, `length_protein_a` → represents the number of residues of protein a: *Source Node Attribute (Shared)*, `length_protein_b` → represents the number of residues of protein b: *Target Node Attribute (Shared)*, `crosslinks_ab` → represents all links (inter and intra) between protein *a* and *b*. The links must be separated by ‘*#*’: *Edge attribute (Shared)*, `crosslinks_ba` → represents all links (inter and intra) between protein *b* and *a*. The links must be separated by ‘*#*’: *Edge attribute (Shared)*, *Optional columns:* `ppi_score` → represents the score of the interaction between two proteins: *Edge attribute (Shared)*, `score_ab` → represents the score of each intra/interlink from protein *a* to protein *b*. The value must be separated by '#': *Edge attribute (Shared)*. *Example: 2.33e-24#3.67e-19#8.55e-7*, `score_ba` → represents the score of each intra/interlink from protein *b* to protein *a*. The value must be separated by '#': *Edge attribute (Shared)*. *Example: 2.33e-24#3.67e-19#8.55e-7*. Example file can be found [here](https://github.com/diogobor/XlinkCyNET/tree/master/example_data). <hr> ###Automation ↪ XlinkCyNET supports Cytoscape Automation from both commands and CyREST by providing six different commands: <li>`applyRestoreStyle` attributes: → *nodesName*: Give the node(s) name, separated by comma, that will be expanded or restored. (type 'all' to set style to all nodes) → *proteinHorizontalExpansion*: Set whether the protein will be expanded horizontally or not. → *proteinScalingFactor*: Set a scale factor (between 0 and 1) to the protein length.</li> <li>`loadProteinDomains` attributes: → *fileName* : Name of the protein domain file. (Supported formats: .tab and .csv) → *fromPfamServer*: Set which server the protein domains will be retrieved. (true = Pfam, false = Supfam) → *nodesName*: Give the node(s) name, separated by comma, to get domains. (type 'all' to get domains of all nodes)</li> <li>`exportProteinDomains` attribute: → *fileName*: Name of the protein domain file. (Supported format: *.csv)</li> <li>`setProteinDomainsColor` attributes: → *domainName*: Name of the protein domain to change the color. → *proteinDomainColor*: Set a color to a protein domain (*e.g., 'red' or '#FF0000' or 'FF0000'*)</li> <li>`loadPTMs ` attributes: → *fileName* : Name of the PTM(s) file. (Supported formats: .csv) → *nodesName*: Give the node(s) name, separated by comma, to find PTM(s). (type 'all' to get domains of all nodes)</li> <li>`exportPTMs` attribute: → *fileName*: Name of the protein domain file. (Supported format: *.csv)</li> <li>`loadMonolinks ` attributes: → *fileName* : Name of the Monolinked peptide(s) file. (Supported formats: .csv)</li> <li>`exportMonolinks` attribute: → *fileName*: Name of the protein domain file. (Supported format: *.csv)</li> <li>`setParameters` attributes: → *displayInterlinks*: Display or hide all identified interlinks → *displayIntralinks*: Display or hide all identified intralinks → *displayMonolinks*: Display or hide all identified intralinked peptides → *displayPTM*: Display or hide all PTM(s) → *displayLinksLegend*: Display or hide the legends of all identified cross-links → *fontSizeLinksLegend*: Set the font size of the legend of all identified cross-links → *fontSizeNodesName*: Set the font size of the name of all nodes → *interlinksColor*: Set a color to all identified interlinks (*e.g., 'red' or '#FF0000' or 'FF0000'*) → *intralinksColor*: Set a color to all identified intralinks (*e.g., 'red' or '#FF0000' or 'FF0000'*) → *pTMColor*: Set a color to all post-translational modifications (*e.g., 'red' or '#FF0000' or 'FF0000'*) → *monoLinksPeptideColor*: Set a color to all identified intralinked peptides (*e.g., 'red' or '#FF0000' or 'FF0000'*) → *nodeBorderColor*: Set a color to all nodes borders (*e.g., 'red' or '#FF0000' or 'FF0000'*) → *opacityBorderNodes*: Set the opacity of the border of all nodes (range between 0 - transparent and 255 - opaque) → *opacityLinks*: Set the opacity of all identified cross-links (range between 0 - transparent and 255 - opaque) → *opacityLinksLegend*: Set the opacity of the legend of all identified cross-links (range between 0 - transparent and 255 - opaque) → *scoreInterlink*: Set the threshold score to interlinks. All interlinks that have a -log(score) above the threshold will be displayed. → *scoreIntralink*: Set the threshold score to intralinks. All intralinks that have a -log(score) above the threshold will be displayed. → *scorePPIlink*: Set the threshold score to PPI links. All PPI links that have a -log(score) above the threshold will be displayed. → *widthBorderNodes*: Set the width of the border of all nodes (range between 1 and 10) → *widthLinks*: Set the width of all identified cross-links (range between 1 and 10) </li> <li>`readMe`</li> <hr/> Don't hesitate to send us any comments, questions or bug reports to: <img src="http://diogobor.droppages.com/emailBorderless.png" alt="email"/> Any feedback is welcomed! Have fun! :)

Authors:

1.5.2

Works with Cytoscape 3.8

Release Notes

**New:** ↪ Visualize cross-linkings in a customized PDB file. Now it is possible to input a PDB file instead of automatically downloading it from Uniprot or AlphaFold servers. To enable it, check the option 'Use customized PDB file' on *'XlinkCyNET Settings'* .

1.5.1

Works with Cytoscape 3.8

Release Notes

**New:** ↪ Predict protein structure using **AlphaFold** algorithm. The feature works not only for a single node but also for single interactions (between two proteins).

1.5

Works with Cytoscape 3.8

Release Notes

**New:** ↪ Predict protein structure using **AlphaFold** algorithm. To enable this feature, check *'AlphaFold'* option in the 'Settings' panel: Apps → XlinkCyNET → Settings

1.4.3

Works with Cytoscape 3.8

Release Notes

**Bug fixed** ↪ Optimized method to restore nodes and edges.

1.4.2

Works with Cytoscape 3.8

Release Notes

**Bug fixed** ↪ Optimized reading method when the number of cross-links is different from the number of cross-link scores.

1.4.1

Works with Cytoscape 3.8

Release Notes

**Bug fixed** ↪ Optimized plotting when vertical proteins are displayed.

1.4

Works with Cytoscape 3.8

Release Notes

###Break changes ↪ Bug fixed when more the one node with the same name was imported into the network. Now, ***at the import time***, it is necessary to set the required columns `crosslinks_ab` and `crosslinks_ba` as well as the optional columns `ppi_score`, `score_ab` and `score_ba` as **Edge Attribute**.

1.3.2

Works with Cytoscape 3.8

Release Notes

**Bug fixed** ↪ Updated URL to retrieve protein domains from *Supfam* server

1.3.1

Works with Cytoscape 3.8

Release Notes

**Bug fixed** ↪ Overlapping of some objects in the Single node interface.

1.3

Works with Cytoscape 3.8

Release Notes

**New:** ↪ Display post-translational modifications. ↪ Display mono-linked peptides throughout the protein.

1.2.5

Works with Cytoscape 3.8

Release Notes

**Bug fixed** ↪ Load subnetworks method when other columns are already included.

1.2.4

Works with Cytoscape 3.8

Release Notes

**Optimization:** ↪ Optimized refresh methods when some parameter is changed on *Settings Panel*. Now the layout is automatically updated. **Bug fixed** ↪ PyMOL feature is fixed on Linux. The feature is compatible with Windows, Linux and MacOS operating systems.

1.2.3

Works with Cytoscape 3.8

Release Notes

**Optimization:** ↪ Optimized method to align two protein sequences in order to figure out the chain in the PDB or CIF file.

1.2.2

Works with Cytoscape 3.8

Release Notes

**Optimization:** ↪ Optimized method to retrieve PDB identifications. **Break changes** ↪ In order to make more sense, we have changed the name of two columns of the input file. They are: **crosslinks_ab** and **cross_links_ba** instead of pro_site_ab and pro_site_ba. Now, the input files must have the following columns: *Required columns:* `gene_a` → represents the node name: *source node (Local)*, `gene_b` → represents the node name: *target node (Local)*, `protein_a` → represents the Uniprot protein accession number of protein a in the following format: db|Unique_Identifier|Entry_Name: *Source Node Attribute (Shared)*, `protein_b` → represents the Uniprot protein accession number of protein b in the following format: db|Unique_Identifier|Entry_Name: *Target Node Attribute (Shared)*, `length_protein_a` → represents the number of residues of protein a: *Source Node Attribute (Shared)*, `length_protein_b` → represents the number of residues of protein b: *Target Node Attribute (Shared)*, `crosslinks_ab` → represents all links (inter and intra) between protein *a* and *b*. The links must be separated by ‘*#*’: *Source Node Attribute (Shared)*, `crosslinks_ba` → represents all links (inter and intra) between protein *b* and *a*. The links must be separated by ‘*#*’: *Target Node Attribute (Shared)*, *Optional columns:* `ppi_score` → represents the score of the interaction between two proteins: *Edge attribute (Shared)*, `score_ab` → represents the score of each intra/interlink from protein *a* to protein *b*. The value must be separated by '#': *Source Node Attribute (Shared)*. *Example: 2.33e-24#3.67e-19#8.55e-7*, `score_ba` → represents the score of each intra/interlink from protein *b* to protein *a*. The value must be separated by '#': *Target Node Attribute (Shared)*. *Example: 2.33e-24#3.67e-19#8.55e-7*.

1.2.1

Works with Cytoscape 3.8

Release Notes

**Bug fixed** ↪ It has fixed an issue in the method for importing protein domains when they have already stored in the table.

1.2

Works with Cytoscape 3.8

Release Notes

**New:** ↪ XlinkCyNET now is integrated to PyMOL. The user can visualize protein structures with all identified cross-links. ↪ XlinkCyNET generates *.pml (script file) with all identified cross-linked and call PyMOL directly from Cytoscape.

1.1.3

Works with Cytoscape 3.8

Release Notes

**New:** ↪ Filter results by using protein-protein interaction (PPI) or inter/intralinks score. In this case, three more columns are required in the initial network: <li>`ppi_score`, which represents the score of the interaction between two proteins (PPI score).</li> <li>`score_ab`, which represents the score of each intra/interlink from protein *a* to protein *b*. The value must be separated by '#'. *Example: 2.33e-24#3.67e-19#8.55e-7*</li> <li>`score_ba`, which represents the score of each intra/interlink from protein *b* to protein *a*. The value must be separated by '#'. *Example: 2.33e-24#3.67e-19#8.55e-7*</li> ↪ XlinkCyNET now supports Cytoscape Automation by providing six commands: <li>`readMe`</li> <li>`applyRestoreStyle`</li> <li>`setParameters`</li> <li>`loadProteinDomains`</li> <li>`exportProteinDomains`</li> <li>`setProteinDomainsColor`</li> <hr/> **Optimization:** ↪ Optimized domains download method (Supfam or Pfam).