1
$\begingroup$

I have noticed that the csv files exported for results don’t have the resolution to correctly describe the output states for larger sets of qubits. It looks like it only exports numbers up to 15 digits long without cutting them. For example, if I try to get results on 17 qubits, it doesn’t carry the information about the last two numbers, so when I change the format to “custom”, in Excel, with 17 0’s, and I have done a circuit with qubits 0, 1, 15 and 16 in superposition and the rest left as 0, there will be, for example, 4 results at the end listed as “11000000000000000”.

Has this been addressed before? Am I doing something wrong? Is there a solution?

Improve this question
$\endgroup$
0

1 Answer 1

Reset to default
2
$\begingroup$

I think the problem you are experiencing comes from Excel and not IBM Quantum Experience. Check this explanation, it explains why the bug you have happens, and ways to work around it.
Hope this will help :)

Edit : I think I found another workaround to your problem. Try this and tell me if this works for you:

  1. Download the CSV file but don't touch it yet.
  2. Open a new Excel file.
  3. Click the "Data" tab, then click on "Get data" on the upper left, then "From file", then "From text/CSV".
  4. Choose your CSV file you want to download.
  5. Normally, at this point you should have a window popping to your screen, and at the bottom of it 3 buttons, "Load", "Transform data", and "Cancel". Click on "Transform data".
  6. Select the first column (the one with all the states) then click on the "Transform" tag at the top of the window, you should have an option right below "Data type : Decimal number". Click on this and select "Text". Click on "File" and select "Close and load".

When I do this, the sheet downloads well and I have the full state written without the bug you mentioned. Does this work for you?

Improve this answer
$\endgroup$
2
  • $\begingroup$ This doesn't work, unfortunately. Changing the cells to text makes the cells say what they originally upload as e.g.: 1.1E+16 and 11000000000000000 in the text box. Changing to numbers first has the same effect. This fix only works if you already know what the number is, and can therefore type it in manually. With this data, you don't know what the number is in order to manually type it. $\endgroup$
    – Requiem
    Jul 22, 2020 at 8:44
  • $\begingroup$ Excel has several limitations for binary numbers. In particular it only knows how to handle binary numbers, and their conversion, for 10 bits or less: support.microsoft.com/en-us/office/… $\endgroup$
    – Paul Nation
    Jul 22, 2020 at 9:37

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service and acknowledge that you have read and understand our privacy policy and code of conduct.

Not the answer you're looking for? Browse other questions tagged or ask your own question.