9-10
Understanding the CITIfile Data Format
CITIfile Keywords
CONSTANT CONSTANT [name] [value] allows for the recording of
values which don’t change when the independent variable
changes.
CONSTANTs are part of the main CITIfile definition.
Users must not define their own CONSTANTs. Use the
#KEYWORD device specification to create your own
KEYWORD instead. The #NA device specification is an
example of this. No constants were defined for revision
A.01.00 of CITIfile. CITIfile revision A.01.01 defined the
following constant:
CONSTANTs are part of the main CITIfile definition.
Users must not define their own CONSTANTs. Use the
#KEYWORD device specification to create your own
KEYWORD instead. The #NA device specification is an
example of this. No constants were defined for revision
A.01.00 of CITIfile. CITIfile revision A.01.01 defined the
following constant:
CONSTANT TIME [year] [month] [day] [hour] [min] [secs]
Example:
• The COMMENT statement is not absolutely required, but is highly recommended to aid
readability.
• The year should always be the full four digits (“1999” is correct, but “99” is not). This is
to avoid problems with the year 2000, when the shortened version of the year will be
“00.”
• The hour value should be in 24-hour “military” time.
• When writing a CITIfile and the fractional seconds value is zero, then the “seconds”
value may be printed either with or without a decimal point: either “47.0” or “47” would
be acceptable. When reading a CITIfile, the seconds value should always be read as if it
were a floating point number.
COMMENT YEAR MONTH DAY HOUR MINUTE SECONDS
CONSTANT TIME 1999 02 26 17 33 53.25
To Next Page
Loading...
Need help?
General
