|
| 1 | +# CLI Reference |
| 2 | + |
| 3 | +## `singlerun.jar` (`SimPathsStart`) |
| 4 | + |
| 5 | +Usage: |
| 6 | + |
| 7 | +```bash |
| 8 | +java -jar singlerun.jar [options] |
| 9 | +``` |
| 10 | + |
| 11 | +### Options |
| 12 | + |
| 13 | +| Option | Meaning | |
| 14 | +|---|---| |
| 15 | +| `-c`, `--country <CC>` | Country code (`UK` or `IT`) | |
| 16 | +| `-s`, `--startYear <year>` | Simulation start year | |
| 17 | +| `-Setup` | Setup only (do not run simulation) | |
| 18 | +| `-Run` | Run only (skip setup) | |
| 19 | +| `-r`, `--rewrite-policy-schedule` | Rebuild policy schedule from policy files | |
| 20 | +| `-g`, `--showGui <true/false>` | Enable or disable GUI | |
| 21 | +| `-h`, `--help` | Print help | |
| 22 | + |
| 23 | +Notes: |
| 24 | + |
| 25 | +- `-Setup` and `-Run` are mutually exclusive. |
| 26 | +- For non-GUI environments, use `-g false`. |
| 27 | + |
| 28 | +### Examples |
| 29 | + |
| 30 | +Setup only: |
| 31 | + |
| 32 | +```bash |
| 33 | +java -jar singlerun.jar -c UK -s 2019 -g false -Setup --rewrite-policy-schedule |
| 34 | +``` |
| 35 | + |
| 36 | +Run only (after setup exists): |
| 37 | + |
| 38 | +```bash |
| 39 | +java -jar singlerun.jar -g false -Run |
| 40 | +``` |
| 41 | + |
| 42 | +## `multirun.jar` (`SimPathsMultiRun`) |
| 43 | + |
| 44 | +Usage: |
| 45 | + |
| 46 | +```bash |
| 47 | +java -jar multirun.jar [options] |
| 48 | +``` |
| 49 | + |
| 50 | +### Options |
| 51 | + |
| 52 | +| Option | Meaning | |
| 53 | +|---|---| |
| 54 | +| `-p`, `--popSize <int>` | Simulated population size | |
| 55 | +| `-s`, `--startYear <year>` | Start year | |
| 56 | +| `-e`, `--endYear <year>` | End year | |
| 57 | +| `-DBSetup` | Database setup mode | |
| 58 | +| `-n`, `--maxNumberOfRuns <int>` | Number of sequential runs | |
| 59 | +| `-r`, `--randomSeed <int>` | Seed for first run | |
| 60 | +| `-g`, `--executeWithGui <true/false>` | Enable or disable GUI | |
| 61 | +| `-config <file>` | Config file in `config/` (default: `default.yml`) | |
| 62 | +| `-f` | Write stdout and logs to `output/logs/` | |
| 63 | +| `-P`, `--persist <root|run|none>` | Persistence strategy for processed dataset | |
| 64 | +| `-h`, `--help` | Print help | |
| 65 | + |
| 66 | +Persistence modes: |
| 67 | + |
| 68 | +- `root` (default): persist to root input area for reuse |
| 69 | +- `run`: persist per run output folder |
| 70 | +- `none`: no processed-data persistence |
| 71 | + |
| 72 | +### Examples |
| 73 | + |
| 74 | +Create setup database using config: |
| 75 | + |
| 76 | +```bash |
| 77 | +java -jar multirun.jar -DBSetup -config test_create_database.yml |
| 78 | +``` |
| 79 | + |
| 80 | +Run two simulations with root persistence: |
| 81 | + |
| 82 | +```bash |
| 83 | +java -jar multirun.jar -config test_run.yml -P root |
| 84 | +``` |
| 85 | + |
| 86 | +Run without persistence and with file logging: |
| 87 | + |
| 88 | +```bash |
| 89 | +java -jar multirun.jar -config default.yml -P none -f |
| 90 | +``` |
0 commit comments