carsim-guide
VerifiedOperate and automate CarSim simulations from an agent, including safe output and parameter discovery, named Run Control execution contexts, structured overrides, isolated batch sweeps, dataset dependency inspection, control-mode selection, result validation, diagnostics, and version-aware CLI/Simulink/VS API routing. Use for executing, configuring, exploring, or debugging CarSim. Do not use for vehicle-dynamics theory alone, generic dataframe work, or unrelated simulators.
references/troubleshooting.md
View on GitHub# Structured troubleshooting
Run `python scripts/diagnose_run.py <run-directory>`. The command reports
PASS/FAIL/NOT RUN by layer and returns nonzero when an error is found.
Stable layers are: environment, base, scenario, compile, solver, license,
output, echo, database, cosim, and version. Stable exception classes live in
`scripts/carsim_errors.py`.
The first diagnostic pass recognizes only evidence-backed signatures:
- missing CLI executable or DLL;
- simfile not pinning `carsim_64.dll`;
- license / “Unable to load library” text;
- missing normal termination;
- missing, stale, or unparsable `run.csv`;
- missing echo or scalar echo mismatch;
- unverified CarSim version.
Do not classify unfamiliar solver prose speculatively. Preserve the original
exception/stdout and ask for the relevant artifact when evidence is missing.
Retry at most once, and only for a temporary file-access failure or a known
short-lived process/file race. Do not retry license failures, base hash
mismatches, unknown parameters or output units, echo mismatches, scenario
validation errors, version warnings that require user judgment, or repeated
abnormal solver termination. Stop, diagnose, and report the evidence instead.
Do not alter speed, road friction, vehicle mass, or control inputs merely to
make a failed run pass unless the user explicitly asks to debug the physical
configuration.
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |