Recent Changes - Search:

HomePage

Main.HomePage History

Hide minor edits - Show changes to output

Changed line 5 from:
Alon S, Erew M, Eisenberg E. DREAM: a webserver for the identification of editing sites in mature miRNAs using deep sequencing data (2015). Bioinformatics, 31:2568-2570.
to:
Alon S, Erew M, Eisenberg E (2015). DREAM: a webserver for the identification of editing sites in mature miRNAs using deep sequencing data. Bioinformatics, 31:2568-2570.
Added line 4:
Added lines 2-4:

'''Based on the Following Publication:'''
Alon S, Erew M, Eisenberg E. DREAM: a webserver for the identification of editing sites in mature miRNAs using deep sequencing data (2015). Bioinformatics, 31:2568-2570.
Changed lines 26-27 from:
The search for possible RNA editing sites is performed for every position in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position must be corrected accordingly. The multiple testing correction can be either 'Bonferroni' or 'Benjamini–Hochberg'. Note that Bonferroni correction is more stringent, but might lead to missing true editing sites. Using Bonferroni correction the reported positions will be only those with P-value less than the supplied P-value divided by the number of tests. If Benjamini–Hochberg correction is chosen, the supplied P-value is the False Discovery Rate (FDR). Note that in the web site the default P-value is set to a high value (0.2). However, the results file contains all the P-values so the detected sites can be easily filtered. Alternatively, the P-value can be adjusted to the required value in the web server. 
to:
The search for possible RNA editing sites is performed for every position in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position must be corrected accordingly. The multiple testing correction can be either 'Bonferroni' or 'Benjamini–Hochberg'. Note that Bonferroni correction is more stringent, but might lead to missing true editing sites. Using Bonferroni correction the reported positions will be only those with P-value less than the supplied P-value divided by the number of tests. If Benjamini–Hochberg correction is chosen, the supplied P-value is the False Discovery Rate (FDR). Note that in the web site the default P-value is set to a high value (0.2). The results file contains all the P-values (including the Raw P-values, the Benjamini-Hochberg-corrected P-values and the Bonferonni-corrected P-values), allowing the user to see directly the effect of various cutoffs on the number of detected sites, and filter the results file accordingly. For users who want to start the process with a more stringent P-value, the P-value can be easily modified in the web server.
Changed lines 32-33 from:
Next, the reads aligned to the genome are converted to counts of each of the four possible nucleotides at each position along the pre-miRNA sequence (miRBase, release 21; http://www.mirbase.org/), for all the pre-miRNAs. Performing this transformation allows focusing the analysis on bona fide miRNA only. In the following step, binomial statistics is applied to distinguish significant modifications in these regions from sequencing errors. The binomial statistics requires the number of mismatches of a given type in a given position, the number of total reads in the given position, and the a-priori sequencing error probability. As only mismatches with Phred score of 30 are allowed (Alon et al., Genome Research, 2012), we use 0.1% as the expected base call error rate. Importantly, binomial statistics do not require any arbitrary expression level filter. It is well suited even for low-expressed miRNAs with low number of sequencing reads, and the P-values computed reflect the absolute number of reads detected, small or large as the case may be. This analysis is performed for every position (except the last two positions of the miRNA due to the extensive adenylation and uridylation) in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position are corrected by using either Bonferroni or Benjamini–Hochberg corrections. Lastly, known SNPs are filtered from the statistically significant modifications detected by the web server, using the lists of common SNPs, dbSNP build 138 and 142 for mouse and human, respectively. 
to:
Next, the reads aligned to the genome are converted to counts of each of the four possible nucleotides at each position along the pre-miRNA sequence (miRBase, release 21; http://www.mirbase.org/), for all the pre-miRNAs. Performing this transformation allows focusing the analysis on bona fide miRNA only. In the following step, binomial statistics is applied to distinguish significant modifications in these regions from sequencing errors. The binomial statistics requires the number of mismatches of a given type in a given position, the number of total reads in the given position, and the a-priori sequencing error probability. As only mismatches with Phred score of 30 are allowed (Alon et al., Genome Research, 2012), we use 0.1% as the expected base call error rate. Importantly, binomial statistics do not require any arbitrary expression level filter. It is well suited even for low-expressed miRNAs with low number of sequencing reads, and the P-values computed reflect the absolute number of reads detected, small or large as the case may be. This analysis is performed for every position (except the last two positions of the miRNA due to the extensive adenylation and uridylation) in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position are corrected by using either Bonferroni or Benjamini–Hochberg corrections. Lastly, known SNPs are filtered from the statistically significant modifications detected by the web server, using the lists of common SNPs, dbSNP builds 138 and 142 for mouse and human, respectively. 
Changed line 68 from:
(a) Known SNPs are filtered from the statistically significant modifications detected by the web server, using the lists of common SNPs, dbSNP build 138 and 142 for mouse and human, respectively. However, the modifications detected can be previously undetected SNPs, rare SNPs, or somatic mutations.
to:
(a) Known SNPs are filtered from the statistically significant modifications detected by the web server, using the lists of common SNPs, dbSNP builds 138 and 142 for mouse and human, respectively. However, the modifications detected can be previously undetected SNPs, rare SNPs, or somatic mutations.
Changed lines 32-33 from:
Next, the reads aligned to the genome are converted to counts of each of the four possible nucleotides at each position along the pre-miRNA sequence (miRBase, release 21; http://www.mirbase.org/), for all the pre-miRNAs. Performing this transformation allows focusing the analysis on bona fide miRNA only. In the following step, binomial statistics is applied to distinguish significant modifications in these regions from sequencing errors. The binomial statistics requires the number of mismatches of a given type in a given position, the number of total reads in the given position, and the a-priori sequencing error probability. As only mismatches with Phred score of 30 are allowed (Alon et al., Genome Research, 2012), we use 0.1% as the expected base call error rate. Importantly, binomial statistics do not require any arbitrary expression level filter. It is well suited even for low-expressed miRNAs with low number of sequencing reads, and the P-values computed reflect the absolute number of reads detected, small or large as the case may be. This analysis is performed for every position (except the last two positions of the miRNA due to the extensive adenylation and uridylation) in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position are corrected by using either Bonferroni or Benjamini–Hochberg corrections.
to:
Next, the reads aligned to the genome are converted to counts of each of the four possible nucleotides at each position along the pre-miRNA sequence (miRBase, release 21; http://www.mirbase.org/), for all the pre-miRNAs. Performing this transformation allows focusing the analysis on bona fide miRNA only. In the following step, binomial statistics is applied to distinguish significant modifications in these regions from sequencing errors. The binomial statistics requires the number of mismatches of a given type in a given position, the number of total reads in the given position, and the a-priori sequencing error probability. As only mismatches with Phred score of 30 are allowed (Alon et al., Genome Research, 2012), we use 0.1% as the expected base call error rate. Importantly, binomial statistics do not require any arbitrary expression level filter. It is well suited even for low-expressed miRNAs with low number of sequencing reads, and the P-values computed reflect the absolute number of reads detected, small or large as the case may be. This analysis is performed for every position (except the last two positions of the miRNA due to the extensive adenylation and uridylation) in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position are corrected by using either Bonferroni or Benjamini–Hochberg corrections. Lastly, known SNPs are filtered from the statistically significant modifications detected by the web server, using the lists of common SNPs, dbSNP build 138 and 142 for mouse and human, respectively.
Changed lines 66-80 from:
Most of the modifications are expected to be A-to-G, which can be a result of A-to-I editing. What can be the nature of the other types of modifications? Among the possible explanations are the following: (a) SNPs or somatic mutations, (b) 5' adenylation and uridylation, (c) problems in the definition of the miRNA, (d) sequencing artifacts, (e) C-to-U RNA editing, or (f) non-canonical RNA editing events:

(a) Known SNPs should be filtered from the statistically significant modifications detected by the web server. This can be done using Galaxy (http://galaxy.psu.edu/):

1. In the Galaxy site choose the “Use Galaxy” option
.

2. Use
the “Get Data” link, and then “UCSC Main” to download data from the UCSC Table Browser.

3. To download the human or mouse SNP dataset, choose “Human” or “Mouse”, respectively, in the “genome” field and “Variation and Repeats” in the “group” field. Make sure that the “track” field is set to “SNPs” and the “region” field is set to “genome”. Then press “get output” and afterwards press “send query to Galaxy”. 

4. Upload the output text file from the web server, using the “Get Data” link, and then “Upload File” link. Choose “interval” in the “File Format” field and locate the file using the “Browse” button. Choose “Human hg19” or “Mouse mm9” in the “Genome” field, for human or mouse respectively, and then press “Execute”.

5. Subtract the genomic locations of the SNPs from the locations of the identified mismatches. Use “Operate on Genomic Intervals” and then “Subtract”. Choose to subtract the SNP dataset from the identified mismatch dataset, make sure that the minimal overlap is set to 1 base, and then press “Execute”. After a while the subtracted file should appear as a new tab in the “History” panel (right side of the screen).

6. View the resulting subtracted file. The file should appear in the upper right corner of the screen under the “History” tab. It can be viewed using the eye icon. If the resulting file is identical to the output file of the web server, then none of the identified modifications are known SNPs.
to:
Most of the modifications are expected to be A-to-G, which can be a result of A-to-I editing. What can be the nature of the other types of modifications? Among the possible explanations are the following: (a) rare SNPs or somatic mutations, (b) 5' adenylation and uridylation, (c) problems in the definition of the miRNA, (d) sequencing artifacts, (e) C-to-U RNA editing, or (f) non-canonical RNA editing events:

(a) Known SNPs are filtered from the statistically significant modifications detected by the web server, using the lists of common SNPs, dbSNP build 138 and 142 for mouse and human, respectively. However, the modifications detected can be previously undetected SNPs, rare SNPs, or somatic mutations.
Changed lines 11-12 from:
Fastq file can be also uploaded directly to the web server, but this option is not recommended as upload times can be quite long for large files (typically ~5GB/hour) and network interruptions may prevent the completion of the upload. To upload the Fastq file, press the 'Choose Files' button and locate the Fastq file in your computer. The progress of the upload is given by a progress bar at the bottom of the page which will be displayed once the 'Start Analyzing' button is pressed. Make sure not to disconnect while the upload is in progress. Once the upload is over a notification email will be sent to you. Make sure to use a unique file name for every uploaded file.
to:
Fastq files can be also uploaded directly to the web server, but this option is not recommended as upload times can be quite long for large files (typically ~5GB/hour) and network interruptions may prevent the completion of the upload. To upload the Fastq file, use the 'Search in folder (Fastq only)' option and press the 'Choose Files' button to locate the Fastq file in your computer. Multiple files can be uploaded simultaneously, use the Control key to select the required files. Compressed Fastq files can also be uploaded using the 'Search in folder (compressed Fastq only)' option. The following compressed file formats are allowed: zip, tar, tar.gz, tar.bz2 and rar. The name of the compressed file must match the name of the fastq file, for example: 'a_data.fastq' should be zipped to 'a_data.zip'. Again, multiple files can be uploaded simultaneously, use the Control key to select the required files. The progress of the upload is given by a progress bar at the bottom of the page which will be displayed once the 'Start Analyzing' button is pressed. Make sure not to disconnect while the upload is in progress. Once the upload is over a notification email will be sent to you. Make sure to use a unique file name for every uploaded file.
Changed line 26 from:
The search for possible RNA editing sites is performed for every position in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position must be corrected accordingly. The multiple testing correction can be either 'Bonferroni' or 'Benjamini–Hochberg'. Note that Bonferroni correction is more stringent, but might lead to missing true editing sites. Using Bonferroni correction the reported positions will be only those with P-value less than the supplied P-value divided by the number of tests. If Benjamini–Hochberg correction is chosen, the supplied P-value is the False Discovery Rate (FDR). 
to:
The search for possible RNA editing sites is performed for every position in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position must be corrected accordingly. The multiple testing correction can be either 'Bonferroni' or 'Benjamini–Hochberg'. Note that Bonferroni correction is more stringent, but might lead to missing true editing sites. Using Bonferroni correction the reported positions will be only those with P-value less than the supplied P-value divided by the number of tests. If Benjamini–Hochberg correction is chosen, the supplied P-value is the False Discovery Rate (FDR). Note that in the web site the default P-value is set to a high value (0.2). However, the results file contains all the P-values so the detected sites can be easily filtered. Alternatively, the P-value can be adjusted to the required value in the web server. 
Changed line 66 from:
Most of the modifications are expected to be A-to-G, which can be a result of A-to-I editing. What can be the nature of the other types of modifications? Among the possible explanations are the following: (a) SNPs or somatic mutations, (b) 5' adenylation and uridylation, (c) problems in the definition of the miRNA, (d) sequencing artifacts, or (e) non-A-to-I RNA editing events:
to:
Most of the modifications are expected to be A-to-G, which can be a result of A-to-I editing. What can be the nature of the other types of modifications? Among the possible explanations are the following: (a) SNPs or somatic mutations, (b) 5' adenylation and uridylation, (c) problems in the definition of the miRNA, (d) sequencing artifacts, (e) C-to-U RNA editing, or (f) non-canonical RNA editing events:
Changed lines 88-90 from:
(e) It has been suggested that non-canonical types of RNA editing may affect RNA (Li et al.,Science, 2011). 
to:
(e) Cytosine-to-uracil (C-to-U) editing can also happen in several mammalian tissues (see for example: Rosenberg et al., Nature Structural & Molecular Biology, 2011).

(f
) It has been suggested that non-canonical types of RNA editing may affect RNA (Li et al.,Science, 2011). 
Changed line 18 from:
The Fastq file of the sequencing reads could be the raw reads without any filter, or filtered reads using Illumina software tools. In the latter case, check 'No, its already pre-processed'. Otherwise, check 'Remove Sequence Adapter' as raw sequencing reads likely contain parts of the adapter sequence. The web server trim these sequences if they are supplied by the user in the fields '5 Adaptor' and '3 Adaptor'. Whereas 5 and 3 are the 5' and 3' ends of the mature miRNA sequence. As the expected length of mature miRNAs is ~21 bases, reads after trimming with length longer than 28 bases or shorter than 15 bases are discarded. Moreover, low-quality reads (as defined by the read quality score) are unlikely to be informative and therefore should be removed. The web server will remove reads with low sequencing quality in more than three positions. Low sequencing quality is defined by Phred quality score (which ranges from 0 to 40) lower than 20.   
to:
The Fastq file of the sequencing reads could be the raw reads without any filter, or filtered reads using Illumina software tools. In the latter case, check 'No, its already pre-processed'. Otherwise, check 'Remove Sequence Adapter' as raw sequencing reads likely contain parts of the adapter sequence. The web server trim these sequences if they are supplied by the user in the fields '5 Adaptor' and '3 Adaptor'. Whereas 5 and 3 are the 5' and 3' ends of the mature miRNA sequence. As the expected length of mature miRNAs is ~21 bases, reads after trimming with length longer than 28 bases or shorter than 15 bases are discarded. Moreover, low-quality reads (as defined by the read quality score) are unlikely to be informative and therefore should be removed. The web server will remove reads with low sequencing quality in more than three positions. Low sequencing quality is defined by Phred quality score (which ranges from 0 to 40) lower than 20 (Alon et al., Genome Research, 2012).   
Changed lines 9-10 from:
The input for the web server is sequencing reads of mature miRNAs in a Fastq format. This web server supports only data obtained using Illumina platform (in Phred+33 format). To upload the Fastq file, press the 'Choose Files' button and locate the Fastq file in your computer. Note that the upload time can be quite long for large files. For example, ~5GB Fastq file will take at least an hour to upload when the average upload speed is 10 Megabits Per Second (Mbps). The progress of the upload is given by a progress bar at the bottom of the page which will be displayed once the 'Start Analyzing' button is pressed. Make sure not to disconnect while the upload is in progress. Once the upload is over a notification email will be sent to you. Make sure to use a unique file name for every uploaded file.
to:
The input for the web server is sequencing reads of mature miRNAs in a Fastq format. This web server supports only data obtained using Illumina platform (in Phred+33 format). The preferred method to supply the sequencing data to the web server is to provide a direct link to the data by choosing the 'Direct link' option. This is done by uploading the data to a public directory in a Dropbox account, then click 'Copy public link' and paste the result in the web server 'Direct link' text box. In addition to the Fastq format, using the direct link the following compressed file formats are allowed: zip, tar, tar.gz, tar.bz2 and rar. Note that the name of the compressed file must match the name of the fastq file, for example: 'a_data.fastq' should be zipped to 'a_data.zip'.

Fastq file can be also uploaded directly to the web server, but this option is not recommended as upload times can be quite long for large files (typically ~5GB/hour) and network interruptions may prevent the completion of the upload. To upload the Fastq file, press the 'Choose Files' button and locate the Fastq file in your computer
. The progress of the upload is given by a progress bar at the bottom of the page which will be displayed once the 'Start Analyzing' button is pressed. Make sure not to disconnect while the upload is in progress. Once the upload is over a notification email will be sent to you. Make sure to use a unique file name for every uploaded file.
Changed lines 15-17 from:
In addition, a direct link to the data can be given by choosing the 'Direct link' option. This is done by uploading the data to a public directory in a dropbox account, then click 'Copy public link' and paste the result in the text box. In addition to the Fastq format, using the direct link the following compressed file formats are allowed: zip, tar, tar.gz, tar.bz2 and rar. Note that the name of the compressed file must match the name of the fastq file, for example: 'a_data.fastq' should be zipped to 'a_data.zip'.

to:
Changed lines 32-35 from:
Next, the reads aligned against the genome are converted to counts of each of the four possible nucleotides at each position along the pre-miRNA sequence, for all the pre-miRNAs. Performing this transformation allow us to focus our analysis only on bona fide miRNA and to use, in the following step, binomial statistics to detect significant modifications inside them. An important parameter for this step is the minimum quality score allowed in the location of the mismatch in order for it to be counted. Naturally, the higher this number is, the lower the probability for sequencing error. However, taking very high quality score filter will give small number of counted modifications. We use a Phred quality score of 30 as the minimum quality score allowed. The sequence and location of the pre-miRNA and the mature miRNA were obtained from miRBase, release 20 (Kozomara and Griffiths-Jones, NAR, 2014).

Finally, binomial statistics is performed to separate sequencing errors from statistically significant modifications. The binomial statistics requires the number of successes (the number of mismatches of a given type in a given position), the number of trials (the total number of counts in the given position), and the sequencing error probability. The sequencing error probability is estimated using the Phred score. As only mismatches with Phred score of 30 are allowed, the expected base call error rate should be 0.1% in each position
. Importantly, binomial statistics do not require any arbitrary expression level filter. It is well suited even for low-expressed miRNAs with low number of sequencing reads, and the P-values computed reflect the absolute number of reads detected, small or large as the case may be. This analysis is performed for every position (except the last two positions of the miRNA due to the extensive adenylation and uridylation) in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position are corrected by using either Bonferroni or Benjamini–Hochberg corrections.
to:
Next, the reads aligned to the genome are converted to counts of each of the four possible nucleotides at each position along the pre-miRNA sequence (miRBase, release 21; http://www.mirbase.org/), for all the pre-miRNAs. Performing this transformation allows focusing the analysis on bona fide miRNA only. In the following step, binomial statistics is applied to distinguish significant modifications in these regions from sequencing errors. The binomial statistics requires the number of mismatches of a given type in a given position, the number of total reads in the given position, and the a-priori sequencing error probability. As only mismatches with Phred score of 30 are allowed (Alon et al., Genome Research, 2012), we use 0.1% as the expected base call error rate. Importantly, binomial statistics do not require any arbitrary expression level filter. It is well suited even for low-expressed miRNAs with low number of sequencing reads, and the P-values computed reflect the absolute number of reads detected, small or large as the case may be. This analysis is performed for every position (except the last two positions of the miRNA due to the extensive adenylation and uridylation) in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position are corrected by using either Bonferroni or Benjamini–Hochberg corrections.
Changed lines 48-49 from:
Location inside pre-miRNA = The position of the modification inside the pre-miRNA (according to miRBase numbering)
to:
Location inside pre-miRNA = The position of the modification inside the pre-miRNA (according to miRBase definitions, release 21)
Changed line 56 from:
Location inside mature sequence = The position of the modification inside the mature miRNA (according to miRBase numbering)
to:
Location inside mature sequence = The position of the modification inside the mature miRNA (according to miRBase definitions, release 21)
Added lines 12-14:

In addition, a direct link to the data can be given by choosing the 'Direct link' option. This is done by uploading the data to a public directory in a dropbox account, then click 'Copy public link' and paste the result in the text box. In addition to the Fastq format, using the direct link the following compressed file formats are allowed: zip, tar, tar.gz, tar.bz2 and rar. Note that the name of the compressed file must match the name of the fastq file, for example: 'a_data.fastq' should be zipped to 'a_data.zip'.

Changed lines 1-3 from:
'''DREAM - Detecting RNA editing associated with miRNAs'''

%center% '''Overview of the Web Server'''
to:
%center% '''DREAM - Detecting RNA editing associated with miRNAs'''

'''Overview of the Web Server'''
Changed lines 1-3 from:
'''Overview of the Web Server'''
to:
'''DREAM - Detecting RNA editing associated with miRNAs'''

%center%
'''Overview of the Web Server'''
Changed line 9 from:
Alternatively, you may want to use a test dataset by choosing the 'Use test dataset' option. The test dataset is of mature miRNAs from mouse cerebellum (accession number SRR346417). If you choose the test dataset there is no need to adjust the parameters, just enter your email address and click 'Start Analyzing'.         
to:
Alternatively, you may want to use a test dataset by choosing the 'Use test dataset' option. The test dataset is of mature miRNAs from mouse cerebellum (accession number SRR346417). If you choose the test dataset the parameters are automatically adjusted, just enter your email address and click 'Start Analyzing'.         
Changed lines 7-8 from:
The input for the web server is sequencing reads of mature miRNAs in a Fastq format. This web server supports only data obtained using Illumina platform (in Phred+33 format). To upload the Fastq file, press the 'Choose Files' button and locate the Fastq file in your computer. Note that the upload time can be quite long for large files. For example, ~5GB Fastq file will take at least an hour to upload when the average upload speed is 10 Megabits Per Second (Mbps). The progress of the upload is given by a progress bar at the bottom of the page which is displayed when the 'Start Analyzing' button is pressed. Make sure not to disconnect while the upload is in progress. Once the upload is over a notification email will be sent to you. Make sure to use a unique file name for every uploaded file.
to:
The input for the web server is sequencing reads of mature miRNAs in a Fastq format. This web server supports only data obtained using Illumina platform (in Phred+33 format). To upload the Fastq file, press the 'Choose Files' button and locate the Fastq file in your computer. Note that the upload time can be quite long for large files. For example, ~5GB Fastq file will take at least an hour to upload when the average upload speed is 10 Megabits Per Second (Mbps). The progress of the upload is given by a progress bar at the bottom of the page which will be displayed once the 'Start Analyzing' button is pressed. Make sure not to disconnect while the upload is in progress. Once the upload is over a notification email will be sent to you. Make sure to use a unique file name for every uploaded file.
Changed lines 17-18 from:
Make sure to enter your email address, without it the run can't start. Only when the email is entered the 'Start Analyzing' button is activated. Two emails should be received, the first is to indicate that the upload of the Fastq file is over and to give an estimate on the process time, based on the amount of your data and the files in queue. The second email will give the results of the analysis in a attached text file. Spreadsheet software, like Microsoft Excel, can be used to open the text file. The second email will also contain explanation of the output (see also below). Note that when using the test dataset only the results email will be sent as there is no need to upload the Fastq file. Please avoid multiple uploads of the same data, unless the upload itself was faulty (based on the first email you got).
to:
Make sure to enter your email address, without it the run can't start. Only when the email is entered the 'Start Analyzing' button is activated. Two emails should be received, the first is to indicate that the upload of the Fastq file is over and to give an estimate on the process time, based on the size of your data and the files in queue. The second email will give the results of the analysis in a attached text file. Spreadsheet software, like Microsoft Excel, can be used to open the text file. The second email will also contain explanation of the output (see also below). Note that when using the test dataset only the results email will be sent as there is no need to upload the Fastq file. Please avoid multiple uploads of the same data, unless the upload itself was faulty (based on the first email you got).
Changed lines 21-22 from:
The search for possible RNA editing site is performed for every position in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position must be corrected accordingly. The multiple testing correction can be either 'Bonferroni' or 'Benjamini–Hochberg'. Note that Bonferroni correction is more stringent, but might lead to missing true editing sites. Using Bonferroni the reported positions will be only those with P-value less than the supplied P-value divided by the number of test. If Benjamini–Hochberg is chosen, the supplied P-value is the False Discovery Rate (FDR). 
to:
The search for possible RNA editing sites is performed for every position in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position must be corrected accordingly. The multiple testing correction can be either 'Bonferroni' or 'Benjamini–Hochberg'. Note that Bonferroni correction is more stringent, but might lead to missing true editing sites. Using Bonferroni correction the reported positions will be only those with P-value less than the supplied P-value divided by the number of tests. If Benjamini–Hochberg correction is chosen, the supplied P-value is the False Discovery Rate (FDR). 
Changed lines 25-28 from:
The filtered and trimmed reads are aligned against the genome of interest using Bowtie (Langmead et al., Genome Biology, 2009). The UCSC hg19 and mm9 versions of the genome are used for human and mouse, respectively. We require unique best alignment, that is, the reads cannot be aligned to other locations in the genome with the same number of mismatches. Only alignments with up to one mismatch are used. These steps taken together solve, by and large, the cross mapping problem that significantly hinders identification of true editing sites in mature miRNAs. The last two bases (the 3' end) of mature miRNA undergo extensive adenylation and uridylation (see Burroughs et al., Genome Research, 2010). Therefore, these bases are not considered in the alignment. Naturally, doing so prevents detection of editing in these locations. However, not taking this measure and still demanding low number of mismatches will severely reduce the number of alignments obtained. 

Next, the reads aligned against the genome are converted to counts of each of the four possible nucleotides at each position along the pre-miRNA sequence, for all the pre-miRNAs. Performing this transformation allow us to focus our analysis only on bona fide miRNA and to use, in the following step, binomial statistics to detect significant modifications inside them. The sequence and location of the pre-miRNA and the mature miRNA were obtained from miRBase, release 20 (Kozomara and Griffiths-Jones, NAR, 2014). An important parameter for this step is the minimum quality score allowed in the location of the mismatch in order for it to be counted. Naturally, the higher this number is, the lower the probability for sequencing error. However, taking very high quality score filter will give small number of counted modifications. We use a Phred quality score of 30 as the minimum quality score allowed.
to:
The filtered and trimmed reads are aligned against the genome of interest using Bowtie (Langmead et al., Genome Biology, 2009). The UCSC hg19 and mm9 versions of the genome are used for human and mouse, respectively. We require unique best alignment, that is, the reads cannot be aligned to other locations in the genome with the same number of mismatches. Only alignments with up to one mismatch are used. These steps taken together solve, by and large, the cross mapping problem that significantly hinders identification of true editing sites in mature miRNAs. The last two bases (the 3' end) of mature miRNA undergo extensive adenylation and uridylation (Burroughs et al., Genome Research, 2010). Therefore, these bases are not considered in the alignment. Naturally, doing so prevents detection of editing in these locations. However, not taking this measure and still demanding low number of mismatches will severely reduce the number of alignments obtained. 

Next, the reads aligned against the genome are converted to counts of each of the four possible nucleotides at each position along the pre-miRNA sequence, for all the pre-miRNAs. Performing this transformation allow us to focus our analysis only on bona fide miRNA and to use, in the following step, binomial statistics to detect significant modifications inside them. An important parameter for this step is the minimum quality score allowed in the location of the mismatch in order for it to be counted. Naturally, the higher this number is, the lower the probability for sequencing error. However, taking very high quality score filter will give small number of counted modifications. We use a Phred quality score of 30 as the minimum quality score allowed. The sequence and location of the pre-miRNA and the mature miRNA were obtained from miRBase, release 20 (Kozomara and Griffiths-Jones, NAR, 2014).
Changed lines 33-34 from:
The output text file gives the locations of the significant modification are given as well as the statistical description of the modifications. The following fields should appear in the text file:
to:
The output text file gives the locations of the significant modification as well as the statistical description of the modifications. The following fields should appear in the text file:
Added line 66:
Changed lines 77-84 from:
6. View the resulting subtracted file. The file should appear in the upper right corner of the screen under the “History” tab. It can be viewed using the eye icon. If the resulting file is identical to the output file of the web server, then that none of the identified modifications are known SNPs.

(b) Some low-abundance isomirs display 5' sequence modifications similar to the biological modifications reported at the 3' of mature miRNAs (Burroughs et al., Genome Research, 2010). We previously identified several isomirs that start one or two bases upstream from a different isomir and display sequence modifications in the 5' end in the form of adenylation and uridylation. In all these events the abundance of the modified isomir was significantly lower than the unmodified isomir. The web server automatically identifies these events and discards them from the analysis if (1) the expression of the modified isomir is more than an order of magnitude lower compared to the expression levels of the main isomir, and (2) the position to discard is in first or second base of the 5'. However, there may be adenylation and uridylation in the 5' that passes these filters.

(c) The definitions of the bona fide miRNAs is constantly improving in each new release of miRBase. However, artifacts as fragments of rRNA can still be present in the database.

(d) We observed several Fastq files of mature miRNAs which show preference for one type of mismatch, for example A-to-C. Interestingly, this mismatch occurred predominantly in one specific position along the mature miRNA (for example, position 6 from the 5' end). Therefore, in these cases in seems to be specific mismatch in one cycle of the sequencing process. These mismatches tend to have lower sequence quality than 'real' editing events. However, it is possible to observe it even when using Phred score of 30 as a cutoff.       
to:
6. View the resulting subtracted file. The file should appear in the upper right corner of the screen under the “History” tab. It can be viewed using the eye icon. If the resulting file is identical to the output file of the web server, then none of the identified modifications are known SNPs.

(b) Some low-abundance isomirs display 5' sequence modifications similar to the biological modifications reported at the 3' of mature miRNAs (Burroughs et al., Genome Research, 2010). We previously identified several isomirs that start one or two bases upstream from a different isomir and display sequence modifications in the 5' end in the form of adenylation and uridylation. In all these events the abundance of the modified isomir was significantly lower than the unmodified isomir. The web server automatically identifies these events and discards them from the analysis if: (1) the expression of the modified isomir is more than an order of magnitude lower compared to the expression levels of the main isomir, and (2) the position to discard is in the first two 5' bases of the miRNA. However, there may be adenylation and uridylation in the 5' that slip through these filters.

(c) The definitions of the bona fide miRNAs are constantly improving in each new release of miRBase. However, artifacts (for example, fragments of rRNA that are identified as miRNA) can still be present in the database.

(d) We observed several Fastq files of mature miRNAs which show a clear preference for one type of mismatch, for example A-to-C. Interestingly, this mismatch type occurred predominantly in one specific position along the mature miRNA (for example, position 6 counting from the 5' end). Therefore, in these cases there seems to be a specific mismatch in one cycle of the sequencing process. These mismatches tend to have lower sequence quality compared to known editing events. However, it is possible to detect these mismatches even when using Phred score of 30 as a cutoff.       
Changed line 91 from:
Alon S, Eisenberg E (2013). Identifying RNA editing sites in miRNAs by deep sequencing. Methods in Molecular Biology, 1038:159-170.
to:
Alon S, Eisenberg E (2013). Identifying RNA editing sites in miRNAs by deep sequencing. Methods in Molecular Biology, 1038:159-170.
Added line 62:
Changed line 84 from:
(e)It has been suggested that non-canonical types of RNA editing may affect RNA (Li et al.,Science, 2011). 
to:
(e) It has been suggested that non-canonical types of RNA editing may affect RNA (Li et al.,Science, 2011). 
Changed lines 62-68 from:
Most of the modifications are expected to be A-to-G, which can be a result of A-to-I editing. What can be the nature of the other types of modifications? Among the possible explanations are the following: (a) problems in the definition of the miRNA, (b) 5' adenylation and uridylation, (c) SNPs or somatic mutations, (d) sequencing artifacts, or (e) non-A-to-I RNA editing events:

(a)

(b) Some low-abundance isomirs display 5' sequence modifications similar to the biological modifications reported at the 3' of mature miRNAs (Burroughs et al
., Genome Research, 2010). We previously identified several isomers that start one or two bases upstream from a different isomer and display sequence modifications in the 5' end in the form of adenylation and uridylation. In all these events the abundance of the modified isomer was significantly lower than the unmodified isomer. The web server automatically identifies these events and discards them from the analysis if the expression modified isomir is more than an order of magnitude lower compared to the expression levels of the main isomer. The maximal position to discard is set to 2. However,

to:
Most of the modifications are expected to be A-to-G, which can be a result of A-to-I editing. What can be the nature of the other types of modifications? Among the possible explanations are the following: (a) SNPs or somatic mutations, (b) 5' adenylation and uridylation, (c) problems in the definition of the miRNA, (d) sequencing artifacts, or (e) non-A-to-I RNA editing events:

(a) Known SNPs should be filtered from the statistically significant modifications detected by the web server. This can be done using Galaxy (http://galaxy.psu.edu/):
1. In the Galaxy site choose the “Use Galaxy” option.

2. Use the “Get Data” link, and then “UCSC Main” to download data from
the UCSC Table Browser.

3. To download the human or mouse SNP dataset, choose “Human” or “Mouse”, respectively, in
the “genome” field and “Variation and Repeats” in the “group” field. Make sure that the “track” field is set to “SNPs” and the “region” field is set to “genome”. Then press “get output” and afterwards press “send query to Galaxy”. 

4. Upload
the output text file from the web server, using the “Get Data” link, and then “Upload File” link. Choose “interval” in the “File Format” field and locate the file using the “Browse” button. Choose “Human hg19” or “Mouse mm9” in the “Genome” field, for human or mouse respectively, and then press “Execute”.

5. Subtract the genomic locations of the SNPs from the locations of the identified mismatches. Use “Operate on Genomic Intervals” and then “Subtract”. Choose to subtract the SNP dataset from the identified mismatch dataset, make sure that the minimal overlap is set to 1 base, and then press “Execute”. After a while the subtracted file should appear as a new tab in the “History” panel (right side of the screen).

6. View the resulting subtracted file. The file should appear in the upper right corner of the screen under the “History” tab. It can be viewed using the eye icon. If the resulting file is identical to the output file of the web server, then that none of the identified modifications are known SNPs.

(b) Some low-abundance isomirs display 5' sequence modifications similar to the biological modifications reported at the 3' of mature miRNAs (Burroughs et al., Genome Research, 2010). We previously identified several isomirs that start one or two bases upstream from a different isomir and display sequence modifications in the 5' end in the form of adenylation and uridylation. In all these events the abundance of the modified isomir was significantly lower than the unmodified isomir. The web server automatically identifies these events and discards them from the analysis if (1) the expression of the modified isomir is more than an order of magnitude lower compared to the expression levels of the main isomir, and (2) the position to discard is in first or second base of the 5'. However, there may be adenylation and uridylation in the 5' that passes these filters.

(c) The definitions of the bona fide miRNAs is constantly improving in each new release of miRBase. However, artifacts as fragments of rRNA can still be present in the database.

(d) We observed several Fastq files of mature miRNAs which show preference for one type of mismatch, for example A-to-C. Interestingly, this mismatch occurred predominantly in one specific position along the mature miRNA (for example, position 6 from the 5' end). Therefore, in these cases in seems to be specific mismatch in one cycle of the sequencing process. These mismatches tend to have lower sequence quality than 'real' editing events. However, it is possible to observe it even when using Phred score of 30 as a cutoff.       

(e)It has been suggested that non-canonical types of RNA editing may affect RNA (Li et al.,Science, 2011). 
Changed lines 34-35 from:
#CHROM  = The chromosome number
to:

CHROM  = The chromosome number
Added line 73:
Changed lines 7-8 from:
The input for the web server is sequencing reads of mature miRNAs in a Fastq format. This web server supports only data obtained using Illumina platform. To upload the Fastq file, press the 'Choose Files' button and locate the Fastq file in your computer. Note that the upload time can be quite long for large files. For example, ~5GB Fastq file will take at least an hour to upload when the average upload speed is 10 Megabits Per Second (Mbps). The progress of the upload is given by a progress bar at the bottom of the page which is displayed when the 'Start Analyzing' button is pressed. Make sure not to disconnect while the upload is in progress. Once the upload is over a notification email will be sent to you. Make sure to use a unique file name for every uploaded file.
to:
The input for the web server is sequencing reads of mature miRNAs in a Fastq format. This web server supports only data obtained using Illumina platform (in Phred+33 format). To upload the Fastq file, press the 'Choose Files' button and locate the Fastq file in your computer. Note that the upload time can be quite long for large files. For example, ~5GB Fastq file will take at least an hour to upload when the average upload speed is 10 Megabits Per Second (Mbps). The progress of the upload is given by a progress bar at the bottom of the page which is displayed when the 'Start Analyzing' button is pressed. Make sure not to disconnect while the upload is in progress. Once the upload is over a notification email will be sent to you. Make sure to use a unique file name for every uploaded file.
Changed lines 23-24 from:
'''Overview of the Analysis'''
to:
'''Overview of the Analysis Process'''
Changed lines 27-35 from:
Next, the reads aligned against the genome are converted to counts of each of the four possible nucleotides at each position along the pre-miRNA sequence, for all the pre-miRNAs. Performing this transformation allow us to focus our analysis only on bona fide miRNA and to use, in the following step, binomial statistics to detect significant modifications inside them. The sequence and location of the pre-miRNA and the mature miRNA were obtained from miRBase, release 20 (Kozomara and Griffiths-Jones, NAR, 2014).

The pre-built files and the Bowtie output file from the previous step are the input for the script “Analyze_mutation.pl”. A key user-defined input for this script is the minimum quality score allowed in the location of the mismatch in order for it to be counted. Naturally, the higher this number is, the lower the probability for sequencing error. However, taking very high quality score filter will give small number of counted modifications. We suggest using 30 as the minimum quality score allowed (see also below and (13)).
Running this script on large sequencing datasets (large Bowtie output files) requires extensive internal memory resources. A way around this hurdle is to divide the sequencing dataset into several smaller files; afterwards the output files can be merged (see Subheading 3.4). We suggest dividing the Bowtie output file if the number of reads is higher than 2.5 million when using 8 GB of RAM.



'''References'''

to:
Next, the reads aligned against the genome are converted to counts of each of the four possible nucleotides at each position along the pre-miRNA sequence, for all the pre-miRNAs. Performing this transformation allow us to focus our analysis only on bona fide miRNA and to use, in the following step, binomial statistics to detect significant modifications inside them. The sequence and location of the pre-miRNA and the mature miRNA were obtained from miRBase, release 20 (Kozomara and Griffiths-Jones, NAR, 2014). An important parameter for this step is the minimum quality score allowed in the location of the mismatch in order for it to be counted. Naturally, the higher this number is, the lower the probability for sequencing error. However, taking very high quality score filter will give small number of counted modifications. We use a Phred quality score of 30 as the minimum quality score allowed.

Finally, binomial statistics is performed to separate sequencing errors from statistically significant modifications. The binomial statistics requires the number of successes (the number of mismatches of a given type in a given position), the number of trials (the total number of counts in the given position), and the sequencing error probability. The sequencing error probability is estimated using the Phred score. As only mismatches with Phred score of 30 are allowed, the expected base call error rate should be 0.1% in each position. Importantly, binomial statistics do not require any arbitrary expression level filter. It is well suited even for low-expressed miRNAs with low number of sequencing reads, and the P-values computed reflect the absolute number of reads detected, small or large as the case may be. This analysis is performed for every position (except the last two positions of the miRNA due to the extensive adenylation and uridylation) in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position are corrected by using either Bonferroni or Benjamini–Hochberg corrections.

'''The Output File'''
 
The output text file gives the locations of the significant modification are given as well as the statistical description of the modifications. The following fields should appear in the text file:
#CHROM  = The chromosome number

START = The location of the position before the modification site
 
END = The location of the modification site

STRAND = The strand in which the modification is located

miRNA name = The miRNA with the modification

Location inside pre-miRNA = The position of the modification inside the pre-miRNA (according to miRBase numbering)

Modification type = The modification type

Number of reads with the modification = The number of reads which show the modified base

Total number of reads in this position = Total number of reads in this position

Location inside mature sequence = The position of the modification inside the mature miRNA (according to miRBase numbering)

Raw P-value = The P-value obtained from the binomial test

Bonferroni P-value = The Bonferroni corrected P-value

BH P-value = The Benjamini-Hochberg corrected P-value

'''Output Interpretation'''
Most of the modifications are expected to be A-to-G, which can be a result of A-to-I editing. What can be the nature of the other types of modifications? Among the possible explanations are the following: (a) problems in the definition of the miRNA, (b) 5' adenylation and uridylation, (c) SNPs or somatic mutations, (d) sequencing artifacts, or (e) non-A-to-I RNA editing events:

(a)

(b) Some low-abundance isomirs display 5' sequence modifications similar to the biological modifications reported at the 3' of mature miRNAs (Burroughs et al., Genome Research, 2010). We previously identified several isomers that start one or two bases upstream from a different isomer and display sequence modifications in the 5' end in the form of adenylation and uridylation. In all these events the abundance of the modified isomer was significantly lower than the unmodified isomer. The web server automatically identifies these events and discards them from the analysis if the expression modified isomir is more than an order of magnitude lower compared to the expression levels of the main isomer. The maximal position to discard is set to 2. However,



'''References for the Analysis Process'''

Deleted line 72:
Changed lines 1-2 from:
'''Introduction'''
to:
'''Overview of the Web Server'''
Changed lines 7-8 from:
The input for the web server is sequencing reads of mature miRNAs in a Fastq format. This web server supports only data obtained using Illumina platform. To upload the Fastq file, press the 'Choose Files' button and locate the Fastq file in your computer. Note that the upload time can be quite long for large files. For example, ~5GB Fastq file will take at least an hour to upload when the average upload speed is 10 MegaBits Per Second (Mbps). The progress of the upload is given by a progress bar at the bottom of the page which is displayed when the 'Start Analyzing' button is pressed. Make sure not to disconnect while the upload is in progress. Once the upload is over a notification email will be sent to you. Make sure to use a unique file name for every uploaded file.
to:
The input for the web server is sequencing reads of mature miRNAs in a Fastq format. This web server supports only data obtained using Illumina platform. To upload the Fastq file, press the 'Choose Files' button and locate the Fastq file in your computer. Note that the upload time can be quite long for large files. For example, ~5GB Fastq file will take at least an hour to upload when the average upload speed is 10 Megabits Per Second (Mbps). The progress of the upload is given by a progress bar at the bottom of the page which is displayed when the 'Start Analyzing' button is pressed. Make sure not to disconnect while the upload is in progress. Once the upload is over a notification email will be sent to you. Make sure to use a unique file name for every uploaded file.
Changed lines 15-21 from:

'''Email for results'''

Make sure to enter your email address, without it no run can start. Only when the email is entered the 'Start Analyzing' button is activated. Two emails should be received, the first is to indicate that the upload of the Fastq file is over and to give an estimate on the process time, based on the amount of your data and the files in queue. The second email will give the results of the analysis in a attached text file. Spreadsheet software, like Microsoft Excel, can be used to open the text file. The second email will also contain explanation of the output (see also below). Note that when using the test dataset only the results email will be sent as there is no need to upload the Fastq file. Please avoid multiple uploads of the same data, unless the upload itself was faulty (based on the first email you got).


to:
'''Email for Results'''

Make sure to enter your email address, without it the run can't start. Only when the email is entered the 'Start Analyzing' button is activated. Two emails should be received, the first is to indicate that the upload of the Fastq file is over and to give an estimate on the process time, based on the amount of your data and the files in queue. The second email will give the results of the analysis in a attached text file. Spreadsheet software, like Microsoft Excel, can be used to open the text file. The second email will also contain explanation of the output (see also below). Note that when using the test dataset only the results email will be sent as there is no need to upload the Fastq file. Please avoid multiple uploads of the same data, unless the upload itself was faulty (based on the first email you got).
Added lines 22-37:

'''Overview of the Analysis'''

The filtered and trimmed reads are aligned against the genome of interest using Bowtie (Langmead et al., Genome Biology, 2009). The UCSC hg19 and mm9 versions of the genome are used for human and mouse, respectively. We require unique best alignment, that is, the reads cannot be aligned to other locations in the genome with the same number of mismatches. Only alignments with up to one mismatch are used. These steps taken together solve, by and large, the cross mapping problem that significantly hinders identification of true editing sites in mature miRNAs. The last two bases (the 3' end) of mature miRNA undergo extensive adenylation and uridylation (see Burroughs et al., Genome Research, 2010). Therefore, these bases are not considered in the alignment. Naturally, doing so prevents detection of editing in these locations. However, not taking this measure and still demanding low number of mismatches will severely reduce the number of alignments obtained. 

Next, the reads aligned against the genome are converted to counts of each of the four possible nucleotides at each position along the pre-miRNA sequence, for all the pre-miRNAs. Performing this transformation allow us to focus our analysis only on bona fide miRNA and to use, in the following step, binomial statistics to detect significant modifications inside them. The sequence and location of the pre-miRNA and the mature miRNA were obtained from miRBase, release 20 (Kozomara and Griffiths-Jones, NAR, 2014).

The pre-built files and the Bowtie output file from the previous step are the input for the script “Analyze_mutation.pl”. A key user-defined input for this script is the minimum quality score allowed in the location of the mismatch in order for it to be counted. Naturally, the higher this number is, the lower the probability for sequencing error. However, taking very high quality score filter will give small number of counted modifications. We suggest using 30 as the minimum quality score allowed (see also below and (13)).
Running this script on large sequencing datasets (large Bowtie output files) requires extensive internal memory resources. A way around this hurdle is to divide the sequencing dataset into several smaller files; afterwards the output files can be merged (see Subheading 3.4). We suggest dividing the Bowtie output file if the number of reads is higher than 2.5 million when using 8 GB of RAM.



'''References'''

Alon S, Mor E, Vigneault F, Gallo A, Locatelli F, Church GM, Shomron N, Eisenberg E (2012). Systematic identification of edited microRNAs in the human brain. Genome Research, 22:1533-1540.
Alon S, Eisenberg E (2013). Identifying RNA editing sites in miRNAs by deep sequencing. Methods in Molecular Biology, 1038:159-170.
Added line 2:
Added lines 5-10:
'''Upload Fastq Sequencing File of Mature miRNA'''

The input for the web server is sequencing reads of mature miRNAs in a Fastq format. This web server supports only data obtained using Illumina platform. To upload the Fastq file, press the 'Choose Files' button and locate the Fastq file in your computer. Note that the upload time can be quite long for large files. For example, ~5GB Fastq file will take at least an hour to upload when the average upload speed is 10 MegaBits Per Second (Mbps). The progress of the upload is given by a progress bar at the bottom of the page which is displayed when the 'Start Analyzing' button is pressed. Make sure not to disconnect while the upload is in progress. Once the upload is over a notification email will be sent to you. Make sure to use a unique file name for every uploaded file.

Alternatively, you may want to use a test dataset by choosing the 'Use test dataset' option. The test dataset is of mature miRNAs from mouse cerebellum (accession number SRR346417). If you choose the test dataset there is no need to adjust the parameters, just enter your email address and click 'Start Analyzing'.         

Changed lines 12-26 from:
The input for the web server is sequencing reads of mature miRNAs in a Fastq format. This web server supports only data obtained using Illumina platform. The Fastq file of the sequencing reads could be the raw reads without any filter, or filtered reads using Illumina software tools. In the latter case, check 'No, its already pre-processed'. Otherwise, check 'Remove Sequence Adapter' as raw sequencing reads likely contain parts of the adapter sequence. The web server trim these sequences if they are supplied by the user in the fields '5 Adaptor' and '3 Adaptor'. Whereas 5 and 3 are the 5' and 3' ends of the mature miRNA sequence. As the expected length of mature miRNAs is ~21 bases, reads after trimming with length longer than 28 bases or shorter than 15 bases are discarded. Moreover, low-quality reads (as defined by the read quality score) are unlikely to be informative and therefore should be removed. The web server will remove reads with low sequencing quality in more than three positions. Low sequencing quality is defined by Phred quality score (which ranges from 0 to 40) lower than 20.   
to:

The Fastq file of the sequencing reads could be the raw reads without any filter, or filtered reads using Illumina software tools. In the latter case, check 'No, its already pre-processed'. Otherwise, check 'Remove Sequence Adapter' as raw sequencing reads likely contain parts of the adapter sequence. The web server trim these sequences if they are supplied by the user in the fields '5 Adaptor' and '3 Adaptor'. Whereas 5 and 3 are the 5' and 3' ends of the mature miRNA sequence. As the expected length of mature miRNAs is ~21 bases, reads after trimming with length longer than 28 bases or shorter than 15 bases are discarded. Moreover, low-quality reads (as defined by the read quality score) are unlikely to be informative and therefore should be removed. The web server will remove reads with low sequencing quality in more than three positions. Low sequencing quality is defined by Phred quality score (which ranges from 0 to 40) lower than 20.   


'''Email for results'''

Make sure to enter your email address, without it no run can start. Only when the email is entered the 'Start Analyzing' button is activated
. Two emails should be received, the first is to indicate that the upload of the Fastq file is over and to give an estimate on the process time, based on the amount of your data and the files in queue. The second email will give the results of the analysis in a attached text file. Spreadsheet software, like Microsoft Excel, can be used to open the text file. The second email will also contain explanation of the output (see also below). Note that when using the test dataset only the results email will be sent as there is no need to upload the Fastq file. Please avoid multiple uploads of the same data, unless the upload itself was faulty (based on the first email you got).



'''Multiple-Correction Procedure'''

The search for possible RNA editing site is performed for every position in every mature miRNA separately. As multiple tests are performed, the resulting P-value for each position must be corrected accordingly. The multiple testing correction can be either 'Bonferroni' or 'Benjamini–Hochberg'. Note that Bonferroni correction is more stringent, but might lead to missing true editing sites. Using Bonferroni the reported positions will be only those with P-value less than the supplied P-value divided by the number of test. If Benjamini–Hochberg is chosen, the supplied P-value is the False Discovery Rate (FDR). 

   
Changed lines 1-6 from:
Deep sequencing has many possible applications; one of them is the identification and quantification of RNA editing sites. The most common type of RNA editing is adenosine to inosine (A-to-I) editing. A prerequisite for this editing process is a double-stranded RNA (dsRNA) structure. Such dsRNAs are formed as part of the microRNA (miRNA) maturation process, and it is therefore expected that miRNAs are affected by A-to-I editing. Indeed, tens of editing sites were found in miRNAs, some of which change the miRNA binding specificity. Here, we describe a protocol for the identification of RNA editing sites in mature miRNAs using deep sequencing data.
to:
'''Introduction'''
Deep sequencing has many possible applications; one of them is the identification and quantification of RNA editing sites. The most common type of RNA editing is adenosine to inosine (A-to-I) editing. A prerequisite for this editing process is a double-stranded RNA (dsRNA) structure. Such dsRNAs are formed as part of the microRNA (miRNA) maturation process, and it is therefore expected that miRNAs are affected by A-to-I editing. Indeed, tens of editing sites were found in miRNAs, some of which change the miRNA binding specificity. This web server was designed for the identification of RNA editing sites in mature miRNAs using deep sequencing data.

'''Pre-Processing of the Fastq File'''
The input for the web server is sequencing reads of mature miRNAs in a Fastq format. This web server supports only data obtained using Illumina platform. The Fastq file of the sequencing reads could be the raw reads without any filter, or filtered reads using Illumina software tools. In the latter case, check 'No, its already pre-processed'. Otherwise, check 'Remove Sequence Adapter' as raw sequencing reads likely contain parts of the adapter sequence. The web server trim these sequences if they are supplied by the user in the fields '5 Adaptor' and '3 Adaptor'. Whereas 5 and 3 are the 5' and 3' ends of the mature miRNA sequence. As the expected length of mature miRNAs is ~21 bases, reads after trimming with length longer than 28 bases or shorter than 15 bases are discarded. Moreover, low-quality reads (as defined by the read quality score) are unlikely to be informative and therefore should be removed. The web server will remove reads with low sequencing quality in more than three positions. Low sequencing quality is defined by Phred quality score (which ranges from 0 to 40) lower than 20.   

 
Changed lines 1-12 from:
Welcome to PmWiki!

A local copy of PmWiki's
documentation has been installed along with the software,
and is available via the [[PmWiki/documentation index]]. 

To continue setting up PmWiki, see [[PmWiki/initial setup tasks]]
.

The [[PmWiki/basic
editing]] page describes how to create pages
in PmWiki
.  You can practice editing in the [[wiki sandbox]].

More information about PmWiki
is available from http://www.pmwiki.org.
to:
Deep sequencing has many possible applications; one of them is the identification and quantification of RNA editing sites. The most common type of RNA editing is adenosine to inosine (A-to-I) editing. A prerequisite for this editing process is a double-stranded RNA (dsRNA) structure. Such dsRNAs are formed as part of the microRNA (miRNA) maturation process, and it is therefore expected that miRNAs are affected by A-to-I editing. Indeed, tens of editing sites were found in miRNAs, some of which change the miRNA binding specificity. Here, we describe a protocol for the identification of RNA editing sites in mature miRNAs using deep sequencing data. 
Edit - History - Print - Recent Changes - Search
Page last modified on July 30, 2015, at 11:08 PM EST