<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to ObtainingRNASeqInputs</title><link>https://sourceforge.net/p/altanalyze/wiki/ObtainingRNASeqInputs/</link><description>Recent changes to ObtainingRNASeqInputs</description><atom:link href="https://sourceforge.net/p/altanalyze/wiki/ObtainingRNASeqInputs/feed" rel="self"/><language>en</language><lastBuildDate>Sat, 01 Feb 2014 01:06:55 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/altanalyze/wiki/ObtainingRNASeqInputs/feed" rel="self" type="application/rss+xml"/><item><title>ObtainingRNASeqInputs modified by Anonymous</title><link>https://sourceforge.net/p/altanalyze/wiki/ObtainingRNASeqInputs/</link><description>&lt;div class="markdown_content"&gt;&lt;h1 id="instructions-for-obtaining-rnaseq-input-files"&gt;Instructions for Obtaining RNASeq Input Files&lt;/h1&gt;
&lt;p&gt;&lt;strong&gt;&lt;em&gt;Please Note:&lt;/em&gt;&lt;/strong&gt; We are actively working on ways to better integrate existing RNA-seq alignment strategies into &lt;a class="" href="/p/altanalyze/wiki/AltAnalyze/"&gt;AltAnalyze&lt;/a&gt;. Recommendations to our &lt;a class="" href="/p/altanalyze/wiki/ContactUs/"&gt;support desk&lt;/a&gt; are always welcome. &lt;/p&gt;
&lt;h3 id="downloading-sample-fastq-data"&gt;Downloading Sample FASTQ Data&lt;/h3&gt;
&lt;p&gt;You are welcome to try with your own FASTQ data, as this is typically easiest for most users rather than downloading large datasets. For optimal junction analysis results, we recommend &amp;gt;50nt reads, however, we have achieved acceptable results from 35nt reads. If you currently do not have your own data, example files and download instructions can be found &lt;a class="" href="/p/altanalyze/wiki/DownloadFASTQ/"&gt;here&lt;/a&gt;. &lt;/p&gt;
&lt;h3 id="using-tophat-and-bowtie"&gt;Using &lt;a class="" href="../TopHat"&gt;TopHat&lt;/a&gt; and Bowtie&lt;/h3&gt;
&lt;p&gt;Currently, we recommend two pipelines for producing input data for &lt;a class="" href="/p/altanalyze/wiki/AltAnalyze/"&gt;AltAnalyze&lt;/a&gt;: 1) &lt;a class="" href="../TopHat"&gt;TopHat&lt;/a&gt; and 2) &lt;a class="" href="/p/altanalyze/wiki/BioScope/"&gt;BioScope&lt;/a&gt;. &lt;a class="" href="../TopHat"&gt;TopHat&lt;/a&gt; should work with most all RNA-seq datasets, while &lt;a class="" href="/p/altanalyze/wiki/BioScope/"&gt;BioScope&lt;/a&gt; is compatible with ABI SOLiD data. As &lt;a class="" href="../TopHat"&gt;TopHat&lt;/a&gt; is open-source and runs on typical hardware configurations, this solution will be more appropriate for most users. For &lt;a class="" href="../TopHat"&gt;TopHat&lt;/a&gt;, junction BED files can be easily obtained using simple command-line arguments to &lt;a class="" href="../TopHat"&gt;TopHat&lt;/a&gt;, once Bowtie and indexed genome files have been downloaded. In addition to aligning junctions, exon read counts can be obtained from the resulting accepted_hits.bam file written to the same folder as the junction BED results, using &lt;a class="" href="/p/altanalyze/wiki/BEDTools/"&gt;BEDTools&lt;/a&gt;. For example Instructions on obtaining exon and junction expression files (BED format), click &lt;a class="" href="/p/altanalyze/wiki/BAMtoBED/"&gt;here&lt;/a&gt;. &lt;/p&gt;
&lt;h3 id="using-bioscope"&gt;Using &lt;a class="" href="/p/altanalyze/wiki/BioScope/"&gt;BioScope&lt;/a&gt;&lt;/h3&gt;
&lt;p&gt;Details on &lt;a class="" href="/p/altanalyze/wiki/BioScope/"&gt;BioScope&lt;/a&gt; usage can be found &lt;a class="" href="http://www3.appliedbiosystems.com/cms/groups/global_marketing_group/documents/generaldocuments/cms_074971.pdf" rel="nofollow"&gt;here&lt;/a&gt;. Once result files are produced, &lt;a class="" href="/p/altanalyze/wiki/AltAnalyze/"&gt;AltAnalyze&lt;/a&gt; will accept the junction and exon reads files produced from this pipeline as input. Prior to import, the extension of these two files must be changed to .tab in order for &lt;a class="" href="/p/altanalyze/wiki/AltAnalyze/"&gt;AltAnalyze&lt;/a&gt; to recognize these from other text files. To ensure the exon and junction files for each sample are properly matched, make sure that the exon and junction file have the same name, followed by a double underscore, followed by a distinguishing annotation. For example: &lt;/p&gt;
&lt;p&gt;&lt;code&gt;Cancer_s1__canonical-junction.tab&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;Cancer_s1__noncanonical-junction.tab&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;Cancer_s1__exon.tab&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;Wt_s1__canonical-junction.tab&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;Wt_s1__noncanonical-junction.tab&lt;/code&gt;&lt;/p&gt;
&lt;p&gt;&lt;code&gt;Wt_s1__exon.tab&lt;/code&gt;&lt;/p&gt;&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Anonymous</dc:creator><pubDate>Sat, 01 Feb 2014 01:06:55 -0000</pubDate><guid>https://sourceforge.net161bc006c3001da9761a992e9c8ced45accb3449</guid></item></channel></rss>