@theRomanMercury @githg22_gitlab: That sounds like an issue with the
DOTNET_ROOT environment variable. This blog post has some good advice for debugging DOTNET_ROOT issues on Linux: https://natemcmaster.com/blog/2018/05/12/dotnet-global-tools/#common-errors
Just wanted to post this here, but if you are working on any Q# project and want to collaborate with Q# community or write a post about your project, let us know! https://qsharp.community/blog/call-for-contributions/
However, I've got a new problem.
I am trying to follow along with the debugging tutorial - https://docs.microsoft.com/en-us/quantum/user-guide/using-qsharp/testing-debugging?tabs=tabid-vscode
It says that I have to create a new project using dotnet new xunit -lang Q# in my terminal.
But doesn't xunit only provide C#, F# and VB? How can I get it to install another language? I thought we could only install new templates?
@achieveordie: If you run
dotnet new -i Microsoft.Quantum.ProjectTemplates, that should provide you with versions of the console, classlib, and xunit templates for use with Q#. If you run dotnet new --list, that will then show you a list of all your installed templates, including what languages you have versions of those templates for. The xunit template for Q# sets up a basic Q# unit testing project that uses the @Test("QuantumSimulator") Q# attribute to denote operations that should be run as unit tests; the Quantum Development Kit will then turn those unit tests into xunit facts, so that they work with the dotnet test command.
FYI, for anyone working through the basics of gates and so on I've found that the symbolic calculator here https://www.symbolab.com/solver/matrix-vector-calculator is a useful aid.
@kevinmcfarlane Something I've found really helpful for working through the linear algebra for quantum computing is to use NumPy to perform calcultions. QuTiP is also a great library for understanding quantum computing, and is more specialized to quantum than NumPy. Both can work great for helping to learn the math being quantum computing.
@kevinmcfarlane Another great option, though, is to use the Microsoft.Quantum.Diagnostics.DumpMachine and DumpRegister callables to explore how different operations modify the state of your simulator as you run them.
Quantum computing questions are fine here @achieveordie, but if you need fancier formatting/longer posts you can also post on the quantum computing stack exchange and link us here!
And don't forget, #QuantumDevelopWithMe will be on twitch.tv/crazy4pi314 in ~2h where I'll be working on the qRAM library for Q#!
@crazy4pi314 I thought the same too, it would have been painful to format the question here, here's the link to my question on SE - https://quantumcomputing.stackexchange.com/questions/12410/creating-a-w-state-for-2k-qubits Thanks a lot for the help! :)
I'm having a hellova' time trying to install iqsharp on jupyter. I keep getting error messages about not being able to acquire a lock. I think it's a dotnet problem, but I'm not familiar with either dotnet or jupyter. Searching on the error message hasn't helped. What can I try next?
@cgrande Oops! "No namespace with the name "Microsoft.Quantum.Intrinsic" exists." Is that possibly because my package versions don't match?
@cgranade (both In[1] and Out[2], that is)
@allmycode_twitter: I'll admit it's a bit hard to diagnose without a bit more detail, sorry. Some screenshots in particular would help provide context. The chat here supports images with
![]() notation, or you can file an issue either at https://github.com/microsoft/iqsharp/ for IQ# issues or https://github.com/microsoft/QuantumKatas/ for kata issues with more detail about the context in which you're encountering these errors. That in turn could help us solve the problem better. That said, in the meantime, installing IQ# as an administrator isn't generally necessary unless your Jupyter installation is locked to Administrator only; in that case, you can always opt for a user-local installation by using dotnet iqsharp install --user instead.
@allmycode_twitter Thanks, that helps a lot! In the first screenshot, you can see that the version of Microsoft.Quantum.Standard is 0.11.2006.403 doesn't match the version of Microsoft.Quantum.Katas, 0.11.2004.2825. It looks like the katas haven't been updated to support the latest version of IQ#, such that I'd recommend using the Binder deployment, or explicitly installing version 0.11.2004.2825 of IQ# locally instead of the latest. You can also file an issue at https://github.com/microsoft/QuantumKatas/issues about the versions of IQ# supported by the katas.
@allmycode_twitter It's this issue: microsoft/QuantumKatas#261. The reason is the leftover build artifacts from building on a previous version of Q#; once you remove bin and obj folders and restart the notebook, the error should disappear.
There aren't any obj or bin folders in the SingleQubitGates folder 
@VashisthMalik_twitter The contest announcement has a lot of starting links, two good resources are https://docs.microsoft.com/quantum and https://github.com/Microsoft/QuantumKatas/, the latter have a lot of practice problems with solutions worked out. Enjoy the contest!
@githg22_gitlab: Taking a hint from the problem statement itself, I'd suggest that the last sentence is especially relevant here.
"This operation can be implemented using just the X gate and its controlled variants."
And I can't find a way to test it locally through python
I've got a small question, Can we apply the unwrapping operator on LittleEndian? I don't think we can do that because of the no-clone theorem, I can solve the increment problem with array of qubits, but cannot wrap my mind to do that on LittleEndian. I couldn't find any relevant operation in Microsoft.Quantum.Arithematic to apply X gate on Little Endian either...
Just write
!
Just write
register!
Stupid gitter
LittleEndian is basically a different name for Qubit[], literally no other difference
I mean, I get what you mean, but I still find it a bit uncomfortable without having to use
using()