Changes between Version 5 and Version 6 of rp_xml_ele_dataset


Ignore:
Timestamp:
Feb 20, 2014 4:37:26 PM (10 years ago)
Author:
ldelgass
Comment:

--

Legend:

Unmodified
Added
Removed
Modified

  • rp_xml_ele_dataset

    v5 v6  
    1010            <label>My Data Set</label>
    1111        </about>
    12         <mesh>output.mymesh</mesh>
    13         <field>output.field1</field>
    14         <field>output.field2</field>
     12        <mesh ref="output.mymesh" />
     13        <field ref="output.field1" />
     14        <field ref="output.field2" />
     15        <field id="field3">
     16          <about>
     17            <label><label>
     18            <description></description>
     19          </about>
     20          <units></units>
     21          <association></association>
     22          <elemtype></elemtype>
     23          <elemsize></elemsize>
     24          <values>...</values>
     25        </field>
    1526    </dataset>
    1627}}}
    … …  
    2031   This is the description of the output.  It is revealed when the user hovers over the output in the drop-down list.
    2132 '''<mesh>'''::
    22    Specifiy the mesh element name over which the fields are defined. The mesh is a separate [wiki:rp_xml_ele_mesh <mesh>] object.
     33   Specifiy the mesh element name over which the fields are defined. The mesh can be defined inline, or as a separate [wiki:rp_xml_ele_mesh <mesh>] object by using a "ref" attribute.  If given inline, the mesh element should have an "id" attribute.
    2334 '''<field>'''::
    24    Specify a field belonging to the dataset.  The field is defined over the mesh specified by <mesh> and is contained in a separate [wiki:rp_xml_ele_field <field>] object.  Note that fields can also be defined with association 'fielddata', in which case the field is simply an array of tuples with no mesh topology.
     35   Specify a field belonging to the dataset.  The field is defined over the mesh specified by <mesh>. The field may be contained in a separate [wiki:rp_xml_ele_field <field>] object by using a "ref" attribute, or inline with an "id" attribute.  Fields can also be defined with association 'fielddata', in which case the field is simply an array of tuples with no mesh topology.  If one of the alternatives below are used, a field element may be used (with id matching the field id in the file data) to specify additional metadata such as units, label and description.
    2536
    2637Alternative to <mesh> and <field> elements: