Bram Evert
Bram Evert
Yes, that's right. Sorry, maybe it should be labelled as a feature request. The other solution would be rejecting non-Qubit inputs. It was just confusing because there was no error...
In pyquil v3, the constant pi was a float. Specifically, the program constructed like so, ```python import numpy as np from pyquil.quil import Program from pyquil.gates import RX program =...
Changing pi to be an expression will cause a tremendous number of bugs, because to date we have assumed that expressions are parametric while fixed values are scalars, and a...
> (1) The statement that the change "will cause a tremendous number of bugs, because to date we have assumed that expressions are parametric while fixed values are scalars, and...
Snippet to modify an XY defcal: ```python calibration_program = qc.compiler.get_calibration_program() defcal = calibration_program.get_calibration(XY(np.pi, 112, 125)) new_instrs = [] for inst in defcal.instrs: if isinstance(inst, ShiftPhase) and isinstance(inst.phase, Expression): if isinstance(inst.phase,...
Note that the plot titles are incorrect. The QVM is operating here on theta, not theta % 2pi
Nice catch, Steve. The implementation is correct btw.
The problem here is that this seems to be non-deterministic. Sometimes the declarations are at the top, sometimes they are not.
I would just like it to be one way or the other. I think the simplest way is when parsing a problem, replace pi with 3.14159... This is ugly for...
Does this occur when running in a jupyter notebook?