This example shows how to estimate models using frequency domain data. The estimation and validation of models using frequency domain data work the same way as they do with time domain data. This provides a great amount of flexibility in estimation and analysis of models using time and frequency domain as well as spectral (FRF) data. You may simultaneously estimate models using data in both domains, compare and combine these models. A model estimated using time domain data may be validated using spectral data or vice-versa.

Frequency domain data can not be used for estimation or validation of nonlinear models.

Frequency domain experimental data are common in many applications. It could be that the data was collected as frequency response data (frequency functions: FRF) from the process using a frequency analyzer. It could also be that it is more practical to work with the input's and output's Fourier transforms (FFT of time-domain data), for example to handle periodic or band-limited data. (A band-limited continuous time signal has no frequency components above the Nyquist frequency). In System Identification Toolbox, frequency domain I/O data are represented the same way as time-domain data, i.e., using `iddata`

objects. The 'Domain' property of the object must be set to 'Frequency'. Frequency response data are represented as complex vectors or as magnitude/phase vectors as a function of frequency. IDFRD objects in the toolbox are used to encapsulate FRFs, where a user specifies the complex response data and a frequency vector. Such IDDATA or IDFRD objects (and also FRD objects of Control System Toolbox) may be used seamlessly with any estimation routine (such as `procest`

, `tfest`

etc).

Let us begin by loading some frequency domain data:

```
load demofr
```

This MAT-file contains frequency response data at frequencies `W`

, with the amplitude response `AMP`

and the phase response `PHA`

. Let us first have a look at the data:

subplot(211), loglog(W,AMP),title('Amplitude Response') subplot(212), semilogx(W,PHA),title('Phase Response')

This experimental data will now be stored as an IDFRD object. First transform amplitude and phase to a complex valued response:

zfr = AMP.*exp(1i*PHA*pi/180); Ts = 0.1; gfr = idfrd(zfr,W,Ts);

`Ts`

is the sample time of the underlying data. If the data corresponds to continuous time, for example since the input has been band-limited, use Ts = 0.

Note: If you have the Control System Toolbox™, you could use an FRD object instead of the IDFRD object. IDFRD has options for more information, like disturbance spectra and uncertainty measures which are not available in FRD objects.

The IDFRD object `gfr`

now contains the data, and it can be plotted and analyzed in different ways. To view the data, we may use `plot`

or `bode`

:

```
clf
bode(gfr), legend('gfr')
```

To estimate models, you can now use `gfr`

as a data set with all the commands of the toolbox in a transparent fashion. The only restriction is that noise models cannot be built. This means that for polynomial models only OE (output-error models) apply, and for state-space models, you have to fix `K = 0`

.

m1 = oe(gfr,[2 2 1]) % Discrete-time Output error (transfer function) model ms = ssest(gfr) % Continuous-time state-space model with default choice of order mproc = procest(gfr,'P2UDZ') % 2nd-order, continuous-time model with underdamped poles compare(gfr,m1,ms,mproc) L = findobj(gcf,'type','legend'); L.Location = 'southwest'; % move legend to non-overlapping location

m1 = Discrete-time OE model: y(t) = [B(z)/F(z)]u(t) + e(t) B(z) = 0.9986 z^-1 + 0.4968 z^-2 F(z) = 1 - 1.499 z^-1 + 0.6998 z^-2 Sample time: 0.1 seconds Parameterization: Polynomial orders: nb=2 nf=2 nk=1 Number of free coefficients: 4 Use "polydata", "getpvec", "getcov" for parameters and their uncertainties. Status: Estimated using OE on frequency response data "gfr". Fit to estimation data: 88.55% FPE: 0.2492, MSE: 0.2482 ms = Continuous-time identified state-space model: dx/dt = A x(t) + B u(t) + K e(t) y(t) = C x(t) + D u(t) + e(t) A = x1 x2 x1 -0.9009 6.635 x2 -3.307 -2.668 B = u1 x1 -32.9 x2 -28.33 C = x1 x2 y1 -0.5073 0.499 D = u1 y1 0 K = y1 x1 0 x2 0 Parameterization: FREE form (all coefficients in A, B, C free). Feedthrough: none Disturbance component: none Number of free coefficients: 8 Use "idssdata", "getpvec", "getcov" for parameters and their uncertainties. Status: Estimated using SSEST on frequency response data "gfr". Fit to estimation data: 88.55% FPE: 0.2492, MSE: 0.2482 mproc = Process model with transfer function: 1+Tz*s G(s) = Kp * ---------------------- * exp(-Td*s) 1+2*Zeta*Tw*s+(Tw*s)^2 Kp = 7.4619 Tw = 0.20245 Zeta = 0.36242 Td = 0 Tz = 0.013617 Parameterization: 'P2DUZ' Number of free coefficients: 5 Use "getpvec", "getcov" for parameters and their uncertainties. Status: Estimated using PROCEST on frequency response data "gfr". Fit to estimation data: 88.55% FPE: 0.2495, MSE: 0.2482

