Split visualization page into three

[frankharkins]

Continuation of #971

The circuit visualizations are most valuable in the build stage of the circuit. This splits the results visualization into a separate file for the analysis/post-processing stage. Additionally, it makes sense to split the quantum information visualizations into the verify (or learning) step.

Preview quick links

• analyze/visualize-results
• build-new/circuit-visualization
• build-new/plot-quantum-states

[review-notebook-app]

Check out this pull request on 

See visual diffs & provide feedback on Jupyter Notebooks.

---

Powered by ReviewNB

[abbycross]

Nice job and I love the use of the tabs for the different visualization types! Super cool. I had some lightweight suggestions and also pushed some changes from my local branch - hope that's ok; feel free to revert anything you don't like!

[Eric-Arellano]

It'd be helpful to talk about how to visualize results for the Estimator primitive. In Hello World, we use plt.errorbar, but I think @kaelynj and Kevin were saying another type of graph would be more useful.

[frankharkins]

Good call, I've had a go at that in Plotting estimator results. I'm gonna get some more reviewers though as my stats knowledge is quite shaky.

[frankharkins]

@abbycross

Oh dear - I see we have both statevector and state vector all throughout our docs, when I do a search! So I don't even know which one to suggest you change to in this PR.... 👀

I think the "correct" term is state vector, but statevector is a common compouding that happens quite a lot within Qiskit (e.g. we called the class Statevector rather than StateVector).

IIRC we discussed this at some point with Jennifer and Becky and decided to double down on the compounding and go with "statevector", but I'm not 100% sure about that and can't find the conversation. I've changed all instances in this PR to statevector for now but we can easily switch back if needed.

[abbycross]

@abbycross

Oh dear - I see we have both statevector and state vector all throughout our docs, when I do a search! So I don't even know which one to suggest you change to in this PR.... 👀

I think the "correct" term is state vector, but statevector is a common compouding that happens quite a lot within Qiskit (e.g. we called the class Statevector rather than StateVector).

IIRC we discussed this at some point with Jennifer and Becky and decided to double down on the compounding and go with "statevector", but I'm not 100% sure about that and can't find the conversation. I've changed all instances in this PR to statevector for now but we can easily switch back if needed.

I remember we had a conversation too but couldn't find where we landed with it! I'm good to leave it compounded.