vita-core 0.2.0

Zero-dependency primitives for atomistic and molecular computation.
Documentation 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49

//! Foundational vocabulary for the vita ecosystem: the questions a physical system can
//! answer, not the structures that store the answers.
//!
//! > What we observe is not nature itself, but nature exposed to our method of
//! > questioning.
//! >
//! > — Werner Heisenberg
//!
//! A system is never a concrete type here. Each kind of question it can answer is a
//! trait: [`HasElements`] what occupies a site, [`HasPositions`] where it sits,
//! [`HasNetCharge`] the total charge. Code bounds on exactly the capabilities it needs
//! and stays blind to the storage behind them.
//!
//! # Sites
//!
//! Per-site data is keyed on an opaque [`SiteId`]; [`HasSites`] enumerates those keys and
//! is the supertrait of every per-site capability. A capability is a keyed getter paired
//! with a `(SiteId, _)` iterator — storage order is never implied. System-wide quantities
//! ([`HasLattice`], [`HasNetCharge`]) are standalone, single-valued traits.
//!
//! # Quantities
//!
//! Physical values carry their dimension and unit in the type via [`units`]; geometry uses
//! the three-dimensional primitives in [`tensor`]. Both are generic over the [`Scalar`]
//! element type, `f32` or `f64`.

mod capability;
mod element;
mod id;
mod isotope;
mod lattice;
mod scalar;

pub mod tensor;
pub mod units;

pub mod prelude;

pub use scalar::Scalar;

pub use element::Element;
pub use id::SiteId;
pub use isotope::Isotope;
pub use lattice::Lattice;

pub use capability::{
    HasAccelerations, HasElements, HasIsotopes, HasLattice, HasMasses, HasNetCharge, HasPositions,
    HasSites, HasVelocities,
};