As shown above a variety of linear model types may be estimated in both continuous and discrete time domains, using spectral data. These models may be validated using, time-domain data. The time-domain I/O data set `ztime`

, for example, is collected from the same system, and can be used for validation of `m1`

, `ms`

and `mproc`

:

```
compare(ztime,m1,ms,mproc) %validation in a different domain
```

We may also look at the residuals to affirm the quality of the model using the validation data `ztime`

. As observed, the residuals are almost white:

```
resid(ztime,mproc) % Residuals plot
```

An important reason to work with frequency response data is that it is easy to condense the information with little loss. The command SPAFDR allows you to compute smoothed response data over limited frequencies, for example with logarithmic spacing. Here is an example where the `gfr`

data is condensed to 100 logarithmically spaced frequency values. With a similar technique, also the original time domain data can be condensed:

sgfr = spafdr(gfr) % spectral estimation with frequency-dependent resolution sz = spafdr(ztime); % spectral estimation using time-domain data clf bode(gfr,sgfr,sz) axis([pi/100 10*pi, -272 105]) legend('gfr (raw data)','sgfr','sz','location','southwest')

sgfr = IDFRD model. Contains Frequency Response Data for 1 output(s) and 1 input(s), and the spectra for disturbances at the outputs. Response data and disturbance spectra are available at 100 frequency points, ranging from 0.03142 rad/s to 31.42 rad/s. Sample time: 0.1 seconds Output channels: 'y1' Input channels: 'u1' Status: Estimated using SPAFDR on frequency response data "gfr".

The Bode plots show that the information in the smoothed data has been taken well care of. Now, these data records with 100 points can very well be used for model estimation. For example:

```
msm = oe(sgfr,[2 2 1]);
compare(ztime,msm,m1) % msm has the same accuracy as M1 (based on 1000 points)
```

It may be that the measurements are available as Fourier transforms of inputs and output. Such frequency domain data from the system are given as the signals Y and U. In loglog plots they look like

Wfd = (0:500)'*10*pi/500; subplot(211),loglog(Wfd,abs(Y)),title('The amplitude of the output') subplot(212),loglog(Wfd,abs(U)),title('The amplitude of the input')

The frequency response data is essentially the ratio between `Y`

and `U`

. To collect the frequency domain data as an IDDATA object, do as follows:

ZFD = iddata(Y,U,'ts',0.1,'Domain','Frequency','Freq',Wfd)

ZFD = Frequency domain data set with responses at 501 frequencies, ranging from 0 to 31.416 rad/seconds Sample time: 0.1 seconds Outputs Unit (if specified) y1 Inputs Unit (if specified) u1

Now, again the frequency domain data set `ZFD`

can be used as data in all estimation routines, just as time domain data and frequency response data:

mf = ssest(ZFD) % SSEST picks best order in 1:10 range when called this way mfr = ssregest(ZFD) % an alternative regularized reduction based state-space estimator clf compare(ztime,mf,mfr,m1)

