Math+Mermaid lane proof page — not production content.
Hand-crafted from real chapter excerpts (see LANE-REPORT-math.md for exact source files/line ranges) to verify remark-math + rehype-katex and rehype-mermaid render correctly at build time. Delete this page, its sibling test-*.md files, and this layout once Phase 1 closes.
Source A: Mathematical Foundations for IoT — The Derivation
Link budget:Prx=14−120=−106 dBm, and margin =−106−(−137)=31.0 dB, or 1031/10=1.26×103 times the minimum receiver power
Sampling: the chapter’s 360 Hz vibration content needs fs≥2(360)=720 Hz; a 2 kHz choice gives 2000/720=2.78× the minimum and a 1000 Hz Nyquist frequency
Sixteen-bit data stream: ideal quantization SNR =6.02(16)+1.76=98.1 dB, while the data rate at 2 kHz is 2000×16=32000 bit/s
RC anti-alias filter: for fc=400 Hz, RC=1/(2π400)=398 us; with R=10 kohm, C=398 us/10000=39.8 nF
Battery record:Iavg=160(2/60)+0.8(58/60)=5.33+0.773=6.11 mA, so 2000/6.11=328 h =13.7 days
Source A continued: Calculus, Exponentials, Logs
(same file, lines 429-620)
Notation: dtdx means “the rate at which x changes with respect to time t”
The PID formula uses derivatives:
P(t)=Kp⋅e(t)+Ki⋅∫e(t)dt+Kd⋅dtde(t)
D term (dtde): How fast is the error changing? (prevents overshooting)
Notation: ∫f(x)dx means “sum up all the tiny pieces of f(x)”
After 1τ: Value drops to 37% of initial (e−1≈0.37)
τ=R×C=100Ω×10μF=1ms
Definition: If bx=y, then logb(y)=x
log10 (common log) - used in dB calculations
ln or loge (natural log) - used in signal processing
log2 (binary log) - used in information theory (bits)
dB=10log10(PinPout)
C=Blog2(1+SNR)
dBm=10log10(PmW)
Source A continued: Vectors and Matrices
(same file, lines 687-773)
Notation: v=xyz or simply [x,y,z]
Magnitude (Length): How “big” is the vector?
∣v∣=x2+y2+z2
Example: Accelerometer reads [0.5,0.3,0.8]g
∣a∣=0.52+0.32+0.82=0.98≈0.99g
Notation:
M=[acbd]
Rotating sensor data to align with a reference frame:
x′y′=xcosθ−ysinθ=xsinθ+ycosθ
State vector might be [position,velocity,acceleration]:
x=pva
State transition predicts next state:
xk+1=F⋅xk
Describes uncertainty in measurements:
P=[σx2σxyσxyσy2]
Example: Transforming a 3D point (a wide equation — deliberately kept
in this proof page to test the overflow-protection rule in
TestMathLayout.astro; see its <style> comment):
200020002123=246
Source B: Fresnel Zones and Deployment
(content/networking-core/net-prop-fresnel.qmd, lines 74-119 — a real
“net-prop-*” file, the task brief’s own example)
At a point with distances (d_1) and (d_2) from the two antennas, the first-zone radius is
r1=d1+d2λd1d2.
The zone is widest near the path midpoint. Lower frequencies have longer wavelengths and therefore larger Fresnel radii for the same geometry.
ITU-R P.526 uses clearance equal to 60% of the first-zone radius as a boundary for the diffraction zone. Treat (0.6r_1) as a useful screening target, not as a guarantee of availability or delivery.
For wavelength (lambda), the radius at one location along the path is
r1=d1+d2λd1d2,
where (d_1) and (d_2) use the same distance unit and the result follows that unit.
With distance in kilometres and frequency in gigahertz, a convenient form is
r1(m)=17.32f(d1+d2)d1d2.
At the midpoint of a total path (D), (d_1=d_2=D/2), so
r1,mid=8.66fD
for (D) in kilometres, (f) in gigahertz, and radius in metres.
Worked Path-Profile Decision
(same file, lines 231-241)
Consider a hypothetical 5 km path at 915 MHz with an obstacle 2 km from the transmitter and 3 km from the receiver.
r1=17.320.915×52×3≈19.8 m,
so the 60% screen is about 11.9 m at that location.
Suppose the direct path line is 18 m above the common datum there and the surveyed obstacle top is 9 m. The geometric clearance is 9 m, or
19.89≈45% of r1.
The obstacle enters the 60% screen.
Coverage check: \begin{align}
(content/coap/coap-api-design.qmd, lines 845-861 verbatim — estate-wide
grep of content/*/*.qmd for \begin{[a-zA-Z*]+} turns up exactly three
environments in use: aligned (35), align (14), bmatrix (13; all
exercised above via Source A). This block is a real align instance,
picked from coap since it overlaps this lane’s hand-picked module.)
CON (Confirmable) message energy:
TX message (50 ms @ 10 mA)RX ACK (100 ms @ 5 mA)Total per message=50×10−3×10×10−3=0.5 mAs=100×10−3×5×10−3=0.5 mAs=1.0 mAs=0.278μAh
Annual comparison (525,600 messages):
CON energySleep energyTotal CONNON energyTotal NONBattery life=525,600×0.278=146 mAh=0.005×24×365=44 mAh=146+44=190 mAh (battery life=220/190=1.16 years)=525,600×0.139=73 mAh=73+44=117 mAh=117220=1.88 years