Qiskit / Qiskit/documentation

Incorrect weak-coupling justification in LSH hadron dynamics tutorial

Open
#5,666 0 comments 0 reactions 1 assignee View on GitHub

@nathanearnestnoble is already working on this.

Since Sep 16, 2026.

content 📄 tutorial 📒
Dominant language
Jupyter Notebook
Stars
106
Forks
223
Avg merge
1d 8h
Merged PRs (30d)
72

Description

URL to the relevant tutorial

https://quantum.cloud.ibm.com/docs/en/tutorials/loop-string-hadron-dynamics

Select all that apply
  • new content request
  • typo
  • code bug
  • out-of-date content
  • broken link
  • other
Describe the fix or the content request.

The tutorial incorrectly states:

In the weak-coupling regime ($x\gg1$), the dynamics is dominated by the electric term $H_E$, which favors states with large $n_l$.

From the Hamiltonian

$$
W=H_E+\mu H_M+xH_I,
$$

we see that large $x$ instead makes the off-diagonal term $xH_I$ dominant. This agrees with the original paper. It is in the strong-coupling regime that $H_E$ dominates; there, flux is energetically expensive and the vacuum has $n_l=0$.

Large $n_l$ is a separate modeling choice motivated by a weak-coupling vacuum ansatz. The authors choose a large incoming boundary flux, producing a large, approximately uniform flux across the lattice. This allows flux-dependent hopping prefactors such as

$$
\sqrt{\frac{n_l}{n_l+1}}
$$

to be approximated by one.

Suggested correction

In the weak-coupling regime $x\gg1$, the off-diagonal interaction term $xH_I$ dominates. The weak-coupling vacuum is modeled using a large incoming boundary flux, giving $n_l\gg1$ across the lattice. The resulting $n_l$-dependent hopping prefactors approach one, simplifying $H_I$ to nearest-neighbor hopping on the fermionic qubits.

For new content requests - if the request is accepted, do you want to write the content?

(No answer)

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.