mf = Continuous-time identified state-space model: dx/dt = A x(t) + B u(t) + K e(t) y(t) = C x(t) + D u(t) + e(t) A = x1 x2 x1 -1.501 6.791 x2 -3.115 -2.059 B = u1 x1 -28.11 x2 -33.39 C = x1 x2 y1 -0.5844 0.4129 D = u1 y1 0 K = y1 x1 0 x2 0 Parameterization: FREE form (all coefficients in A, B, C free). Feedthrough: none Disturbance component: none Number of free coefficients: 8 Use "idssdata", "getpvec", "getcov" for parameters and their uncertainties. Status: Estimated using SSEST on frequency domain data "ZFD". Fit to estimation data: 97.21% FPE: 0.0423, MSE: 0.04179 mfr = Discrete-time identified state-space model: x(t+Ts) = A x(t) + B u(t) + K e(t) y(t) = C x(t) + D u(t) + e(t) A = x1 x2 x3 x4 x5 x6 x1 0.7613 -0.3831 0.321 0.07434 0.02412 -0.09706 x2 0.2344 -0.3703 -0.3424 0.2434 0.1759 0.3081 x3 -0.2537 -0.3356 0.6258 0.187 0.03533 -0.2034 x4 0.01546 -0.1524 0.002201 -0.1254 0.3533 -0.3331 x5 0.03737 -0.009442 -0.2139 0.4935 -0.3062 0.08732 x6 -0.01654 0.4029 0.2052 0.2842 0.04186 0.1247 x7 0.02909 -0.2977 -0.03749 -0.2714 -0.334 0.5494 x8 -0.01963 0.06478 0.08439 -0.1188 0.436 -0.002226 x9 0.003241 -0.1324 -0.1104 0.03777 -0.11 -0.4325 x10 -0.01584 0.04655 -0.02159 0.1068 -0.02053 -0.237 x7 x8 x9 x10 x1 0.1403 -0.006208 -0.05144 0.1339 x2 -0.3417 0.002803 0.2707 -0.1197 x3 0.2048 -0.1172 0.05818 -0.08935 x4 -0.1197 0.1596 0.1085 -0.24 x5 0.6575 0.2477 -0.06297 -0.02847 x6 -0.206 -0.4284 0.5788 -0.1484 x7 -0.2762 -0.7054 0.1077 -0.3599 x8 0.5337 -0.2678 -0.01389 0.09196 x9 -0.1807 -0.3665 -0.1045 0.5082 x10 -0.03758 -0.6059 -0.4597 -0.5852 B = u1 x1 1.587 x2 0.1269 x3 0.1005 x4 0.005173 x5 -0.0188 x6 -0.03685 x7 -0.002292 x8 0.04005 x9 -0.06693 x10 0.005684 C = x1 x2 x3 x4 x5 x6 x7 y1 0.7632 0.5577 -2.661 -1.165 -0.5682 -1.529 1.043 x8 x9 x10 y1 -0.07261 0.964 -0.3095 D = u1 y1 0 K = y1 x1 -0.03023 x2 0.0185 x3 -0.08796 x4 0.04731 x5 0.03953 x6 0.0164 x7 -0.009579 x8 0.0002737 x9 0.002402 x10 0.001213 Sample time: 0.1 seconds Parameterization: FREE form (all coefficients in A, B, C free). Feedthrough: none Disturbance component: estimate Number of free coefficients: 130 Use "idssdata", "getpvec", "getcov" for parameters and their uncertainties. Status: Estimated using SSREGEST on frequency domain data "ZFD". Fit to estimation data: 65.67% (prediction focus) FPE: 6.867, MSE: 6.339

Time and frequency domain input-output data sets can be transformed to either domain by using FFT and IFFT. These commands are adapted to IDDATA objects:

dataf = fft(ztime) datat = ifft(dataf)

dataf = Frequency domain data set with responses at 501 frequencies, ranging from 0 to 31.416 rad/seconds Sample time: 0.1 seconds Outputs Unit (if specified) y1 Inputs Unit (if specified) u1 datat = Time domain data set with 1000 samples. Sample time: 0.1 seconds Outputs Unit (if specified) y1 Inputs Unit (if specified) u1

Time and frequency domain input-output data can be transformed to frequency response data by SPAFDR, SPA and ETFE:

