Mercurial > repos > bgruening > hicexplorer_hicmergematrixbins

diff hicMergeMatrixBins.xml @ 3:5186eda61ca4 draft

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
planemo upload for repository https://github.com/maxplanck-ie/HiCExplorer/tree/master/galaxy/wrapper/ commit 80462804e4fd7deafbcf8e8c5283cc7a98fa7dd5
author bgruening
date Sat, 30 Dec 2017 09:16:29 -0500
parents cdff00acac0f
children d04398893232
line wrap: on
line diff
--- a/hicMergeMatrixBins.xml	Sat Dec 16 16:33:36 2017 -0500
+++ b/hicMergeMatrixBins.xml	Sat Dec 30 09:16:29 2017 -0500
@@ -6,11 +6,8 @@
     </macros>
     <expand macro="requirements" />
     <command detect_errors="exit_code"><![CDATA[
-
-        ln -s '$matrix' input.npz.h5 &&
-
         hicMergeMatrixBins
-            --matrix input.npz.h5
+            --matrix '$matrix_h5_cooler'
             --numBins $numBins
             $runningWindow
             --outFileName ./out.npz.h5
@@ -18,7 +15,8 @@
 ]]>
     </command>
     <inputs>
-        <param argument="--matrix" type="data" format="h5" label="Matrix to reduce" />
+        <expand macro='matrix_h5_cooler_macro' />
+
         <param argument="--numBins" type="integer" min="1" value="3" label="Number of bins to merge" />
         <param argument="--runningWindow" type="boolean" falsevalue="" truevalue="--runningWindow" label="Merge using a running window of length --numBins" />
     </inputs>
@@ -27,7 +25,7 @@
     </outputs>
     <tests>
         <test>
-            <param name="matrix" value="small_test_matrix.h5" />
+            <param name="matrix_h5_cooler" value="small_test_matrix.h5"/>
             <param name="numBins" value="5" />
             <output name="outFileName" file="hicMergeMatrixBins_result1.npz.h5" ftype="h5" compare="sim_size" delta="24000" />
         </test>
@@ -44,7 +42,10 @@
 
 100 kb * 10 = 1000 kb = 1 Mb
 
-This functionality is useful especially for plotting. The higher the resolution of an contact matrix is, the more likely it is to run out of memory while plotting. This is caused by the circumstances that we compute internally with a sparse matrices but to plot we need a dense one. Furthermore, the higher the resolution of a matrix the more detailed it is which can make it difficult to interpret, especially if the read depth of the Hi-C data is not high.
+This functionality is useful especially for plotting. The higher the resolution of an contact matrix is, the more likely it is
+to run out of memory while plotting. This is caused by the circumstances that we compute internally with a sparse matrices but 
+to plot we need a dense one. Furthermore, the higher the resolution of a matrix the more detailed it is which can make it 
+difficult to interpret, especially if the read depth of the Hi-C data is not high.
 
 Input
 -----