To learn how to configure the "classic" platform model, consult the Platform Modeling How-To section.
The "generic" platform model is only available when using DIRSIG4. This platform model is configured via an XML-based file that contains a set of data entries with location and 3-axis rotation values as a function of time. There are several key upgrades to the "classic" platform model that are realized in the "generic" platform model.
The position and orientation angles are a function of time and the model will interpolate the position and orientation for arbitrary times. In contrast, the position and orientation data used in the "classic" model specified each capture. This essentially ignored the time associated with each position and orientation entry and the instrument scan rate.
The axis rotations are always absolute about the relevant axis and never relative to the "inertial" flight line. These rotation angles are based on a right-handed coordinate system and the same angle descriptors are used for both static and dynamic positioning schemes.
The user can specify the order of the axis rotations.
When used with the "tasking" feature, different sections of a very long location/orientation history can be used to model a series of data captures (and corresponding image files).
All of these features are fully described in the Generic Platform XML File. This file is used to describe both static and dynamic positioning simulations. The name of the Generic Platform XML File is specified in the Input Configuration File using the XML_POSITION variable in place of the POSITION section. Unfortunately, the replacement of the POSITION section with the XML_POSITION variable must be performed manually using a text editor at this time.
XML_POSITION = FlightLine1.ppd
Since the Generic Platform XML File is simply a series of way points, the user needs a way to specify a time window over which the model is to simulate the collection of data. This is accomplished through the TASKS section of the Input Configuration File. The TASKS section contains a series of TASK sections that each define a data collection task. At this time, a task is described by a start and stop that is relative to the main time in the SCENE section of the Input Configuration File. This allows the user to provide the generic platform model with a very extensive record of location/orientation way points, and instruct the model to "turn on" the simulated instrument only for specific windows. During an active capture window, the instrument will perform data captures using the instrument or focal plane scan rate(s).