g1 = spafdr(ztime) g2 = spafdr(ZFD); clf; bode(g1,g2)

g1 = IDFRD model. Contains Frequency Response Data for 1 output(s) and 1 input(s), and the spectra for disturbances at the outputs. Response data and disturbance spectra are available at 100 frequency points, ranging from 0.06283 rad/s to 31.42 rad/s. Sample time: 0.1 seconds Output channels: 'y1' Input channels: 'u1' Status: Estimated using SPAFDR on time domain data "ztime".

Frequency response data can also be transformed to more smoothed data (less resolution and less data) by SPAFDR and SPA;

g3 = spafdr(gfr);

Frequency response data can be transformed to frequency domain input-output signals by the command IDDATA:

gfd = iddata(g3)

gfd = Frequency domain data set with responses at 100 frequencies, ranging from 0.031416 to 31.416 rad/seconds Sample time: 0.1 seconds Outputs Unit (if specified) y1 Inputs Unit (if specified) u1

Time domain data can naturally only be stored and dealt with as discrete-time, sampled data. Frequency domain data have the advantage that continuous time data can be represented correctly. Suppose that the underlying continuous time signals have no frequency information above the Nyquist frequency, e.g. because they are sampled fast, or the input has no frequency component above the Nyquist frequency. Then the Discrete Fourier transforms (DFT) of the data also are the Fourier transforms of the continuous time signals, at the chosen frequencies. They can therefore be used to directly fit continuous time models. In fact, this is the correct way of using band-limited data for model fit.

This will be illustrated by the following example.

Consider the continuous time system:

```
m0 = idpoly(1,1,1,1,[1 1 1],'ts',0)
```

m0 = Continuous-time OE model: y(t) = [B(s)/F(s)]u(t) + e(t) B(s) = 1 F(s) = s^2 + s + 1 Parameterization: Polynomial orders: nb=1 nf=2 nk=0 Number of free coefficients: 3 Use "polydata", "getpvec", "getcov" for parameters and their uncertainties. Status: Created by direct construction or transformation. Not estimated.

Choose an input with low frequency contents that is fast sampled:

rng(235,'twister'); u = idinput(500,'sine',[0 0.2]); u = iddata([],u,0.1,'intersamp','bl');

0.1 is the sample time, and `'bl'`

indicates that the input is band-limited, i.e. in continuous time it consists of sinusoids with frequencies below half the sampling frequency. Correct simulation of such a system should be done in the frequency domain:

uf = fft(u); uf.ts = 0; % Denoting that the data is continuous time yf = sim(m0,uf); % % Add some noise to the data: yf.y = yf.y + 0.05*(randn(size(yf.y))+1i*randn(size(yf.y))); dataf = [yf uf] % This is now a continuous time frequency domain data set.

dataf = Frequency domain data set with responses at 251 frequencies, ranging from 0 to 31.416 rad/seconds Sample time: 0 seconds Outputs Unit (if specified) y1 Inputs Unit (if specified) u1

Look at the data:

plot(dataf) axis([0 10 0 2.5])

Using `dataf`

for estimation will by default give continuous time models: State-space:

```
m4 = ssest(dataf,2); %Second order continuous-time model
```

For a polynomial model with `nb = 2`

numerator coefficient and `nf = 2`

estimated denominator coefficients use:

nb = 2; nf = 2; m5 = oe(dataf,[nb nf])

m5 = Continuous-time OE model: y(t) = [B(s)/F(s)]u(t) + e(t) B(s) = -0.01826 s + 1.008 F(s) = s^2 + 1.001 s + 0.9967 Parameterization: Polynomial orders: nb=2 nf=2 nk=0 Number of free coefficients: 4 Use "polydata", "getpvec", "getcov" for parameters and their uncertainties. Status: Estimated using OE on frequency domain data "dataf". Fit to estimation data: 70.08% FPE: 0.004842, MSE: 0.004728

Compare step responses with uncertainty of the true system `m0`

and the models `m4`

and `m5`

. The confidence intervals are shown with patches in the plot.

clf h = stepplot(m0,m4,m5); showConfidence(h,1) legend('show','location','southeast')

