# HG changeset patch # User bgruening # Date 1450899343 18000 # Node ID 85c9cda86b1db1c3e899638ad3415dedc39ab93a # Parent d7961ecf5290262747d114547d8cf68f3fd0667c planemo upload for repository https://github.com/fidelram/deepTools/tree/master/galaxy/wrapper/ commit 4f515024772311c950d277246db548453d24abd7 diff -r d7961ecf5290 -r 85c9cda86b1d bigwigCorrelate.xml --- a/bigwigCorrelate.xml Wed Dec 23 07:26:45 2015 -0500 +++ b/bigwigCorrelate.xml Wed Dec 23 14:35:43 2015 -0500 @@ -43,9 +43,9 @@ @@ -53,7 +53,7 @@ + help="Length in bases for a window used to sample the genome. (--binSize)"/> @@ -98,13 +98,13 @@ Given two or more bigWig files, bigwigCorrelate computes the average scores for each of the files in every genomic region. This analysis is performed for the entire genome by running the program in 'bins' mode, or for certain user selected regions -in 'BED-file' mode. Most commonly, the output of bigwigCorrelate is used by other tools such as 'plotCorrelation' or 'plotPCA' +in 'BED-file' mode. Typically the output of bigwigCorrelate is used by other tools, such as 'plotCorrelation' or 'plotPCA', for visualization and diagnostic purposes. **Output files**: -- **Coverage scores**: Coverage scores computed and saved in a format detected by 'plotCorrelation' or 'plotPCA' tools. +- **Coverage scores**: Coverage scores computed and saved in a format appropriate for 'plotCorrelation' or 'plotPCA'. - Data matrix (optional,select to save raw counts to a file above): If you want to have a look at the coverage values or compute statistics yourself using a different program (like R). diff -r d7961ecf5290 -r 85c9cda86b1d deepTools_macros.xml --- a/deepTools_macros.xml Wed Dec 23 07:26:45 2015 -0500 +++ b/deepTools_macros.xml Wed Dec 23 14:35:43 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)" />