Skip to contents

The changes ctModelImprove would consider for a fit: the relaxations its score tests indicate and, given an adequacy check, the structural changes the check's families point to – a process of an item's own or shared by two, a slow process, a cycle, a second order. Rows can be handed to ctModelImprove(changes = ), which refits with them and judges each by the search's criterion: a search made a step at a time, by hand.

Usage

ctModelProposals(
  fit,
  score = NULL,
  adequacy = NULL,
  covariates = NULL,
  relax = c("heterogeneity", "covariates", "statedependence", "volatility", "fixed",
    "level", "slow", "unique", "periodic", "order"),
  alpha = 0.05,
  cores = getOption("mc.cores", 2L)
)

Arguments

fit

A fit from ctFit with backend = 'julia'.

score

A ctScoreTest of fit. Run when neither it nor adequacy is given.

adequacy

Optionally a ctFitAdequacy of fit, for the structural changes.

covariates, relax, alpha, cores

As for ctModelImprove.

Value

A data frame of class ctModelProposals, one row per change, strongest first within the relaxations and within the structural changes: change (as a search's history names it), family, p (the evidence ranked by), class, and proposal, what ctModelImprove() needs to make the change.

Details

Unlike a search's rounds, every indicated change is listed, including relaxations the tests cannot tell apart (one class), of which a round refits only the strongest; and the structural changes are listed beside the relaxations, where a round turns to them only once the screen is clean.