Waveform Files (Y Values) (.txt)
Y-value waveform files are ASCII files (.txt) comprised of a header followed by amplitude values for each data point. The ASCII amplitude values are in Volts or Watts and are separated by a carriage return and line feed. This format is convenient for transferring data to other software applications, as you can import this file into many spreadsheet or word processing programs.
Although the file does not include time values for each data point, proper X-axis scaling is achieved by XOrg (X-axis origin) and XInc (X-axis time increment) values contained in the metadata. Because individual time values are not included, this format creates smaller files than the XY-Values format.
Y-value format is designed for waveforms in which the data points are separated by equal time increments. Do not use Y-value format if any the following conditions are true. Use the XY-value format instead:
- The waveform is the output of the versus operator in a function.
Y-value format files use more disk space than HDF5 format files (.h5).
Options for saving Y-Value Waveforms (.txt format)
You can choose to save All Data or just the On-Screen Data.
Select Linearly Interpolate to enforce equal spacing of waveform data points. In cases where data is missing for sample locations, linear interpolation is used to fill-in the missing data values.
Example Y-Value Format File
File Format, WaveformYValues
Format Version, 2
Instrument, D9300A
SwVersion, P.23.02.51
SerialNumber, LAB-MYST-LP2-41
Date, 9/26/2023 10:07:06 GMT-06:00
Source Name, Channel 1
DataDigest,
Points, 102401
Signal Type, Unspecified
Acquisition Type, RealTime
Channel Bandwidth, 1.5E+10
Channel Noise, 0.002
XOrg, -5.0000000000000004E-08
XInc, 9.765625E-13
Symbol Rate (Baud), 2970000000
X Units, Second
Y Units, Volt
Data,
float
-0.2508791
-0.25027373
-0.24949397
.
.
.
Y-value format definition version 2 explicitly describes the precision of the Y data values (for example, 32-bit "float" in the previous example). In version 1, the Y value precision is assumed to be a 64-bit "double" (although values could have been saved with limited significant digits).