Study Notes

Personal knowledge base for robotics (Eragon), math from first principles, NumPy, and AI fundamentals.

How these notes are organized

Conventions follow common personal-knowledge and technical-docs practice:

Practice	How it shows up here
Domain folders	One top-level folder per subject (eragon/, math/, ai/, numpy/)
One concept, one home	Definitions live in a single file; related notes link instead of copying
Stable filenames	kebab-case.md within each domain
Predictable headings	# title → ## topic → ### concept → #### detail
Map of content	This README plus each domain’s own index
Assets separate	Images and diagrams live in assets/
Stubs marked	Incomplete sections use _Stub — to be filled._

Map of content

Eragon — 3D-printed bipedal robot

Note	Focus
structure.md	Bipedal mechanics, balance, DoF, loads
electrical.md	Circuits, Ohm’s law, semiconductors, MCU hardware
material.md	Thermodynamics, crystallography, PLA / 3D printing
physics.md	SI units, atoms, gravity, measurement tools
software.md	Virtualization and OS notes
code.md	Compilers, interpreters, language notes
general.md	Design methodology, research links, cross-cutting ideas

Math — first-principles math

Note	Focus
math.md	Algebra, geometry, matrices, tensors
resources.md	External references

AI — AI fundamentals

Note	Focus
notes.md	Matrices, tensors, training, inference

NumPy — array computing

Note	Focus
notes.md	ndarray, axes, dtypes
study.py	Hands-on examples

Assets

Diagrams and images referenced from notes (e.g. SI units, ESP32 pinout, algebra terms).

Writing guide (quick)

1. Put new material in the domain it belongs to; use eragon/general.md only when it fits nowhere else.
2. Prefer linking to an existing definition over pasting a second copy.
3. Keep each ## section about one topic; put formulas next to the concept they define.
4. When adding an image, store it under assets/ and link with a relative path (../assets/name.png from a domain file).