Skip to content

feat: add manifest-driven simulator configuration workflow - #14

Open
matthewrossi wants to merge 6 commits into
fix-simulator-issuesfrom
model-config-manifest
Open

feat: add manifest-driven simulator configuration workflow#14
matthewrossi wants to merge 6 commits into
fix-simulator-issuesfrom
model-config-manifest

Conversation

@matthewrossi

Copy link
Copy Markdown
Collaborator

Adds river-manifest, a CLI that discovers supported Simulink C++ model data from ELF/DWARF metadata, generates editable YAML manifests, and compiles refined manifests into the simulator’s existing JSON configuration format.

  Add river-manifest to discover Simulink models from ELF/DWARF metadata,
  generate editable YAML hook manifests, and compile refined manifests into
  the simulator’s existing JSON configuration format.

  Validate symbols, instruction offsets, build IDs, data addresses, signal
  limits, and model selections; infer post-output hooks and solver cadence.
  Document the workflow and add a make target for manifest generation.
  List each model function once and select its probe phase in active hooks.
  Resolve entry, return, and post-output phases during compilation, while
  allowing validated custom instruction offsets for manual probe points.
  Only expose scalar float64 values as supported manifest data and retain
  unsupported entries with an explanatory reason. Validate selected data ranges
  against the target ELF, allowing parameter writes when their load segment is
  writable.

  Rename configuration APIs and diagnostics to use simulator terminology, and
  document the supported state and parameter behavior.
  Allow manifests to define custom float64 inputs, outputs, and states through
  ELF virtual addresses, and resolve manual hooks through explicit symbols.
  Add timer_hook selection and allow compilation without DWARF when all selected
  data and hooks are explicitly specified.

  Generate an editable skeleton for binaries without a recognized Simulink model,
  document the manual workflow, and cover it with no-DWARF manifest tests.
  Update the M4 trajectory signal names and ignore the root river-manifest build
  artifact.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant