Command line interface

Met.3D supports the following command line arguments when started from a shell. Run met3d --help for a quick overview.

Argument	Description
`-d`, `--datasets`	Load one or more dataset configuration files on startup
`-a`, `--actors`	Load one or more actor configuration files on startup
`-b`, `--batch`	Run in batch mode using the given batch configuration file
`--gen-grib-index`	Generate GRIB index files for the given datasets and exit
`-t`, `--threads`	Set the maximum number of worker threads
`--metview`	Start in Metview interface mode
`--path`	Semicolon-separated list of Metview dataset paths (used with `--metview`)
`--run-tests`	Run internal tests (development use)

Loading datasets

After configuring a dataset through the GUI (see Loading data into Met.3D), Met.3D saves the configuration to a .pipeline.conf file. Pass this file on startup with -d / --datasets to reload it automatically:

met3d --datasets /path/to/dataset.pipeline.conf

Multiple datasets can be loaded by separating the paths with semicolons:

met3d -d /path/to/dataset1.pipeline.conf;/path/to/dataset2.pipeline.conf

Loading actors

Actor configurations saved from the GUI can be loaded automatically with -a / --actors:

met3d --actors /path/to/actor.actor.conf

Multiple actor configs can be passed as a semicolon-separated list. All actors are created in every available scene. Actors should be loaded together with the datasets they depend on:

met3d -d /path/to/dataset.pipeline.conf -a /path/to/actor.actor.conf

Batch mode

Batch mode allows Met.3D to run non-interactively, for example to produce images or export data without user interaction. Pass a batch mode configuration file with -b / --batch:

met3d --batch /path/to/batch_config.batch.conf

The configuration file uses INI format with a [BatchMode] section. An example configuration can be found in config/batch_mode.batch.conf.template in the Met.3D installation directory. See Batch mode for full documentation of the batch mode configuration format.

Generating GRIB index files

GRIB datasets require index files for fast access. To generate these without starting the full application, combine --gen-grib-index with --datasets:

met3d --gen-grib-index -d /path/to/grib_dataset.pipeline.conf

Met.3D generates the index files and exits immediately.

Thread count

By default, Met.3D uses all available CPU threads minus one. Use -t / --threads to override this:

met3d --threads 8

Setting this to a lower value can be useful to leave resources for other processes running on the same machine.

Metview interface mode

Met.3D can be integrated with Metview using the --metview flag. In this mode, dataset paths are provided via --path as a semicolon-separated list:

met3d --metview --path "/path/to/data/*.grib;/another/path/*.grb"