Skip to contents

Settings that change how ctsem behaves across a session, rather than per-call. Set them with options(), typically once at the top of a script or in a front end's startup.

Value

Nothing; this page documents options rather than defining a function.

Progress and output

ctsem.progress.overwrite

Whether progress reporting rewrites a single line with a carriage return (TRUE) or prints occasional separate lines (FALSE). Unset, ctsem detects it: an active Shiny session, a sink(), or a knitr chunk all capture output, where a carriage return is a character rather than a cursor movement. Set it explicitly if that detection is wrong for your front end.

ctsem.cluster.outfile

Where parallel workers send their output. Unset, they are silent. Setting it to "" forwards worker stdout and stderr to the console, which is useful only when debugging a worker – it also restores the startup chatter that made a two-core fit announce itself six times.

Per-call alternatives

Progress and reporting are also controlled per fit, and those win over these: verbose in ctFit (0 quiet, 1 reports progress, 2 keeps every line rather than overwriting), optimcontrol$callback for a function called while the fit runs, and optimcontrol$progress to force progress on or off for one fit.

Julia

The Julia backend is mostly located through the environment rather than options: JULIA_BINDIR names the binary directory, JULIA_NUM_THREADS the thread count of the session that starts next, and ctJuliaSetup(project=) points the session at a different engine environment. See ctJuliaSetup.

ctsem.julia.restart

Whether a fit asking for more cores than the running Julia session has threads may restart the session to get them. FALSE by default: Julia fixes its thread count at process start, so the only way to raise it is to end the process, which discards the engine's compiled model shapes and costs seconds. Left FALSE, such a fit runs at the threads it has and says so.