You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
What is the expected feature or enhancement?
I think the documentation of Sampler should be updated. For example, I create a circuit from composer and run it on ibm_brussels, then when loading data the approach on this website does not work. Instead, I use something below to extract the shot information.
Moreover, I think now you are outputing the measurement result for each time with a hex format number and I found that if using the suggestion conversion from GPT-o3-mini, some will only output a single string (e.g., '0'). Keep in mind that the order of output string really matters when doing post-processing so I think when upgrading your documentation, you had better to add the code to help user convert.
---from a Premier Plan user
The text was updated successfully, but these errors were encountered:
Hi @dawei-zh thanks for opening an issue - we double checked the code in the link you sent and were not able to reproduce the issue you are facing. This means the issue is likely something to do with your job or the circuit you were trying to run, not the documentation. If you can send more code with the circuit you were trying to run we can take another look, or as a premium plan user you can reach out to IBM Quantum Support for personalised help debugging your code
Hi @javabster Thanks for your comments and I try to run a sampler job this morning. It seems that the Sampler works properly right now but I still have the confusion, since I saw something on the previous screenshot two weeks ago. I put my jupyter-notebook here (https://github.com/dawei-zh/issues-reproduce/blob/main/qiskit-feedback-new.ipynb) and I appreciate that you take a look at it.
What is the expected feature or enhancement?
I think the documentation of Sampler should be updated. For example, I create a circuit from composer and run it on ibm_brussels, then when loading data the approach on this website does not work. Instead, I use something below to extract the shot information.
Moreover, I think now you are outputing the measurement result for each time with a hex format number and I found that if using the suggestion conversion from GPT-o3-mini, some will only output a single string (e.g., '0'). Keep in mind that the order of output string really matters when doing post-processing so I think when upgrading your documentation, you had better to add the code to help user convert.
---from a Premier Plan user
The text was updated successfully, but these errors were encountered: