Keywords | File Formats
Interval File Format (*.int) for Custom Simulation Schedules
An interval file is an ASCII text file that contains a series of time intervals (start and stop times) that can be read into STK and Orbit Determination Tool Kit. Each interval can define an optional string of data that contains the truncated path of an object.
Keywords
Some of the keywords in an interval file are optional and some allow specification of the time format.
| Keyword |
Required |
Description |
| stk.v.4.3 |
Yes |
Must be the first line in the file. This is the earliest version of STK for which the file is formatted. Later versions of STK can read files for earlier versions, but not vice versa. |
BEGIN IntervalList
END IntervalList |
Yes |
These enclose the data in the file to be processed. |
| ScenarioEpoch |
See Note |
If you wish to enter interval start and stop times in seconds, then you must specify the "ScenarioEpoch"
ScenarioEpoch is used to convert the numerical seconds to a date/time. Note that this epoch really has nothing to do with a scenario.
Example:
ScenarioEpoch 1 Jul 2000 00:00:00.000000000
(Sample interval: 3600.0 7600.0)
|
| DATEUNITABRV |
See Note |
If you are entering start and stop times as date/time strings, then you must specify the format of the strings.
Example:
DATEUNITABRV UTCG
(Sample interval: "1 Jul 2003 00:00:00" "1 Jul 2003 04:00:00")
Example: DATEUNITABRV DD/MM/YYYY
(Sample interval: "05/07/2012 20:20:20" "05/07/2012 21:21:21")
DATEUNITABRV can be any valid format: YYDDD, YYYYDDD, JDate, etc., as long as the interval strings are in that format. |
BEGIN Intervals
END Intervals |
No |
Used to group interval data. |
File Format
Each line of data is an interval specification that contains a start time, a stop time and an optional data string. Whether or not the string is used depends on how the application is using the file. If the start and stop times are not numerical, they must be enclosed in quotes. Numerical start and stop times may be quoted or not. Follow the links below to samples of interval files:
Sat1.int: with the optional data string but not using the BEGIN/END Intervals keywords.
Sat2.int: with the optional data string and using the BEGIN/END Intervals keywords.
Sat2_noData.int: without the optional data string and not using the BEGIN/END Intervals keywords.