· Identity · Claim-safe

Log-space filtering: why GSRF lives in log domain

Restates locked Evidence / workbench numbers only. Not universal performance.

GSRF Practical does not smooth the raw level with a linear IIR. It maintains an internal state in log-space, updates that state, then maps back with exp.

Why log-space

Hard constraints for users

Public formula (identity, not full production pack)

update ≈ baseline + k_return·(−(x − x*)) + mem·tanh(Δx) + w_obs·tanh(x_obs − x)
output = exp(x)

Verdict

Log-space + spring is the product identity. Full runnable loop: /try. Theory narrative: What GSRF really is.

Sources: public Practical identity · try snippet · WHAT_GSRF_REALLY_IS_MASTER

Questions people actually ask

Why log-space?

GSRF Practical updates an internal log-state on strictly positive observations, then exp() back. That is the soft-thermostat geometry for multiplicative-scale signals.

What is a soft thermostat for signals?

A filter that gently pulls toward a declared normal x* while still admitting observation pull — peaks and ring compress toward normal rather than fully tracking them.

Do signals need to be positive?

Yes for Practical log-space. Offset or transform non-positive series before filtering.

Related research