# HG changeset patch
# User pieter.lukasse@wur.nl
# Date 1427574092 -3600
# Node ID a4c4656ad9e067b5be67f2bbe83f3f087a3300aa
# Parent  fb265c83b8848865760d36c35317b1a5a33a864e
some improvements/fixes?

diff -r fb265c83b884 -r a4c4656ad9e0 OntologyAndObservationsVis.jar
Binary file OntologyAndObservationsVis.jar has changed
diff -r fb265c83b884 -r a4c4656ad9e0 TermMapperTool.jar
Binary file TermMapperTool.jar has changed
diff -r fb265c83b884 -r a4c4656ad9e0 ontologyvis.xml
--- a/ontologyvis.xml	Sat Mar 28 16:07:09 2015 +0100
+++ b/ontologyvis.xml	Sat Mar 28 21:21:32 2015 +0100
@@ -69,18 +69,17 @@
      	       individual observation items per ontology entry."/>
 		
 		<param name="oneTermOnlyAnnotation" type="boolean" checked="true" 
-		  label="Use only one annotation per observation items" 
-     	  help="Check this to force each observation item to keep only one of its ontology annotations,
-	            as a form of redundancy reduction. If checked, the algorithm will 
-	           keep the ontology annotation that has most other (sibling) observation items."/>
+		  label="Try to use only one term per observation items" 
+     	  help="If checked, the algorithm will try to reduce the number of terms to which an 
+     	       observation item is associated. The observation item can still appear in more than one 
+     	       term circle, but the algorithm will try to reduce this by preferring the bigger circles."/>
 	           
 		<param name="allowMultipleSuperClasses" type="boolean" checked="false" 
 		  label="Allow ontology terms to be nested under more than one super class" 
-     	  help="Some ontology classes have multiple super classes. Check this to allow
-     	        nesting the classes under each of its super classes. Not checking this option
-     	        will cause the ontology classes that have more than one super class to 
-     	        be nested under the super class that has (initially) most observation items
-     	        under it (directly or in its sub classes)."/>
+     	  help="Some ontology classes can have multiple super classes. Check this to allow
+     	        nesting the classes under each of its super classes. Even when NOT checking this option,
+     	        the ontology classes can still appear in more than one 
+     	        term circle/superclass, but the algorithm will try to reduce this by preferring the bigger circles."/>
      	
 	</inputs>
 	<outputs>