munich-quantum-toolkit / munich-quantum-toolkit/predictor
Implementation of a "Standard" Intermediate Representation (IR)
Nobody has claimed this yet.
- Dominant language
- Python
- Stars
- 87
- Forks
- 23
- Avg merge
- 6h 23m
- Merged PRs (30d)
- 35
Description
So far, mqt-predictor uses different types of IR for its method interfaces, such as Qiskit.QuantumCircuit, TKET.Circuit, str, or Path to stored quantum circuits. This should be unified.
This should also be reflected in, e.g., rl.helper.qcompile that currently accepts only Qiskit.QuantumCircuit or a Path but no TKET.Circuit object.
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
Start by tracing the method interfaces that currently accept Qiskit.QuantumCircuit, TKET.Circuit, str, or Path, then inspect rl.helper.qcompile and its current Qiskit.QuantumCircuit and Path handling. Done means the project uses one defined intermediate representation consistently, including support for TKET.Circuit in qcompile.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- python
- Domain
- backend-api-design, compilers
- Issue type
- Refactor
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100