Evidaxis

As of 2026-11-07: MuJoCo (Robotics & Embodied AI) is under weekly measurement. Axis coverage: 3 of 3 axes measurable. Gate: not computable — reference measurement

MuJoCo

repo reference measurement
Robotics & Embodied AI · n = 16 · google-deepmind/mujoco
3 of 3 axes measurable · conf medium
convergence gate
Convergence gate: Gate: not computable — reference measurement Development velocity: rising vote Citation momentum: measured × Direct-dependents momentum (deps.dev): rising vote
gate
2 of 3 axes

Gate: not computable — reference measurement

Gate: not computable — reference measurement
position in cohort distribution one of 16 in cohort
percentile 73 within cohort p25 p50 p75 p0 p100
percentile
p73
momentum averages present-axis z-scores; two- and three-axis scores are not strictly comparable
velocity z
velocity z gaugevelocity z+1.86 within cohort, log-slope +0.046/wk.0+1.86
velocity z
+1.86 σ
slope
+0.046/wk
log-slope +0.046/wk
citation z
citation z gaugecitation z-0.26 within cohort, log-slope +0.396/yr.0-0.26
citation z
-0.26 σ
slope
+0.396/yr
log-slope +0.396/yr
direct-dependents z
direct-dependents z gaugedirect-dependents z+1.14 within cohort, log-slope +0.020/point.0+1.14
direct-dependents z
+1.14 σ
slope
+0.020/point
Direct-dependents axis: measured.
cohort
16
systems measured
weekly commits
93
Development velocity axis: measured.
total citations
4,754
Citation axis: measured.
momentum
61.5
percentile p73
commit heatmap, last 26 weeks93/wk
weekly commits, 26 weeks26 weeks of commits, peak 177 in a week, 26 active weeks, 1722 total.week 1: 42 commitsweek 2: 38 commitsweek 3: 43 commitsweek 4: 38 commitsweek 5: 69 commitsweek 6: 51 commitsweek 7: 41 commitsweek 8: 52 commitsweek 9: 41 commitsweek 10: 44 commitsweek 11: 42 commitsweek 12: 44 commitsweek 13: 45 commitsweek 14: 16 commitsweek 15: 51 commitsweek 16: 66 commitsweek 17: 52 commitsweek 18: 72 commitsweek 19: 67 commitsweek 20: 73 commitsweek 21: 53 commitsweek 22: 148 commitsweek 23: 108 commitsweek 24: 139 commitsweek 25: 110 commitsweek 26: 177 commits
weeks
26
peak/wk
177
active
26
total
1722
citations by yeartotal 4,754
Citations by year2012: 2, 2013: 9, 2014: 12, 2015: 18, 2016: 27, 2017: 87, 2018: 211, 2019: 363, 2020: 561, 2021: 609, 2022: 433, 2023: 554, 2024: 669, 2025: 729, 2026: 470. Total 4754 citations.2012: 2 citations1222013: 9 citations1392014: 12 citations14122015: 18 citations15182016: 27 citations16272017: 87 citations17872018: 211 citations182112019: 363 citations193632020: 561 citations205612021: 609 citations216092022: 433 citations224332023: 554 citations235542024: 669 citations246692025: 729 citations257292026: 470 citations26470
total cites
4754
years
15
latest yr
470
Daily dependents count (unscored) 294 dependents 208 direct, 90 indirect · pypi/mujoco · deps.dev · the scored m5 axis uses weekly partitions

Derived signals

second-order reads, computed from the published series

Three signals ship when the commit series is statistically sufficient; the rest are held in a reserved state until the data supports them. A reserved signal shows its reason, never a fabricated number. How these are computed.

