Rushing Time Functions: A Cross-Disciplinary Overview
- Rushing Time Functions are constructs that reparameterize and constrain time measurements across various domains by altering clock mechanisms or descent lengths.
- In musical performance analysis, they quantify microtiming residuals relative to a metrical grid, distinguishing between rushing (negative residuals) and dragging (positive residuals).
- In abstract settings, such functions underpin causality in spacetime, clock-based penalization in stochastic processes, and runtime estimations in computational proof theory.
Searching arXiv for the cited papers to ground the article. arxiv_search(query="(Gordon et al., 2019)", max_results=5, sort_by="relevance") arxiv_search(query="(Gordon et al., 2019)", max_results=5, sort_by="relevance") “Rushing time functions” does not denote a single standardized object across the arXiv literature. The expression, or closely related constructions explicitly interpreted that way, appears in several technically distinct settings: as microtiming residuals that quantify “rushing” and “dragging” relative to a metrical grid in drum performance; as continuous functions on abstract spacetimes satisfying a metric-dominating monotonicity inequality; as families of random times (“clocks”) used to take long-time limits in Lévy-process penalization; and as runtime measures induced by ordinally or combinatorially indexed witnessing flows in proof theory (Gordon et al., 2019, Minguzzi, 16 Aug 2025, Takeda et al., 2022, Tabatabai, 2024). Related nearby usages also occur in numerical studies of metastable bacterial respiration and in work on reducing execution time in R, but those uses are terminologically looser than the formal notions above (Kundu et al., 2023, Uyttendaele, 2015).
1. Taxonomy of the term
The main usages can be organized as follows.
| Domain | Object called or interpreted as a rushing time function | Core role |
|---|---|---|
| Drum microtiming | Residuals | Ahead/behind-grid timing |
| Abstract spacetime | Rushing function with | Encodes order and distance |
| Lévy penalization | Random clocks such as , , , | Sends observation time to infinity |
| Witnessing flows | Length of ordinal or -flow descent | Bounds feasible computation time |
In the drumming literature, the operative object is a time series of residuals relative to a nominal beat period. In the spacetime literature, the object is a continuous real-valued function that dominates proper time along causal pairs. In Lévy-process penalization, the relevant objects are random times along which limits are taken. In witnessing-flow analysis, the relevant object is a runtime induced by the length of a descending sequence of feasible proof-theoretic transformations. This suggests that the common semantic core is not a single definition but a family of constructions in which “time” is reparameterized, constrained, or accelerated in a domain-specific way.
2. Microtiming residuals in performance analysis
In the musical setting, the relevant quantities are defined relative to a metrical grid. For hi-hat onset times , inter-onset intervals are , and the microtiming residuals are
0
The sign convention is explicit: 1 means rushing, while 2 means dragging. For the “Tom Sawyer” task analyzed at 3 bpm, the quarter-note period is 4 and the nominal sixteenth-note interval is 5; complementary fluctuation measures are the mean-centered IOI deviations 6 and the onset amplitudes 7 (Gordon et al., 2019).
The empirical analysis used 8 hi-hat samples from 9 participants, including experienced drummers and non-drummers. Onset detection used a 5th-order Butterworth low-pass with cutoff 0–1 Hz and Matlab’s findpeaks() within a prediction window centered on 2 with 3 ms tolerance; erroneous intervals with 4 deviating beyond 5 ms were removed. Detrended fluctuation analysis (DFA) was then applied to the integrated, mean-centered timing or amplitude series. With
6
window size 7, linear detrending order 8, and
9
the exponent 0 was interpreted conventionally: 1 for short-range anti-correlations, 2 for white noise, and 3 for long-range positive correlations. For stationary fractional Gaussian noise, the spectral relation is 4.
The principal result is negative with respect to universality. A previous Porcaro analysis had reported a clear crossover from short-range anti-correlations to long-range positive correlations, but in the larger “Tom Sawyer” dataset positive crossovers were rare: 5 of IOI series and 6 of amplitude series. Most series were statistically close to white noise: 7 of IOI series and 8 of amplitude series were approximately linear in 9 versus 0, typically with 1. Negative crossovers occurred in 2 of IOI series and 3 of amplitude series, and were interpreted cautiously as likely DFA artifacts or nonstationarities. No systematic differences in 4 or crossover prevalence were found between experienced drummers and non-drummers, or between single-handed and double-handed techniques within this task (Gordon et al., 2019).
The same study also provides a methodological warning that is central to this usage. DFA is described as prone to bias and spurious crossovers, especially for anti-correlated signals. Strong anti-correlations with 5 often produce curvature in 6 versus 7 and unstable exponent estimates; missing data, window-range choice, detrending order, and subjective crossover placement can all distort inference. In this literature, therefore, a “rushing time function” is not merely a residual series but an object whose interpretation depends strongly on robust fluctuation analysis.
3. Rushing functions in abstract spacetime theory
In the spacetime setting, the terminology is formal and axiomatic. A spacetime may be defined as a quadruple
8
where 9 is a closed preordered space and 0 is 1-upper semi-continuous, vanishes off the preorder, and satisfies the reverse triangle inequality
2
An equivalent time-separation form uses
3
with 4 and 5 (Minguzzi, 16 Aug 2025).
Against this background, a function 6 is rushing if
7
equivalently
8
A time function is a continuous utility that is strictly isotone, and a rushing time function is both rushing and a time function. The intended intuition is explicit: such an 9 “runs faster than proper time.” Along any nontrivial causal pair 0 one therefore has
1
The central technical device is the product trick. One passes from 2 to
3
equipped with product topology and preorder
4
equivalently 5. A translationally invariant function
6
is continuous and isotone on 7 if and only if 8 is a continuous rushing function on 9. This reduces “metricity” to causality in one higher dimension and unifies proper time with time functions.
The representation theorems are the distinguishing feature of this usage. For locally compact, 0-compact, stable spacetimes, the family 1 of continuous rushing functions reconstructs topology, order, and Lorentzian distance:
2
Under second-countability, one may restrict to the family 3 of rushing time functions without losing reconstruction. In this sense, spacetime can be represented as a family of rushing time functions, and “time fully characterizes spacetime” (Minguzzi, 16 Aug 2025).
The paper’s Minkowski example makes the idea concrete. In 4 with coordinates 5, the linear functions
6
are strictly isotone and rushing, and they recover the Lorentzian distance through an infimum formula. Here the term is not metaphorical: it names a function class with a precise order-metric inequality and a full reconstruction theorem.
4. Random clocks in Lévy-process penalization
For one-dimensional Lévy processes, the pertinent objects are families of random times used to define long-time penalization limits. The process is observed on càdlàg path space with canonical filtration, and the local time at 7, denoted 8, is assumed well defined under the regularity hypotheses stated in the paper. The inverse local time is
9
The penalization scheme studies weighted expectations of the form
0
where 1 is not deterministic but chosen from a parametrized family of random clocks (Takeda et al., 2022).
The paper considers four such clocks: the exponential clock 2 with 3, the hitting time clock 4 with 5, the two-point hitting time clock 6 with 7 under a balance condition, and the inverse local time clock 8 with either 9 or 0. These families are explicitly interpreted as “rushing time functions” in the sense that they push the observation horizon to infinity in different probabilistic ways: exponential scaling, hitting distant levels, hitting one of two distant levels, or accumulating local time.
The limit law is characterized by a non-negative martingale built from the invariant function
1
and
2
The process killed upon hitting zero has 3 as an invariant function, and the limiting penalized law is the corresponding Doob 4-transform. The choice of clock determines 5: the exponential clock yields 6, one-sided hitting clocks yield 7, the two-point clock yields 8 depending on the asymptotic balance, and inverse local time clocks with 9 again yield 00.
A central distinction is between recurrent finite-variance and infinite-variance regimes. When 01, different clocks produce genuinely different limit martingales and limit laws; the paper states that “the limit law varies according to the chosen clock when 02.” When 03, one has 04 and 05, so all four clock families lead to the same limit. In the transient regime, the penalization becomes clock-independent again, governed by a single martingale. In this literature, therefore, a rushing time function is not a deterministic function on state space but a clocking mechanism that selects a particular asymptotic excursion bias.
5. Rushing time in witnessing flows and bounded arithmetic
In proof theory and bounded arithmetic, the expression is used for a runtime induced by witnessing mechanisms rather than for a temporal observable or a geometric function. The paper develops ordinal flows and 06-flows, each consisting of feasible, PV- or PV07-provable stepwise transformations whose length acts as a time measure (Tabatabai, 2024).
For a ptime ordinal representation
08
an 09-flow from 10 to 11 is a pair 12 satisfying
13
14
and
15
The associated ordinal local search program 16 starts from 17, applies a modifier 18 while strictly decreasing an ordinal measure through
19
and reads a witness at level 20 via 21.
Here the rushing time function is the total runtime induced by this descent. If each modification step is polynomial-time and the number of steps is bounded by the length of the descending 22-chain, then
23
where 24 measures the number of decreases to reach 25. The controlling principle is well-foundedness: termination is guaranteed by transfinite induction or, equivalently at the 26 level, by the absence of primitive recursive descending sequences below 27.
The paper’s main characterization theorem states
28
and
29
For bounded arithmetic, a 30-flow of length 31 is defined by
32
and
33
This yields explicit runtime bounds:
34
Thus the “rushing” is the proof-extracted descent through ordinal height or bounded iteration length. Unlike the geometric and stochastic usages, the object is explicitly computational.
6. Related usages, limits of unification, and common confusions
Two additional papers use nearby but looser language. In the Fairen–Velarde model of bacterial respiration, the reported phenomenon is “a fast time scale (after leaving the zone of limit cycle) in rushing towards the stable fixed point.” The model exhibits two time scales: a slow metastable lifetime near the stable limit cycle and a faster late-time decay toward the stable fixed point. The analysis uses semilogarithmic plots of peak–dip amplitudes, where straight lines indicate exponential decay and define 35 and 36, with 37 observed; decreasing the nutrient parameter 38 reduces the gross residence time near the limit cycle (Kundu et al., 2023). This is a dynamical-timescale usage rather than a formal function class.
In “How to speed up R code,” the subject is the reduction of total execution time rather than an object called a rushing time function. The paper discusses measurement with proc.time() and system.time(), profiling via Rprof, vectorization, preallocation, compiled C code via .C, shared-memory parallelism, and cluster submission. Reported examples include a loop-to-apply change from 39 to 40, a kernel-smoothing rewrite from 41 to 42, and a pseudo-observation rewrite from 43 to 44 (Uyttendaele, 2015). This is best understood as a runtime-optimization context, not as a definition of the encyclopedia topic.
A recurrent misconception would be to treat all these usages as instances of one mathematical object. The sources do not support that. In performance analysis, the object is a residual time series 45; in spacetime theory, it is a continuous rushing function satisfying a causal inequality; in Lévy penalization, it is a family of random clocks; in witnessing flows, it is a runtime function derived from descent length. A plausible implication is that “rushing time function” functions more as a cross-domain label for accelerated, dominant, or asymptotically directing temporal structures than as a universally fixed term.
Another misconception would be to identify “rushing” with a universal signature or with a single correlation law. The drumming study explicitly rejects universality of the Porcaro-style crossover and stresses that most timing and amplitude fluctuations in its larger dataset are consistent with white noise, while the Lévy-process study shows that asymptotic behavior can depend sharply on the chosen clock when 46 (Gordon et al., 2019, Takeda et al., 2022).
Across these literatures, the most robust commonality is structural rather than definitional: a rushing time function is a device that constrains how time-like progression is measured. Whether that progression is musical, causal, stochastic, or computational depends entirely on the ambient theory.