Recent changes to FileFormat

FileFormat modified by Nikolaus Vahrenkamp

Nikolaus Vahrenkamp — Thu, 27 Nov 2014 20:39:07 -0000

FileFormat modified by Valerij Wittenbeck

Valerij Wittenbeck — Wed, 02 Jul 2014 10:55:08 -0000

--- v20
+++ v21
@@ -1,4 +1,4 @@
-On this page you will find a detailed description of the XML data structure that is used to setup robots and environments in Simox. Please have a look at [ Build a robot model](RobotModels_), to see how a robot can be defined. 
+On this page you will find a detailed description of the XML data structure that is used to setup robots and environments in Simox. Please have a look at [Build a robot model](RobotModels), to see how a robot can be defined.

 [TOC]

@@ -15,10 +15,10 @@
   * xs:string 
   * xs:decimal 
   * xs:boolean 
-  * Unit-Length-Type: A string that could be "m", "meter", "mm" or "millimeter". 
-  * Unit-Angle-Type: A string that could be "rad", "radian", "deg" or "degree". 
-  * Unit-Weight-Type: A string that could be "g", "gram", "kg", "kilogram", "t" or "ton". 
-  * Unit-Time-Type: A string that could be "sec", "second", "min", "minute", "h" or "hour". 
+  * Unit-Length-Type: A string that could be "m", "meter", "mm" or "millimeter"
+  * Unit-Angle-Type: A string that could be "rad", "radian", "deg" or "degree"
+  * Unit-Weight-Type: A string that could be "g", "gram", "kg", "kilogram", "t" or "ton"
+  * Unit-Time-Type: A string that could be "sec", "second", "min", "minute", "h" or "hour"
   * FileLocation-Type: A string that is either "absolute" or "relative", specifying whether a filename is given absolutely or relatively to the current XML file. 

 ## Transformations
@@ -26,49 +26,47 @@
 Geometric transformations can be specified in several ways, which are encapsulated by a ``. Note, that either a Matrix4x4 or a rotation (Quaternion, Matrix3x3 or RollPitchYaw) together with a Translation can be used. 

   * Matrix4x4-Type. A homogeneous transformation given as a 4x4 matrix. Here is an example: 
-    
-        
-          
-          
-          
-          
-        
-    
+
+~~~~~~
+   
+     
+     
+     
+     
+   
+~~~~~~

   * Matrix3x3-Type. A rotation given as a 3x3 matrix. Here is an example: 

-        
-          
-          
-          
-        
-    
-
-  
-
+~~~~~~
+   
+     
+     
+     
+   
+~~~~~~

   * RollPitchYaw-Type. A rotation given as roll, pitch and yaw angles. Here is an example: 

-        
-    
-
-  
-
+~~~~~~
+   
+~~~~~~

   * Quaternion-Type. A rotation given as quaternions. Here is an example: 
-    
-        
-    
+
+~~~~~~    
+   
+~~~~~~

   * Translation-Type. A translation. Here is an example: 

-        
-    
+~~~~~~
+   
+~~~~~~

 # Robot Definitions

-[[img src=Xsd_Robot.png width=100%]]  
-
+[[img src=Xsd_Robot.png width=50%]]  

 ## RobotNode

@@ -79,8 +77,7 @@
   * A visualization that is linked at the resulting pose (optional `` tag). 
   * A collision model which is used for collision detection (optional `` tag). 

-[[img src=Xsd_RobotNode2.png width=100%]]  
-
+[[img src=Xsd_RobotNode2.png width=50%]]  

 ### Joint

@@ -92,40 +89,39 @@

 As shown below, Joints can be defined either with Denavit-Hartenberg conventions (``), or by defining transformations (`` or ``). A valid Joint definition must either be defined the first or the second way; mixing is not allowed and will result in an exception during parsing. 

-[[img src=Xsd_Joint2.png width=100%]] 
+[[img src=Xsd_Joint2.png width=50%]] 

 ### Physics

-The _Coord-Location-type_ is a string that specifies where the CoM is located. When it's set to "VisualizationBBoxCenter" the CoM location is automatically set to the center of the bounding box of the RobotNode's visualization and the other attributes are ignored. If set to "joint", the CoM location is defined by the x,y,z attributes in the joint's coordinate system. 
+The `Coord-Location-type` is a string that specifies where the CoM is located. When it's set to "VisualizationBBoxCenter" the CoM location is automatically set to the center of the bounding box of the RobotNode's visualization and the other attributes are ignored. If set to "joint", the CoM location is defined by the x,y,z attributes in the joint's coordinate system. 

-[[img src=Xsd_Physics.png width=100%]] 
+[[img src=Xsd_Physics.png width=50%]] 

 ### Visualization

