It seems to me than there is an issue with the getParamState function and/or with the wiki explaining it:
- In the wiki, the example says to put something like
[~,phi] = getStateParamInput(x_t,P_t,in, 'observation');
in the observation function...
--> Usually, at this level the "in" argument is already defined as an inG (i.e. options.inG) or as a inF (i.e. options.inF)
- But in the function, the first lines are a switch that select options.inG or options.inF according to the value of "functionType"...
I guess the "wiki" solution is the good one to avoid something like options.inG.inG but maybe I missed a point in the way you wanted to use the function?
It seems to me than there is an issue with the getParamState function and/or with the wiki explaining it:
[~,phi] = getStateParamInput(x_t,P_t,in, 'observation');
in the observation function...
--> Usually, at this level the "in" argument is already defined as an inG (i.e. options.inG) or as a inF (i.e. options.inF)
I guess the "wiki" solution is the good one to avoid something like options.inG.inG but maybe I missed a point in the way you wanted to use the function?