‍IMPLEMENTATION ONGOING

While an application contains configuration values, a user might want to change some of them at startup time of the application - for debugging, customization or disabling unneeded parts of the pipeline. These differences can be define in one or more .app-config.json files which are passed as command line arguments to the invocation of the application.

The following kind of configuration value can be overridden:

Add/update/remove command line arguments of processes
Override component parameters
Skip nodes from being run by STM
Add new or modify existing sensor layouts
Various configuration values for other aspects (extraInfo, recorder, roadcast)

Limitations

Since the changes are dynamically applied at startup, they aren't checked before and are therefore only intended to be used by developers. While these configuration changes can affect the data pipeline (skipping certain nodes) and STM will be able to utilize the freed resources differently, the STM schedule is not being rebuild and therefore can't be expected to be optimal for the reduced data pipeline.

See transformations for more invasive changes to an application which aren't performed at startup time but at build time and are not subject to the above limitations.

References

The schema for .app-config.json files describes all JSON keys and values as well as their semantic.