Time bounds from deterministic transducer space bounds #
A one-way-output deterministic transducer has only finitely many execution- relevant configurations once its input length and auxiliary-space budget are fixed. A halting run cannot repeat one of these reduced snapshots, yielding an explicit time bound.
Main results #
TM.IsTransducer.reachesIn_succ_le_transducerConfigBound— exact halted-run boundTM.IsTransducer.reachesIn_le_transducerConfigBound— convenient weak boundTM.ComputesInSpace.computesInTime_configBound— space computation gives timeTM.DecidesInSpace.decidesInTime_configBound— decision-space bound gives time
A halting transducer run staying within auxiliary space space has one
more time index than steps, and all those indices inject into the explicit
type of reduced transducer snapshots.
A halting transducer run staying within auxiliary space space takes no
more steps than the explicit number of reduced transducer snapshots.
A total deterministic function transducer using space S computes within
the corresponding finite reduced-configuration bound.
A deterministic language decider with one-way output and auxiliary-space
bound S decides within the corresponding finite reduced-configuration bound.