I would also please like to have this feature!

Results such as the ones produced by this code snipet:

from qualtran.bloqs.basic_gates import Ry
from qualtran.cirq_interop.t_complexity_protocol import t_complexity

for eps in [1e-11, 1e-3]:
    print(f"t_cost at eps={eps}:", t_complexity(Rx(angle, eps=eps)).t_incl_rotations())

are pretty confusing at first. I know this can be "fixed" by passing eps=eps to .t_incl_rotations() but this is not elegant.

Moreover, imagine one wants to get T gate counts for Bloqs containing rotations with different level of precision. To my understanding this is currently not possible:

from qualtran import Bloq, BloqBuilder
from qualtran.drawing import show_bloq
from qualtran.cirq_interop.t_complexity_protocol import t_complexity

class TwoRotations(Bloq):
    @property
    def signature(self):
        return Signature([
            Register('x', QBit()),
        ])

    def build_composite_bloq(self, bb: BloqBuilder, *, x):
        x = bb.add(Rx(angle=0.1, eps=1e-11), q=x)
        x = bb.add(Ry(angle=0.2, eps=1e-3), q=x)
        return {'x': x}

two_rotations = TwoRotations()

show_bloq(two_rotations)
show_bloq(two_rotations.decompose_bloq())

t_complexity(two_rotations).t_incl_rotations()

This will always output 2 * 52 = 104 even though, due to the lower precision of the Ry rotation the T count should be lower.

Or is there a way to get correct resource estimates in such cases?

Propagate rotation epsilon in gate cost #1250

Description

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions