State
Hamiltonian whose eigenvalues are wanted
A Hamiltonian you can query, plus the declaration that what is being asked for is a piece of its spectrum rather than an evolution under it. Which piece — the bottom of it, or a state above the bottom — is the next distinction down, and the two are separate states because the methods that answer them do not substitute for one another.
A state is an object you can be holding, named once so that two routes reaching the same thing are drawn as reaching the same thing. It says nothing about how you got here or where you can go next — that is entirely in the processes below.
This is a kind of
Anything that asks for one of these will accept this, because it is narrower. The reverse does not hold.
- Hamiltonian you can query
A Hermitian operator reachable as a sum of terms you can exponentiate one at a time, as sparse-access oracles, or as a block-encoding — plus the norm parameter the simulation cost will be quoted against.
- Matrix you can query
Some way of asking about a matrix without writing it down — sparse row and column oracles, a Pauli or LCU decomposition, a purification, or an explicit arithmetic rule. Which one you have decides which routes are open.
Narrower kinds of this
- Hamiltonian whose ground state is wanted
A Hamiltonian you can query, plus the declaration that the quantity being asked for is its lowest eigenvalue. The second half is not decoration: the same operator can be handed to a simulator to evolve a state under it, and evolving it and minimising it are different questions with different answers.
- Hamiltonian whose excited state is wanted
A Hamiltonian you can query, plus a declaration of which state above the lowest one is being asked for — the k-th, the lowest in a chosen symmetry sector, or the one nearest a target energy. That target is part of the problem, not a setting: a method that finds the ground state has not answered this question, and most methods here need the ground state before they can start.
Records that are this object
Nothing in the catalogue has been joined to this state. That is a gap in the join rather than a claim that no such object exists; the shelf on /repository lists what is joined and what is not, with the reason.
Work that arrives here
No recorded process returns this. Either it is where a reader starts — a problem, a matrix, a machine — or it is an object this graph names and no route yet reaches.
Work that starts here
- Choose a parameterised trial state
Fix the gate structure of a circuit family and leave its rotation angles open. What comes back is not a circuit but the set of states the later optimisation is allowed to search — which is why this is a slot of its own and not a paragraph in one method's write-up.
Also accepted where something broader is wanted
These ask for an object this one is a kind of. Narrowing composes in that direction and only that direction: handing on something broader than a process asks for would be a skipped conversion.
- Block-encode a matrix
Wrap an operator inside a larger unitary so that sits in 's top-left block, giving every routine above it one uniform way to touch the matrix. The subnormalization and the ancilla count are outputs of this layer, not free parameters.
- Simulate Hamiltonian evolution
Implement to error given some access model for . It is an application in its own right and also the engine inside phase estimation and several linear-system solvers.