forked from epfl-lasa/control-libraries
-
Notifications
You must be signed in to change notification settings - Fork 1
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add utilities to map from parameter type to the type label #152
Labels
good first issue
Good for newcomers
Comments
@domire8 I am not quite confident with the naming convention I followed (which is altered from the example), so let me know if this needs adjustments. There is also different conventions followed between DSE and the StateType for example. |
bpapaspyros
added a commit
that referenced
this issue
Jan 10, 2024
(#152) This will move the functions introduced in the previous commit to the ParameterType.hpp header instead of the Parameter.hpp/.cpp. This makes for a cleaner and context-specific organization.
Merged
2 tasks
Merged
2 tasks
bpapaspyros
added a commit
that referenced
this issue
Jan 11, 2024
bpapaspyros
added a commit
that referenced
this issue
Jan 11, 2024
(#152) This will move the functions introduced in the previous commit to the ParameterType.hpp header instead of the Parameter.hpp/.cpp. This makes for a cleaner and context-specific organization.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
state_representation
has theParameter
object that can have differenttype
s, see the available types here. It would be great if we could have a human readable string associated with each parameter type such that we can be more precise when logging errors. For that, I propose to add under the parameters namespace some utilities:The text was updated successfully, but these errors were encountered: