Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Implement a TaperedQubitMapper #974

Closed
mrossinek opened this issue Nov 17, 2022 · 2 comments · Fixed by #1031
Closed

Implement a TaperedQubitMapper #974

mrossinek opened this issue Nov 17, 2022 · 2 comments · Fixed by #1031
Assignees
Labels
type: feature request New feature or request
Milestone

Comments

@mrossinek
Copy link
Member

mrossinek commented Nov 17, 2022

What should we add?

As the third step of #967 we should implement a TaperedQubitMapper which gathers all the Z2Symmetries-related tapering techniques currently controlled via the QubitConverter in a single QubitMapper wrapper:

class TaperedQubitMapper:
    def __init__(self, mapper: QubitMapper, z2symmetries: list[int]):
        ...
        
    @classmethod
    def from_problem(cls, mapper: QubitMapper, problem: ElectronicStructureProblem):
        # implies the previous z2symmetries == "auto" case
        # extract problem.hamiltonian and problem.symmetry_sector_locator
        
    def map(self):
        # uses self.mapper.map + applies tapering
        
    # provide 2-step tapering i.e. one method for _only_ mapping and one to apply tapering on-top
    # this is necessary for cases like the HF bitstring and qEOM

Just like with my proposal in #973, this mapper will be stateful.


This is blocked by Qiskit/qiskit#9140

@mrossinek mrossinek added type: feature request New feature or request on hold Can not fix yet labels Nov 17, 2022
@mrossinek mrossinek added this to the 0.6.0 milestone Nov 17, 2022
@Anthony-Gandon
Copy link
Contributor

Hi @mrossinek, I can contribute here

@Anthony-Gandon
Copy link
Contributor

  • Once we work on that mapper we need to think about how to handle the suppress_none=False case
    which we had in the QubitConverter.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
type: feature request New feature or request
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants