[WIP] Adding SynthesisData
and porting some of the MCX synthesis methods to Rust
#13929
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
First, this PR implements the
SynthesisData
struct, with the goal to simplify porting synthesis algorithms to rust (including synthesis of hierarchical circuits) and standardize the already existing code incrates/accelerate/src/synthesis
.Ideally, we should be using
CircuitData
instead of introducingSynthesisData
, however at the momentCircuitData
has a significant overhead. For the sake of an experiment, I have locally rewrittenpauli_evolution.rs
code, and it became 10x slower when usingCircuitData
and only 1.1x slower when usingSynthesisData
. Hopefully we would eventually replaceSynthesisData
byCircuitData
.To illustrate the above usage of
SynthesisData
, I am planning to port several MCX synthesis algorithms from Python to Rust. So far:synth_c3x