Specifications

8-6
Understanding the CITIfile Data Format
The CITIfile Data Format
Example 3, 8510 Data file
Example 3 shows a CITIfile package created from the data register of an 8510 Network
Analyzer. In this case 10 points of real and imaginary data was stored, and frequency
information was recorded in a segment list table.
Example:
CITIFILE A.01.00
#NA VERSION HP8510B.05.00
NAME DATA
#NA REGISTER 1
VAR FREQ MAG 10
DATA S[1,1] RI
SEG_LIST_BEGIN
SEG 1000000000 4000000000 10
SEG_LIST_END
BEGIN
0.86303E-1,-8.98651E-1
8.97491E-1,3.06915E-1
-4.96887E-1,7.87323E-1
-5.65338E-1,-7.05291E-1
8.94287E-1,-4.25537E-1
1.77551E-1,8.96606E-1
-9.35028E-1,-1.10504E-1
3.69079E-1,-9.13787E-1
7.80120E-1,5.37841E-1
-7.78350E-1,5.72082E-1
END
Example 4, 8510 3-Term Frequency List Cal Set File
Example 4 shows how CITIfile may be used to store instrument setup information. In the
case of an 8510 Cal Set, a limited instrument state is needed in order to return the
instrument to the same state that it was in when the calibration was done. Three arrays of
error correction data are defined by using three DATA statements. Some instruments
require these arrays to be in the proper order, from E1 to E3. In general, CITIfile
implementations should strive to handle data arrays that are arranged in any order.
Example:
CITIFILE A.01.00
#NA VERSION HP8510B.05.00
NAME CAL_SET
#NA REGISTER 1
VAR FREQ MAG 4
DATA E[1] RI
DATA E[2] RI
DATA E[3] RI
#NA SWEEP_TIME 9.999987E-2
#NA POWER1 1.0E1
#NA POWER2 1.0E1