Mercurial > repos > pieterlukasse > primo_multiomics
changeset 13:a4c4656ad9e0
some improvements/fixes?
| author | pieter.lukasse@wur.nl |
|---|---|
| date | Sat, 28 Mar 2015 21:21:32 +0100 |
| parents | fb265c83b884 |
| children | 7dfda218dca1 |
| files | OntologyAndObservationsVis.jar TermMapperTool.jar ontologyvis.xml |
| diffstat | 3 files changed, 8 insertions(+), 9 deletions(-) [+] |
line wrap: on
line diff
--- 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>