Although it was not necessary in this case, it is generally advised to focus the fit to a limited frequency band (low pass filter the data) when estimating using continuous time data. The system has a bandwidth of about 3 rad/s, and was excited by sinusoids up to 6.2 rad/s. A reasonable frequency range to focus the fit to is then [0 7] rad/s:

m6 = ssest(dataf,2,ssestOptions('Focus',[0 7])) % state space model

m6 = Continuous-time identified state-space model: dx/dt = A x(t) + B u(t) + K e(t) y(t) = C x(t) + D u(t) + e(t) A = x1 x2 x1 -0.2714 -1.809 x2 0.4407 -0.7282 B = u1 x1 0.5873 x2 -0.3025 C = x1 x2 y1 0.7565 1.526 D = u1 y1 0 K = y1 x1 0 x2 0 Parameterization: FREE form (all coefficients in A, B, C free). Feedthrough: none Disturbance component: none Number of free coefficients: 8 Use "idssdata", "getpvec", "getcov" for parameters and their uncertainties. Status: Estimated using SSEST on frequency domain data "dataf". Fit to estimation data: 87.08% (filter focus) FPE: 0.004804, MSE: 0.003682

m7 = oe(dataf,[1 2],oeOptions('Focus',[0 7])) % polynomial model of Output Error structure

m7 = Continuous-time OE model: y(t) = [B(s)/F(s)]u(t) + e(t) B(s) = 0.9866 F(s) = s^2 + 0.9791 s + 0.9761 Parameterization: Polynomial orders: nb=1 nf=2 nk=0 Number of free coefficients: 3 Use "polydata", "getpvec", "getcov" for parameters and their uncertainties. Status: Estimated using OE on frequency domain data "dataf". Fit to estimation data: 87.05% (filter focus) FPE: 0.004829, MSE: 0.0037

opt = procestOptions('SearchMethod','lsqnonlin','Focus',[0 7]); % Requires Optimization Toolbox(TM) m8 = procest(dataf,'P2UZ',opt) % process model with underdamped poles

m8 = Process model with transfer function: 1+Tz*s G(s) = Kp * ---------------------- 1+2*Zeta*Tw*s+(Tw*s)^2 Kp = 1.0124 Tw = 1.0019 Zeta = 0.5021 Tz = -0.017474 Parameterization: 'P2UZ' Number of free coefficients: 4 Use "getpvec", "getcov" for parameters and their uncertainties. Status: Estimated using PROCEST on frequency domain data "dataf". Fit to estimation data: 87.08% (filter focus) FPE: 0.004804, MSE: 0.003682

opt = tfestOptions('SearchMethod','lsqnonlin','Focus',[0 7]); % Requires Optimization Toolbox m9 = tfest(dataf,2,opt) % transfer function with 2 poles

m9 = From input "u1" to output "y1": -0.01647 s + 1.003 ----------------------- s^2 + 0.9949 s + 0.9922 Continuous-time identified transfer function. Parameterization: Number of poles: 2 Number of zeros: 1 Number of free coefficients: 4 Use "tfdata", "getpvec", "getcov" for parameters and their uncertainties. Status: Estimated using TFEST on frequency domain data "dataf". Fit to estimation data: 87.09% (filter focus) FPE: 0.004843, MSE: 0.00368

```
h = stepplot(m0,m6,m7,m8,m9);
showConfidence(h,1)
legend('show')
```

We saw how time, frequency and spectral data can seamlessly be used to estimate a variety of linear models in both continuous and discrete time domains. The models may be validated and compared in domains different from the ones they were estimated in. The data formats (time, frequency and spectrum) are interconvertible, using methods such as `fft`

, `ifft`

, `spafdr`

and `spa`

. Furthermore, direct, continuous-time estimation is achievable by using `tfest`

, `ssest`

and `procest`

estimation routines. The seamless use of data in any domain for estimation and analysis is an important feature of System Identification Toolbox.

For more information on identification of dynamic systems with System Identification Toolbox visit the System Identification Toolbox product information page.

Was this topic helpful?