-[[img src=Visualization.png width=100%]] 
+[[img src=Visualization.png width=50%]] 

 ### CollisionModel

-[[img src=Xsd_CollisionModel.png width=100%]] 
+[[img src=Xsd_CollisionModel.png width=50%]] 

 ### Sensor

 Sensors are located w.r.t. the coordinate system of the RobotNode and can additionally define a local transformation. Currently two types of sensors are implemented: Position and Camera. 

-[[img src=Xsd_Sensor.png width=100%]] 
+[[img src=Xsd_Sensor.png width=50%]] 

 ## RobotNodeSet

-[[img src=Xsd_RobotNodeSet.png width=100%]] 
+[[img src=Xsd_RobotNodeSet.png width=50%]] 

 ## EndEffector

-The _EEFActorCollision-Type_ specifies if and how the element of an finger/actor should be considered for collision detection. The string attribute can be 
+The `EEFActorCollision-Type` specifies if and how the element of an finger/actor should be considered for collision detection. The string attribute can be 

-  * None: No collision detection should be performed with this segment. 
-  * Actors: Collision detection is performed with all other actors. 
-  * Static: Collision detection is performed with the static part of the EEF. 
-  * All: Collision detection is performed with all other actors and the static part. 
-
+  * `None`: No collision detection should be performed with this segment. 
+  * `Actors`: Collision detection is performed with all other actors. 
+  * `Static`: Collision detection is performed with the static part of the EEF. 
+  * `All`: Collision detection is performed with all other actors and the static part. 

-[[img src=Xsd_EEF_open.png width=100%]] 
+[[img src=Xsd_EEF_open.png width=50%]]

FileFormat modified by Valerij Wittenbeck

Valerij Wittenbeck — Tue, 01 Jul 2014 11:04:48 -0000

--- v19
+++ v20
@@ -4,9 +4,9 @@

 # XSD Schema defintion

-Simox provides an XSD Schema defintion file that can be used to validate XML defintions and/or for documentation purposes. The file can be found in **<Your_Simox_Dir>/doc/file_formats**. 
+Simox provides an XSD Schema defintion file that can be used to validate XML defintions and/or for documentation purposes. The file can be found in **`/doc/file_formats`**. 

-Note, that XSD definitions are case sensitive, while Simox does not consider the case while parsing XML tags. So the tags _<RobotNode>_, _<robotnode>_ and _<ROBOTNODE>_ are all starting a valid RobotNode definition. 
+Note, that XSD definitions are case sensitive, while Simox does not consider the case while parsing XML tags. So the tags ``, `` and `` are all starting a valid RobotNode definition. 

 ## Types

@@ -23,25 +23,25 @@

 ## Transformations

-Geometric transformations can be specified in several ways, which are encapsulated by a <Transform-Type>. Note, that either a Matrix4x4 or a rotation (Quaternion, Matrix3x3 or RollPitchYaw) together with a Translation can be used. 
+Geometric transformations can be specified in several ways, which are encapsulated by a ``. Note, that either a Matrix4x4 or a rotation (Quaternion, Matrix3x3 or RollPitchYaw) together with a Translation can be used. 

   * Matrix4x4-Type. A homogeneous transformation given as a 4x4 matrix. Here is an example: 

-    <matrix4x4>
-      <row1 c1="1" c2="0"  c3="0" c4="100"/>
-      <row2 c1="0" c2="0"  c3="1" c4="200"/>
-      <row3 c1="0" c2="-1" c3="0" c4="300"/>
-      <row4 c1="0" c2="0"  c3="0" c4="1"/>
-    </matrix4x4>
+        
+          
+          
+          
+          
+        

   * Matrix3x3-Type. A rotation given as a 3x3 matrix. Here is an example: 

-    <matrix3x3>
-      <row1 c1="1" c2="0"  c3="0"/>
-      <row2 c1="0" c2="0"  c3="1"/>
-      <row3 c1="0" c2="-1" c3="0"/>
-    </matrix3x3>
+        
+          
+          
+          
+        

@@ -49,7 +49,7 @@

   * RollPitchYaw-Type. A rotation given as roll, pitch and yaw angles. Here is an example: 

-    <rollpitchyaw roll="90" pitch="0" yaw="45" unitsAngle="degree"/>
+        

@@ -57,29 +57,29 @@

   * Quaternion-Type. A rotation given as quaternions. Here is an example: 

-    <quaternion x="1.0" y="0" z="0" w="0.2"/>
+        

   * Translation-Type. A translation. Here is an example: 

-    <Translation x="100" y="200" z="300" unitsLength="mm"/>
+        

 # Robot Definitions

-[[img src=Xsd_Robot.png]]  
+[[img src=Xsd_Robot.png width=100%]]  

 ## RobotNode

 A RobotNode can specify 

