Yannick Stade
Yannick Stade
## Description Benchmark creation APIs now accept arbitrary configuration options via **kwargs: Unpack[ConfigurationOptions] and propagate them through the pipeline. A new ConfigurationOptions TypedDict with optional seed was added. The graphstate...
## Description This PR adds a—for the moment—minimalistic SC QDMI device that only features a coupling map. The changes extend the QDMI device framework by relocating the Device class to...
As pointed out in by @burgholzer in https://github.com/munich-quantum-toolkit/core/issues/1328#issuecomment-3570503942_ , especially, the NA devices lives currently out of place compared to other QDMI devices. Consequently, the NA device should be moved...
As pointed out by @burgholzer in https://github.com/munich-quantum-toolkit/core/issues/1328#issuecomment-3570499719_, the implementation of the initial, minimalistic SC device needs to be further polished. In particular, this involves: - Proper handling of operations -...
### Problem Statement The code added in #1236 could not be tested throughly to reach a sufficient test coverage. In particular, there was a way missing to mock a device...
### Problem Statement The current solution offers an elegant way to transform a JSON representation of an NA device into a corresponding QDMI device as a shared library. As mentioned...
## Problem During a discussion with @MatthiasReumann on implementing QMAP as a transformation pass in MQTOpt, the question arose of how static qubits—defined by a quantum device—should be allocated and...
### Problem Statement The conversion from `MQTOpt` to `MQTMem` requires information about the hardware. This must somehow be fed to the conversion pass. ### Proposed Solution The end-user should be...
### Problem Statement MLIR is a convenient way to define representations of programs, i.e., quantum programs. It also allows for easy interface with other tools by defining conversions between the...
### Problem Statement When loading a MLIR plugin, the optimization tool must be provided with two options `--load-pass-plugin` and `--load-dialect-plugin`. As of now, we pass the same `.dylib` to both...