Skip to content
formal librarypublicsource:physlib

The Physlib community

Native namespace leanprover-community/physlib:API-map

Exact JSON

232 source-native objects · 0 Repository bindings

Native API map

Browse 232 source-attributed requirements from the exact native revision. Implemented and planned are publisher labels, never Vela Standing.

Source-native objects

Stable native key order · 20 shown

A gauge field (connection) for a general/non-abelian structure group, valued in the Lie algebra of G

api requirement · reference only

api-map:Physlib/ClassicalFieldTheory/GaugeTheory/API-map.yaml#requirement:10

source: planned
The gauge-covariant derivative D = d + A acting on matter fields, and its transformation law

api requirement · reference only

api-map:Physlib/ClassicalFieldTheory/GaugeTheory/API-map.yaml#requirement:11

source: planned
Non-abelian field strength (Yang-Mills curvature) F = dA + A wedge A and its covariant transformation

api requirement · reference only

api-map:Physlib/ClassicalFieldTheory/GaugeTheory/API-map.yaml#requirement:12

source: planned
The Yang-Mills action and its Euler-Lagrange (field) equations

api requirement · reference only

api-map:Physlib/ClassicalFieldTheory/GaugeTheory/API-map.yaml#requirement:13

source: planned
Parallel transport, Wilson lines/loops, and holonomy of the connection

api requirement · reference only

api-map:Physlib/ClassicalFieldTheory/GaugeTheory/API-map.yaml#requirement:14

source: planned
A principal-bundle / fibre-bundle formulation of gauge fields as connections

api requirement · reference only

api-map:Physlib/ClassicalFieldTheory/GaugeTheory/API-map.yaml#requirement:15

source: planned
A general abstract gauge group G (an arbitrary Lie group as structure group), not tied to the Standard Model

api requirement · reference only

api-map:Physlib/ClassicalFieldTheory/GaugeTheory/API-map.yaml#requirement:9

source: planned
A general, system-agnostic ConfigurationSpace construction (a configuration manifold abstracting over the choice of mechanical system) usable across the Lagrangian API.

api requirement · reference only

api-map:Physlib/ClassicalMechanics/Lagrangian/API-map.yaml#requirement:1

source: planned
A general treatment of generalized coordinates and the velocity phase space (tangent bundle TQ) built over a shared configuration-space abstraction, on which a Lagrangian is defined for the Euler-Lagrange API.

api requirement · reference only

api-map:Physlib/ClassicalMechanics/Lagrangian/API-map.yaml#requirement:2

source: planned
The API shall contain the structure of a manifold on the configuration space.

api requirement · reference only

api-map:Physlib/ClassicalMechanics/Pendulum/API-map.yaml#requirement:2

source: planned
The API shall contain a map from the configuration space to Space, giving the position of the pendulum in real space.

api requirement · reference only

api-map:Physlib/ClassicalMechanics/Pendulum/API-map.yaml#requirement:3

source: planned
The API shall contain the definition of a trajectory based on the configuration space.

api requirement · reference only

api-map:Physlib/ClassicalMechanics/Pendulum/API-map.yaml#requirement:4

source: planned
The API shall subsequently contain the definition of the lagrangian.

api requirement · reference only

api-map:Physlib/ClassicalMechanics/Pendulum/API-map.yaml#requirement:5

source: planned
The API contains the definition of Euler angles for a rigid body.

api requirement · reference only

api-map:Physlib/ClassicalMechanics/RigidBody/API-map.yaml#requirement:12

source: planned
Redefine RigidBody using continuous linear maps instead of plain linear maps from the space of smooth functions to (existing TODO).

api requirement · reference only

api-map:Physlib/ClassicalMechanics/RigidBody/API-map.yaml#requirement:13

source: planned
The inertia tensor of the solid sphere equals 2/5 m R^2 times the identity. Stated as solidSphere_inertiaTensor but currently proved with sorry.

api requirement · reference only

api-map:Physlib/ClassicalMechanics/RigidBody/API-map.yaml#requirement:8

source: planned
The API shall contain the definition of the EM potential from a connection on a U(1)-gauge bundle. This relationship is only noted in the module documentation; no such construction is formalised.

api requirement · reference only

api-map:Physlib/Electromagnetism/Kinematics/API-map.yaml#requirement:4

source: planned
The key data structure for a fluid, given by the spatial distribution of its velocity, density, and pressure, is defined. (FluidFlow currently provides the density and velocity fields; pressure is not a field of the structure and enters separately through the stress laws.)

api requirement · reference only

api-map:Physlib/FluidDynamics/API-map.yaml#requirement:1

source: planned with partial location
Flow out of a volume: the flux of fluid through the boundary of a spatial region.

api requirement · reference only

api-map:Physlib/FluidDynamics/API-map.yaml#requirement:2

source: planned
Definition of the entropy flux density.

api requirement · reference only

api-map:Physlib/FluidDynamics/API-map.yaml#requirement:7

source: planned

Repository bindings

Exact local relationships · 0 shown

No Repository bindings on this page

A source observation does not create a local scientific record.

Source declarations, observations, source-native object rows, and Repository bindings record provenance. None creates scientific Standing; only an admitted local Claim can enter the attributed Decision path.

Search problems.science

Find a Problem, Result, source, or page