-  * A fixed Transformation (optional <Transform> tag). 
-  * A joint that applies a second transformation according to the joint value (optional <Joint> tag). 
-  * A visualization that is linked at the resulting pose (optional <Visualization> tag). 
-  * A collision model which is used for collision detection (optional <CollisionModel> tag). 
+  * A fixed Transformation (optional `` tag). 
+  * A joint that applies a second transformation according to the joint value (optional `` tag). 
+  * A visualization that is linked at the resulting pose (optional `` tag). 
+  * A collision model which is used for collision detection (optional `` tag). 

-[[img src=Xsd_RobotNode2.png]]  
+[[img src=Xsd_RobotNode2.png width=100%]]  

 ### Joint
@@ -90,33 +90,33 @@
   * revolute: A revolute joint that can be rotated around an axis. 
   * prismatic: A prismatic joint that realizes a translational movement. 

-As shown below, Joints can be defined either with Denavit-Hartenberg conventions (_<DH>_), or by defining transformations ((_<Axis>_ or _<TranslationDirection>_). A valid Joint definition must either be defined the first or the second way; mixing is not allowed and will result in an exception during parsing. 
+As shown below, Joints can be defined either with Denavit-Hartenberg conventions (``), or by defining transformations (`` or ``). A valid Joint definition must either be defined the first or the second way; mixing is not allowed and will result in an exception during parsing. 

-[[img src=Xsd_Joint2.png]] 
+[[img src=Xsd_Joint2.png width=100%]] 

 ### Physics

 The _Coord-Location-type_ is a string that specifies where the CoM is located. When it's set to "VisualizationBBoxCenter" the CoM location is automatically set to the center of the bounding box of the RobotNode's visualization and the other attributes are ignored. If set to "joint", the CoM location is defined by the x,y,z attributes in the joint's coordinate system. 

-[[img src=Xsd_Physics.png]] 
+[[img src=Xsd_Physics.png width=100%]] 

 ### Visualization

-[[img src=Visualization.png]] 
+[[img src=Visualization.png width=100%]] 

 ### CollisionModel

-[[img src=Xsd_CollisionModel.png]] 
+[[img src=Xsd_CollisionModel.png width=100%]] 

 ### Sensor

 Sensors are located w.r.t. the coordinate system of the RobotNode and can additionally define a local transformation. Currently two types of sensors are implemented: Position and Camera. 

-[[img src=Xsd_Sensor.png]] 
+[[img src=Xsd_Sensor.png width=100%]] 

 ## RobotNodeSet

-[[img src=Xsd_RobotNodeSet.png]] 
+[[img src=Xsd_RobotNodeSet.png width=100%]] 

 ## EndEffector

@@ -128,4 +128,4 @@
   * All: Collision detection is performed with all other actors and the static part. 

-[[img src=Xsd_EEF_open.png]] 
+[[img src=Xsd_EEF_open.png width=100%]]

FileFormat modified by Nikolaus Vahrenkamp

Nikolaus Vahrenkamp — Mon, 23 Jun 2014 06:40:15 -0000

--- v18
+++ v19
@@ -72,7 +72,12 @@

 ## RobotNode

-A RobotNode may specify a Transformation 
+A RobotNode can specify 
+
+  * A fixed Transformation (optional <Transform> tag). 
+  * A joint that applies a second transformation according to the joint value (optional <Joint> tag). 
+  * A visualization that is linked at the resulting pose (optional <Visualization> tag). 
+  * A collision model which is used for collision detection (optional <CollisionModel> tag). 

 [[img src=Xsd_RobotNode2.png]]  

@@ -105,6 +110,8 @@

 ### Sensor

+Sensors are located w.r.t. the coordinate system of the RobotNode and can additionally define a local transformation. Currently two types of sensors are implemented: Position and Camera. 
+
 [[img src=Xsd_Sensor.png]] 

 ## RobotNodeSet

FileFormat modified by Nikolaus Vahrenkamp

Nikolaus Vahrenkamp — Mon, 23 Jun 2014 06:40:15 -0000

--- v17
+++ v18
@@ -72,7 +72,9 @@

 ## RobotNode

-[[img src=Xsd_RobotNode.png]]  
+A RobotNode may specify a Transformation 
+
+[[img src=Xsd_RobotNode2.png]]  

 ### Joint
@@ -85,7 +87,7 @@

 As shown below, Joints can be defined either with Denavit-Hartenberg conventions (_<DH>_), or by defining transformations ((_<Axis>_ or _<TranslationDirection>_). A valid Joint definition must either be defined the first or the second way; mixing is not allowed and will result in an exception during parsing. 

-[[img src=Xsd_Joint2.png.]] 
+[[img src=Xsd_Joint2.png]] 

 ### Physics

@@ -100,6 +102,10 @@
 ### CollisionModel

 [[img src=Xsd_CollisionModel.png]] 
+
+### Sensor
+
+[[img src=Xsd_Sensor.png]] 

 ## RobotNodeSet

FileFormat modified by Nikolaus Vahrenkamp

Nikolaus Vahrenkamp — Mon, 23 Jun 2014 06:40:15 -0000

--- v16
+++ v17
@@ -79,13 +79,13 @@

 For each Joint tag the type has to be specified: Currently the following Joint-types are implemented: 

-  * fixed: A fixed joint that cannot be moved. Such joints can be used to rotate coordinate systems. 
+  * fixed (standard): A fixed joint that cannot be moved. This joint type is implicitly chosen when no joint is specified within a RobotNode. 
   * revolute: A revolute joint that can be rotated around an axis. 
   * prismatic: A prismatic joint that realizes a translational movement. 

-As shown below, Joints can be defined either with Denavit-Hartenberg conventions (_<DH>_), or by defining prejoint-, joint- and postjoint-transformations ((_<PreJointTransform>_, _<Axis>_ or _<TranslationDirection>_ and _<PostJointTransform>_). A valid Joint definition must either be defined the first or the second way; mixing is not allowed and will result in an exception during parsing. 
+As shown below, Joints can be defined either with Denavit-Hartenberg conventions (_<DH>_), or by defining transformations ((_<Axis>_ or _<TranslationDirection>_). A valid Joint definition must either be defined the first or the second way; mixing is not allowed and will result in an exception during parsing. 

-[[img src=Xsd_Joint_open.png]] 
+[[img src=Xsd_Joint2.png.]] 

 ### Physics

FileFormat modified by Nikolaus Vahrenkamp

Nikolaus Vahrenkamp — Mon, 23 Jun 2014 06:40:14 -0000

--- v15
+++ v16
@@ -7,6 +7,8 @@
 Simox provides an XSD Schema defintion file that can be used to validate XML defintions and/or for documentation purposes. The file can be found in **<Your_Simox_Dir>/doc/file_formats**.

 Note, that XSD definitions are case sensitive, while Simox does not consider the case while parsing XML tags. So the tags _<RobotNode>_, _<robotnode>_ and _<ROBOTNODE>_ are all starting a valid RobotNode definition. 
+
+## Types

 The following types are used: 

@@ -19,10 +21,9 @@
   * Unit-Time-Type: A string that could be "sec", "second", "min", "minute", "h" or "hour". 
   * FileLocation-Type: A string that is either "absolute" or "relative", specifying whether a filename is given absolutely or relatively to the current XML file. 

+## Transformations
+
 Geometric transformations can be specified in several ways, which are encapsulated by a <Transform-Type>. Note, that either a Matrix4x4 or a rotation (Quaternion, Matrix3x3 or RollPitchYaw) together with a Translation can be used. 
-
-  
-

   * Matrix4x4-Type. A homogeneous transformation given as a 4x4 matrix. Here is an example:

FileFormat modified by Nikolaus Vahrenkamp

Nikolaus Vahrenkamp — Mon, 23 Jun 2014 06:40:14 -0000

--- v14
+++ v15
@@ -19,7 +19,10 @@
   * Unit-Time-Type: A string that could be "sec", "second", "min", "minute", "h" or "hour". 
   * FileLocation-Type: A string that is either "absolute" or "relative", specifying whether a filename is given absolutely or relatively to the current XML file.

-Geometric transformations can be specified in the following ways: 
+Geometric transformations can be specified in several ways, which are encapsulated by a <Transform-Type>. Note, that either a Matrix4x4 or a rotation (Quaternion, Matrix3x3 or RollPitchYaw) together with a Translation can be used. 
+
+  
+

   * Matrix4x4-Type. A homogeneous transformation given as a 4x4 matrix. Here is an example:

FileFormat modified by Nikolaus Vahrenkamp

Nikolaus Vahrenkamp — Mon, 23 Jun 2014 06:40:14 -0000

--- v13
+++ v14
@@ -58,7 +58,7 @@

   * Translation-Type. A translation. Here is an example: 

-    <ranslation x="100" y="200" z="300" unitsLength="mm"/>
+    <Translation x="100" y="200" z="300" unitsLength="mm"/>

 # Robot Definitions

FileFormat modified by Nikolaus Vahrenkamp

Nikolaus Vahrenkamp — Mon, 23 Jun 2014 06:40:14 -0000

--- v12
+++ v13
@@ -58,7 +58,7 @@

   * Translation-Type. A translation. Here is an example: 

-    <quaternion x="100" y="200" z="300" unitsLength="mm"/>
+    <ranslation x="100" y="200" z="300" unitsLength="mm"/>

 # Robot Definitions