munich-quantum-toolkit / munich-quantum-toolkit/qmap
✨ Separation and Structure of Neutral Atom Mapper
Nobody has claimed this yet.
- Dominant language
- C++
- Stars
- 146
- Forks
- 41
- Avg merge
- 6h 47m
- Merged PRs (30d)
- 45
Description
What's the problem this feature will solve?
To make the code and the mapping process clearer, it would be good to clearly separate the different tasks:
- Map circuit
- Insert SWAP and MOVE operations
- Convert MOVE to AodOperations
- Schedule circuit
In this regard a possible idea is to consider a "reset" functionality for the mapper which deletes/resets all information needed temporarily during the mapping (e.g. position of mapping, ...) See here
Describe the solution you'd like
Functionality already exists, just restructure the functionality.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
No files or tests are named. Start by tracing the existing mapper flow and identify where mapping, SWAP/MOVE insertion, MOVE conversion, and scheduling currently occur. Done means these responsibilities are clearly separated and temporary mapping state can be reset without changing existing functionality.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- cpp
- Domain
- compilers
- Issue type
- Refactor
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100