This should be made more clear in a released version
From the top of my head: Perhaps, model parameters can be a property, which gathers free and fixed parameters. free and fixed parameters are also properties that have associated setters, which calls update on the parameters.
This prevents any parameters to be deleted which are set during the initialization of the simulation (i.e. reading the config file) overriding initialized parameters in the user-define initialize method is then still a choice.
Using a setter is a good idea, because it allows the use of helpful error messages where the problem occurs
This should be made more clear in a released version
From the top of my head: Perhaps, model parameters can be a property, which gathers free and fixed parameters. free and fixed parameters are also properties that have associated setters, which calls update on the parameters.
This prevents any parameters to be deleted which are set during the initialization of the simulation (i.e. reading the config file) overriding initialized parameters in the user-define
initializemethod is then still a choice.Using a setter is a good idea, because it allows the use of helpful error messages where the problem occurs