handoverlab 2.4.1__tar.gz → 2.4.2__tar.gz

{handoverlab-2.4.1 → handoverlab-2.4.2}/CHANGELOG.md

@@ -7,6 +7,46 @@ All notable changes to this project are documented in this file. The format foll
 
 ## [Unreleased]
 
+## [2.4.2] - 2026-10-23
+
+No change of results.
+
+### Added
+
+- A picture for every option, each drawn from a real run by its own script in `tools/`: the handover
+  procedures side by side (`procedures.png`), mobility robustness optimisation (`mro.png`), fast fading
+  (`fading.png`), the slot scheduler with the Numba timings (`scheduler.png`), buffers at handover
+  (`buffers.png`), dual connectivity (`dual-connectivity.png`), UE receive beams (`ue-beams.png`) and the
+  traffic models (`traffic.png`); shown in the README and in each guide.
+- `tools/make_dashboard_screenshots.py`: the dashboard screenshots taken with Edge through the DevTools
+  protocol; all four dashboard pictures redone with this version.
+
+### Fixed
+
+- The speed-ups stated for 2.4.0 ("8 to 60" times, "50-80" times the rate model) were not all supported by the
+  measurements: `docs/performance.md` gives 23 to 59 times for the Numba scheduler and, measured again for 2.4.2
+  on the configuration of the scheduler picture, 42 (round robin) and 93 times (proportional fair), with the
+  NumPy scheduler about 91 times the rate model. The README, `docs/comparison.md`, the scheduler and fading guides
+  and `docs/performance.md` now give these measured numbers.
+
+### Documentation
+
+- 7 GHz calibration: README, `docs/comparison.md`, `docs/calibration-3gpp.md` and
+  `docs/standard-compliance.md` say which cases they count (at 7 GHz 228 percentiles, largest distance
+  1.69-2.43 dB; with the two 6 GHz reruns 342 percentiles, 1.65-2.88 dB).
+- README model boundaries: the slot scheduler (2.2.0) and the user-plane buffers (2.3.0) listed as options,
+  with what is still not modelled.
+- Scenario cards `suburban-sma-7ghz`, `rural-700mhz` and `indoor-office-4ghz`: the 7 GHz calibration of 2.4.0
+  and the hard-LOS results of `docs/guides/indoor-rural.md`; scenario pages regenerated.
+- Examples rerun with this version and their numbers, and where needed their conclusions, updated: the guides
+  on buffers, MRO (the faster MRO setting is no better), beams and layers, indoor and rural scenarios, the
+  learning rule and fast fading; tutorial 2; the README traffic table; the `status` example in the user guide.
+- User guide: all 15 cards, the `a3_pred` rule, `ttt_d2_s`, the layout kinds `indoor` and `ntn`, `run.backend`
+  under `run`, `ntn.hpbw_deg` (tabled widths at 2 GHz only), `ntn.los_model` and `radio.vegetation`; the study
+  example with a main guard. `docs/index.md`: the current layouts and cards. `docs/stability.md`: the missing
+  import. Tutorial 3: the cap of four extensions dates from 2.4.1.
+- Citation with the DOI of 2.4.1.
+
 ## [2.4.1] - 2026-10-22
 
 No change of results.
@@ -1080,7 +1120,8 @@ First alpha release (stage 1: the core simulator).
 - Documentation: README, user guide, contribution guide, citation file; CI on Linux, Windows and
   macOS with Python 3.9-3.12.
 
-[Unreleased]: https://github.com/mjs19971997/handoverlab/compare/v2.4.1...HEAD
+[Unreleased]: https://github.com/mjs19971997/handoverlab/compare/v2.4.2...HEAD
+[2.4.2]: https://github.com/mjs19971997/handoverlab/compare/v2.4.1...v2.4.2
 [2.4.1]: https://github.com/mjs19971997/handoverlab/compare/v2.4.0...v2.4.1
 [2.4.0]: https://github.com/mjs19971997/handoverlab/compare/v2.3.0...v2.4.0
 [2.3.0]: https://github.com/mjs19971997/handoverlab/compare/v2.2.0...v2.3.0

{handoverlab-2.4.1 → handoverlab-2.4.2}/CITATION.cff

@@ -14,7 +14,7 @@ abstract: >-
   handover rules (including a measurement-prediction rule after TR 38.744), equal-budget tuning
   studies with paired statistics, and verification against hand-computed values, golden event-log
   fingerprints, the 3GPP large-scale calibration and ns-3 / 5G-LENA.
-version: "2.4.1"
+version: "2.4.2"
 doi: 10.5281/zenodo.23409131
 identifiers:
   - type: doi
@@ -29,7 +29,10 @@ identifiers:
   - type: doi
     value: 10.5281/zenodo.23582521
     description: "Version 2.4.0 on Zenodo"
-date-released: 2026-10-22
+  - type: doi
+    value: 10.5281/zenodo.23585308
+    description: "Version 2.4.1 on Zenodo"
+date-released: 2026-10-23
 license: MIT
 repository-code: "https://github.com/mjs19971997/handoverlab"
 url: "https://mjs19971997.github.io/handoverlab/"

{handoverlab-2.4.1 → handoverlab-2.4.2}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: handoverlab
-Version: 2.4.1
+Version: 2.4.2
 Summary: System-level handover simulator for 5G-Advanced and beyond-5G research
 Author: Mostafa Jalili Sanjarani, Yasser Elmi Sola
 License-Expression: MIT
@@ -70,7 +70,7 @@ received-power-level radio model from TR 38.901 (TR 38.811 for the satellite) (o
 and several carriers), an L3-filtered measurement chain, a radio-link failure model, and an
 outcome label for every handover attempt.
 
