VizSchema

# OtherMetaData

# Other metadata

The file can optionally contain other data to assist in visualization or be used for other purposes, for example, tracking provenance. At the moment, we use attributes starting from vs, but the plan is to separate them as needed in the future. 

**Jump to**

* [Variables and their metadata](https://ice.txcorp.com/vizschema/wiki/Variables) 

* [Variables that are combined with their meshes](https://ice.txcorp.com/vizschema/wiki/VariablesWithMesh)

* [Data ordering](https://ice.txcorp.com/vizschema/wiki/DataOrdering)

* [Variables defined in terms of other variables](https://ice.txcorp.com/vizschema/wiki/DerivedVariables) 

* [Multidomain metadata](https://ice.txcorp.com/vizschema/wiki/MultiDomainMetaData)

* [Other metadata](https://ice.txcorp.com/vizschema/wiki/OtherMetaData)

**Time data**

Time data is in a group, 

```

Group "mytime" {

  Att vsType = "time"                        // Required string

  Att vsStep = 500                           // Optional integer scalar (may not be applicable)

  Att vsTime = 1.e-10                        // Required float scalar

}

```

* vsStep gives the simulation step 

* vsTime gives the simulation time at the dump time. 

These values will be loaded by VisIt, and will appear on any plot made from this file. The value of "vsStep" will be displayed with the title "Cycle:", and the value of "vsTime" will be displayed with the title "Time:". (These labels are supplied by VisIt, and are not controlled by the plugin) 

If a file contains one of the two values listed above, only the supplied value will be reported to VisIt. There is no default time or step number. 

Any variable wishing to declare that it uses a particular time group should contain the attribute vsTimeGroup with the name of the time group as the value. For the above example, we would have: 

```

  Att vsTimeGroup = "mytime"

```

**Visualization Limits**

Default bounding region for the mesh for which this is an attribute. 

```

Group "mylimits" {

  Att vsType = "limits"                      // Required string

  Att vsKind = "Cartesian"                   // Required string

  Att vsLowerBounds = [-2.5, -2.5, -1.3]     // Required float array

  Att vsUpperBounds = [2.5, 2.5, 1.3]        // Required float array

}

```

* vsType denotes that this is a limits group 

* vsKind denotes that the limits are specified (in this case) by Cartesian coordinates (for instance, one could use Cylindrical for Z-R-Phi coordinate systems) 

* vsLowerBounds gives the smallest possible value of each coordinate 

* vsUpperBounds gives the largest possible value of each coordinate 

**Axis Labels**

Since meshes supply spatial information for data, all meshes support an optional attribute named "vsAxisLabels". The value of this attribute must be a comma-delimited string containing a list of axis names. If this attribute is not present, the default axis labels are "x,y,z". If the attribute is present, the string is split at every comma, and the axis labels are set accordingly. 

For example, a mesh whose dimensions were measured in meters could specify vsAxisLabels to be "x (m), y (m), z (m)".