Category: Software
Product Number: LTspice
Software Version: (Windows 10, (X64) LTspice version 26.1.1 and previous versions.
.PARAM N1 = 2
.PARAM N2 = 2
.PARAM Rb TABLE(N1, 1, 866K, 2, 365K)
.PARAM Rd TABLE(N2, 1, 3160, 2, 4020, 3, 3010)
.MEAS Rl PARAM Rb
.MEAS Rc PARAM Rd
Results in the R's (L's and C's not shown) being printed in dB units (real dB, 0degree imaginary), while all voltage and current magnitudes are printed correctly in dB units.
Using .OPTIONS MEASCPLXFMT=CARTESIAN corrects the R, L, and C values to being in the correct units, but then the voltage and current magnitudes are in Cartesian coordinates (real, imaginary). As a result, the user cannot see all the selected values in the correct units in the log file at any one time. Shouldn't all the passive component values always printed in "Cartesian" form rather than in dB form?
