You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I believe this is because the change in #190 makes the value of UINTMAX depend on 64-bits but the pytket translation of QASM circuits is still using 32-bits for the range predicate translation. See
@cqc-alec do you think this is a bug in pytket or do we need to treat QASM inputs specially assuming max 32 bits?
There is a maxwidth parameter to circuit_from_qasm, which defaults to 32. Would changing this to 64 in the get_qasm_as_circuit() method (or to 64 if pytket.__dict__.get("bit_width_64", False) else 32 as used in the definition of UINTMAX) fix the issue?
Describe the bug
With upgrade to pytket==0.13.1, all tests involving range predicate fail (see here):
I believe this is because the change in #190 makes the value of
UINTMAX
depend on 64-bits but the pytket translation of QASM circuits is still using 32-bits for the range predicate translation. SeeTo Reproduce
Upgrade to pytket==0.13.1
Expected behavior
Tests should pass.
Additional context
Changes in #190
The text was updated successfully, but these errors were encountered: