Skip to contents

Each manifest variable in items gains a latent, named u_ and the variable's name, that loads on it alone with a fixed unit loading and has its own persistence and innovations. The variable then carries, beside what it shares through the model's other latents and its measurement error, a part that is specific to it and carried over time: an item whose wording picks up something besides the construct, and picks it up persistently.

Usage

ctModelUniqueProcess(ctm, items, shared = FALSE, name = NULL)

Arguments

ctm

A model from ctModel(type = 'ct').

items

Which manifest variables, by name or position.

shared

One process for all of items, named u_ and their names joined by _, rather than one each.

name

The new latents' names, in place of those: one for a shared process, one per item otherwise. For a second process on the same items, at another time scale.

Value

The extended model.

Details

Without it, that part can only go to the measurement error, which is independent over time, so the item's prediction errors stay correlated with its own at nearby times – what the residuals family of ctFitAdequacy shows for that item alone – or to the shared latents, whose dynamics it then distorts. The specific process and the measurement error are told apart by persistence: the one carries over time, the other does not.

The process has no intercept (the item's own carries its level), ctsem's default drift transform, so it is mean reverting, and innovations independent of every other latent's. It starts from its stationary distribution: mean zero and the variance its persistence and innovations imply (the T0VAR diagonal 'stationary', see ctFit).

With shared = TRUE the items share one process instead, loading on the first at one and on the others freely: what moves them together beyond the model's other latents. Measurement errors that are correlated within an occasion are usually better read this way – an error is meant to be random, and co-movement it does not carry over to the next occasion is a process faster than the occasions – unless the design gives a reason for correlated error, such as a method shared by the items.

See also

ctModelImprove, which adds one for the items the adequacy check points to.

Examples

m <- ctModel(type = 'ct', manifestNames = c('Y1', 'Y2', 'Y3'),
  latentNames = 'eta', LAMBDA = matrix(c(1, 'l2', 'l3'), 3))
m2 <- ctModelUniqueProcess(m, 'Y2')
m2$latentNames
p <- m2$pars
p[p$col %in% 2 & p$matrix %in% c('LAMBDA', 'DRIFT', 'DIFFUSION'),
  c('matrix', 'row', 'col', 'param', 'value')]
ctModelUniqueProcess(m, c('Y2', 'Y3'), shared = TRUE)$latentNames