Currently, the Parameter class in qupulse.pulses.parameter has an outdated docstring with contradicting information. The role of the parameter class itself is rather undefined.
Source file docstring:
Parameter specifies a concrete value which is inserted instead of the parameter declaration reference in a PulseTemplate if it satisfies the minimum and maximum boundary of the corresponding ParameterDeclaration. Implementations of Parameter may provide a single constant value or obtain values by computation (e.g. from measurement results).)
Actual usage:
The only function of the parameter class is to provide some lazy evaluation of parameter mappings
Tasks:
[ ] Give a strong reason why we need the parameter class
[ ] clarify the scope of the parameter class (who uses it, user facing, pulse tempalte internal)
Currently, the
Parameter
class inqupulse.pulses.parameter
has an outdated docstring with contradicting information. The role of the parameter class itself is rather undefined.Written documentation and discussion:
Actual usage:
Tasks:
Scope
objects (See #418 / #344 )