|
3 | 3 |
|
4 | 4 | """`dotbot sim` — standalone simulator (no hardware). |
5 | 5 |
|
6 | | -Equivalent to `dotbot controller --adapter dotbot-simulator`. The name |
7 | | -advertises the no-hardware case so students can discover the offline |
8 | | -path from `dotbot --help` without reading adapter docs. |
9 | | -
|
10 | | -Implementation: prepend `--adapter dotbot-simulator` to argv and |
11 | | -delegate to the controller's Click command. A future refactor will |
12 | | -turn this into a first-class entry that wires Engine + SimulatorAdapter |
13 | | -directly. |
| 6 | +Equivalent to `dotbot controller --conn simulator`. The name advertises |
| 7 | +the no-hardware case so students can discover the offline path from |
| 8 | +`dotbot --help` without reading connection docs. |
| 9 | +
|
| 10 | +Implementation: prepend `--conn simulator` to argv and delegate to the |
| 11 | +controller's Click command. `dotbot sim --sailbot` forwards through to |
| 12 | +the controller's robot-type selector. A future refactor may turn this |
| 13 | +into a first-class entry (and possibly a separate sim process). |
14 | 14 | """ |
15 | 15 |
|
16 | 16 | import click |
|
31 | 31 | def cmd(ctx): |
32 | 32 | """Run a standalone simulator (no hardware required). |
33 | 33 |
|
34 | | - All other controller flags are forwarded as-is. Try |
| 34 | + `dotbot sim` runs a dotbot simulator; `dotbot sim --sailbot` runs a |
| 35 | + sailbot one. Other controller flags are forwarded as-is. Try |
35 | 36 | `dotbot sim --help` for the full option list. |
36 | 37 | """ |
37 | | - args = ["--adapter", "dotbot-simulator", *ctx.args] |
| 38 | + args = ["--conn", "simulator", *ctx.args] |
38 | 39 | _controller_main.main(args=args, standalone_mode=True) |
0 commit comments