MotionView User's Guide

Metadata File Format

Metadata File Format

 Previous topic Next topic No expanding text in this topic  

Metadata File Format

 Previous topic Next topic JavaScript is required for expanding text JavaScript is required for the print function  

The metadata file consists of multiple data blocks denoted by keyword pairs. The file begins with the header information block and is followed by one or more body blocks. The header information block must begin with Begin_Header and end with End_Header.  Each body block is must begin with Begin_Body and end with End_Body.

Each body block begins with a body information data section followed by one or multiple request blocks that begin with Begin_Request and end with End_Request.  The body information section provides detailed information about the body on which force outputs are requested. In each request block, detailed information about the force action points, action/reaction/reference markers are provided.

The number of Begin_Body and End_Body blocks depends on the number of bodies that have force output requests. Each Begin_Request and End_Request block corresponds to a force REQUEST statement in the ADAMS or MotionSolve input deck.

The general structure of a metadata file is shown below:

Begin_Header

 <The Header Information>

End_Header

Begin_Body

 <Body Information>

 <Begin_Marker>

         <LPRF Marker Information>

 <End_Marker>

 <Begin_Marker>

         <CM Marker Information>

 <End_Marker>

 Begin_Request

         <Request Information>

         <Begin_Marker>

                 <Action Marker Information>

         <End_Marker>

         <Begin_Marker>

                 <Reaction Marker Information>

         <End_Marker>

         <Begin_Marker>

                 <Reference Marker Information>

         <End_Marker>

 End_Request

 Begin_Request

 End_Request

 …

 Begin_Request

 End_Request

End_Body

Begin_Body

 …

 Begin_Request

 End_Request

End_Body

…

Begin_Body

 …

 Begin_Request

 End_Request

End_Body