Mercurial > repos > lecorguille > msnbase_readmsdata

changeset 6:32c20be7002f draft

Find changesets by keywords (author, files, the commit message), revision number or hash, or revset expression.
planemo upload for repository https://github.com/workflow4metabolomics/xcms commit d481a27556155e3587901d702d364b71f28e30b9
author lecorguille
date Thu, 07 Mar 2019 07:35:39 -0500
parents 2a69f9923a70
children d7a7ef786fbe
files msnbase_readmsdata.xml
diffstat 1 files changed, 5 insertions(+), 5 deletions(-) [+]
line wrap: on
line diff
--- a/msnbase_readmsdata.xml	Mon Feb 11 05:48:13 2019 -0500
+++ b/msnbase_readmsdata.xml	Thu Mar 07 07:35:39 2019 -0500
@@ -61,7 +61,7 @@
             </assert_stdout>
         </test>
         <!-- DISABLE FOR TRAVIS
-        Useful to generate test-data for the further steps-->
+        Useful to generate test-data for the further steps
         <test>
             <param name="input" value="ko16.CDF"  ftype="netcdf" />
             <assert_stdout>
@@ -86,7 +86,7 @@
                 <has_text text="./wt16.CDF        wt16            ." />
             </assert_stdout>
         </test>
-        <!-- -->
+        -->
     </tests>
 
     <help><![CDATA[
@@ -132,7 +132,7 @@
 xcms.findChromPeaks         ``*``.raw.RData      rdata.msnbase.raw
 =========================== ==================== ====================
 
- 
+
 
 **Example of a metabolomic workflow**
 
@@ -158,7 +158,7 @@
 
 You have two methods for your inputs:
 
-    | Single file (recommended): You can put a single file as input. That way, you will be able to launch several readMSData and findChromPeaks in parallel and use "findChromPeaks Merger" before groupChromPeaks. 
+    | Single file (recommended): You can put a single file as input. That way, you will be able to launch several readMSData and findChromPeaks in parallel and use "findChromPeaks Merger" before groupChromPeaks.
     | Zip file: You can put a zip file containing your inputs: myinputs.zip (containing all your conditions as sub-directories).
 
 Zip file: Steps for creating the zip file
@@ -223,7 +223,7 @@
 
     | Tabular file that contains for each sample its associated class and polarity (positive,negative and mixed).
     | This file is necessary in further steps of the workflow, as the Anova and PCA steps for example.
-    | You get a sampleMetadata.tsv only if you use a zip. Otherwise, you have to provide one for the findChromPeaks Merger step. 
+    | You get a sampleMetadata.tsv only if you use a zip. Otherwise, you have to provide one for the findChromPeaks Merger step.
 
 ---------------------------------------------------