[ModelicaSystem] improve set functions

[syntron]

improve input handling for set*() functions

• use a Pythonic way for input:

 setParameters(a=123)
param = {'a': 123}
setParameters(**param)

Based on PR #314 with input from SengerM (see PR #326); this replaces PR #326

[syntron]

@adeas31 one thing I did not checked but which is quite important to confirm here: are there the same rules for variable names in Python and OpenModelica? I assume yes and then all is fine - if not this PR should not be applied!

[adeas31]

@adeas31 one thing I did not checked but which is quite important to confirm here: are there the same rules for variable names in Python and OpenModelica? I assume yes and then all is fine - if not this PR should not be applied!

Which variables are you talking about? Did you mean Modelica and not OpenModelica?

[adeas31]

Also as I understand this supersedes PR #326.

[syntron]

Also as I understand this supersedes PR #326.

@adeas31 Yes, the interface uses the idea of @SengerM (PR #326). It adds this way of defining arguments not only to setParameters() but all set*() functions.

Which variables are you talking about? Did you mean Modelica and not OpenModelica?

Just to confirm: the definition of a valid variable in Modelica is eual to the definition in Python, i.e. must start with a letter (or underscore?) and can only contain leters, numbers and underscore.

The reason for this is that by using the code in this PR, the Modelica variables are used as Python variables. Thus, the rules should match in this direction.

[SengerM]

Which variables are you talking about? Did you mean Modelica and not OpenModelica?

The rules for identifiers in Python and the ones for Modelica.

The reason for this is that by using the code in this PR, the Modelica variables are used as Python variables. Thus, the rules should match in this direction.

Even if the naming rules are a bit different, you can overcome this issue if the current string interface is maintained for those specific cases.