Python Tutorial
SciPy Constants
scipy.constants ships mathematical and physical constants in SI units.
Math and Physics
from scipy import constants
print(constants.pi)
print(constants.c) # speed of light
print(constants.g) # gravity
print(constants.Avogadro)
print(constants.hour) # seconds in an hourUnit Prefixes
print(constants.kilo) # 1000
print(constants.milli) # 0.001📘 Real-World Deep Dive
Knowing <strong>SciPy Constants (SciPy)</strong> well is what turns SciPy from a curiosity into a daily tool — you'll reach for it in nearly every real project.
Real-Life Scenario
An end-to-end usage of SciPy Constants that you'd actually see in a data pipeline or analytics notebook.
Real-Life Example
from scipy import constants as C
print("pi:", C.pi)
print("Planck (J·s):", C.Planck)
print("Avogadro:", C.Avogadro)Expected Output
(see source)Common mistakes
- Many SciPy functions take
methodstrings with subtle spelling differences ("trust-constr"vs."trust-constr") — readscipy.optimize.least_squaresdocs. - Sparse matrices need explicit conversion to dense (
toarray()) before being fed to functions that don't acceptscipy.sparse. scipy.signalfunctions often return arrays whose length differs from input — always inspectlen(out)defensively.- Treating SciPy Constants as a black box without reading the docs — the API has subtle defaults that bite when you scale.
🚀 Performance & Best Practices
- Use vectorised
scipy.statsdistributions instead of looping per-sample for large parametric studies. scipy.sparse.csr_matrixis the right format for arithmetic;csc_matrixis right for slicing columns.- Prefer Cython/Numba (or NumPy ufuncs) over Python loops inside SciPy callbacks (e.g.
odeint). - When working with SciPy, prefer vectorised / batched operations over Python loops.
🧪 Try It Yourself
- Reproduce the snippet on a representative slice of your own data.
- Profile the snippet with
cProfileortimeitand find the single biggest improvement. - Generalise the snippet into a small, reusable function you can drop into future projects.