*kf algorithm generation engine combines a set of filter architectures and filtering ideas with a user's problem description to intelligently generate high-quality filtering algorithms.
It start with selecting the filter archiecture:
A user selects among these options and provides information about the dynamics and observation functions, noise terms, Jacobians, etc. The engine combines these for an efficient custom filter and generates the approriate code, whether as efficient MATLAB or C code.
The engine contains a set of tools for:
The engine is wrapped with a graphical user interface, exposing all of the applicable options to the user as architectures and options change. The interface is not necessary to use the engine (it can be invoked with a struct), but for the sake of this documentation, the engine and interface will always be described together.
The interface can be brought up at any time.
When a filter is generated, it will consist of an initialization function and a function to call on each step, e.g.:
% Initialize [x, P, constants] = my_filter_init(); % For each sample... for k = 2:n % Run the filter. [x, P] = my_filter(t(k-1), t(k), x, P, z(:, k), constants); end
z(:, k) is the observation vector at time
Note that the filter has no internal state (it is reentrant); it simply processes based on the inputs. Therefore, we could use multiple filters at once or manually change the state estimate or information at any point with worrying about adverse effects.
The engine is broken into several sections to keep things tidy.
This consists of setting the name of the filter, the initial conditions, and the overall architecture of the filter.
This box displays help about the selected field. It updates when the user changes something or right-clicks on a field.
These options change for each filter architecture and consist of things like inputs for the observation function, whether consider covariance should be used, if it's desirable to output the innovation vector, etc.
When the filter is generated, it will expect to call several of the user's functions, such as the propagation function. When the user clicks "Update" or "Generate", this box will update with the interfaces expected, using shorthand variable names described in nomenclature.
This box controls how the example simulation and Monte-Carlo test are generated, such as what time step and input to use and how many runs are desired.
This box controls what type of code is generated and how it is wrapped, such as selecting C code for implementation with a Simulink block wrapper.
See setup next.