# HG changeset patch # User bgruening # Date 1450899294 18000 # Node ID ccef78c65fcfdaa9d2605551a932b13455e23e2f # Parent b67afe81e29c4230739c084d14d809d0910a3c61 planemo upload for repository https://github.com/fidelram/deepTools/tree/master/galaxy/wrapper/ commit 4f515024772311c950d277246db548453d24abd7 diff -r b67afe81e29c -r ccef78c65fcf bamCorrelate.xml --- a/bamCorrelate.xml Wed Dec 23 07:26:06 2015 -0500 +++ b/bamCorrelate.xml Wed Dec 23 14:34:54 2015 -0500 @@ -45,8 +45,8 @@ @@ -56,7 +56,7 @@ + help="Length in bases of the window used to sample the genome. (--binSize)"/> @@ -104,15 +104,15 @@ **What it does** -This tool generates a matrix of read-coverages for a list of genomic regions and a number of two or more samples (BAM files) -The tool splits the genome into bins of given length. For each bin, the number of reads found in each BAM file is counted. +This tool generates a matrix of read-coverages for a list of genomic regions and at least two samples (BAM files). +The genome is split into bins of the given size. For each bin, the number of reads found in it in each BAM file is counted. Alternatively, a bed file with pre-defined genomic regions can be provided. In each case the calculation can further be limited to a given genomic interval (e.g. a given chromosome). This option is mostly used for testing and efficiency. -A typical follow-up application is to check and visuzalize the similarity between replicates or published data sets (see: plotPCA and plotCorrelation). +A typical follow-up application is to check and visualize the similarity between replicates or published data sets (see: plotPCA and plotCorrelation). **Output files**: -- **score matrix**: a compressed matrix where every row correponds to a genome region (or bin) and each column corresponds to a sample (BAM file) +- **score matrix**: a compressed matrix where every row corresponds to a genomic region (or bin) and each column corresponds to a sample (BAM file) - Optional : Uncompressed **score matrix**, in case you want to analyse the coverage scores yourself. (Select to "Save raw counts" from above) ======= diff -r b67afe81e29c -r ccef78c65fcf deepTools_macros.xml --- a/deepTools_macros.xml Wed Dec 23 07:26:06 2015 -0500 +++ b/deepTools_macros.xml Wed Dec 23 14:34:54 2015 -0500 @@ -55,7 +55,7 @@ + help="If set, then regions with zero counts for *all* BAM files are included. The default behavior is to ignore such regions." /> @@ -68,7 +68,7 @@ + help="This is useful when testing parameters to reduce the time required. The format is chr:start:end, for example "chr10" or "chr10:456700:891000"." /> --numberOfProcessors "\${GALAXY_SLOTS:-4}" @@ -86,8 +86,8 @@ + label="Smooth values using the following length (in bases)" + help ="The smooth length defines a window, larger than the bin size, over which the number of reads is to be averaged. For example, if the bin size is set to 20 and the smooth length is 60, then, for each bin, its value is set to the average of it and its left and right neighbors. Any value smaller than the bin size will be ignored and no smoothing will be applied."/> @@ -107,11 +107,10 @@ + run the clustering using other software."/> @@ -157,11 +156,11 @@ + By default *each* read mate is extended. + This can be modified using the SAM flags (see --samFlagInclude and --samFlagExclude options) to keep only the first or the second mate. + Unmated reads, mate reads that map to different chromosomes or too far apart are extended to the given value. + Reads are only extended if --extendReads is set to a value greater than the read length. *NOTE*: For spliced-read data, this option is not + recommended as it will extend reads over skipped regions, e.g. introns in RNA-seq data."> @@ -189,14 +188,14 @@ help="By default, bamCorrelate considers consecutive bins of the specified 'Bin size'. However, to reduce the computation time, a larger distance between bins can - by given. Larger distances result in less bins being + be given. Larger distances result in fewer bins being considered."/> + help="For paired-end data the fragment is defined by the bounds of the reads. For single-end data the bounds are defined by the read and the user-definable fragment/extension length. This option is useful to get a sharper signal around enriched regions."/> @@ -229,19 +228,19 @@ + help= "If set, only reads with a mapping quality score higher than this value are considered."/> + help ="If set, then zero counts that happen for *all* BAM files given are ignored. This may result in fewer considered regions." /> + help ="If paired-end reads are used, the fragment length is computed from the BAM file, so this is only needed for single-end data."/> @@ -302,7 +301,7 @@ + help="A Bigwig file."/> @@ -394,8 +393,8 @@ should be skipped. The default is to treat those regions as having a value of zero. The decision to skip non-covered regions depends on the interpretation - of the data. Non-covered regions may represent for - example repetitive regions that want to be skipped. + of the data. Non-covered regions may represent, for + example, repetitive regions that should be ignored. (default: False)" />