Allows for easy integration of the result of NetSurfP2 (performing external sequence analysis which include Intrinsically Disordered Regions (IDR)) in the IsoformSwitchAnalyzeR workflow. This function also supports using a sliding window to extract IDRs. Please note that due to the 'removeNoncodinORFs' option in
analyzeCPC2 we recommend using analyzeCPC2/analyzeCPAT before using analyzeNetSurfP2, analyzePFAM and analyzeSignalP if you have predicted the ORFs with
1 2 3 4 5 6 7 8 9
A string indicating the full path to the NetSurfP-2 result file. Can be gziped. If multiple result files were created (multiple web-server runs) just supply all the paths as a vector of strings.
An integer indicating how large a sliding window should be used to calculate a smoothed (via mean) disordered probability score of a particular position in a peptide. This has as a smoothing effect which prevents IDRs from not being detected (or from being split into sub-IDRs) by a single residue with low probability. The trade off is worse accuracy of detecting the exact edges of the IDRs. To turn of smoothing simply set to 1. Default is 5 amino acids.
A double indicating the cutoff applied to the (smoothed) disordered probability score (see "smoothingWindowSize" argument above) for calling a residue as "disordered". The default, 30 amino acids, is an accepted standard for long IDRs.
An integer indicating how long a stretch of disordered amino acid constitute the "region" part of the Intrinsically Disordered Region (IDR) definition. The default, 30 amino acids, is an accepted standard for long IDRs.
A logic indicating whether to make a progress bar (if TRUE) or not (if FALSE). Default is TRUE.
A logic indicating whether to avoid printing progress messages (incl. progress bar). Default is FALSE
Intrinsically Disordered Regions (IDR) are regions of a protein which does not have a fixed three-dimensional structure (opposite protein domains). Such regions are thought to play important roles in all aspects of biology (and when it goes wrong) through multiple different functional aspects - including facilitating protein interactions.
The NetSurfP web-server currently have a restriction of max 4000 sequences in the file uploaded. If you have more than that (one for each isoform in
summary( switchAnalyzeRlist)) we recommend multiple runs each with one of the the files containing subsets - else you can just run the combined fasta file. See extractSequence for info on how to split the amino acid fasta files.
Notes for how to run the external tools:
Use default parameters. If you want to use the webserver it is easily done as follows: 1) Go to http://www.cbs.dtu.dk/services/NetSurfP-2.0/ 2) Upload the amino avoid file (_AA) created with
3) Submit your job.
4) Wait till job is finished (if you submit your email you will receive a notification).
5) In the top-right corner of the result site use the "Export All" bottom to download the results as a CNV file.
6) Supply a string indicating the path to the downloaded cnv file directly to the "pathToNetSurfP2resultFile" argument.
If you run NetSurfP-2 locally just use the "–csv" argument and provide the resulting csv file to the
IDR are only added to isoforms annotated as having an ORF even if other isoforms exists in the file. This means if you quantify the same isoform many times you can just run NetSurfP2 once on all isoforms and then supply the entire file to
Please note that the
analyzeNetSurfP2() function will automatically only import the NetSurfP-2 results from the isoforms stored in the switchAnalyzeRlist - even if many more are stored in the result file.
A column called 'idr_identified' is added to
isoformFeatures containing a binary indication (yes/no) of whether a transcript contains any protein domains or not. Furthermore the data.frame 'idrAnalysis' is added to the
switchAnalyzeRlist containing positional data of each IDR identified.
The data.frame added have one row per isoform and contains the columns:
isoform_id: The name of the isoform analyzed. Matches the 'isoform_id' entry in the 'isoformFeatures' entry of the switchAnalyzeRlist
orf_aa_start: The start coordinate given as amino acid position (of the ORF).
orf_aa_end: The end coordinate given as amino acid position (of the ORF).
idr_type: A text string indicating the IDR type (one of 'IDR' or 'IDR_w_binding_region'.
transcriptStart: The transcript coordinate of the start of the IDR.
transcriptEnd: The transcript coordinate of the end of the IDR.
idrStarExon: The exon index in which the start of the IDR is located.
idrEndExon: The exon index in which the end of the IDR is located.
idrStartGenomic: The genomic coordinate of the start of the IDR.
idrEndGenomic: The genomic coordinate of the end of the IDR.
This function : Vitting-Seerup et al. The Landscape of Isoform Switches in Human Cancers. Mol. Cancer Res. (2017).
NetSurfP-2 : Klausen et al: NetSurfP-2.0: improved prediction of protein structural features by integrated deep learning. BioRxiv (2018).
Add the following code to your website.
For more information on customizing the embed code, read Embedding Snippets.