Skip to content

feat(QuantumMechanics): Hamiltonian and related operators of the Pöschl-Teller system - #1651

Open
KevorkianPhilippe wants to merge 1 commit into
leanprover-community:masterfrom
KevorkianPhilippe:poschl-teller-1
Open

KevorkianPhilippe wants to merge 1 commit into
leanprover-community:masterfrom
KevorkianPhilippe:poschl-teller-1

Conversation

@KevorkianPhilippe

Copy link
Copy Markdown
Contributor

Resolves the TODO "Define the Hamiltonian and related operators for the Pöschl-Teller quantum system" of QuantumMechanics/PoschlTeller/Basic.lean, by filling the empty sections C.1 (kinetic energy), C.2 (potential energy), C.3 (Hamiltonian) and D (as a quantum system) of that file on the model of SpaceDQuantumSystem, and by adding the properties of the potential that make these operators usable.

Section A (potential). New depth = ℏ² κ² N (N + 1) / (2 m) with potential_eq (V = -depth / cosh² (κ x)), potential_eq_tanh (V = -depth (1 - tanh² (κ x))), depth_pos, potential_neg, neg_depth_le_potential, potential_zero, potential_neg_eq (even), and the regularity lemmas tanh_hasTemperateGrowth, ofReal_comp_tanh_hasTemperateGrowth, potential_hasTemperateGrowth (from tanh_const_mul_hasTemperateGrowth composed with the coordinate), ofReal_comp_potential_hasTemperateGrowth, potential_continuous.

Section C (operators). kineticCLM = (2m)⁻¹ 𝐩 ⬝ᵥ 𝐩 with kineticCLM_apply (dimension one), potentialCLM = smulLeftCLM ℂ (ofReal ∘ potential) with potentialCLM_apply, hamiltonianCLM with hamiltonianCLM_apply; the unbounded kineticOperator, potentialOperator (with potentialOperator_isSelfAdjoint and schwartzSubmodule_le_potentialOperator_domain) and hamiltonianOperator. For the existing ladder operators: tanhCLM_apply, creationCLM_apply, annihilationCLM_apply, and the relations creationCLM_add_annihilationCLM (= (2/√(2m)) 𝐩 0) and creationCLM_sub_annihilationCLM (= (2 i ℏ κ/√(2m)) tanhCLM).

Section D. toSpaceDQuantumSystem : SpaceDQuantumSystem of dimension 1, with toSpaceDQuantumSystem_hamiltonianCLM and toSpaceDQuantumSystem_hamiltonianOperator (both rfl), so that the generic results on SpaceDQuantumSystem apply to this system.

Not touched: the eigensystem via the ladder operators and the reflectionless property (the two other TODOs), which need the commutator of 𝐩 with tanh (κ X).

Changes to existing content: only the TODO line removed, the SpaceDQuantumSystem import added, and MeasureTheory, SpaceDHilbertSpace opened; the key results and the table of contents are filled in.

Checks: lake build, lint-style.sh, runPhyslibLinters, check_file_imports, codespell; standard axioms only.

AI disclosure. The statements were frozen first (with sorry) and their proofs were produced by Kimi K2.7 Code (Moonshot AI) running in the DeepSeek Harness against physlib, then rewritten and shortened by Claude Fable 5.1 (Claude Code) for the physlib style (in particular the continuity of the potential now follows from its temperate growth); a type-identity check between the frozen statements and the final lemmas was compiled. I reviewed the statements, the docstrings and the proofs.

🤖 Generated with Claude Code

…hl-Teller system

Fill the kinetic, potential and Hamiltonian sections of the Poschl-Teller module on the
model of SpaceDQuantumSystem (Schwartz-space and unbounded versions), add the depth of the
well and the sign, bounds, parity, temperate growth and continuity of the potential, the
pointwise formulas of the ladder operators and their sum and difference, and realise the
system as a SpaceDQuantumSystem of dimension one. Resolves the corresponding TODO.
Proofs first produced by Kimi K2.7 Code in the DeepSeek Harness, rewritten for physlib.

Co-authored-by: Claude Fable 5.1 <noreply@anthropic.com>
@github-actions

Copy link
Copy Markdown
Contributor

Thank you for this pull-request (PR). If this is your first PR, welcome to the community!

Below is what will happen next. Please read carefully if you are not familiar with the process. You may open other PRs while this one is being reviewed, and can stack PRs on top of each other, so don't let these steps slow you down.

  1. Some automated checks will be run on your PR. You can see the results of these checks at the buttom of your PR page. If any of these checks fail, you will need to fix the issues before your PR can be merged. You can learn more about these here, including how to run them locally, which is sometimes quicker than relying on the GitHub Actions. If you have never had a PR merged before, you may have to wait for a reviewer to manually start these checks (this is for security).

  2. A reviewer will look at your PR and may ask you to make changes. This may happen a couple of days after you submit your PR, so you may need to be patient. But it should not be longer than that - if it is please bring it to the attention of the community on the Zulip. The level of review will depend on where your PR is submitted. If it is submitted to ./Physlib or ./QuantumInfo, the review will be more thorough than if it is submitted to ./PhyslibAlpha. You can find out more about what the review process is looking for in our review guidelines. If a reviewer adds an awaiting-author label to your PR, address the review comments, then please remove that label by adding a comment with -awaiting-author. This helps us keep track of reviews.

  3. The reviewer will either approve your PR, or request more changes (in which case we return to step 2). Once your PR is approved, it will be merged by a maintainer, this should happen shortly after approval, though you may get more comments at this stage.

Tip: The easiest way to get have a fast review is to submit a PR that is small and self-contained, and has clear documentation explaining why things are the way they are in your chages.

If you have any problems or questions, please reach out to the community on the Zulip.

@github-actions github-actions Bot added the t-quantum-mechanics Quantum mechanics label Sep 11, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant