Where communities thrive


  • Join over 1.5M+ people
  • Join over 100K+ communities
  • Free without limits
  • Create your own community
People
Activity
    Esteban Ginez
    @eginez
    hello all and thanks Sarah for the invite
    super trivial PR: qsharp-community/qsharp-integrations#4, for when you guys get some time :D
    Sarah Kasier
    @crazy4pi314
    @eginez Welcome! and thanks for the contribution! I would love to discuss with you a blog post on getting started in Q# in spanish 💖
    Esteban Ginez
    @eginez
    for sure happy to help
    Robert Rand
    @rnrand
    Hi everyone! What's the go-to place for Q# related programming questions?
    Sarah Kasier
    @crazy4pi314
    @rnrand Here is a pretty good option, else https://quantumcomputing.stackexchange.com/ is pretty active with Q# folks!
    Joe Clapis
    @jclapis
    Hi all, I just published a VS extension that brings automatic doc comment generation to Q# (like how it works for C#'s XML comments): https://marketplace.visualstudio.com/items?itemName=JoeClapis.QSharpTripleSlash
    Sarah Kasier
    @crazy4pi314
    Oh awesome!! Would you be interested in writing a short something about that we can post on the blog? I have been wanting something like this for a while instead of copy pasta 😆
    Joe Clapis
    @jclapis
    Sure, what do you have in mind? Like, what it does and why I made it or something?
    Sarah Kasier
    @crazy4pi314
    Yeah, I think that makes sense! I went looking for a similar style post, and I think something like this is what I was thinking: https://dev.to/mgranados/built-my-first-chat-app-with-react-hooks-exclusively-it-was-great-14dj
    Something short that has some examples of how you use the extension and what motivated you :)
    You can just make a PR with the markdown file for the post here: https://github.com/qsharp-community/qsharp-community.github.io/tree/master/_post and if you have any questions let me know!
    Rolf Huisman
    @RolfHuisman
    Agree, thats indeed a cool extension.
    Joe Clapis
    @jclapis
    @crazy4pi314 okay, I wrote up a thing for you: qsharp-community/qsharp-community.github.io#7
    Sarah Kasier
    @crazy4pi314
    @/all :tada: New blog post up thanks to @jclapis :tada:
    They made a Visual Studio extension that helps make writing Q# docs easier! :sparkling_heart:
    https://qsharp.community/blog/qsharp-triple-slash/
    also @jclapis do you have a twitter/insta you want me to tag when I post about this on the community social media accounts?
    Joe Clapis
    @jclapis
    Thanks Sarah! I don't have a Twitter or IG account. I guess if someone wants to poke me, they can just do it on here?
    Sarah Kasier
    @crazy4pi314
    Anyone have any cool projects they are working on?
    Aaron Hadley
    @aahadley

    Not sure if this is still active, but I'll try.

    In the C# driver, we use .wait() because the Q# code is run asynchronously. Is this not needed in Python or is there an equivalent operation that I need to use?

    Also, (in response to your question from August) I'm working on mapping qubit states to RGB color space so we can build a quantum circuit visualizer with Arduino+Pi.
    Sarah Kasier
    @crazy4pi314
    @aahadley Oh dang this is awesome!!
    Sarah Kasier
    @crazy4pi314
    wrt your question, though likely you have figured it out by now, but the .simulate() method should return the results of the Q# function or operation: https://github.com/microsoft/Quantum/blob/67f75e857c26c68168c0d404dc879abeee1682dd/samples/getting-started/intro-to-iqsharp/Notebook.ipynb#L346
    No additional operations needed I think
    cgranade @cgranade waves hi from the Q# development team. @crazy4pi314 has it exactly right, the .simulate() method in Python returns a value, while the .Run() method in C# host programs returns a task that needs to be awaited on. We're in the process of clarifying this in documentation, so we really appreciate the feedback! 💕
    Aaron Hadley
    @aahadley
    beautiful. Thank you both!
    Chris Granade
    @cgranade
    Happy to help!
    If you're interested, by the way, I put together a very quick sample of calling .simulate() from Python: https://mybinder.org/v2/gh/cgranade/6e1d177dc33f0bb34132319672c149bf/master
    Sarah Kasier
    @crazy4pi314
    Some exciting new news today from Microsoft Ignite today! https://twitter.com/QSharpCommunity/status/1191385169669873665?s=20
    Azure Quantum now will let you requisition quantum hardware resources in the cloud and run the same Q# code you develop on whatever target machine you want!
    Sign up for early access to this open source platform here: https://azure.microsoft.com/en-us/services/quantum/#contact
    Aaron Hadley
    @aahadley
    This is great news. And welcome to Orlando!
    Sarah Kasier
    @crazy4pi314
    Is anyone else here at Ignite?
    Aaron Hadley
    @aahadley
    Didn't get in ☚ī¸ but I'm in town 😃
    Sarah Kasier
    @crazy4pi314
    Dang! I should have asked sooner, I fly out in the morning :( But good news, I have lots of new ideas for projects now that we can run Q# ON HARDWARE :D
    Esteban Ginez
    @eginez
    hey all I have been reading some of the q# compiler code, so far I am a bit fuzzy on what the output of the compiler is? is it C# code? that seems to be the case right?
    also I was going thru some of the optimizations the compiler has and I think it be interesting to implement a few more, for example DeadCode elimiation is a typical one that could be added
    bettinaheim
    @bettinaheim

    @eginez Cool that you've looked at the compiler code! Let me give what I hope are some helpful pointers where to find things:

    The output of the compiler right now is binary json (that may change in the future) and/or a dll that contains the same as resource (that might also change). Both at the moment contain the data structures here: https://github.com/microsoft/qsharp-compiler/blob/master/src/QsCompiler/DataStructures/SyntaxTree.fs
    That output can be loaded by the compiler e.g. via the CompilationLoader: https://github.com/microsoft/qsharp-compiler/blob/bd09e7c63adf0d9420399c451d2e4a2e0c6b8479/src/QsCompiler/Compiler/CompilationLoader.cs#L747.

    The command line compiler (https://github.com/microsoft/qsharp-compiler/tree/master/src/QsCompiler/CommandLineTool) allows to pass arbitrary .NET Core dlls via the handle --load path/to/your/dll that are invoked at the end of the compilation process. Any class implementing IRewriteStep in that dll will be executed as part of the compilation process (at the end of it). An example that invokes the C# generation in this way can be found here: https://github.com/microsoft/qsharp-compiler/blob/master/src/QsCompiler/TestTargets/Simulation/Target/Program.cs

    It would be terrific to get some additional optimizations! Sounds like you have already found the project that one of my interns (Rory Soiffer) started this summer: https://github.com/microsoft/qsharp-compiler/tree/master/src/QsCompiler/Optimizations/OptimizingTransformations. I am happy to assist with pointers and such on how to add more! :)

    Esteban Ginez
    @eginez
    sweet @bettinaheim, thanks for the pointers. I'll keep looking around the source code
    one follow up question what project turns the bson into architecture specific asm?
    bettinaheim
    @bettinaheim
    Hi @eginez,
    Sorry for the delay in response. Targeting executables for particular hardware is currently work in progress. In particular, the compiler so far does in fact not have a handle to receive the information regarding what the execution target is - that should be amended shortly. There is definitively a long way to go to build a full compilation process and a prototypical runtime that will make this as universal and useful as it is intended to be. If you have more specific questions related to targeting and/or are interested in contributing a particular functionality I may be able to give you a more useful answer. :)
    Sarah Kasier
    @crazy4pi314
    Hey @/all , check out the Q# advent calendar for some project inspiration! There are also still some slots left later in the month if folks are interested in contributing.
    Esteban Ginez
    @eginez
    great thanks for the info @bettinaheim
    I was reading this paper a couple of days ago (Compiling SU(4) quantum Circuits to IBM QX Architectures https://arxiv.org/pdf/1808.05661.pdf) and it inspired me to look at q# in more detail
    I tried running some of the compiler unittests but I found some build problems with it, probably mac os related. I'll send a PR once I figure out what is going on with the test target
    bettinaheim
    @bettinaheim
    @eginez Sorry about that! If you let me know in more detail what the build error is I may be able to help? Also, please be sure to pull the latest master - we had a PR for some Mac related build issues just recently.
    Esteban Ginez
    @eginez
    will do
    Esteban Ginez
    @eginez
    hey all I wrote a blog post on my experiences of building the q# compiler on mac os x: http://www.eginez.xyz/post/qsharp_macos/
    hope you all find it interesting
    Sarah Kasier
    @crazy4pi314
    @cgranade wrote an awesome post on what it's like to be a quantum developer at Microsoft! https://dev.to/cgranade/what-is-a-quantum-developer-anyway-38l
    bettinaheim
    @bettinaheim
    @eginez Cool post - I love it! I think I've already given the explicit disclaimer that the data structures that the compiler output may/will change in the future, so you should not rely on them. However, the API of the CompilationLoader that allows to read the output back in should be stable-ish. FYI, this might also be of interest to you: https://github.com/microsoft/qsharp-compiler/tree/master/src/QuantumSdk (early alpha version obviously, and I'm happy for feedback).
    Sarah Kasier
    @crazy4pi314
    Anyone have some cool projects they are working on?