recency-weighted swing trailing 13-week vs prior 39-week log-slope ratio +9.68, regime accelerating. prior slope +0.014, recent slope +0.133 per week. +0.014prior 39w+0.133recent 13w+9.68×
swing
+9.68×
regime
accelerating
windows
13w vs 39w
snapshot 1 of 1 · · m5
commit-axis Sharpe log-linear slope over residual std, value +0.051 with 95% CI +0.023 to +0.080, 50 degrees of freedom. CI excludes zero.0+0.05195% CI +0.023, +0.080+0.023+0.080
sharpe
+0.051
95% ci
+0.023, +0.080
dof
50
snapshot 1 of 1 · · m5
commit changepoint52 weekly commit points. No significant changepoint detected (|delta slope| within the noise floor).no significant changepoint
changepoint
none detected
snapshot 1 of 1 · · m5
code-leads-citation lag reserved

reserved: citation series too short / axis absent for cross-correlation

status
reserved
value
insufficient data
snapshot 1 of 1 · · m5
axis alpha vs cohort reserved

reserved: cohort N too small for regression (power ~0)

status
reserved
value
insufficient data
snapshot 1 of 1 · · m5
gate ETA reserved

reserved: needs snapshot history (1 snapshot exists)

status
reserved
value
insufficient history
snapshot 1 of 1 · · m5
methodology gate snapshot 1 of 1 · · m5
commit weeks
52
citation years
15
shipped
3
reserved
3

shipped

  • recency-swing
  • commit-sharpe
  • commit-changepoint

reserved

  • code-leads-citation-lag
  • axis-alpha
  • gate-eta
snapshot 1 of 1 · · m5

Daily dependents count (unscored)

MuJoCo dependents over time19 points, range 226 to 294 dependents.
min
226 dependents
max
294 dependents
latest
294 dependents
points
19

Downstream packages depending on pypi/mujoco (deps.dev), captured point-in-time each snapshot. This daily series is unscored. The scored axis in m5 uses weekly partitions.

Measurement states

MuJoCo is under weekly measurement. History: 20 weekly observations; minimum 4. Development velocity axis: measured. Citation axis: measured. Direct-dependents axis: measured. Gate: not computable — reference measurement

Sources

google-deepmind/mujoco development-velocity axis
OpenAlex paper citation-momentum axis
mujoco.org homepage

Direct-dependents momentum (deps.dev)

Direct-dependents axis: measured.

Coverage state
scored
Cohort z
+1.14
OLS slope
+0.020
Theil-Sen slope
+0.020
Latest direct dependents
236
Confirmed-clean points
29
Reconstructed history points
15
As-of partition
2026-10-19
Fragility veto
inactive
Rising vote
yes

This axis measures the trajectory of a system's own packages: declared in its own tree, published under that name, and not attributed by deps.dev to another repository. A package with no repository link is unverified and stays. The self-name exclusion list is fixed at the v2h.1 panel. Systems with no admitted package are not measured on this axis. Points that cannot be derived exactly are withheld, and the series restarts after a withheld point.

The earliest weekly points of each series were read from deps.dev's BigQuery history on 2026-07-21; later points are weekly captures. m5 does not replay those partitions: each point is the stored system total, one package's unique_direct, or a complete sketch union, and a point that is not exact is withheld. Each record reports how many of its points are reconstructed history.

Source: deps.dev (Google), CC-BY 4.0. Modified: aggregated to system-level counts and momentum scores.

Axis definition · Snapshot axis correlations

Cite this measurement

Plain citation

Evidaxis. MuJoCo measurement record. Snapshot 2026-11-07. https://evidaxis.org/e/e_03QFRGK7VQX/ Concept DOI: 10.5281/zenodo.21076011.

BibTeX

@dataset{evidaxis_e_03QFRGK7VQX_20261107,
  title = {MuJoCo measurement record},
  publisher = {Evidaxis},
  year = {2026},
  url = {https://evidaxis.org/e/e_03QFRGK7VQX/},
  doi = {10.5281/zenodo.21076011}
}

Download record (JSON)

entity_id e_03QFRGK7VQX methodology m5 snapshot 868e3c39d9c7 period 2026-w45 record JSON ↓ source snapshot

Score derived from public data on Evidaxis methodology m5, never edited by hand. Cite as: “Evidaxis, MuJoCo, entity e_03QFRGK7VQX, snapshot 2026-w45.”

Durable reference (format-independent): urn:evidaxis:claim:e_03QFRGK7VQX:m5:2026-11-07