leanprover-community / leanprover-community/physlib

API: Finite dimensional Quantum mechanics system

Open
#848 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

API help-wanted
Dominant language
Lean
Stars
749
Forks
189
Avg merge
1d 21h
Merged PRs (30d)
75

Description

Finite dimensional Hilbert Space

Key data structure

The key data structure is the finite dimensional Hilbert space, which takes as an input the dimension of the Hilbert space. This is for a general system and not for any specific Hamiltonian.

  • is defined

Need

Finite dimensional quantum mechanical systems are prevalent in lots of aspects of physics, including qubits in quantum information, and the Hilbert space of finite lattices. For example the tight binding chain.

Requirements

The following are requirements of the API:

  • ability to easily define notation for basis vectors
  • statements about the dimensions
  • used in the definition of the qubit
  • used in the definition of the tight binding chain
  • easy conversion between bras and kets
  • tensor products
  • pure states

Corresponding File System

This file system exists, the link needs adding here.

Contributing to this API

This API is open to contributions from anyone. If you believe that the requirements outlined above need modification, feel free to comment here. If you make a PR which is related to this API, please link it to this issue.

Contributor guide

Open the contributing guide

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.

Research direction

Start by locating the existing finite-dimensional Hilbert space definition; the issue does not name a file, entry point, or test. Review the listed API requirements and determine how basis notation, dimension statements, qubits, tight-binding chains, bras and kets, tensor products, and pure states should be represented. Done means the required API elements are implemented and their use in the stated examples is demonstrated.

Written by the indexing model from the issue text.

Assessment

Domain
api
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
30/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.