Module sequence 

Wire-format AnalysisSequence — mirrors the PySees AnalysisStage discriminated union: Static (pushover-style), Modal (eigenvalue), and Transient (Newmark time-history, optionally driven by GroundMotionSpec).

Structs

ArcLengthSpec

Wire form of core::ArcLength. Omitted minRadius/maxRadius default to initialRadius (a fixed-radius run).

ArcSeedComponentSpec

One component of a seed direction: node/dof index into NodeTable.

ArcSeedSpec

ArcStopSpec

Optional criteria that end an arc-length stage before its step cap.

BacktrackingSpec

DampingSpec

Rayleigh damping (C = alpha_m*M + beta_k*K) — see core::RayleighDamping’s doc comment. Use alpha_m: 0.0, beta_k: 0.0 for undamped (core::RayleighDamping::NONE).

DisplacementTargetSpec

GroundMotionSpec

One core::GroundMotion: a uniform acceleration time history applied along one global translational axis (direction: 0=x, 1=y, and for the spatial profile 2=z — never a rotational DOF). series is typically TimeSeriesSpec::Path (the accelerogram itself), reusing the same wire type a static LoadPatternTable entry uses — an accelerogram is exactly a piecewise-linear series, no separate representation needed (core::GroundMotion’s own doc comment).

LoadFactorTargetSpec

ModalDampingAnchors

SequenceSpec

Enums

AlgorithmSpec

ArcDirectionSpec

ArcPredictorSpec

ArcScalesSpec

The continuation metric’s scales (core::ArcScales): explicit characteristic translation/rotation/load-factor sizes, or auto (translation/rotation scales derived from the first elastic tangent).

ConvergenceSpec

FiberResponseKind

One recorder: a single scalar channel’s history against its stage’s load factor. NodeDisp was the first variant (node displacement/load-factor history for a static pushover); ElementForce (results-storage-indexeddb.md’s “several more types of recorders” plan) is the second, sharing the exact same batching/storage machinery — see session::ResolvedRecorder and StepOutcome::recorder_batches, neither of which needed to change shape to add it. ElementForce’s element_kind/element_index pair mirrors ElementLoadTable’s existing disambiguation between per-kind element tables (ElasticBeamColumn2dTable, FiberBeamColumn3dTable, …) — there is no single flat element table to index into directly, unlike NodeTable. Adding a future response kind (velocity, acceleration, …) is one more variant here plus one more match arm in ModelSession::record_sample, not a new parallel type or a new Session/StepOutcome field. Which half of a fiber’s (strain, stress) pair (core::FiberSection:: fiber_responses’s doc comment) a RecorderSpec::Fiber reads — one scalar channel per recorder, same as every other kind here.

GaussQuantity

Whether a RecorderSpec::GaussPoint reads strain or stress.

IntegratorSpec

LineSearchSpec

RecorderSpec

StageSpec

TangentStrategySpec