Skip to main content

General Ideas and Feature Requests

General questions and feedback on Microsoft's Quantum Developer Kit

(thinking…)

Enter your idea and we'll search to see if someone has already suggested it.

If a similar idea already exists, you can support and comment on it.

If it doesn't exist, you can post your idea so others can support it.

Enter your idea and we'll search to see if someone has already suggested it.

  1. Memory allocation and de-allocation peaks with (Controlled X) operations

    Hello,

    I've posted on the Quantum Dev Kit GitHub page about bad simulation performance when testing the Grover algorithm (found in the 'Samples' folder) for larger databases: https://github.com/Microsoft/Quantum/issues/42 .

    This is due to a large memory allocation and de-allocation done by the operation '(Controlled X)' if it has a large number of controlling qubits, and at least one non-zero controlling qubits. During this process, most OMP threads stay in a "wait" state, indicated by the low CPU usage.

    Here's a small sample Q# operator with this behavior. It uses 13 qubits, and the peak memory usage is around 3Gb. The…

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  2. Bug : Saved the code, but no effect in the results.

    example) Bell State have two source code. (Driver.cs, Operation.qs)

    1. save Driver.cs

    2. edit Operation.qs

    H(qubits[0]);
    let res = M (qubits[0]);

    3. save Operation.qs and run

    Init:Zero 0s=482 1s=518
    Init:One 0s=462 1s=538
    Press any key to continue...
    -----------> result is correct <-------------

    4. edit Operation.qs

    X(qubits[0]);
    let res = M (qubits[0]);

    5. save Operation.qs and run

    Init:Zero 0s=482 1s=518
    Init:One 0s=462 1s=538
    Press any key to continue...
    -----------> result is incorrect <-------------

    6. save Driver.cs and run

    Init:Zero 0s=0 1s=1000
    Init:One 0s=1000 1s=0
    Press any key to continue...
    -----------> result is correct <-------------

    7.
    I think edit .qs code, save…

    1 vote
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    1 comment  ·  Flag idea as inappropriate…  ·  Admin →
  3. Bug in Microsoft.Quantum.Development.Kit.props in nuget package

    When attempting to use the QDK, I had an issue where nothing would build. After some troubleshooting, I found that the build command that invokes qsc.dll was failing to find that dll as the path to it (in a folder off .nuget off my home directory) contained a space (my home directory's full path has a space in it). The path, as outlined in the Microsoft.Quantum.Development.Kit.props file did not quote the path.

    This was on a Mac, running MacOS 10.13.3.

    This section...

    <PropertyGroup>
    <QscExe Condition="'$(QscExe)' == ''">dotnet $(MSBuildThisFileDirectory)../tools/qsc/qsc.dll</QscExe>
    <QDocGen Condition="'$(QDocGen)' == ''">dotnet $(MSBuildThisFileDirectory)../tools/qdocgen/qdocgen.dll</QDocGen>
    </PropertyGroup>

    Needed to be changed to this...

    2 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  4. Port to .NET Core

    If I understand it correctly, the current QDK (simulator, compilator, libraries and tooling) targets .NET Framework 4.6.1

    I suggest you make an effort to port at least the simulator compilator and libraries to .NET Core, so that it will be possible to use it cross-plattform (Windows, Linux, MacOS)

    4 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    0 comments  ·  Flag idea as inappropriate…  ·  Admin →
  5. Q# compiler fails with decimal separator other than .

    As explained in https://github.com/Microsoft/Quantum/issues/6

    Using a decimal separator other than . (i.e. "," for German computers) will fail to compile even the example libraries. The issue can be fixed by changing the separator, but this is breaking, as it will interfere with all other software on the computer.

    By @StLange:
    "That means there is at least one double to string conversion in the Q# compiler that misses CultureInfo.InvariantCulture and uses regional number format (German uses comma as decimal point)."

    12 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    4 comments  ·  Flag idea as inappropriate…  ·  Admin →
  6. 7 votes
    Sign in
    Signed in as (Sign out)

    We’ll send you updates on this idea

    2 comments  ·  Flag idea as inappropriate…  ·  Admin →
  • Don't see your idea?

General Ideas and Feature Requests

Feedback and Knowledge Base