# HG changeset patch # User yhoogstrate # Date 1392740021 18000 # Node ID 3bb39a9058d97f1b84f393edbe0817ae46776427 # Parent 7946b09020e02f20790fbf7498c8da3795421bda Uploaded diff -r 7946b09020e0 -r 3bb39a9058d9 all_fasta.loc.sample --- a/all_fasta.loc.sample Tue Feb 18 05:29:59 2014 -0500 +++ /dev/null Thu Jan 01 00:00:00 1970 +0000 @@ -1,18 +0,0 @@ -#This file lists the locations and dbkeys of all the fasta files -#under the "genome" directory (a directory that contains a directory -#for each build). The script extract_fasta.py will generate the file -#all_fasta.loc. This file has the format (white space characters are -#TAB characters): -# -# -# -#So, all_fasta.loc could look something like this: -# -#apiMel3 apiMel3 Honeybee (Apis mellifera): apiMel3 /path/to/genome/apiMel3/apiMel3.fa -#hg19canon hg19 Human (Homo sapiens): hg19 Canonical /path/to/genome/hg19/hg19canon.fa -#hg19full hg19 Human (Homo sapiens): hg19 Full /path/to/genome/hg19/hg19full.fa -# -#Your all_fasta.loc file should contain an entry for each individual -#fasta file. So there will be multiple fasta files for each build, -#such as with hg19 above. -# diff -r 7946b09020e0 -r 3bb39a9058d9 tool-data/all_fasta.loc.sample --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tool-data/all_fasta.loc.sample Tue Feb 18 11:13:41 2014 -0500 @@ -0,0 +1,18 @@ +#This file lists the locations and dbkeys of all the fasta files +#under the "genome" directory (a directory that contains a directory +#for each build). The script extract_fasta.py will generate the file +#all_fasta.loc. This file has the format (white space characters are +#TAB characters): +# +# +# +#So, all_fasta.loc could look something like this: +# +#apiMel3 apiMel3 Honeybee (Apis mellifera): apiMel3 /path/to/genome/apiMel3/apiMel3.fa +#hg19canon hg19 Human (Homo sapiens): hg19 Canonical /path/to/genome/hg19/hg19canon.fa +#hg19full hg19 Human (Homo sapiens): hg19 Full /path/to/genome/hg19/hg19full.fa +# +#Your all_fasta.loc file should contain an entry for each individual +#fasta file. So there will be multiple fasta files for each build, +#such as with hg19 above. +# diff -r 7946b09020e0 -r 3bb39a9058d9 tool_data_table_conf.xml.sample --- /dev/null Thu Jan 01 00:00:00 1970 +0000 +++ b/tool_data_table_conf.xml.sample Tue Feb 18 11:13:41 2014 -0500 @@ -0,0 +1,5 @@ + + + name, dbkey, display_name, value + +
\ No newline at end of file diff -r 7946b09020e0 -r 3bb39a9058d9 varscan_mpileup2snp_from_bam.xml --- a/varscan_mpileup2snp_from_bam.xml Tue Feb 18 05:29:59 2014 -0500 +++ b/varscan_mpileup2snp_from_bam.xml Tue Feb 18 11:13:41 2014 -0500 @@ -9,21 +9,6 @@ #if $reference_genome_source.source_select == "attribute" and len({ alignment.metadata.dbkey:True for alignment in $alignments }.keys()) != 1 echo "Invalid number of dbkeys are found: ${ len({ alignment.metadata.dbkey:True for alignment in $alignments }.keys()) }, while only one should be used. Make sure that the alignments are done on the same reference genome and that 'tool-data/all_fasta.loc' is configured properly!" >&2 #else - - - samtools-mpileup-parallel mpileup -t $samtools_threads -f @@ -93,9 +78,9 @@ $varscan_variants #end if - $varscan_output_vcf + --output-vcf $varscan_output_vcf - > $output_table + > $snv_output #end if @@ -199,11 +184,15 @@ - + - + + + + +