The following options are available for managing simulator output:
|Measurements.Filename||Click the current value to display a file selection window, where you can specify the path and filename of the measurement file to which the simulator measurements are to be written.|
Option to reset the Scenario Measurement Files list upon successful conclusion of the simulator run.
If set to true (the default):
If set to false:
|Measurements.AdditionalFiles||A scripting aid to tell if the simulator had to create additional files to store the generated measurements. This would be the case, for instance, if the user specified a GEOSC file as the output format and then generated GPS measurements in addition to ground tracking.|
|Measurements.Files||A list of the user-specified file and any additional files created by the simulator.|
|Measurements.OutputByPass||When the true observation for each pass will be output to a
separate file. A pass is a series of tracking measurements for a
(tracker, primary object) where the primary object is nominally the
satellite being tracked. A pass is terminated when the gap between
successive measurements exceeds the "MinPassDelta" property given
in the primary object properties. The Measurements.Filename is used
as a proxy for the name(s) of the output files.
Let the Measurements.Filename="<Basename>.<ext>"
Then the output files will be named in the form:
<Basename>_<tracker name>_<primary object id>_<start name>_<end time>.<ext>
<tracker name> is the unique alphanumeric name of the tracker
<primary object id> is the tracking id of the primary object
<start time> is the UTC time of first observation in the pass
<end time> is the UTC time of the last observation in the pass
The time is output in the form yymmdd_hhmmss
Let Measurements.Filename = "\user\ODTK 6\Tracking Data\Scen1.gobs
Then the following would be a possible output file:
<------Basename------> <tracker> <id> <------start time------> <------end time------><ext>
|DataArchive||Various Data Archive options are available.|
Configure the STKEphemeris attribute to output the truth ephemeris for each satellite, written to the Ephemeris directory as<satname>_Truth_<SIM START TIME>.ext
Where ext is one of the following:
Only applies to scenarios containing one or more Constellation objects where Constellation.SVEstimated states include the ephemeris and clock.
The SP3Ephemeris parameter is used to optionally reformat the output ephemeris and clock data into a sp3 (http://igscb.jpl.nasa.gov/components/formats.html) file. One file is generated for each Constellation object for which ephemeris and clocks were estimated.
You can generate the sp3 data over:
Data over the process interval requires that STKEphemeris be generated over the process interval and that clock data be added to the process run file.
Data over the predict interval requires that the STKEphemeris be generated over the predict interval.
The granularity for the STKEphemeris may be different than the SP3 ephemeris.
The output file name is in the form:
<GNSS Name>_<Process Type>_yyymmdd_hhmmss.sp3
<Process_Type> = “Truth”| “Filter| “Smoother”
yyymmdd_hhmmss refers to the start time of the SP3 file in Scenario.Units.DateFormat system.
Example filename is:GPS_Filter_20120601_120000.sp3