EpochGapScenario

Robotics scenarios · Implementation: mlsysim/engine/scenario_definitions/robotics/estimation.py.

Construct this scenario with keyword inputs. The fields below show the types and defaults declared by this class.

Named acquisition epochs in one cycle; the pair to fuse is projected across its gap at speed.

Notes

Equation: result evaluates the configured solver; its contract owns the governing equations.

Assumptions: Sensor epochs use a common clock and displacement across their gap is speed times elapsed time.

Excludes: Clock-conversion error, acceleration, and fusion uncertainty.

References

Derivation: The scenario binds declared inputs to EpochGapModel. Those implementations document their derivations and sources.

Examples

Execute the registered worked inputs; this is a modeled calculation.

>>> from mlsysim import Scenarios
>>> case = Scenarios.ArmSensorEpochGap
>>> value = case.result
>>> print(f"{value.travel:.3f~P}")
4.250 mm

Attributes

Name	Description
epochs
pair
result	Evaluate the configured inputs with mlsysim.solvers.EpochGapModel.solve.
speed

epochs

Type: Dict[str, Quantity].

Declared default: required.

pair

Type: List[str].

Declared default: required.

speed

Type: Quantity.

Declared default: required.

result

engine.scenario_types.EpochGapScenario.result

Evaluate the configured inputs with mlsysim.solvers.EpochGapModel.solve.

The returned typed result retains the solver’s documented units, assumptions, and feasibility semantics; this property adds no measurement or safety claim. Equation: result = EpochGapModel().solve(...) using the fields shown below.