Comments (5)
Fig 9 in the paper does show a "Circuit Depth" of 31 as you mention (after one level of decompose).
But it also shows the "Transpiled Depth" as ~78 which you also indicate is the correct depth. What is shown in the bar chart seems to match your numbers. I am not clear what it is that you are reporting as incorrect ... perhaps you can clarify?
Note that the "Transpiled Depth" is what we use as a "normalized" depth for the x coordinate in the volumetric plots.
The assumption was also made is that the transpilation does not account for connectivity, so the larger depth due to swapping of qubits will not show in these charts. They are intended to represent a normalized depth independent of any knowledge of connectivity. The other issue you mentioned about qubit mapping might address some of this concern. See the comment there.
from qc-app-oriented-benchmarks.
Ok I see. It is a bit confusing because there is only a mention of the basis set [‘rx’, ‘ry’, ‘rz’, ‘cx’]
, which is not what decompose()
gives you. The end of Sec 3C also says:
‘circuit depth’ always refers to our normalized
definition for circuit depth unless otherwise stated
which makes you think it uses the above mentioned basis set given that the figure legend says "Circuit Depth" for the decomposed data. The only way the corresponding transpiled data could be any deeper is if going to the IBM default basis and including swaps.
from qc-app-oriented-benchmarks.
I agree it is a bit confusing. Concrete suggestions on how to make clear both in the repo and paper are welcome!
Note that the decompose(0 is primarily being used to "flatten" the circuits, as we use subcircuits everywhere
from qc-app-oriented-benchmarks.
I would just use the "transpiled" data for the "Gate depth" data and just drop the former. There is no need for the decomposed data as the decomposition definitions are someone arbitrary. It also clears things up a bit because when listing fidelities right above "transpiled" depths, it is natural to assume that that depth is what was run on the HW to generate the corresponding fidelity right above it.
from qc-app-oriented-benchmarks.
Closed after clarification on the explanation in the paper
from qc-app-oriented-benchmarks.
Related Issues (16)
- (AE/MC) Controlled Circuits in Braket
- MCX Shim in braket grover's doesn't work
- Deutsch-Josza Benchmarking Test is giving throwing Error HOT 5
- hamiltonian-simulation is throwing the error HOT 3
- Circuit depth in the paper :Application-Oriented Performance Benchmarks for Quantum Computing
- Problem in executing the vqe code HOT 6
- Let's add benchmarks for Quantum Wavelet Transforms HOT 1
- Add High Level Intuition README sections
- Qiskit transpilation for circuit depth determination is slow; cache data for performance
- Implement optional execution of multiple circuits in each job in Qiskit version
- polarization fidelity is not a valid comparator HOT 4
- [new feature] Add possibility of multiple transpilation passes in Qiskit HOT 1
- No ability to specify which qubits used in Qiskit transpiler HOT 10
- Generating invalid expected distribution
- `execute` performance vs simple qiskit execute calls on simulator HOT 1
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from qc-app-oriented-benchmarks.