Here are some examples:

• Root README is missing machine learning category of samples
• README in algorithms is missing repeat-until-success and sudoku-grover
• [README in diagnostics](https://github.com/microsoft/Quantum/blob/main/samples/diagnostics/RE

What is the expected enhancement?

Currently, the CircuitSampler requires a parameter binding dictionary in the following format
{‘a’: [0]}, i.e. it requires an iterable to be assigned to a parameter.
The foll

Include a script that can generate weekly status reports to dev's leadership. The report should have enough buzzwords to make leadership feel as if progress is being made without providing any specific detail that defines said progress.

QuTiP currently uses QCircuit 2 (version of 2011) to generate LaTeX circuits that are printed to screen or saved to file. A newer version of QCircuit is available, 2.6.0 (2018) https://www.ctan.org/pkg/qcircuit.

• qcircuit could be updated to the latest version

• Also, the use of this open source package could be highlighted more evidently in the documentation.

• Another package has be

It would be nice to allow users to set a custom value for the tensorflow dtype if they are really pushing their simulations (and aware of the memory tradeoffs). This would be a very straightforward feature to add, most likely by adjusting backend_options to accept a dtype argument or something similar

See, e.g., the discussion below:

You could change this line https://github.com/XanaduAI

Most documentation comments in the compiler only use the <summary> tag. For short comments, this is fine, but in many cases the summary is several paragraphs long and would be easier to read if it used standard documentation tags to structure the information. This is especially important for exceptions - exceptions mentioned in the <summary> tag are easy to miss, whereas the special `<exceptio

Describe the bug
If I provide Partitioned an array of length N and partition sizes of total length N, the return contains an extra partition of length 0 in the end. This makes it inconvenient to use: if I want to split an array into K parts of equal length ([example](https://github.com/microsoft/Quantum

Now, there's no unit test.

It would be helpful to add a tutorial explaining how to run things in parallel (mpirun etc). There are some users who are not familiar with mpi (see #173 ) and it is useful to explain the basic steps to do this.

When the Q# entry point has a parameter with no associated documentation, the description of the option on the command line is blank:

@EntryPoint()
operation Foo(myParam : Int) : Unit {}

> dotnet run
Option '--my-param' is required.

Usage:
  App [options] [command]

Options:
  --my-param <my-param> (REQUIRED)
  -s, --simulator <simulator>         The name of th

We need to create a Q.History documentation page that is similar in nature to the existing Q class documentation pages. See Q-ComplexNumber.html as an example.

Whenever a slide has minted code, like so:

\begin{frame}[fragile]{Example minted}
	\begin{minted}{python}
		from qiskit_aqua import run_algorithm

		print(run_algorithm(params)['result'])
	\end{minted}
\end{frame}

One is unable to add the \pagenumber before \end{frame} as it gets left aligned instead of right aligned:
![image](https://user-images.githubusercontent.com/1