Comments (4)
The difference in the descriptions is in the last line (after the output): in task 1 "The state of the qubits at the end of the operation does not matter.", while in task 2 "The state of the qubits at the end of the operation should be the same as the starting state." The solution for task 2 is accepted in task 1, since it performs the same task in a more restricted way.
This pair of tasks shows that you can distinguish the states with different parity using regular measurements, but this will collapse the superposition; to keep superposition you need to use joint measurements which allow to get some information without collapsing the state.
from quantumkatas.
Thanks, @tcNickolas, for explanation. Now I clearly see the difference and its didactic value. So I am closing the issue.
But there is still a question, can there be any practical value in using the solution like in reference for SingleQubitMeasurement instead of that for ParityMeasurement. For example, I know that some quantum operations can consume significantly more energy than others. So are the solutions of these tasks consume energy at the same level or one of them is preferable in terms of energy consuming provided that we don't care the state at the end of operation?
If this discussion is not relevant here, can you please suggest where can ask this question or start this discussion in context of these Katas?
from quantumkatas.
Also, some noticeable comment regarding this difference in requirements could be introduced somewhere in task description.
It would be helpful especially for those who go through the katas in parallel with other activities and this is why can easily overlook this important condition.
from quantumkatas.
Usually joint measurements use cases are driven not by their efficiency when compared to single-qubit measurements for the same task, but rather by the need to perform a different task (extract some information about the system without collapsing it all the way to a basis state or perform a certain transformation).
A good place for such questions is Quantum Computing SE.
This difference is already in task description - right between output and operation signature. It's hard to make it more prominent, since there is only so much formatting we can do in source code :-)
from quantumkatas.
Related Issues (20)
- Sample solutions for task 1.14 of the Superposition katas. HOT 2
- Mistake in multi-qubit measurement tutorial exercise 2 calculations. HOT 1
- Enable tests that are currently excluded with multicell solution tag HOT 2
- [MultiQubitSystemMeasurements] Add code to Exercise 2 solution to show state in Pauli X basis HOT 2
- Fix math mode rendering in browser HOT 5
- Task 1.15 in Measurements Kata says two states are orthogonal. HOT 2
- Exercise 5 for RandomNumberGenerationTutorial - slightly cleaner solution HOT 4
- QFT Question HOT 9
- Late introduction of `ControlledOnInt` operation HOT 4
- Disable cell id generation while working on jupyter notebooks locally HOT 2
- Validate only changed katas…
- %kata magic doesn't work with lambda expressions HOT 1
- O(1) time complexity solution to Oracles tutorial, task 4.2 HOT 9
- Add error-free arbitrary state transmission demo to QEC_BitFlipCode kata HOT 7
- docker image creation is stuck HOT 1
- Add Memory Management Tutorials and Concepts HOT 1
- Systems of Equations not properly explained HOT 1
- BasicGates kata task 1.6 PhaseChange fails
- Docker Build Failing HOT 1
- getting issue in exit command 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 quantumkatas.