Data Map and User Correction

User correction is a function to correct the power value using correction data set for the following measurement results.

 

Measurement Class

Measurement Value to be Corrected

Phase noise

Carrier signal level

Transient

Power measurement value (array)

VCO Characterization

Power measurement value (array)

 

Correction method

 

Power data correction is performed as follows. (The correction value is Corr shown below.)

Data after correction (dBm) = data before correction (dBm) + Corr (dB)

In this case, a correction coefficient after linear interpolation (Corr') is used for calculation.

Data after correction (Watt) = data before correction (Watt) x correction value (Corr')

Corr' = 10 ^ (Corr / 10)

 

The correction is applied to the raw measurement data (access point 0) which is before formatting.

 

Raw Measurement Data Standard Acquisition Data Calibration Error Terms Memory Error Correction Trace Math Filter Gating Display Formatting Data Smoothing Display

 

Format of correction data file

Correction data files must be written in CSV format.

Writing Correction Data File

Write a frequency value and a correction value for the frequency with a comma (,) separator. Deal them as a pair, and write pairs for all correction points with comma separators.

Line break characters are recognized as data separators in the same way as commas. Therefore, two formats as shown below are available: writing pairs in a single line, or writing a pair of a frequency value and a correction value in each line.

Write frequencies in Hz, and correction values in dB.

[Example of Data Written in Single Line]

10E+6,0.04,100E+6,0.06,200E+6,0.07,300E+6,0.06

[Example of Data Written in Multiple Lines]

10E+6,0.04
100E+6,0.06
200E+6,0.07
300E+6,0.06

Restrictions on Writing

There are some restrictions on writing correction data files. They are:

1.   The maximum number of data items is 1001. Data after that is ignored when loaded.

2.   Lines that start with a pound sign (#) are skipped as comment lines. Data in those lines is not recognized.

3.   The frequency in Data must be ordered sequentially. If there is a frequency is equal to or smaller than the previous one, the read operation ends immediately. This does not cause any error, and the correction data immediately before the end of the read operation is reflected.