<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to wiki</title><link>https://sourceforge.net/p/atlas2/wiki/</link><description>Recent changes to wiki</description><atom:link href="https://sourceforge.net/p/atlas2/wiki/feed.rss" rel="self"/><language>en</language><lastBuildDate>Wed, 19 Jun 2013 18:05:15 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/atlas2/wiki/feed.rss" rel="self" type="application/rss+xml"/><item><title>Atlas2 Suite modified by Danny Challis</title><link>https://sourceforge.net/p/atlas2/wiki/Atlas2%2520Suite/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v27
+++ v28
@@ -45,7 +45,7 @@
 * Version 1.4.3 released on 3 January,2013. New options in Atlas-SNP2, major bug fixes in Atlas-INDEL2 and major updates to vcfPrinter.
 * Version 1.4.1 adds new output options for Atlas-SNP2
 * Version 1.4.1 adds new options for Atlas-Indel2, and makes several bugfixes
-Full changelog: [https://sourceforge.net/p/atlas2/wiki/Changelog/]
+Full changelog: [Changelog]

 Acknowledgements
 --------------------
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Danny Challis</dc:creator><pubDate>Wed, 19 Jun 2013 18:05:15 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net6a7b6f0a1330a42b3c4df0321297edfa79042960</guid></item><item><title>Changelog modified by Danny Challis</title><link>https://sourceforge.net/p/atlas2/wiki/Changelog/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v8
+++ v9
@@ -1,5 +1,5 @@

-**Full Commit List** :   [https://sourceforge.net/p/atlas2/code/commit_browser]
+**Full Commit List** :   

 [TOC]

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Danny Challis</dc:creator><pubDate>Wed, 19 Jun 2013 18:02:58 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net9d9fb9ece7919521b655035896c868083f45b9c6</guid></item><item><title>Best Practices and Workflows modified by Danny Challis</title><link>https://sourceforge.net/p/atlas2/wiki/Best%2520Practices%2520and%2520Workflows/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v15
+++ v16
@@ -64,7 +64,7 @@
 :::bash
 mkdir target
 for file in *.vcf
-  do ruby Atlas2/utils/bed_filter.rb $file &gt; target/$file
+  do ruby Atlas2/utils/bed_filter.rb $file phase3-like.illum.capture.union.bed &gt; target/$file
 done
 ~~~~~~~~~~

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Danny Challis</dc:creator><pubDate>Mon, 17 Jun 2013 17:03:59 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net586299d7f2e6781a41d29d97d5138196fec5047d</guid></item><item><title>WikiPage Atlas-SNP modified by Ian Gibson</title><link>https://sourceforge.net/p/atlas2/wiki/Atlas-SNP/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v15
+++ v16
@@ -56,7 +56,7 @@

 ####For Ion Torrent data####

-The Atlas2 Ion software incorporates the well-established algorithms of current Atlas2 builds, but also focuses attention on the specific systematic error modes of the platform's base-caller in order to return results of the highest quality. Although analysis platforms already exist that have been adapted to call [Ion](http://www.iontorrent.com/) data to a good standard, we aim to improve upon these already-existing projects by building an Ion-specific platform. This should provide end-users with increased confidence in their data and in the Ion torrent platform itself. It will also expand the scope of the Atlas2 project itself, which aims to remain the leading platform of its type.
+The Atlas2 Ion software incorporates the well-established algorithms of current Atlas2 builds, but also focuses attention on the specific systematic error modes of the platform's base-caller in order to return results of the highest quality. Although analysis platforms already exist that have been adapted to call [Ion](http://www.iontorrent.com/) data to a good standard (for example [GATK](http://www.broadinstitute.org/gatk/)), we aim to surpass these projects by building an Ion-specific platform. This should provide end-users with increased confidence in their data and in the Ion torrent platform itself. It will also expand the scope of the Atlas2 project itself, which aims to remain the leading platform of its type.

 Analysis capabilities for the Ion Torrent PGM are currently in the late stages of development. The features are currently being fine-tuned prior to the software's version 1 release. Several new algorithms have been developed, with a focus on Ion-specific error modes such as those related to read length, homopolymer length and GC content. Other, more generally-applicable, algorithms are also being calibrated to the Ion platform.

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Gibson</dc:creator><pubDate>Tue, 12 Mar 2013 18:30:05 -0000</pubDate><guid isPermaLink="false">https://sourceforge.netd0c4556d04a44ae2fb2d05c1a2b44150a56d3058</guid></item><item><title>WikiPage Atlas-SNP modified by Ian Gibson</title><link>https://sourceforge.net/p/atlas2/wiki/Atlas-SNP/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v14
+++ v15
@@ -56,10 +56,8 @@

 ####For Ion Torrent data####

-[Ion](http://www.iontorrent.com/) semiconductor sequencing is a radically new approach to next-generation sequencing, utilizing the chemistry of hydrogen ion release that accompanies DNA synthesis, rather than directly observing the specific incorporated bases (as the current mainstream NGS technologies do). This means that there is no requirement for expensive differentially-labeled nucleotides along with the lasers and optics needed to detect them; Ion technology is based around inexpensive and disposable semiconductor chips. 
+The Atlas2 Ion software incorporates the well-established algorithms of current Atlas2 builds, but also focuses attention on the specific systematic error modes of the platform's base-caller in order to return results of the highest quality. Although analysis platforms already exist that have been adapted to call [Ion](http://www.iontorrent.com/) data to a good standard, we aim to improve upon these already-existing projects by building an Ion-specific platform. This should provide end-users with increased confidence in their data and in the Ion torrent platform itself. It will also expand the scope of the Atlas2 project itself, which aims to remain the leading platform of its type.

-The rapid results of the latest generation of benchtop sequencers such as Ion Torrent bring genomics within the reach of many laboratories and research groups who formerly had to farm out their sequencing to large genome centers. However, there is a clear need for analysis software that is capable of providing robust and accurate base-calling for the platform. Building on the larger Atlas2 project, and utilizing the successful approach established there, the Atlas2 Ion software focuses on the specific systematic error modes of the platform's base-caller in order to return results of the highest quality.
+Analysis capabilities for the Ion Torrent PGM are currently in the late stages of development. The features are currently being fine-tuned prior to the software's version 1 release. Several new algorithms have been developed, with a focus on Ion-specific error modes such as those related to read length, homopolymer length and GC content. Other, more generally-applicable, algorithms are also being calibrated to the Ion platform.

-Analysis capabilities for the Ion Torrent PGM are currently in the late stages of development. The algorithms are currently being fine-tuned prior to the software's version 1 release. Atlas2 Ion will initially be made available as a stand-alone product, with integration into the main Atlas2 suite possible in the future.
-
-There will be an announcement once Atlas2 Ion Version 1 is released. Comprehensive usage documentation will also be added to this wiki page at that time.
+Atlas2 Ion will initially be made available as a stand-alone product, with integration into the main Atlas2 suite possible in the future. There will be an announcement once Atlas2 Ion Version 1 is released. Comprehensive usage documentation will also be added to this wiki page at that time.
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Ian Gibson</dc:creator><pubDate>Thu, 07 Mar 2013 15:50:01 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net0bbdd70fa3695435533904c1990da99ff1978985</guid></item><item><title>WikiPage Best Practices and Workflows modified by Danny Challis</title><link>https://sourceforge.net/p/atlas2/wiki/Best%2520Practices%2520and%2520Workflows/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v14
+++ v15
@@ -202,7 +202,7 @@
 ruby vcfPrinter/RunPrinter.rb -i "*.vcf.gz" -o ../all.snps.vcf -p --cluster -n 15
 ~~~~~~~~~~~

-Make sure not to forget the quotes around the glob or it will not work.  If you are merging indel VCFs you should include the --indel flag
+Make sure not to forget the quotes around the glob or it will not work.  If you are merging indel VCFs you should include the --indel flag:

 ~~~~~~~~~~
 :::bash
@@ -211,7 +211,7 @@

 ##Step 4: VCF Cleanup and Annotation

-The population VCF produced by VcfPrinter is extremely data-rich and for large populations is often too crowded for some applications.  To remove uncalled alleles and also add in allele-count and allele-frequency annotations (AN/AC/AF) you can use the add_allele_freq.rb scipt in the Atlas2 utils directory with the -clean flag as follows:
+The project-level VCF produced by VcfPrinter is extremely data-rich and for large populations is often too crowded for some applications.  To remove uncalled alleles and also add in allele-count and allele-frequency annotations (AN/AC/AF) you can use the add_allele_freq.rb scipt in the Atlas2 utils directory with the -clean flag as follows:

 ~~~~~~~~~~~~~~~~~~~~~
 :::bash
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Danny Challis</dc:creator><pubDate>Fri, 08 Feb 2013 21:00:14 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net4ce81486f4e8860c930c5e0366e3c49fcf463569</guid></item><item><title>WikiPage Best Practices and Workflows modified by Danny Challis</title><link>https://sourceforge.net/p/atlas2/wiki/Best%2520Practices%2520and%2520Workflows/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v13
+++ v14
@@ -51,7 +51,7 @@

 ##Step 0:(Optional) Filter calls to the capture target region

-While not required filtering the variant calls to the capture target or other region of interest will drastically reduce the amount of time and resources to build a project-level VCF.  A simple tool for filtering VCF files to a target BED file is included in the Atlas2 package and can be used as follows:
+While not required, filtering the variant calls to the capture target or other region of interest will drastically reduce the amount of time and resources to build a project-level VCF.  A simple tool for filtering VCF files to a target BED file is included in the Atlas2 package and can be used as follows:

 ~~~~~~~~
 :::bash
@@ -119,6 +119,8 @@
   do echo "ruby ../Atlas-Indel2/Atlas-Indel2.rb -b ../bams/$sample.*.bam -r ~/refs/human_g1k_v37.fasta -o $sample.vcf -I -n $sample -a master-site-list" | msub -q analysis -d $PWD -l pmem=1gb -N atlas2.indels.regeno.$sample
 done
 ~~~~~~~
+
+**Note:** As Atlas-Indel2 does not yet have the -w option (only call sites in the master-site-list), it is a good idea to once again filter the VCF files to the catpure target region as described in Step 0.

 ##Step 3: VcfPrinter

@@ -206,3 +208,12 @@
 :::bash
 ruby vcfPrinter/RunPrinter.rb -i "*.vcf.gz" -o ../all.indels.vcf -p --cluster -n 15 --indel
 ~~~~~~~~~~~~
+
+##Step 4: VCF Cleanup and Annotation
+
+The population VCF produced by VcfPrinter is extremely data-rich and for large populations is often too crowded for some applications.  To remove uncalled alleles and also add in allele-count and allele-frequency annotations (AN/AC/AF) you can use the add_allele_freq.rb scipt in the Atlas2 utils directory with the -clean flag as follows:
+
+~~~~~~~~~~~~~~~~~~~~~
+:::bash
+ruby Atlas2/utils/add_allele_freq.rb all.snps.vcf -clean &gt; all.snps.final.vcf
+~~~~~~~~~~~~~~~~~~~~~
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Danny Challis</dc:creator><pubDate>Fri, 08 Feb 2013 20:58:28 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net15ae330ef581a89d28bdb41df11260d528e731b2</guid></item><item><title>WikiPage Best Practices and Workflows modified by Danny Challis</title><link>https://sourceforge.net/p/atlas2/wiki/Best%2520Practices%2520and%2520Workflows/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v12
+++ v13
@@ -70,7 +70,9 @@

 ##Step 1: Generate master site list

-Concatenating variant sites across all single samples vcfs create a master list of unique variants sites found in at least one sample.
+In order to provide genotypes and coverage information for all samples at all sites (not just the variant samples), you can run Atlas2 a second time providing a master list of sites that Atlas2 will always include in the output VCF.  If you do not need the genotype/coverage information for non-variant sample-sites you can skip to Step 3.
+
+Concatenate variant sites across all single samples vcfs create a master list of unique variants sites found in at least one sample.

 Below code will create a unique master site list

@@ -83,21 +85,38 @@
 rm tmp
 ~~~~~~~

-##Step 2: Force call sites using Atlas-SNP2
-
-Re-run Atlas-SNP2 on all the samples using the master-site-list generated in step 1.
-
-~~~~~~
-:::bash
-ruby Atlas-SNP2 -i [bam file] -r [reference fasta file] -o [output file] -n [sample name] --Illumina -a master-site-list -w
-~~~~~~
-
-for example:
+##Step 2: Genotype all called sites with Atlas2
+ Run Atlas2 a second time providing the master site list you have generated to generate genotypes and coverage data for all sample-sites.
+
+###SNPs
+
+~~~~~~
+:::bash
+ruby Atlas-SNP2 -i [bam file] -r [reference fasta file] -o [output file] -n [sample name] --Illumina -a [master-site-list] -w
+~~~~~~
+
+So for all the files you could do:

 ~~~~~~~
 :::bash
 for sample in `cat ../samples ` 
   do echo "ruby ../Atlas-SNP2/Atlas-SNP2.rb -i ../bams/$sample.*.bam -r ~/refs/human_g1k_v37.fasta -o $sample.vcf --Illumina -n $sample -a master-site-list -w" | msub -q analysis -d $PWD -l pmem=4gb -N atlas2.snps.regeno.$sample
+done
+~~~~~~~
+
+###Indels
+
+~~~~~~~~~~~
+:::bash
+ruby Atlas-Indel.rb -i [bam file] -r [reference fasta file] -o [output file] -I -a [master-site-list]
+~~~~~~~~~~~~
+
+So for all the files you could do:
+
+~~~~~~~
+:::bash
+for sample in `cat ../samples ` 
+  do echo "ruby ../Atlas-Indel2/Atlas-Indel2.rb -b ../bams/$sample.*.bam -r ~/refs/human_g1k_v37.fasta -o $sample.vcf -I -n $sample -a master-site-list" | msub -q analysis -d $PWD -l pmem=1gb -N atlas2.indels.regeno.$sample
 done
 ~~~~~~~

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Danny Challis</dc:creator><pubDate>Fri, 08 Feb 2013 20:46:06 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net532df7e508496fd54baa47d59e0c9f93b35a5000</guid></item><item><title>WikiPage Best Practices and Workflows modified by Danny Challis</title><link>https://sourceforge.net/p/atlas2/wiki/Best%2520Practices%2520and%2520Workflows/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v11
+++ v12
@@ -49,7 +49,24 @@

 Here we describe the workflow to combine single sample vcf files to generate a multi-sample vcf a.k.a project-level vcf. The goal is to provide genotype calls from sequence data across all samples at every variant position called in at least one sample. The idea is to report coverage information for reference homozygous sites. This approach is better than providing pileups for individual samples because of the differences in methods calculating reference and variant read depths and differences in filtering reads based on quality . 

+##Step 0:(Optional) Filter calls to the capture target region

+While not required filtering the variant calls to the capture target or other region of interest will drastically reduce the amount of time and resources to build a project-level VCF.  A simple tool for filtering VCF files to a target BED file is included in the Atlas2 package and can be used as follows:
+
+~~~~~~~~
+:::bash
+ruby Atlas2/utils/bed_filter.rb [vcf_file] [bed_file] &gt; [filtered_vcf_file]
+~~~~~~~~
+
+So to filter all the VCF files we run:
+
+~~~~~~~~~
+:::bash
+mkdir target
+for file in *.vcf
+  do ruby Atlas2/utils/bed_filter.rb $file &gt; target/$file
+done
+~~~~~~~~~~

 ##Step 1: Generate master site list

&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Danny Challis</dc:creator><pubDate>Fri, 08 Feb 2013 20:23:06 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net5637bb51b6a1c6818b654cd11964f23b8ab85989</guid></item><item><title>WikiPage Best Practices and Workflows modified by Danny Challis</title><link>https://sourceforge.net/p/atlas2/wiki/Best%2520Practices%2520and%2520Workflows/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v10
+++ v11
@@ -1,13 +1,14 @@
 [TOC]

-#SNP calling on 1000 Genomes Phase3-like data#
+#Variant calling on 1000 Genomes Phase3-like data#

 Following is the command line template to call SNP by taking high coverage exome capture sequencing BAM files as inputs and output the SNP calls in VCF file. We have already tuned the best practice parameters into the tool. Please refer [Atlas-SNP2 usage page](https://sourceforge.net/p/atlas2/wiki/Atlas-SNP/) for the explanation and default value of each parameter.

 Input: ftp://ftp.1000genomes.ebi.ac.uk/vol1/ftp/alignment_indices/20120522.exome.alignment.index

+##SNPs
 Reference fasta: ftp://ftp-trace.ncbi.nih.gov/1000genomes/ftp/technical/reference/human_g1k_v37.fasta.gz

 For each BAM file run:
@@ -26,6 +27,22 @@
 done
 ~~~~~~~

+##Indels
+For each BAM file run:
+
+~~~~~~~
+:::bash
+ruby Atlas-Indel.rb -i [bam file] -r [reference fasta file] -o [output file] -I 
+~~~~~~~
+
+for example:
+
+~~~~~~~
+:::bash
+for sample in `cat ../samples ` 
+  do echo "ruby ../Atlas-Indel2/Atlas-Indel2.rb -i ../bams/$sample.*.bam -r ~/refs/human_g1k_v37.fasta -o $sample.vcf -I" | msub -q analysis -d $PWD -l pmem=1gb -N atlas2.indels.$sample
+done
+~~~~~~~

 #Project-level VCF#

@@ -153,4 +170,3 @@
 :::bash
 ruby vcfPrinter/RunPrinter.rb -i "*.vcf.gz" -o ../all.indels.vcf -p --cluster -n 15 --indel
 ~~~~~~~~~~~~
-
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Danny Challis</dc:creator><pubDate>Wed, 06 Feb 2013 20:59:51 -0000</pubDate><guid isPermaLink="false">https://sourceforge.net66e90123d4a41d5976e2b4be22f57beef64fef16</guid></item></channel></rss>