-> **Status: 2.4.1** (`python -m pip install handoverlab`). The public surface (configuration and
+> **Status: 2.4.2** (`python -m pip install handoverlab`). The public surface (configuration and
 > result formats with a schema version, the rule interface, metric names, commands and the
 > documented Python names) follows the [stability policy](https://github.com/mjs19971997/handoverlab/blob/main/docs/stability.md): within 2.x it only grows,
 > and anything removed is deprecated first. 2.0.0 makes the 3GPP values the defaults (the protocol profile,
@@ -150,6 +150,47 @@ accurate than sample and hold 400 ms ahead (1.84 / 2.66 / 3.14 dB against 2.38 /
 
 ![Prediction error against horizon for the ridge predictor and sample and hold at 30, 60 and 90 km/h](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/ai-mobility.png)
 
+**Handover procedures side by side.** On one card failures fall from 0.6 (A3) to 0.2 (LTM and CLTM) per
+UE-minute; DAPS has no execution interruption; LTM pays with 192 RRC messages per UE-minute against 45 for A3:
+
+![Failures and ping-pong, interruption and RRC messages for A3, CHO, DAPS, LTM and CLTM](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/procedures.png)
+
+**Mobility robustness optimisation.** `a3_mro` moves the offset of every cell pair from its own failures;
+here 17 pairs move and failures fall from 0.22 to 0.14 per UE-minute when starting from 3 dB:
+
+![Cell-pair offsets over time under a3_mro, and failures against fixed A3](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/mro.png)
+
+**Fast fading.** With TDL-A or TDL-C the 5th percentile of the link-monitoring SINR on the ns-3 card falls
+from 8.3 dB to 3.8 and 3.4 dB:
+
+![Received power of one vehicle with no fading, TDL-A and TDL-C, and the distribution of the link-monitoring SINR](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/fading.png)
+
+**Slot scheduler.** Round robin and proportional fair with the MCS, TBS and HARQ of TS 38.214; with
+`run.backend: numba` the same runs take 2.2 s and 1.0 s instead of 92.7 s and 93.3 s with NumPy, with identical
+fingerprints (the default rate model takes about 1.0 s for the same run):
+
+![Delivered rate of each vehicle against its SINR for round robin and proportional fair, and the wall time with NumPy and Numba](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/scheduler.png)
+
+**Buffers at handover.** Without data forwarding A3 loses 2.17 % of the data and DAPS 0.34 %; with
+forwarding nothing is lost, and the forwarded data wait 85-349 ms:
+
+![Lost data with and without forwarding, and the PDCP delay, for A3, CHO, DAPS and LTM](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/buffers.png)
+
+**Dual connectivity.** A 4 GHz master cell and a 30 GHz secondary cell: the secondary cell group carries data
+96 % of the time and 183 Mbit/s per user, against 10.1 Mbit/s on the master cell group:
+
+![One user's 4 GHz master cell and 30 GHz secondary cell over time with the dual-connectivity events, and the procedure rates](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/dual-connectivity.png)
+
+**UE receive beams.** Two panels with DFT beams (peak gain 13.7 dBi) raise the mean SINR from 10.9 to 19.2 dB
+and cut failures from 3.60 to 1.44 per UE-minute; a beam sweep keeps them at 3.36:
+
+![Receive beam patterns of a two-panel UE, and SINR and failures for four UE receive-beam setups](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/ue-beams.png)
+
+**Traffic models.** The same handovers (11.3 per UE-minute) under fixed rates, full buffer, periodic packets and FTP model 3,
+with very different rate, cell load and energy per bit:
+
+![Rate, cell load and energy per bit for the four traffic models](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/traffic.png)
+
 ## What it models
 
 - **Scenarios**: the TR 37.885 urban street grid (configurable number of blocks; 433 m x 250 m
@@ -213,7 +254,7 @@ the clause-by-clause detail is in [standard compliance](https://github.com/mjs19
 | Channel | TR 38.901 path loss and LOS (UMi, UMa, RMa, SMa, InH), LOS from buildings, spatially consistent LOS and shadowing, car and O2I building penetration loss, radio maps from a file (clause 8), TR 38.811 for the satellite | received power per site and step with a slow time-varying component; indoor users keep the LOS state and shadowing of their position; optional TDL fast fading with effective SINRs (clause 7.7.2, since 2.2.0) | CDL and the full fast-fading model of clause 7.5, MIMO |
 | Beams and carriers | SSB beams per sector, cell quality from beams, beam failure detection and recovery, several carriers with gaps and Event A5; dual connectivity (NR-DC: SN addition, PSCell change, SN release, SCG failure; option since 2.3.0) | the TR 38.901 antenna element and DFT beams; isotropic UE unless UE receive panels are set (option since 2.4.0); the SCG as one PSCell with a full-buffer share | UE transmit beams and polarisation, conditional PSCell change, fast MCG recovery |
 | Mobility | street-following vehicles (60 km/h, two lanes), highway lanes at 70/140 km/h, a train at 350 km/h (TR 38.854), random waypoints, pedestrians | constant speed per user | handheld rotation and body blockage |
-| Traffic and load | constant rates per 5QI, full buffer, periodic, FTP model 3; cell load drives interference | rate from SINR (Shannon-type mapping), no scheduler | slot scheduler, HARQ, RLC/PDCP, TCP and applications |
+| Traffic and load | constant rates per 5QI, full buffer, periodic, FTP model 3; cell load drives interference; options: a slot scheduler (`protocol.scheduler`: round robin or proportional fair) with the MCS, TBS and HARQ of TS 38.214 (since 2.2.0), and user-plane buffers at handover (`protocol.buffers`: simplified PDCP / RLC in AM or UM with Xn data forwarding, since 2.3.0) | by default the rate from the SINR (Shannon-type mapping) without a scheduler; with the scheduler the channel is held for the 10 ms step and the MCS is chosen from the SINR of one measurement interval earlier (no CSI reports); buffers: downlink only, one bearer per user, the interruption quantised to the measurement interval; both options need the base engine (no beams, layers, NTN or TS 38.133 periods) | uplink data, CSI-based link adaptation, PDCP reordering and status reports at the UE, TCP and applications |
 | Measurements | L1 samples with error, TS 38.331 L3 filter, TS 38.133 measurement periods and gaps (option) | wideband RSRP; SS-RSRP per resource element with beams/carriers | RSRQ, CSI reporting |
 | Procedures | baseline (A3), CHO, DAPS, LTM, conditional LTM, CHO with D1/D2 for satellites, A3/A5 between carriers; rules `a3`, `a3a5`, `a3_mro`, `a3_bandit`, `dqn`, `a3_pred`, `cho`, `cho_d2`, `daps`, `ltm`, `cltm` | fixed preparation, command and execution delays; re-establishment always succeeds after a fixed outage | condEventT1, RACH-less NTN handover, Xn signalling in detail |
 | Failure model | Qout/Qin with windows, N310/N311/T310, T304, command received during T310, re-establishment, link-monitoring restart | Qout/Qin as SINR thresholds (TR 36.839 values) instead of the BLER of a hypothetical PDCCH | BLER-based link monitoring; absolute failure rates are not calibrated: compare rules with each other |
@@ -254,8 +295,10 @@ Ericsson, Nokia, Samsung, Qualcomm and others), for UMa, UMi and the indoor offi
 30 GHz. 325 of 342 compared percentiles are inside the range, none is more than about 1 dB from
 the industry mean, and `handoverlab verify` repeats the check
 ([details](https://github.com/mjs19971997/handoverlab/blob/main/docs/calibration-3gpp.md)). Since 2.4.0 the
-same check runs at 7 GHz (Table 7.8-1A) against the companies of R1-2506406: all 342 percentiles lie inside
-their range, but 1.65-2.88 dB from their mean, which misses the 1.5 dB criterion set before the run.
+same check runs for Table 7.8-1A against the companies of R1-2506406. At 7 GHz (UMa, UMi and SMa with ISD
+1299 m and 1732 m) all 228 percentiles lie inside their range, but the largest distance from their mean is
+1.69-2.43 dB, which misses the 1.5 dB criterion set before the run; the two 6 GHz reruns of UMa and UMi with
+the updated model add 114 percentiles, also all inside, at 1.65 and 2.88 dB.
 
 ![CDFs of coupling loss and geometry for UMa, UMi and SMa at 7 GHz, with the HandoverLab curve inside the company range of R1-2506406](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/calibration_7ghz.png)
 
@@ -304,8 +347,8 @@ L1/L2-triggered mobility.
 
 - **2.4.0**: UE receive beams (panels of TR 38.802, best beam or a sweep); a measurement-prediction rule after
   TR 38.744 (`a3_pred`: predicted Event A3 or measurement skipping, sample and hold or a trained ridge
-  predictor); the slot scheduler as a compiled kernel (`run.backend: numba`, bit-identical, 8-60 times
-  faster); the 7 GHz large-scale calibration against the companies of R1-2506406 (every percentile inside the
+  predictor); the slot scheduler as a compiled kernel (`run.backend: numba`, bit-identical; on the ns-3 card
+  42 times (`rr`) and 93 times (`pf`) faster than the NumPy loop); the 7 GHz large-scale calibration against the companies of R1-2506406 (every percentile inside the
   range, the distance to the mean criterion missed); a [comparison with other simulators](https://github.com/mjs19971997/handoverlab/blob/main/docs/comparison.md).
 - **2.3.0**: user-plane buffers at handover (PDCP / RLC, Xn data forwarding for baseline, conditional, DAPS and
   L1/L2-triggered handover); the TR 37.885 urban macro grid, suburban macro (SMa) and O2I penetration of indoor
@@ -436,13 +479,13 @@ traffic models (one seed, 30 users, 60 s on the urban grid at 10 GHz):
 
 ```text
 model        cell load  rate [Mbit/s]  delivered  SINR [dB]  failures/UE-min
-fixed             0.28          14.25       0.98       24.3             0.12
-full_buffer       0.52         725.93       0.49       21.9             0.08
-periodic          0.28           0.04       0.80       24.4             0.12
-ftp3              0.28           3.93       0.85       24.4             0.12
+fixed             0.28          14.10       0.97       23.6             0.08
+full_buffer       0.52         717.77       0.48       21.2             0.08
+periodic          0.28           0.04       0.86       23.7             0.08
+ftp3              0.28           3.93       0.87       23.7             0.08
 ```
 
-Busier cells interfere more: under full buffer the SINR drops by about 2.5 dB. With one seed each
+Busier cells interfere more: under full buffer the SINR drops by about 2.4 dB. With one seed each
 failure rate counts only a few failures; compare them over several seeds.
 
 The full script is [examples/compare_a3_cho.py](https://github.com/mjs19971997/handoverlab/blob/main/examples/compare_a3_cho.py). Writing your own
@@ -524,9 +567,11 @@ the pages are plain Markdown in [docs/](https://github.com/mjs19971997/handoverl
 25. 2.3.0: buffers at handover, urban macro, SMa and O2I, the high-speed train, dual connectivity.
 26. 2.4.0: UE receive beams, the TR 38.744 prediction rule, the compiled
     scheduler, the 7 GHz calibration and the comparison with other simulators.
-27. **2.4.1 (this release)**: pictures, citation and tutorials brought up to date; the example study
+27. 2.4.1: pictures, citation and tutorials brought up to date; the example study
     completes again; no change of results.
-28. Later (planned, not done), staying a handover simulator: the effect of a handover on what the user
+28. **2.4.2 (this release)**: every option has a picture; the dashboard pictures show the current version;
+    guide and tutorial examples rerun; facts made consistent; no change of results.
+29. Later (planned, not done), staying a handover simulator: the effect of a handover on what the user
     sees (simple TCP and application models on top of the buffers), MIMO as an SINR gain, hundreds of
     users per run, and one scenario definition that also runs in ns-3; condEventT1 and earth-fixed beams.
 
@@ -535,8 +580,11 @@ the pages are plain Markdown in [docs/](https://github.com/mjs19971997/handoverl
 If you use HandoverLab, please cite it as described in [CITATION.cff](https://github.com/mjs19971997/handoverlab/blob/main/CITATION.cff) (GitHub shows
 it under *Cite this repository*). Every release is archived on Zenodo:
 [doi:10.5281/zenodo.23409131](https://doi.org/10.5281/zenodo.23409131) cites all versions (it resolves to
-the latest). To cite the exact version you used, take its DOI from the version list on that page; version
-2.4.0 is [doi:10.5281/zenodo.23582521](https://doi.org/10.5281/zenodo.23582521).
+the latest). To cite the exact version you used, take its DOI from the version list on that page, where
+the DOI of the latest version is listed; for example, version 2.4.1 is
+[doi:10.5281/zenodo.23585308](https://doi.org/10.5281/zenodo.23585308) and version 2.4.0
+[doi:10.5281/zenodo.23582521](https://doi.org/10.5281/zenodo.23582521). The BibTeX entry below cites 2.4.1;
+replace version and DOI with those of the version you used.
 
 ```bibtex
 @software{handoverlab,
@@ -544,8 +592,8 @@ the latest). To cite the exact version you used, take its DOI from the version l
   title     = {{HandoverLab}: system-level handover simulator for 5G-Advanced and beyond-5G research},
   year      = {2026},
   publisher = {Zenodo},
-  version   = {2.4.0},
-  doi       = {10.5281/zenodo.23582521},
+  version   = {2.4.1},
+  doi       = {10.5281/zenodo.23585308},
   url       = {https://github.com/mjs19971997/handoverlab}
 }
 ```

{handoverlab-2.4.1 → handoverlab-2.4.2}/README.md

@@ -12,7 +12,7 @@ received-power-level radio model from TR 38.901 (TR 38.811 for the satellite) (o
 and several carriers), an L3-filtered measurement chain, a radio-link failure model, and an
 outcome label for every handover attempt.
 
-> **Status: 2.4.1** (`python -m pip install handoverlab`). The public surface (configuration and
+> **Status: 2.4.2** (`python -m pip install handoverlab`). The public surface (configuration and
 > result formats with a schema version, the rule interface, metric names, commands and the
 > documented Python names) follows the [stability policy](https://github.com/mjs19971997/handoverlab/blob/main/docs/stability.md): within 2.x it only grows,
 > and anything removed is deprecated first. 2.0.0 makes the 3GPP values the defaults (the protocol profile,
@@ -92,6 +92,47 @@ accurate than sample and hold 400 ms ahead (1.84 / 2.66 / 3.14 dB against 2.38 /
 
 ![Prediction error against horizon for the ridge predictor and sample and hold at 30, 60 and 90 km/h](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/ai-mobility.png)
 
+**Handover procedures side by side.** On one card failures fall from 0.6 (A3) to 0.2 (LTM and CLTM) per
+UE-minute; DAPS has no execution interruption; LTM pays with 192 RRC messages per UE-minute against 45 for A3:
+
+![Failures and ping-pong, interruption and RRC messages for A3, CHO, DAPS, LTM and CLTM](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/procedures.png)
+
+**Mobility robustness optimisation.** `a3_mro` moves the offset of every cell pair from its own failures;
+here 17 pairs move and failures fall from 0.22 to 0.14 per UE-minute when starting from 3 dB:
+
+![Cell-pair offsets over time under a3_mro, and failures against fixed A3](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/mro.png)
+
+**Fast fading.** With TDL-A or TDL-C the 5th percentile of the link-monitoring SINR on the ns-3 card falls
+from 8.3 dB to 3.8 and 3.4 dB:
+
+![Received power of one vehicle with no fading, TDL-A and TDL-C, and the distribution of the link-monitoring SINR](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/fading.png)
+
+**Slot scheduler.** Round robin and proportional fair with the MCS, TBS and HARQ of TS 38.214; with
+`run.backend: numba` the same runs take 2.2 s and 1.0 s instead of 92.7 s and 93.3 s with NumPy, with identical
+fingerprints (the default rate model takes about 1.0 s for the same run):
+
+![Delivered rate of each vehicle against its SINR for round robin and proportional fair, and the wall time with NumPy and Numba](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/scheduler.png)
+
+**Buffers at handover.** Without data forwarding A3 loses 2.17 % of the data and DAPS 0.34 %; with
+forwarding nothing is lost, and the forwarded data wait 85-349 ms:
+
+![Lost data with and without forwarding, and the PDCP delay, for A3, CHO, DAPS and LTM](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/buffers.png)
+
+**Dual connectivity.** A 4 GHz master cell and a 30 GHz secondary cell: the secondary cell group carries data
+96 % of the time and 183 Mbit/s per user, against 10.1 Mbit/s on the master cell group:
+
+![One user's 4 GHz master cell and 30 GHz secondary cell over time with the dual-connectivity events, and the procedure rates](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/dual-connectivity.png)
+
+**UE receive beams.** Two panels with DFT beams (peak gain 13.7 dBi) raise the mean SINR from 10.9 to 19.2 dB
+and cut failures from 3.60 to 1.44 per UE-minute; a beam sweep keeps them at 3.36:
+
+![Receive beam patterns of a two-panel UE, and SINR and failures for four UE receive-beam setups](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/ue-beams.png)
+
+**Traffic models.** The same handovers (11.3 per UE-minute) under fixed rates, full buffer, periodic packets and FTP model 3,
+with very different rate, cell load and energy per bit:
+
+![Rate, cell load and energy per bit for the four traffic models](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/traffic.png)
+
 ## What it models
 
 - **Scenarios**: the TR 37.885 urban street grid (configurable number of blocks; 433 m x 250 m
@@ -155,7 +196,7 @@ the clause-by-clause detail is in [standard compliance](https://github.com/mjs19
 | Channel | TR 38.901 path loss and LOS (UMi, UMa, RMa, SMa, InH), LOS from buildings, spatially consistent LOS and shadowing, car and O2I building penetration loss, radio maps from a file (clause 8), TR 38.811 for the satellite | received power per site and step with a slow time-varying component; indoor users keep the LOS state and shadowing of their position; optional TDL fast fading with effective SINRs (clause 7.7.2, since 2.2.0) | CDL and the full fast-fading model of clause 7.5, MIMO |
 | Beams and carriers | SSB beams per sector, cell quality from beams, beam failure detection and recovery, several carriers with gaps and Event A5; dual connectivity (NR-DC: SN addition, PSCell change, SN release, SCG failure; option since 2.3.0) | the TR 38.901 antenna element and DFT beams; isotropic UE unless UE receive panels are set (option since 2.4.0); the SCG as one PSCell with a full-buffer share | UE transmit beams and polarisation, conditional PSCell change, fast MCG recovery |
 | Mobility | street-following vehicles (60 km/h, two lanes), highway lanes at 70/140 km/h, a train at 350 km/h (TR 38.854), random waypoints, pedestrians | constant speed per user | handheld rotation and body blockage |
-| Traffic and load | constant rates per 5QI, full buffer, periodic, FTP model 3; cell load drives interference | rate from SINR (Shannon-type mapping), no scheduler | slot scheduler, HARQ, RLC/PDCP, TCP and applications |
+| Traffic and load | constant rates per 5QI, full buffer, periodic, FTP model 3; cell load drives interference; options: a slot scheduler (`protocol.scheduler`: round robin or proportional fair) with the MCS, TBS and HARQ of TS 38.214 (since 2.2.0), and user-plane buffers at handover (`protocol.buffers`: simplified PDCP / RLC in AM or UM with Xn data forwarding, since 2.3.0) | by default the rate from the SINR (Shannon-type mapping) without a scheduler; with the scheduler the channel is held for the 10 ms step and the MCS is chosen from the SINR of one measurement interval earlier (no CSI reports); buffers: downlink only, one bearer per user, the interruption quantised to the measurement interval; both options need the base engine (no beams, layers, NTN or TS 38.133 periods) | uplink data, CSI-based link adaptation, PDCP reordering and status reports at the UE, TCP and applications |
 | Measurements | L1 samples with error, TS 38.331 L3 filter, TS 38.133 measurement periods and gaps (option) | wideband RSRP; SS-RSRP per resource element with beams/carriers | RSRQ, CSI reporting |
 | Procedures | baseline (A3), CHO, DAPS, LTM, conditional LTM, CHO with D1/D2 for satellites, A3/A5 between carriers; rules `a3`, `a3a5`, `a3_mro`, `a3_bandit`, `dqn`, `a3_pred`, `cho`, `cho_d2`, `daps`, `ltm`, `cltm` | fixed preparation, command and execution delays; re-establishment always succeeds after a fixed outage | condEventT1, RACH-less NTN handover, Xn signalling in detail |
 | Failure model | Qout/Qin with windows, N310/N311/T310, T304, command received during T310, re-establishment, link-monitoring restart | Qout/Qin as SINR thresholds (TR 36.839 values) instead of the BLER of a hypothetical PDCCH | BLER-based link monitoring; absolute failure rates are not calibrated: compare rules with each other |
@@ -196,8 +237,10 @@ Ericsson, Nokia, Samsung, Qualcomm and others), for UMa, UMi and the indoor offi
 30 GHz. 325 of 342 compared percentiles are inside the range, none is more than about 1 dB from
 the industry mean, and `handoverlab verify` repeats the check
 ([details](https://github.com/mjs19971997/handoverlab/blob/main/docs/calibration-3gpp.md)). Since 2.4.0 the
-same check runs at 7 GHz (Table 7.8-1A) against the companies of R1-2506406: all 342 percentiles lie inside
-their range, but 1.65-2.88 dB from their mean, which misses the 1.5 dB criterion set before the run.
+same check runs for Table 7.8-1A against the companies of R1-2506406. At 7 GHz (UMa, UMi and SMa with ISD
+1299 m and 1732 m) all 228 percentiles lie inside their range, but the largest distance from their mean is
+1.69-2.43 dB, which misses the 1.5 dB criterion set before the run; the two 6 GHz reruns of UMa and UMi with
+the updated model add 114 percentiles, also all inside, at 1.65 and 2.88 dB.
 
 ![CDFs of coupling loss and geometry for UMa, UMi and SMa at 7 GHz, with the HandoverLab curve inside the company range of R1-2506406](https://raw.githubusercontent.com/mjs19971997/handoverlab/main/docs/images/calibration_7ghz.png)
 
@@ -246,8 +289,8 @@ L1/L2-triggered mobility.
 
 - **2.4.0**: UE receive beams (panels of TR 38.802, best beam or a sweep); a measurement-prediction rule after
   TR 38.744 (`a3_pred`: predicted Event A3 or measurement skipping, sample and hold or a trained ridge
-  predictor); the slot scheduler as a compiled kernel (`run.backend: numba`, bit-identical, 8-60 times
-  faster); the 7 GHz large-scale calibration against the companies of R1-2506406 (every percentile inside the
+  predictor); the slot scheduler as a compiled kernel (`run.backend: numba`, bit-identical; on the ns-3 card
+  42 times (`rr`) and 93 times (`pf`) faster than the NumPy loop); the 7 GHz large-scale calibration against the companies of R1-2506406 (every percentile inside the
   range, the distance to the mean criterion missed); a [comparison with other simulators](https://github.com/mjs19971997/handoverlab/blob/main/docs/comparison.md).
 - **2.3.0**: user-plane buffers at handover (PDCP / RLC, Xn data forwarding for baseline, conditional, DAPS and
   L1/L2-triggered handover); the TR 37.885 urban macro grid, suburban macro (SMa) and O2I penetration of indoor
@@ -378,13 +421,13 @@ traffic models (one seed, 30 users, 60 s on the urban grid at 10 GHz):
 
 ```text
 model        cell load  rate [Mbit/s]  delivered  SINR [dB]  failures/UE-min
-fixed             0.28          14.25       0.98       24.3             0.12
-full_buffer       0.52         725.93       0.49       21.9             0.08
-periodic          0.28           0.04       0.80       24.4             0.12
-ftp3              0.28           3.93       0.85       24.4             0.12
+fixed             0.28          14.10       0.97       23.6             0.08
+full_buffer       0.52         717.77       0.48       21.2             0.08
+periodic          0.28           0.04       0.86       23.7             0.08
+ftp3              0.28           3.93       0.87       23.7             0.08
 ```
 
-Busier cells interfere more: under full buffer the SINR drops by about 2.5 dB. With one seed each
+Busier cells interfere more: under full buffer the SINR drops by about 2.4 dB. With one seed each
 failure rate counts only a few failures; compare them over several seeds.
 
 The full script is [examples/compare_a3_cho.py](https://github.com/mjs19971997/handoverlab/blob/main/examples/compare_a3_cho.py). Writing your own
@@ -466,9 +509,11 @@ the pages are plain Markdown in [docs/](https://github.com/mjs19971997/handoverl
 25. 2.3.0: buffers at handover, urban macro, SMa and O2I, the high-speed train, dual connectivity.
 26. 2.4.0: UE receive beams, the TR 38.744 prediction rule, the compiled
     scheduler, the 7 GHz calibration and the comparison with other simulators.
-27. **2.4.1 (this release)**: pictures, citation and tutorials brought up to date; the example study
+27. 2.4.1: pictures, citation and tutorials brought up to date; the example study
     completes again; no change of results.
-28. Later (planned, not done), staying a handover simulator: the effect of a handover on what the user
+28. **2.4.2 (this release)**: every option has a picture; the dashboard pictures show the current version;
+    guide and tutorial examples rerun; facts made consistent; no change of results.
+29. Later (planned, not done), staying a handover simulator: the effect of a handover on what the user
     sees (simple TCP and application models on top of the buffers), MIMO as an SINR gain, hundreds of
     users per run, and one scenario definition that also runs in ns-3; condEventT1 and earth-fixed beams.
 
@@ -477,8 +522,11 @@ the pages are plain Markdown in [docs/](https://github.com/mjs19971997/handoverl
 If you use HandoverLab, please cite it as described in [CITATION.cff](https://github.com/mjs19971997/handoverlab/blob/main/CITATION.cff) (GitHub shows
 it under *Cite this repository*). Every release is archived on Zenodo:
 [doi:10.5281/zenodo.23409131](https://doi.org/10.5281/zenodo.23409131) cites all versions (it resolves to
-the latest). To cite the exact version you used, take its DOI from the version list on that page; version
-2.4.0 is [doi:10.5281/zenodo.23582521](https://doi.org/10.5281/zenodo.23582521).
+the latest). To cite the exact version you used, take its DOI from the version list on that page, where
+the DOI of the latest version is listed; for example, version 2.4.1 is
+[doi:10.5281/zenodo.23585308](https://doi.org/10.5281/zenodo.23585308) and version 2.4.0
+[doi:10.5281/zenodo.23582521](https://doi.org/10.5281/zenodo.23582521). The BibTeX entry below cites 2.4.1;
+replace version and DOI with those of the version you used.
 
 ```bibtex
 @software{handoverlab,
@@ -486,8 +534,8 @@ the latest). To cite the exact version you used, take its DOI from the version l
   title     = {{HandoverLab}: system-level handover simulator for 5G-Advanced and beyond-5G research},
   year      = {2026},
   publisher = {Zenodo},
-  version   = {2.4.0},
-  doi       = {10.5281/zenodo.23582521},
+  version   = {2.4.1},
+  doi       = {10.5281/zenodo.23585308},
   url       = {https://github.com/mjs19971997/handoverlab}
 }
 ```

{handoverlab-2.4.1 → handoverlab-2.4.2}/docs/calibration-3gpp.md

@@ -91,8 +91,9 @@ InterDigital and ZTE, "Calibration Results for 7 - 24 GHz SI";
 `Calibration_LS_v35`, based on TR 38.901 V19.0.0). The criteria were fixed before the first run: every
 percentile 5-95 % inside the company range widened by 0.5 dB (C1, the rule of the cases above), and the
 largest distance from the company mean at most 1.5 dB per case (C2). Result, 30 000 users per case, seed 1:
-**C1 passes for all 18 case-metric pairs (342 of 342 percentiles strictly inside the range); C2 fails for all
-six cases (largest distance 1.65-2.88 dB).** `handoverlab verify` runs C1 as checks and C2 as notes in the
+**C1 passes for all 18 case-metric pairs of the six cases (342 of 342 percentiles strictly inside the range;
+228 of 228 for the four 7 GHz cases); C2 fails for all six cases (largest distance 1.65-2.88 dB; 1.69-2.43 dB
+for the four 7 GHz cases, 1.65 and 2.88 dB for the two 6 GHz reruns).** `handoverlab verify` runs C1 as checks and C2 as notes in the
 group `calibration`.
 
 **The reference.** `src/handoverlab/verify/data/r1_2506406.csv` keeps, in the format of `r1_165974.csv`, the

{handoverlab-2.4.1 → handoverlab-2.4.2}/docs/comparison.md

@@ -41,7 +41,7 @@ Tools compared (latest release found on 2026-10-22):
 
 | Tool | NTN | Beams | Fast fading and link-to-system mapping | Scheduler |
 |---|---|---|---|---|
-| HandoverLab 2.4.0 | one LEO satellite with earth-moving beams (TR 38.811, TR 38.821), CHO with D2; no several satellites, Doppler or earth-fixed beams ([NTN guide](guides/ntn.md)) | SSB beams per sector from the TR 38.901 element and DFT beams, cell quality from beams, beam failure detection and recovery; UE receive beams optional (1, 2 or 4 panels, [UE beams](guides/ue-beams.md)), isotropic UE by default; no MIMO ([beams](guides/beams-layers.md)) | off by default (large-scale channel with a slow time-varying part); option: TDL-A to TDL-E with MIESM for link monitoring and a capacity-equivalent SINR for the rate; no CDL ([fading](guides/fading.md)) | by default a rate model without a scheduler; option: slot scheduler RR or PF with MCS, TBS and HARQ (base engine only; with `run.backend: numba` 11-59 times faster than its NumPy loop, bit-identical) ([scheduler](guides/scheduler.md)) |
+| HandoverLab 2.4.0 | one LEO satellite with earth-moving beams (TR 38.811, TR 38.821), CHO with D2; no several satellites, Doppler or earth-fixed beams ([NTN guide](guides/ntn.md)) | SSB beams per sector from the TR 38.901 element and DFT beams, cell quality from beams, beam failure detection and recovery; UE receive beams optional (1, 2 or 4 panels, [UE beams](guides/ue-beams.md)), isotropic UE by default; no MIMO ([beams](guides/beams-layers.md)) | off by default (large-scale channel with a slow time-varying part); option: TDL-A to TDL-E with MIESM for link monitoring and a capacity-equivalent SINR for the rate; no CDL ([fading](guides/fading.md)) | by default a rate model without a scheduler; option: slot scheduler RR or PF with MCS, TBS and HARQ (base engine only; with `run.backend: numba` bit-identical and, on the ns-3 card, 42 (`rr`) and 93 (`pf`) times faster than its NumPy loop) ([scheduler](guides/scheduler.md)) |
 | ns-3 5G-LENA v5.1 | NTN channel (TR 38.811, from ns-3 mainline [L9]) and a LEO mobility example [L1, L2] | ideal and SRS-based realistic beamforming; beam management "Simplified model; no SSB blocks" [L1]; quasi-omni beams in the RRC / handover context [L3] | TR 38.901 with fast fading; EESM-based PHY abstraction with SINR-BLER tables [L1, L8] | PF, RR, MR, QoS-aware, RL-based; OFDMA and TDMA [L1] |
 | ns-3 mmWave v8.0 | TR 38.811 channel inherited from ns-3.42; no NTN protocol features stated [M2] | SVD- and DFT-based beamforming; NR beam tracking listed as future work [M1, M3] | TR 38.901 channel, ray-tracing and measured traces; EESM error model from 5G-LENA [M1, M3] | flexible-TTI RR, PF, max-rate, max-weight [M1] |
 | Simu5G 1.8.0 | not in the official release; separate third-party work exists [S10] | not stated; antenna-gain link budget only [S1] | path loss, LOS and shadowing of TR 36.814 / 36.873 / 38.901 with Jakes or Rayleigh fading; reception from SINR and BLER curves [S5, S6] | MAX C/I, PF, DRR, QoS-aware PF [S1] |
@@ -54,7 +54,7 @@ Tools compared (latest release found on 2026-10-22):
 
 | Tool | Speed and scale | Validation against 3GPP |
 |---|---|---|
-| HandoverLab 2.4.0 | one process: 2 rules, 40 users, 76 cells, 60 s simulated in 10-15 s on a modest virtual machine (1.11.0 timings, [performance](performance.md)); many rules share one world; no published figures for thousands of nodes | large-scale calibration of TR 38.901 clause 7.8.1 against the 21 companies of R1-165974 (325 of 342 percentiles inside the range) and at 7 GHz against R1-2506406 (all 342 percentiles inside the range, 1.7-2.9 dB from the company mean, [details](calibration-3gpp.md)); handover counts against ns-3 / 5G-LENA; failure levels differ from ns-3 ([calibration](calibration.md)); clause-by-clause [standard compliance](standard-compliance.md) |
+| HandoverLab 2.4.0 | one process: 2 rules, 40 users, 76 cells, 60 s simulated in 10-15 s on a modest virtual machine (1.11.0 timings, [performance](performance.md)); many rules share one world; no published figures for thousands of nodes | large-scale calibration of TR 38.901 clause 7.8.1 against the 21 companies of R1-165974 (325 of 342 percentiles inside the range) and against R1-2506406 (at 7 GHz all 228 percentiles of UMa, UMi and SMa inside the company range, largest distance from the company mean 1.69-2.43 dB; with the two 6 GHz reruns 342 percentiles, 1.65-2.88 dB, [details](calibration-3gpp.md)); handover counts against ns-3 / 5G-LENA; failure levels differ from ns-3 ([calibration](calibration.md)); clause-by-clause [standard compliance](standard-compliance.md) |
 | ns-3 5G-LENA v5.1 | runtime numbers: not stated for the module; a MIMO channel speed-up of up to 16 times is reported in a WNS3 paper [L11]; the calibration scenario has 12 gNBs and 120 UEs [L10] | calibrated in 3GPP outdoor reference scenarios (SIMPAT 2022) [L7]; calibration examples for RP-180524 [L2]; mobility checked against TR 36.839 (v5.1) [L5] |
 | ns-3 mmWave v8.0 | not stated | not stated (examples "verify its correct functioning" [M6]) |
 | Simu5G 1.8.0 | background cells and UEs for large scenarios; real-time emulation of "hundreds of simulated users and tens of cells" on one desktop [S1, S9] | PHY abstraction validated in 3GPP-based scenarios [S8]; fingerprint regression tests [S1] |

{handoverlab-2.4.1 → handoverlab-2.4.2}/docs/guides/beams-layers.md

@@ -50,15 +50,16 @@ UE-minute):
 
 | Rule | Handovers | Failures | Beam switches | Beam failures | recovered | ended in RLF | Interruption [s] | SINR [dB] |
 |---|---|---|---|---|---|---|---|---|
-| A3 | 25.0 | 1.50 | 46.6 | 2.58 | 1.27 | 0.80 | 2.53 | 14.0 |
-| CHO | 25.9 | 1.23 | 49.5 | 1.98 | 1.32 | 0.45 | 1.77 | 15.5 |
-| LTM | 31.3 | 0.80 | 51.1 | 1.55 | 0.93 | 0.28 | 1.12 | 16.0 |
-| CLTM | 31.4 | 0.75 | 50.1 | 1.38 | 0.88 | 0.25 | 1.09 | 16.4 |
+| A3 | 20.4 | 5.50 | 42.9 | 11.43 | 4.83 | 5.42 | 6.36 | 9.8 |
+| CHO | 22.0 | 3.88 | 46.6 | 8.73 | 4.12 | 3.83 | 3.67 | 11.6 |
+| LTM | 30.6 | 2.80 | 50.0 | 7.33 | 3.30 | 2.75 | 2.60 | 13.1 |
+| CLTM | 30.6 | 2.72 | 49.6 | 7.40 | 3.60 | 2.67 | 2.55 | 13.5 |
 
-Half to two thirds of the detected beam failures are recovered on another beam of the same cell; most
-of the rest end in a radio-link failure because no beam of the serving cell is good enough any more
-(the user needed a handover), a few are ended by a handover. Faster cell changes (LTM, conditional LTM) leave fewer
-beam failures to recover.
+A little less than half (42-49 %) of the detected beam failures are recovered on another beam of the
+same cell; 36-47 % end in a radio-link failure because no beam of the serving cell is good enough any
+more (the user needed a handover), and these make up 98-99 % of the failures; the rest (9-17 %) are
+ended by a handover. Faster cell changes (LTM, conditional LTM) leave fewer beam failures to recover
+(7.3-7.4 per UE-minute against 11.4 with A3).
 
 ## 2. Two carriers: a macro layer and a small-cell layer
 

{handoverlab-2.4.1 → handoverlab-2.4.2}/docs/guides/buffers.md

@@ -8,6 +8,10 @@ delayed by the interruption. It works with every procedure (baseline handover su
 DAPS, LTM and conditional LTM). It is off by default; with it off every result of 2.2.0 is
 unchanged bit for bit (the new metrics are 0).
 
+![Lost data with and without forwarding, and the PDCP delay, for A3, CHO, DAPS and LTM](../images/buffers.png)
+
+*Without forwarding A3 loses 2.17 % of the data, CHO 1.16 %, DAPS 0.34 % and LTM 0.41 %; with forwarding nothing is lost, and the forwarded data wait 85-349 ms.*
+
 ```yaml
 scenario:
   base: smoke
@@ -97,15 +101,17 @@ forwarding and links below Qout (no data in the rate model) add.
 
 | Rule | forwarded kbyte/UE-min | lost share without forwarding | mean PDCP delay | delay of forwarded data |
 |---|---|---|---|---|
-| A3 | 6.2 | 2.1 % | 2.9 ms | 123 ms |
-| CHO (late / early forwarding) | 4.2 | 1.4 % | 1.3 ms | 80 / 70 ms |
-| DAPS | 6.2 (copies) | 0 | 2.6 ms | 157 ms |
-| LTM | 1.6 | 0.5 % | 0.6 ms | 92 ms |
-
-With forwarding nothing is lost. Late forwarding adds the 2 x 5 ms wait for CHO; for LTM the wait
-ends before the next measurement instant and does not show. DAPS gains little here: most of its
-executions start with the source SINR already below Qout, where the rate model sends nothing, so the
-data left for the target are the oldest ones.
+| A3 | 7.4 | 2.2 % | 8.3 ms | 313 ms |
+| CHO (late / early forwarding) | 3.5 | 1.2 % | 1.1 / 0.9 ms | 85 / 75 ms |
+| DAPS | 6.7 (copies) | 0.3 % (all at failures) | 6.4 ms | 349 ms |
+| LTM | 1.2 | 0.4 % | 0.4 ms | 94 ms |
+
+With forwarding nothing is lost. Without it DAPS loses no data at its executions; its 0.3 % are
+lost at failures and re-establishments. Late forwarding adds the 2 x 5 ms wait for CHO; for LTM the
+wait ends before the next measurement instant and does not show (94 ms either way). DAPS gains
+little here: most of its executions start with the source SINR already below Qout, where the rate
+model sends nothing, so the data left for the target are the oldest ones, and its forwarded data
+wait longest (349 ms).
 
 ## 7. Checks
 

{handoverlab-2.4.1 → handoverlab-2.4.2}/docs/guides/daps-ltm.md

@@ -2,6 +2,10 @@
 
 Since 1.0.0rc2 HandoverLab has two procedures next to baseline and conditional handover:
 
+![Failures and ping-pong, interruption and RRC messages for A3, CHO, DAPS, LTM and CLTM](../images/procedures.png)
+
+*On one card failures fall from 0.6 (A3) to 0.2 (LTM and CLTM) per UE-minute; DAPS has no execution interruption; LTM sends 192 RRC messages per UE-minute against 45 for A3.*
+
 | Rule | Procedure | Specification | What changes compared with `a3` |
 |---|---|---|---|
 | `daps` | DAPS handover (Rel-16) | TS 38.300 clause 9.2.3.2, TS 38.331 clause 5.3.5.8.3 | the source keeps serving during the execution; a failed execution falls back to the source |

{handoverlab-2.4.1 → handoverlab-2.4.2}/docs/guides/dual-connectivity.md

@@ -4,6 +4,10 @@ Since 2.3.0 a user can hold a secondary cell group (SCG) next to its master cell
 NR-DC case of TS 37.340 V19.3.0 clause 4.1.3.3, one gNB as master node (MN) and another as secondary
 node (SN). The option `protocol.dc` is off by default; with it off every result stays as it was.
 
+![One user's 4 GHz master cell and 30 GHz secondary cell over time with the dual-connectivity events, and the procedure rates](../images/dual-connectivity.png)
+
+*The SCG carries data 96 % of the time; per UE-minute there are 21.1 PSCell changes and 16.3 MCG handovers, and per user the SCG carries 183 Mbit/s against 10.1 Mbit/s on the MCG.*
+
 The model is the simplest consistent subset that a system-level simulator needs: when an SCG is
 added, changed or lost, what that costs in signalling and interruption, and how much time the
 user spends with a second link. The MCG behaves exactly as without dual connectivity: its handover

{handoverlab-2.4.1 → handoverlab-2.4.2}/docs/guides/fading.md

@@ -6,6 +6,10 @@ slow time-varying component, with radio-link monitoring on the wideband SINR. Si
 the SINR at several frequencies to one effective SINR. It is off by default; with it off every
 result of 2.1.0 is unchanged bit for bit.
 
+![Received power of one vehicle with no fading, TDL-A and TDL-C, and the distribution of the link-monitoring SINR](../images/fading.png)
+
+*On the ns-3 card (10 vehicles, 20 s) the 5th percentile of the link-monitoring SINR falls from 8.3 dB without fading to 3.8 dB (TDL-A) and 3.4 dB (TDL-C); the MIESM value of QPSK saturates at 18.5 dB.*
+
 ```yaml
 scenario:
   base: ns3-urban-3.5ghz
@@ -45,9 +49,13 @@ another simulator is used; a BLER per MCS (TS 38.214 tables) follows with the sl
 
 ## 3. Cost and limits
 
-- A single run is about twice as long (32 sinusoids per tap, every step; 10 users on the ns-3 card:
-  about 6 s instead of 3 s for 20 s simulated); many rules on one world take longer (24 rules: about
-  6 to 8 times), as the batched and compiled loops are not used with fading.
+- The engine takes about 10 times as long (32 sinusoids per tap, every step; 10 users on the
+  ns-3 card, 20 s simulated, without building the world, median of seven runs: 7.7 s with `tdl-a`
+  and 7.8 s with `tdl-c` instead of 0.74 s, with the default traffic of the card; the 1.02 s of the
+  [scheduler measurement](../performance.md) is another session with full-buffer traffic, and machine load
+  changes such times by up to a factor of two); many
+  rules on one world the same (24 rules: 53 s instead of 5.4 s), as the batched and compiled loops
+  are not used with fading.
 - This version needs the base engine: no beams, layers, NTN or TS 38.133 periods
   (`meas_periods: sample`, `rlm_eval: fixed`); such a configuration is refused.
 - The step stays 10 ms. At 30 m/s and 3.5 GHz the coherence time is about 1 ms, so successive

{handoverlab-2.4.1 → handoverlab-2.4.2}/docs/guides/indoor-rural.md

@@ -69,27 +69,29 @@ Means over three seeds per user-minute, with the cards as they are and with the
 
 | Scenario | Rule | LOS state | Handovers | Failures | Unnecessary | Ping-pong | Interruption [s] |
 |---|---|---|---|---|---|---|---|
-| indoor | A3 3 dB 160 ms | soft | 6.74 | 0.02 | 2.82 | 0.41 | 0.29 |
-| indoor | A3 3 dB 160 ms | hard | 7.12 | 0.16 | 3.04 | 0.46 | 0.45 |
-| indoor | A3 5 dB 320 ms | soft | 4.74 | 0.10 | 1.28 | 0.06 | 0.29 |
-| indoor | `a3_mro` | soft | 6.69 | 0.02 | 2.80 | 0.40 | 0.29 |
-| rural | A3 3 dB 160 ms | soft | 11.93 | 0.33 | 6.86 | 1.71 | 0.82 |
-| rural | A3 3 dB 160 ms | hard | 13.16 | 1.41 | 7.58 | 1.95 | 1.97 |
-| rural | A3 5 dB 320 ms | soft | 7.80 | 0.42 | 3.49 | 0.39 | 0.74 |
-| rural | `a3_mro` | soft | 10.36 | 0.23 | 5.55 | 1.15 | 0.65 |
-
-- **Indoors**, many handovers are unnecessary or ping-pong even at walking speed, because every
-  neighbour is close. This is the point of the scenario: a rule has to avoid switching between
-  nearly equal cells. A larger offset and time-to-trigger halve the unnecessary handovers at the
-  price of more late ones.
+| indoor | A3 3 dB 160 ms | soft | 3.81 | 0.00 | 0.86 | 0.02 | 0.15 |
+| indoor | A3 3 dB 160 ms | hard | 3.95 | 0.00 | 0.96 | 0.05 | 0.16 |
+| indoor | A3 5 dB 320 ms | soft | 2.91 | 0.02 | 0.23 | 0.00 | 0.14 |
+| indoor | `a3_mro` | soft | 3.77 | 0.00 | 0.84 | 0.02 | 0.15 |
+| rural | A3 3 dB 160 ms | soft | 13.07 | 0.07 | 7.58 | 1.82 | 0.67 |
+| rural | A3 3 dB 160 ms | hard | 15.62 | 0.18 | 9.24 | 2.57 | 1.06 |
+| rural | A3 5 dB 320 ms | soft | 8.86 | 0.21 | 4.09 | 0.45 | 0.63 |
+| rural | `a3_mro` | soft | 10.56 | 0.08 | 5.51 | 0.97 | 0.56 |
+
+- **Indoors**, about a quarter of the handovers are unnecessary even at walking speed (0.86 of 3.81
+  per user-minute), because every neighbour is close; ping-pong is rare. This is the point of the
+  scenario: a rule has to avoid switching between nearly equal cells. A larger offset and
+  time-to-trigger cut the unnecessary handovers by about three quarters at the price of a few late
+  ones (0.02 failures per user-minute, all too late, against none).
 - **In rural cells**, the handover rate is far above what the cell size alone would give, and most
   handovers are unnecessary: the 8 dB shadowing with 120 m decorrelation, uncorrelated between
   sites (TR 38.901 clause 7.5 step 4; half correlated until 2.0.0), moves the best cell often at
   120 km/h. Compare rules with each other here, and do
   not read the absolute handover rate as that of a real rural network.
 - **Hard against soft LOS**: with the hard switch, a link jumps by about 20 dB (RMa at 1-2 km) or
-  about 15 dB (InH at 20 m) when its state changes, and these jumps cause most failures. The soft state
-  removes most of them without changing the handover rate much.
+  about 15 dB (InH at 20 m) when its state changes. In rural cells these jumps raise the failures from
+  0.07 to 0.18 per user-minute and the handovers by about a fifth (13.07 to 15.62); indoors there are
+  no failures with either state, and the hard switch adds only a few handovers (3.81 to 3.95).
 - The failure model is not calibrated in absolute terms in any scenario; read failure rates
   relative to each other.