Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Mariia Mykhailova
    @tcNickolas_twitter
    @amirebrahimi Check that the IQ# version you have installed is the same as the version used by the tutorial, and either install older IQ# or update the tutorial to newer version (if you do that, make sure you update both the Jupyter notebook and the csproj file).
    Harshit Garg
    @githg22_gitlab
    How do you people use prettier w/ Q#?
    Considering there isn't a formatter yet
    Gopal Ramesh Dahale
    @Gopal-Dahale
    I am not able to think about how to start with problem A5 (Z vs -Z). Can anyone give me a starting Hint? Global phase makes all my measurements same.
    Harshit Garg
    @githg22_gitlab
    Well, it didn't work out w/ just one qubit for me
    And you can't differentiate b/w them with simple |0> and |1>
    Think some clever superposition
    Harshit Garg
    @githg22_gitlab
    People who completed the machine learning tasks,
    How did you decide upon which design to use?
    How do I generally decide in what way to design a circuit
    Mariia Mykhailova
    @tcNickolas_twitter
    @Gopal-Dahale Does the "official" hint from the contest help you? "Z and -Z gates differ by a global phase they introduce, so you cannot distinguish them by applying them to a single qubit. Take advantage of the fact that the given unitary has controlled variant defined."
    Mariia Mykhailova
    @tcNickolas_twitter
    @githg22_gitlab In this particular case your data is encoded in just 1 qubit, so you have a choice of Rx, Ry and Rz gates :-) In general that's the same kind of challenge that classical machine learning faces - you need to figure out the feature engineering and the model structure before you can train it
    Amir Ebrahimi
    @amirebrahimi

    @amirebrahimi I think it's the same issue as discussed at https://quantumcomputing.stackexchange.com/questions/12466/qsharp-reload-throws-error-in-python and in comments at https://codeforces.com/blog/entry/77614

    This fixed it for me. Thank you @tcNickolas_twitter!

    vashisth malik
    @VashisthMalik_twitter
    hey there i need some help in increment problem. every term in this Question is new to me. can you please explain the Question?
    Amir Ebrahimi
    @amirebrahimi
    @VashisthMalik_twitter - can you share a bit more about what you don't understand?

    Re: D1 - I'm trying to modify the ClassifierStructure() to simply add an additional controlled rotation:
    ControlledRotation((1, new Int[0]), PauliY, 1)
    but get the following error:
    Unhandled exception. System.ArgumentOutOfRangeException: Specified argument was out of the range of valid values. ---> Microsoft.Quantum.MachineLearning.EstimateGradient on D:\a\1\s\submodules\QuantumLibraries\MachineLearning\src\GradientEstimation.qs:line 78 at Microsoft.Quantum.MachineLearning._RunSingleTrainingStep on D:\a\1\s\submodules\QuantumLibraries\MachineLearning\src\Training.qs:line 148 at Microsoft.Quantum.MachineLearning._RunSingleTrainingEpoch on D:\a\1\s\submodules\QuantumLibraries\MachineLearning\src\Training.qs:line 229 at Microsoft.Quantum.MachineLearning._TrainSequentialClassifierAtModel on D:\a\1\s\submodules\QuantumLibraries\MachineLearning\src\Training.qs:line 388 at Microsoft.Quantum.MachineLearning.TrainSequentialClassifierAtModel on D:\a\1\s\submodules\QuantumLibraries\MachineLearning\src\Training.qs:line 322 at Microsoft.Quantum.MachineLearning.TrainSequentialClassifier on D:\a\1\s\submodules\QuantumLibraries\MachineLearning\src\Training.qs:line 98 at Microsoft.Quantum.Kata.QuantumClassification.TrainLinearlySeparableModel on C:\Users\AmirEbrahimi\dev\qc\CodeForces2020\Warmup\notebook\Backend.qs:line 0

    I've dug through the source on GitHub a bit and it seems it is failing at estimating the number of qubits needed. Any ideas of how to resolve this? I would think simply by adding that ControlledRotation with another qubit referenced that it would expand the number of qubits.

    vashisth malik
    @VashisthMalik_twitter
    @amirebrahimi What i understand from the Question is that we have a register of little Endian and than i have to increment it with X gate and its Controlled variant? But i donot know how put operation on little endian what will be the syntax?
    Amir Ebrahimi
    @amirebrahimi

    So, this isn't immediately apparent, but you need to use the unwrap '!' operator to get at the qubits:
    https://docs.microsoft.com/en-us/quantum/user-guide/language/expressions#unwrap-expressions

    e.g. - register![0]

    As far as the rest, you need to consider how adders work and the equivalent on a quantum computer (that is also reversible).

    Harshit Garg
    @githg22_gitlab

    @githg22_gitlab In this particular case your data is encoded in just 1 qubit, so you have a choice of Rx, Ry and Rz gates :-) In general that's the same kind of challenge that classical machine learning faces - you need to figure out the feature engineering and the model structure before you can train it

    But I'm getting a very high value of Miss rate (0.4)

    Using LocalRotationsLayer(1, PauliX)
    And indeed with PauliY and PauliZ
    Mariia Mykhailova
    @tcNickolas_twitter
    @amirebrahimi The number of qubits required is not defined by the indices of qubits used in the model, it's defined by the encoding used in the model. In this case the model uses only 1 qubit, so you can't reference qubit with index 1, only 0
    Amir Ebrahimi
    @amirebrahimi
    @githg22_gitlab - what's the difference between LocalRotationsLayer and ControlledRotations?
    @tcNickolas_twitter - how come the halfmoon example has more than 1 qubit interactions?
    Mariia Mykhailova
    @tcNickolas_twitter
    @githg22_gitlab The miss rate depends not only on the model structure but also on the parameters. It is possible to have 100% miss rate with correct model and incorrect parameters :-) As a hint, you need one Ry gate
    @amirebrahimi HalfMoons uses a different encoding scheme - I wrote about it at https://codeforces.com/blog/entry/77614?#comment-641653
    Harshit Garg
    @githg22_gitlab

    @githg22_gitlab - what's the difference between LocalRotationsLayer and ControlledRotations?

    It applies the uncontrolled rotations, so far as I have understood

    Amir Ebrahimi
    @amirebrahimi
    Thank you both.
    Chris Granade
    @cgranade
    @amirebrahimi: This is actually a broader community for Q# developers and users, but it's really cool to see everyone from the contest! If you're interested in the Q# community, I'd encourage checking out what the Q# community has done at https://qsharp.community. There's some neat blog posts, GitHub projects, and so forth hosted there.
    @githg22_gitlab: There's indeed not a formatter for Q# yet, but that could be a great feature request at https://github.com/microsoft/qsharp-compiler/, or if you'd like to contribute one yourself, you may be interested in checking out some other compiler extensions such as the one @crazy4pi314 and @bettinaheim were working on in their stream yesterday at https://www.twitch.tv/videos/649894848 and in @crazy4pi314's fork at https://github.com/crazy4pi314/qsharp-compiler.
    Harshit Garg
    @githg22_gitlab

    @githg22_gitlab: There's indeed not a formatter for Q# yet, but that could be a great feature request at https://github.com/microsoft/qsharp-compiler/, or if you'd like to contribute one yourself, you may be interested in checking out some other compiler extensions such as the one @crazy4pi314 and @bettinaheim were working on in their stream yesterday at https://www.twitch.tv/videos/649894848 and in @crazy4pi314's fork at https://github.com/crazy4pi314/qsharp-compiler.

    I'll check them out thanks

    Amir Ebrahimi
    @amirebrahimi
    Well, that was a lot of fun :) I see you came out right above me @githg22_gitlab. It's quite hilarious to me how much of the time I spent was just about getting the dev environment set up, learning how the Q# QML approach is architected, and figuring out how to reduce the training time iterations.

    @amirebrahimi: This is actually a broader community for Q# developers and users, but it's really cool to see everyone from the contest! If you're interested in the Q# community, I'd encourage checking out what the Q# community has done at https://qsharp.community. There's some neat blog posts, GitHub projects, and so forth hosted there.

    Thanks, @cgranade - I remember hearing about this community a while back I think from an interview you had either on QCN or meQuanics. Good to finally jump into Q# and give it a try. It's an interesting model and very different from the rest. In some ways I feel more restricted though.

    Harshit Garg
    @githg22_gitlab

    Well, that was a lot of fun :) I see you came out right above me @githg22_gitlab. It's quite hilarious to me how much of the time I spent was just about getting the dev environment set up, learning how the Q# QML approach is architected, and figuring out how to reduce the training time iterations.

    Haha. I agree with a lot of time spent over setting up the environment.

    Chris Granade
    @cgranade
    @amirebrahimi: No worries, happy to help, and glad you're having fun jumping into Q#! If I may ask to try and understand, what do you mean by more restricted?
    @githg22_gitlab: No worries, happy to help!
    Sarah Kasier
    @crazy4pi314

    Welcome everyone, its really exciting to see so many new faces here! Hopefully the warm-ups have been going well 😄

    @githg22_gitlab I have been wanting to work on a Q# linter/code formatter for a while, that would be a great project if you wanted to collaborate with the community here! (also my code would look so much nicer :P )

    Sarah Kasier
    @crazy4pi314
    And to build on what @cgranade mentioned, the qsharp.community group is a great place for sharing and building your Q# code and knowledge! We are always looking for posts on any Q# related projects you are working on, projects for folks to collaborate building and that the community can help maintain as the language evolves. Some great examples of posts can be found on the blog and we have a growing collection of projects too! I am working on a project with some other community members where we are creating a new library to implement memory for a quantum computer (sometimes called qRAM).
    Amir Ebrahimi
    @amirebrahimi

    @cgranade - It's nuanced for me and perhaps just temporary by the current level of documentation or feature set: not being able to construct a gate from a unitary directly, not being able to easily construct a kronecker product of pauli matrices without having to create a new operation, not being able to print the circuit easily (or having the concept of a circuit), etc. I think having used Cirq a little bit and mostly having used Qiskit it's me adjusting to the difference.

    Now on the + side: I love being able to use Visual Studio (keybindings for commenting selected blocks would go a long way though!). I love having the easy connection to work with C#. I love the representation of data structures in QDK.

    Thanks, @crazy4pi314 / @cgranade - Also, happily picked up a copy of your book during ISCA 2020 w/ the promo.
    Sarah Kasier
    @crazy4pi314
    I can address maybe a little bit of this:
    • Re: the kronecker product you don't have to do this in Q#. If you want to apply say XYXZ to a register of 4 qubits you can use the ApplyPauli operation. One of the design goals of Q# is to get the user to be thinking about the algorithms at a higher level and not needing to construct matrices.
    And yeah I use visual studio code and having intelesense there is hella nice
    Chris Granade
    @cgranade

    Thanks for the feedback, I really appreciate it, @amirebrahimi! I think if I could offer some clarification as to some of what you raised, Q# really is at some level about sending instructions to a quantum device, rather than about constructing matrices for those instructions. One of the architects on the Quantum Development Kit team, Alan Geller, summarized it a couple years ago as that Q# exists "because we want to build algorithms, not circuits." From that perspective, matrix decompositions are the things we keep in our heads, or internal to the simulator as we write Q# code.

    It's entirely possible to mesh that with thinking of state vectors and unitary matrices as special kinds of programs, however. The PrepareArbitraryState operation takes an array of complex numbers describing a state vector, and uses them to prepare that state by decomposing that input into the right sequence of instructions needed to do so. The same approach would work well for inputs that represent unitary matrices, of course; if you're interested, that could be a great feature request or even contribution.

    In any case, we definitely really appreciate the feedback; I'll be sure to pass that along. Thanks as well for picking up our book, @crazy4pi314 and I really appreciate it!
    Sarah Kasier
    @crazy4pi314

    Seconded! :sparkling_heart:

    To the bit about not really using circuit representations, that goes to the design goal again where the user shouldn't need to think about specific gate sequences (people building the language and runtime are) to be able to code their quantum program. As a former QC researcher myself who really liked the circuit representations (I was an experimentalist :P ), I have really grown to like not having to use them, and thinking more like I would for writing in any other programming language when I write quantum code (maps/apply/list comprehensions/types etc.).

    Sarah Kasier
    @crazy4pi314
    .m. Me mm
    Amir Ebrahimi
    @amirebrahimi
    Thank you both for this information. Since this is a different approach it might be helpful to call it out from the outset in the documentation for newcomers. I find that "setting the frame" can help to put someone into a specific mindset. Ideally, I'd put this info at every entry point where Q# is mentioned in the docs. I'd be happy to make the PR to the docs assuming this is agreeable, @cgranade. NM, for some reason I thought that the docs were in a github repo. I can create an issue for it though if preferred.
    Sarah Kasier
    @crazy4pi314
    You can find a list of the official repos in the docs or on https://qsharp.community/resources/#
    Amir Ebrahimi
    @amirebrahimi
    Ahh...in that case, I'll just wait to hear from you @cgranade if you like what I'm proposing.