InstructionScheduleMap parameters should be ParameterExpressions
See original GitHub issueWhat is the expected enhancement?
The input parameters into the InstructionScheduleMap should be expected to be ParameterExpression
s. Types and tests should be updated accordingly. This is a follow on to #3385.
Issue Analytics
- State:
- Created 4 years ago
- Comments:12 (11 by maintainers)
Top Results From Across the Web
Source code for qiskit.pulse.instruction_schedule_map
This can be used for scheduling circuits with custom definitions, for instance:: ... from qiskit.circuit.parameterexpression import ParameterExpression from ...
Read more >Load parametrized Qiskit Instructions that act on multiple qubits
This results in the following Exception: TypeError: ParameterExpression with unbound parameters ({Parameter(θ)}) cannot be cast to a float. Is there a way ...
Read more >#999540 - qiskit-terra: FTBFS with matplotlib 3.5 (in experimental ...
This version will soon be uploaded to unstable. ... copying qiskit/circuit/parameterexpression.py ... copying qiskit/circuit/parameter.py ...
Read more >qiskit-terra Changelog - PyUp.io
Cast ParameterExpression to float in RZXBuilder and ... "cregbundle set to False" warning should not raised when no classical bits are involved (8689)...
Read more >Instruction schedule map cannot be pickled with python3.6 - qiskit ...
ParameterExpression, float]: it's not the same object as typing. ... named arguments (i.e. pulse parameters), but can have default values and also partially ......
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
For now if a
ParameterExpression
is passed toget
/pop
could we just pass it through to the underlying function? If passed to the very rough https://github.com/Qiskit/qiskit-terra/blob/f132cf7fc69920f393bc2055e98f20e8e7d6bce0/qiskit/pulse/schedule.py#L744 (was originally meant to be temporary and replaced by #3384).This class could be modified to try and cast the
ParameterExpression
to a float, and raise if not possible.If you have questions that need quicker answers you can always feel free to find me on our Slack.