Plotting methods ‘setar’ and ‘lstar’ subclasses

1 2 3 4 | ```
## S3 method for class 'setar'
plot(x, ask=interactive(), legend=FALSE, regSwStart, regSwStop, ...)
## S3 method for class 'lstar'
plot(x, ask=interactive(), legend=FALSE, regSwStart, regSwStop, ...)
``` |

`x` |
fitted ‘setar’ or ‘lstar’ object |

`ask` |
graphical option. See |

`legend` |
Should a legend be plotted? (logical) |

`regSwStart, regSwStop` |
optional starting and stopping time indices for regime switching plot |

`...` |
further arguments to be passed to and from other methods |

These plot methods produce a plot which gives to you an idea of the behaviour of the fitted model.

Firstly, if embedding dimension is, say, `m`, `m` scatterplots are
produced. On the x axis you have the lagged time series values. On the y
axis the ‘response’ time series values. Observed points are
represented with different colors-symbols depending on the level of the
threshold variable. Specifically, for the setar model, black means
‘low regime’, red means ‘high regime’. For the lstar
model, where the self-threshold variable is continuous, threshold values
are grouped in 5 different zones with the same number of points in
each. Note that if more than 300 points are to be plotted, they all
share the same symbol, and regimes can be distinguished only by
color. If you want, by specifying `legend=TRUE`

a legend is added
at the upper-left corner of each scatterplot. To each scatterplot, a
dashed line is superposed,
which links subsequent fitted values.

Finally, a new time series plot is produced, with lines segments coloured depending on the regime (colors meanings are the same of those in the preceding scatterplots). Optionally, you can specify a starting and ending time indices, for zooming on a particular segment of the time series.

Antonio, Fabio Di Narzo

`setar`

, `lstar`

nlar-methods for other generic available methods for this kind of objects.

1 2 3 | ```
##
##See 'setar' examples
##
``` |

Questions? Problems? Suggestions? Tweet to @rdrrHQ or email at ian@mutexlabs.com.

All documentation is copyright its authors; we didn't write any of that.