Configuration

This section describes main CARS configuration structure through a json configuration file.

The structure follows this organisation:

{
    "pipeline": "sensor_to_full_resolution_dsm",
    "inputs": {
        ...
    },

    "applications": {
        "name_application_used_in_pipeline": {
            "parameter": value_parameter
        }
    }

    "orchestrator": {
        "mode": "local_dask"
    },

    "output": {
          "out_dir"="output_directory_path"
    }
}

Warning

Be careful with commas to separate each section. None needed for the last json element.

To have a full configuration, use Sensor to full resolution dsm main pipeline section for main pipeline configuration examples.

Pipeline

This key is optional and defined the choice of CARS pipeline. At the moment, there are two of them:

Inputs

Values associated to this key are defined by pipeline so let’s refer to Sensor to full resolution dsm main pipeline for details.

Applications

This key is optional and allows to redefine parameters for each application defined in each “application_name” section used by pipeline.

See Applications for each 3D steps for details.

Note

For the particular case of the application Point Cloud outliers removing in the Sensor to full resolution dsm main pipeline, please refer not only in Applications for each 3D steps but also on Applications

Orchestrator

This key is optional and allows to define orchestrator configuration that controls the distributed computations:

Name

Description

Type

Default value

Required

mode

Parallelization mode “local_dask”, “pbs_dask” or “mp”

string

local_dask

No

nb_workers

Number of workers

int, should be > 0

2

No

walltime

Walltime for one worker

string, Should be formatted as HH:MM:SS

00:59:00

No

Outputs

Values associated to this key are defined by pipeline so let’s refer to Sensor to full resolution dsm main pipeline.