Check for unexpected config values
A problem I periodically have is that I either misspell a configuration parameter in the .pipe file or I mess up the block structure such that the configuration parameter is not parsed/applied, and I end up silently using the default value for that parameter. There should be a more framework level check to raise an error when an unexpected/unhandled configuration parameter is encountered.
Due to the dynamic nature of the pipeline, it is not possible to validate a config file in the framework as is done in VidTK. There is a config_difference class that can determine mismatches in config blocks between what is expected and what is received. There is an example in the header file.