[Feature] Add system of annotations to the parser

[ocots]

Thanks to @gdupont1, we thought about adding a system of annotations to the parser to give the possibility to extend our parsing to external developers.

Question. @jbcaillau Why do we have to write == instead of = for the constraints?

Remark. Another idea is to provide an intermediate structured data between the definition of the optimal control problem and the OptimalControlModel to facilitate manipulations such as adding a state, normalizing the time, etc.

[jbcaillau]

@ocots @gdupont1 hi!

Thanks to @gdupont1, we thought about adding a system of annotations to the parser to give the possibility to extend our parsing to external developers.

Question. @jbcaillau Why do we have to write == instead of = for the constraints?

= for aliases, == for constraints (including dynamical ones). CaML spirit 🙂 (a constraint is not a definition but sth you want to enforce). it is standard for all but dynamical constraints (still, it also makes sense in this case).

Remark. Another idea is to provide an intermediate structured data between the definition of the optimal control problem and the OptimalControlModel to facilitate manipulations such as adding a state, normalizing the time, etc.

please write sth illustrating what you think of on a relevant use case