<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Recent changes to ChipsterToolConventions</title><link>https://sourceforge.net/p/chipster/wiki/ChipsterToolConventions/</link><description>Recent changes to ChipsterToolConventions</description><atom:link href="https://sourceforge.net/p/chipster/wiki/ChipsterToolConventions/feed" rel="self"/><language>en</language><lastBuildDate>Thu, 26 Jun 2014 06:43:07 -0000</lastBuildDate><atom:link href="https://sourceforge.net/p/chipster/wiki/ChipsterToolConventions/feed" rel="self" type="application/rss+xml"/><item><title>ChipsterToolConventions modified by Aleksi Kallio</title><link>https://sourceforge.net/p/chipster/wiki/ChipsterToolConventions/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v2
+++ v3
@@ -1,22 +1 @@
-[TOC]
-
-## Conventions for Chipster analysis tools
-
-Here we describe different conventions that should be followed when developing or integrating tools to Chipster. The goal in Chipster is always to produce a coherent user experience, for which reason a lot of attention should be placed to harmonising the tools. 
-
-### Common conventions
-
-### Microarray analysis module
-
-  * The default data format is TSV (tab separated values), with one row for each gene or probeset 
-  * The first column should be unnamed or "identifier" and contain the gene/probeset name 
-  * Tool should not removed any existing columns unless the row structure is changed 
-    * In other words, inputs can have annotation etc. data that just passes through analysis steps 
-  * See AnalysisToolInputsAndOutputs for more information, in version 2.0 typing will be decided by the analysis module and will be described in this page 
-
-### Sequence analysis module
-
-### NGS analysis module
-
-  * Tools should accept and produce read data in BAM format 
-  * Tools should assume chromosome names to not have any prefices or suffices (so "12" instead of "chr12") 
+Moved to https://sourceforge.net/apps/mediawiki/chipster/index.php?title=TechnicalManual14#Conventions_for_Chipster_analysis_tools 
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Aleksi Kallio</dc:creator><pubDate>Thu, 26 Jun 2014 06:43:07 -0000</pubDate><guid>https://sourceforge.net3cbfadd4e8b22f9f59b71078b5e50dfabd05700d</guid></item><item><title>ChipsterToolConventions modified by Aleksi Kallio</title><link>https://sourceforge.net/p/chipster/wiki/ChipsterToolConventions/</link><description>&lt;div class="markdown_content"&gt;&lt;pre&gt;--- v1
+++ v2
@@ -2,19 +2,21 @@

 ## Conventions for Chipster analysis tools

+Here we describe different conventions that should be followed when developing or integrating tools to Chipster. The goal in Chipster is always to produce a coherent user experience, for which reason a lot of attention should be placed to harmonising the tools. 
+
 ### Common conventions

 ### Microarray analysis module
-    
-      * The default data format is TSV (tab separated values), with one row for each gene or probeset
-      * The first column should be unnamed or "identifier" and contain the gene/probeset name
-      * See AnalysisToolInputsAndOutputs for more information, in version 2.0 typing will be decided by the analysis module and will be described in this page
-    
+
+  * The default data format is TSV (tab separated values), with one row for each gene or probeset 
+  * The first column should be unnamed or "identifier" and contain the gene/probeset name 
+  * Tool should not removed any existing columns unless the row structure is changed 
+    * In other words, inputs can have annotation etc. data that just passes through analysis steps 
+  * See AnalysisToolInputsAndOutputs for more information, in version 2.0 typing will be decided by the analysis module and will be described in this page 

 ### Sequence analysis module

 ### NGS analysis module
-    
-      * Tools should accept and produce read data in BAM format
-      * Tools should assume chromosome names to not have any prefices or suffices (so "12" instead of "chr12")
-    
+
+  * Tools should accept and produce read data in BAM format 
+  * Tools should assume chromosome names to not have any prefices or suffices (so "12" instead of "chr12") 
&lt;/pre&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Aleksi Kallio</dc:creator><pubDate>Thu, 26 Jun 2014 06:43:07 -0000</pubDate><guid>https://sourceforge.net19c0a9d6547274dc47d0063e48d9df158496feb1</guid></item><item><title>ChipsterToolConventions modified by Aleksi Kallio</title><link>https://sourceforge.net/p/chipster/wiki/ChipsterToolConventions/</link><description>&lt;div class="markdown_content"&gt;&lt;div class="toc"&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href="#conventions-for-chipster-analysis-tools"&gt;Conventions for Chipster analysis tools&lt;/a&gt;&lt;ul&gt;
&lt;li&gt;&lt;a href="#common-conventions"&gt;Common conventions&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#microarray-analysis-module"&gt;Microarray analysis module&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#sequence-analysis-module"&gt;Sequence analysis module&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href="#ngs-analysis-module"&gt;NGS analysis module&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;/div&gt;
&lt;h2 id="conventions-for-chipster-analysis-tools"&gt;Conventions for Chipster analysis tools&lt;/h2&gt;
&lt;h3 id="common-conventions"&gt;Common conventions&lt;/h3&gt;
&lt;h3 id="microarray-analysis-module"&gt;Microarray analysis module&lt;/h3&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;  &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;The&lt;/span&gt; &lt;span class="k"&gt;default&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt; &lt;span class="n"&gt;format&lt;/span&gt; &lt;span class="n"&gt;is&lt;/span&gt; &lt;span class="n"&gt;TSV&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;tab&lt;/span&gt; &lt;span class="n"&gt;separated&lt;/span&gt; &lt;span class="n"&gt;values&lt;/span&gt;&lt;span class="p"&gt;),&lt;/span&gt; &lt;span class="n"&gt;with&lt;/span&gt; &lt;span class="n"&gt;one&lt;/span&gt; &lt;span class="n"&gt;row&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;each&lt;/span&gt; &lt;span class="n"&gt;gene&lt;/span&gt; &lt;span class="n"&gt;or&lt;/span&gt; &lt;span class="n"&gt;probeset&lt;/span&gt;
  &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;The&lt;/span&gt; &lt;span class="n"&gt;first&lt;/span&gt; &lt;span class="n"&gt;column&lt;/span&gt; &lt;span class="n"&gt;should&lt;/span&gt; &lt;span class="n"&gt;be&lt;/span&gt; &lt;span class="n"&gt;unnamed&lt;/span&gt; &lt;span class="n"&gt;or&lt;/span&gt; &lt;span class="s"&gt;&amp;quot;identifier&amp;quot;&lt;/span&gt; &lt;span class="n"&gt;and&lt;/span&gt; &lt;span class="n"&gt;contain&lt;/span&gt; &lt;span class="n"&gt;the&lt;/span&gt; &lt;span class="n"&gt;gene&lt;/span&gt;&lt;span class="o"&gt;/&lt;/span&gt;&lt;span class="n"&gt;probeset&lt;/span&gt; &lt;span class="n"&gt;name&lt;/span&gt;
  &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;See&lt;/span&gt; &lt;span class="n"&gt;AnalysisToolInputsAndOutputs&lt;/span&gt; &lt;span class="k"&gt;for&lt;/span&gt; &lt;span class="n"&gt;more&lt;/span&gt; &lt;span class="n"&gt;information&lt;/span&gt;&lt;span class="p"&gt;,&lt;/span&gt; &lt;span class="n"&gt;in&lt;/span&gt; &lt;span class="n"&gt;version&lt;/span&gt; &lt;span class="mf"&gt;2.0&lt;/span&gt; &lt;span class="n"&gt;typing&lt;/span&gt; &lt;span class="n"&gt;will&lt;/span&gt; &lt;span class="n"&gt;be&lt;/span&gt; &lt;span class="n"&gt;decided&lt;/span&gt; &lt;span class="n"&gt;by&lt;/span&gt; &lt;span class="n"&gt;the&lt;/span&gt; &lt;span class="n"&gt;analysis&lt;/span&gt; &lt;span class="n"&gt;module&lt;/span&gt; &lt;span class="n"&gt;and&lt;/span&gt; &lt;span class="n"&gt;will&lt;/span&gt; &lt;span class="n"&gt;be&lt;/span&gt; &lt;span class="n"&gt;described&lt;/span&gt; &lt;span class="n"&gt;in&lt;/span&gt; &lt;span class="n"&gt;this&lt;/span&gt; &lt;span class="n"&gt;page&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;h3 id="sequence-analysis-module"&gt;Sequence analysis module&lt;/h3&gt;
&lt;h3 id="ngs-analysis-module"&gt;NGS analysis module&lt;/h3&gt;
&lt;div class="codehilite"&gt;&lt;pre&gt;  &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;Tools&lt;/span&gt; &lt;span class="n"&gt;should&lt;/span&gt; &lt;span class="n"&gt;accept&lt;/span&gt; &lt;span class="n"&gt;and&lt;/span&gt; &lt;span class="n"&gt;produce&lt;/span&gt; &lt;span class="n"&gt;read&lt;/span&gt; &lt;span class="n"&gt;data&lt;/span&gt; &lt;span class="n"&gt;in&lt;/span&gt; &lt;span class="n"&gt;BAM&lt;/span&gt; &lt;span class="n"&gt;format&lt;/span&gt;
  &lt;span class="o"&gt;*&lt;/span&gt; &lt;span class="n"&gt;Tools&lt;/span&gt; &lt;span class="n"&gt;should&lt;/span&gt; &lt;span class="n"&gt;assume&lt;/span&gt; &lt;span class="n"&gt;chromosome&lt;/span&gt; &lt;span class="n"&gt;names&lt;/span&gt; &lt;span class="n"&gt;to&lt;/span&gt; &lt;span class="n"&gt;not&lt;/span&gt; &lt;span class="n"&gt;have&lt;/span&gt; &lt;span class="n"&gt;any&lt;/span&gt; &lt;span class="n"&gt;prefices&lt;/span&gt; &lt;span class="n"&gt;or&lt;/span&gt; &lt;span class="n"&gt;suffices&lt;/span&gt; &lt;span class="p"&gt;(&lt;/span&gt;&lt;span class="n"&gt;so&lt;/span&gt; &lt;span class="s"&gt;&amp;quot;12&amp;quot;&lt;/span&gt; &lt;span class="n"&gt;instead&lt;/span&gt; &lt;span class="n"&gt;of&lt;/span&gt; &lt;span class="s"&gt;&amp;quot;chr12&amp;quot;&lt;/span&gt;&lt;span class="p"&gt;)&lt;/span&gt;
&lt;/pre&gt;&lt;/div&gt;
&lt;/div&gt;</description><dc:creator xmlns:dc="http://purl.org/dc/elements/1.1/">Aleksi Kallio</dc:creator><pubDate>Thu, 26 Jun 2014 06:43:07 -0000</pubDate><guid>https://sourceforge.netb6473ac3cf3a09b28f9797ace1027a099246821e</guid></item></channel></rss>