Feature #1525
Feature #1534: === Parameter handling ===
consider parameters of types int, enum, bool
| Status: | Rejected | Start date: | 21 Jul 2016 | |
|---|---|---|---|---|
| Priority: | Low | Due date: | ||
| Assignee: | - | % Done: | 0% | |
| Category: | - | |||
| Target version: | - |
Description
Parameters of types enum would allow us to merge physical models, provided they have the same number of parameters, and parameters have the same meaning in all models. For instance, FFGauss and FFLorentz could be merged into FFSoftSphere, and enum={Gauss,Lorentz} would allow the user to toggle the distribution function.
Once there are parameters of type bool and int, we may get rid of the separate SimulationOption mechanism.
History
#1 Updated by herck about 4 years ago
Enums are famous code smells in OO code. We already have too many of these.
Parameterizing the distribution for such a form factor makes the API in python more difficult to use (in comparison with just instantiating a specific class).
#2 Updated by wuttke about 4 years ago
By enum I mean a finite set of keywords. This must not imply implementation using the C/C++ 'enum' datatype.
#3 Updated by wuttke about 4 years ago
- Parent task set to #1290
#4 Updated by wuttke about 4 years ago
- Parent task changed from #1290 to #1534
#5 Updated by wuttke about 4 years ago
- Status changed from Long Term Idea to Rejected
Structure is ready to accomodate such parameters. Further implementation must be driven by a use case ...