Applications

The applications key is optional and is used to redefine parameters for each application used in pipelines. If the pipeline is ran at multiple resolutions, you can personnalize the configuration for each resolution, or override the parameters for all resolutions at once, as explained in the section right below.

Overriding all resolutions at once

To override all resolutions in a pipeline that is called at multiple resolutions, you can use the resolution value all.

This example overrides the configuration of application_1 for all resolutions at once :

pipeline_1:
  applications:
    all:
      application_1:
        method: application_dependent
        parameter1: 3
        parameter2: 0.3

{
    "pipeline_1": {
        "applications": {
            "all": {
                "application_1": {
                    "method": "application_dependent",
                    "parameter1": 3,
                    "parameter2": 0.3
                }
            }
        }
    }
}

Overriding a single resolution

To override a configuration at a specific resolution, you first need to identify which resolution you want to modify. By default, CARS uses the resolutions 16, 4, and 1 :

Resolution 16 corresponds to 16 times the original resolution (e.g., 16m if the original resolution is 1m).

Resolution 4 corresponds to 4 times the original resolution (e.g., 4m if the original resolution is 1m).

Resolution 1 corresponds to the original resolution (e.g., 1m).

Once you have chosen the resolution value, you can override the configuration by adding an entry to the applications dictionary with the key {resolution_value} (with resolution_value an integer).

The following example overrides the configuration for application_name at resolutions 4 and 1, using different parameters for each. Resolution 16 will retain its default configuration.
---
pipeline_1:
  applications:
    4:
      application_name:
        method: first_method
        parameter1: 26
        parameter2: 0.9
    1:
      application_name:
        method: second_method
        parameter1: 8
        parameter2: 0.2
{
    "pipeline_1": {
        "applications": {
            "4": {
                "application_name": {
                    "method": "first_method",
                    "parameter1": 26,
                    "parameter2": 0.9
                }
            },
            "1": {
                "application_name": {
                    "method": "second_method",
                    "parameter1": 8,
                    "parameter2": 0.2
                }
            }
        }
    }
}

The pages below describes all the available parameters for each CARS application.

CARS applications are defined and called by their name. An example configuration is provided for each application.

Be careful with these parameters: no mechanism ensures consistency between applications for now. Some parameters can degrade performance and DSM quality heavily. The default parameters have been set as a robust and consistent end to end configuration for the whole pipeline.

Application parameters

The default configuration can be different for the first resolution, the intermediate resolution(s) and the last resolution. The changes to the default values can be modified in the source code, in cars/pipelines/conf_resolution/*.

The section below includes the files directly.

This is empty for now.

---
tie_points:
  applications:
    sparse_matching:
      decimation_factor: 100

This is empty for now.

---
{}

---
surface_modeling:
  applications:
    dense_matching:
      confidence_filtering:
        activated: false