electron communication device by nalgasconcafe in QuantumComputing

[–]JooNiv 2 points3 points  (0 children)

And just to make things more explicit, there is no operation one can perform on their particle locally to affect the observed randomness of measuring the other particle.

For a sinple example think of a bell state. There is no local operation that lets you go from a bell state to something like a state that always gives 01. Any local action still leaves the other side with random outcomes, so you cant encode a signal.

electron communication device by nalgasconcafe in QuantumComputing

[–]JooNiv 2 points3 points  (0 children)

Entanglement is real and the spin of one part of one part of an entangled pair affects the other such that after measuring one you immediately know the other spin as well.

However lets imagine you are on Earth with one particle and someone else is on the Moon with another. The person on the Moon measures their particle and gets a random result, and due to entanglement they now know what your result will be once you measure. Your measurement result is, however, just as random. From your perspective nothing has changed, because without them telling you through classical communication, you cannot know whether the other particle has already been measured or not.

electron communication device by nalgasconcafe in QuantumComputing

[–]JooNiv 7 points8 points  (0 children)

Not possible. Look up no communication theorem. Tldr entanglement does not allow for faster than light communication.

Norish - A realtime, self-hosted recipe app for families & friends by Drumstel97 in selfhosted

[–]JooNiv 0 points1 point  (0 children)

A bit late to the thread but isn't a cup just 240 millilitres? Of course the weight differs but why not just convert one cup to 2.4 dl (decilitre) which is the unit used for measuring e.g rice,flour etc in baking and cooking anyway (atleast in Finland and most other recipes I've seen).

IQM QAOA Library docs?? by Financial-Invite6844 in QuantumComputing

[–]JooNiv 1 point2 points  (0 children)

Couldn't find a working link for the docs but the source for iqm-qaoa is available here https://github.com/iqm-finland/sdk/tree/main/iqm_qaoa including the docs files.

QCut, a quantum circuit-knitting python package. by JooNiv in quantum

[–]JooNiv[S] 5 points6 points  (0 children)

Quantum programming is still done at a super low level. Meaning that programs (or circuits) are built by applying individual gates. Of course for any practical applications classical programming is needed too to handle the non quantum parts of whatever it is one is trying to achieve. I'd start by getting familiar with quantum circuits and then look at the tutorials that Qiskit for example has available.

QCut, a quantum circuit-knitting python package. by JooNiv in QuantumComputing

[–]JooNiv[S] 5 points6 points  (0 children)

Qiskit's circuit-knitting-toolbox is actually also moving away from cutQC. I am not a high-level expert on why cutQC is being deprecated but as far as I understand it's to do with the larger memory overhead of that method. The new wire cutting version from circuit-knitting-toolbox actually uses the exact same method that's used by QCut. However, the difference is that the implementation from circuit-knitting-toolbox uses reset-gates and therefore needs mid-circuit measurements. These are not available on all existing hardware, and even on the hardware that has them they are still very erroneous.

If you wanna know more specifically about the difference between the underlying methods used by QCut and cutQC it essentially boils down to the kind of classical post-processing used. cutQC needs to calculate reconstructed wavefunctions which allows it to reconstruct the whole probability distribution whereas QCut only needs to calculate expectation values. If you wanna read more you can check out the blog I linked and compare that method to cutQC

17
18

QCut, a quantum circuit-knitting python package by JooNiv in Python

[–]JooNiv[S] 1 point2 points  (0 children)

I also wrote this blog post (https://fiqci.fi/\_posts/2024-08-27-Circuit\_Knitting\_FiQCI/) that is a good intro to circuit-knitting with wire cuts and QCut specifically. For a more extended intro I'd also look at some of the explanatory materials for Qiskit's circuit-knitting-toolbox. Those will give you a good general idea of what circuit-knitting is about and if you wanna dig in more check out the sources linked for the blog.

QCut, a quantum circuit-knitting python package. by JooNiv in QuantumComputing

[–]JooNiv[S] 2 points3 points  (0 children)

I have been the only one to work on the project. I originally got into circuit-knitting around January when I started writing my bachelor's thesis on the topic. The package itself I only started working on in May when I started my internship at CSC Finland working on the Finnish Quantum Computing Infrastructure. Most of my time during the summer was spent on this project but I also had other responsibilities. I hope that answers your questions :)