You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, all solvers declare #defines with the same names, such as nn for the state dimension. They also all call the MPC solver the same way, independently of the value given to options.save_name. This can cause a name-conflict issue if two or more solvers are included in the same .c file.
The solution is for all #defines to be called after the save_name, e.g., if save_name is myMPC, then the #defines will be something like: #define myMPC_nn. This would require a search and substitute in the generated files, substituting nn for myMPC_nn.
Same goes for the function name, which should be called like the save_name, instead of by the name of the MPC formulation and the solver.
The text was updated successfully, but these errors were encountered:
Currently, all solvers declare
#define
s with the same names, such asnn
for the state dimension. They also all call the MPC solver the same way, independently of the value given tooptions.save_name
. This can cause a name-conflict issue if two or more solvers are included in the same.c
file.The solution is for all
#define
s to be called after thesave_name
, e.g., ifsave_name
ismyMPC
, then the#define
s will be something like:#define myMPC_nn
. This would require a search and substitute in the generated files, substitutingnn
formyMPC_nn
.Same goes for the function name, which should be called like the
save_name
, instead of by the name of the MPC formulation and the solver.The text was updated successfully, but these errors were encountered: