rosotacom-dev 2.5.dev75__py3-none-any.whl → 2.5.dev77__py3-none-any.whl

rosotacom/resources/examples/profiles.yaml

@@ -169,3 +169,150 @@ profiles:
   # camera stream - a source-side case. Deliberately unshaped: play the case
   # bag with `--profile none` to see that the link is not the cause.
   field-20260817-case6-source-gap: {}
+
+  # ---- fragment-law tilt (B1): three loss processes, one delay model -------
+  # The field fit says message loss follows 1-(1-p)^ceil(size/F) and the field
+  # residual is systematic in size: the smallest class loses about half of what
+  # the fit predicts and the largest about 2.9x more. The campaign cannot
+  # separate an accounting artefact from a property of the link. These three
+  # can: the delay model is the drive's own table in all of them, and the only
+  # thing that moves is how the loss is distributed over packets.
+  #
+  # The rate is raised to ~1% per packet in every arm so a 240 s run at 10 Hz
+  # resolves the small end; the law's *form* is what is under test, and it does
+  # not depend on the level.
+
+  # A -- independent per packet. The law is exact by construction here, so this
+  # arm measures the measurement chain and nothing else.
+  tilt-iid:
+    uplink:
+      delay: 25ms
+      jitter: 18ms
+      distribution: field-20260817
+      distribution_file: dist/field-20260817.dist
+      loss: 1%
+    downlink: { delay: 7ms, jitter: 5ms }
+
+  # B -- the drive's own two-state process, scaled to the same mean. Clustering
+  # correlates the fragments of one message, so large messages should lose
+  # *less* than the independent law predicts -- the opposite sign to the field.
+  # p and r are the drive's, so the runs and gaps keep their measured lengths.
+  tilt-bursty:
+    uplink:
+      delay: 25ms
+      jitter: 18ms
+      distribution: field-20260817
+      distribution_file: dist/field-20260817.dist
+      loss_gemodel: { p: 0.102%, r: 2.5%, loss_bad: 13.5%, loss_good: 0.49% }
+    downlink: { delay: 7ms, jitter: 5ms }
+
+  # C -- A plus a queue a burst can fill. 4 Mbit/s is above the largest class's
+  # mean offered rate (38 kB at 10 Hz is ~3.0 Mbit/s of payload) and below its
+  # instantaneous one, so a 38-fragment message meets a queue and a 1-fragment
+  # message does not. That is the burst-tilt candidate, isolated.
+  tilt-iid-queued:
+    uplink:
+      rate: 4mbit
+      delay: 25ms
+      jitter: 18ms
+      distribution: field-20260817
+      distribution_file: dist/field-20260817.dist
+      loss: 1%
+    downlink: { delay: 7ms, jitter: 5ms }
+
+  # B2 -- the boundary of the design rule. Same delay model, two per-fragment
+  # rates: the one the rule is applied at, and one twice as bad. The rule says
+  # what the size distribution does; it does not say what the link will be.
+  tilt-iid-worse:
+    uplink:
+      delay: 25ms
+      jitter: 18ms
+      distribution: field-20260817
+      distribution_file: dist/field-20260817.dist
+      loss: 2%
+    downlink: { delay: 7ms, jitter: 5ms }
+
+  # B4 -- a serialisation constraint tight enough that a burst cannot fit in
+  # its own send interval, which is the shape an EN-DC uplink on a TDD carrier
+  # would present from above: a small probe survives what a 38-fragment burst
+  # does not.
+  tilt-iid-tight:
+    uplink:
+      rate: 1.5mbit
+      delay: 25ms
+      jitter: 18ms
+      distribution: field-20260817
+      distribution_file: dist/field-20260817.dist
+      loss: 1%
+    downlink: { delay: 7ms, jitter: 5ms }
+
+  # B1-prime -- the two-state process with its chain rescaled per cell.
+  #
+  # netem advances a Gilbert-Elliott chain once per *packet*, so the fitted p
+  # and r describe a process in packets and not in time. At the drive's own
+  # 380 fragments/s they mean a bad run of about 105 ms; on a size ladder at a
+  # fixed 10 Hz the packet rate is N x 10, so the same p and r stretch the bad
+  # run by 380/(N x 10) and every cell meets a different link. Forcing the
+  # packet rate constant instead was tried and measured the wrong thing: the
+  # pipeline serves messages, not packets, and at 60 messages/s the depth-1 OTA
+  # queue overwrites its own backlog -- both loss processes then reported
+  # 10.7 % to two digits.
+  #
+  # So the chain is rescaled instead: p and r are multiplied by 380/(N x 10) in
+  # each cell, which leaves the stationary bad fraction at 3.92 % and the mean
+  # loss at 1 % while making the bad run 105 ms of wall clock everywhere. The
+  # comparison against `tilt-iid` is then a comparison of one thing.
+
+  bp-frag-one:
+    uplink:
+      delay: 25ms
+      jitter: 18ms
+      distribution: field-20260817
+      distribution_file: dist/field-20260817.dist
+      loss_gemodel: { p: 3.876%, r: 95%, loss_bad: 13.5%, loss_good: 0.49% }
+    downlink: { delay: 7ms, jitter: 5ms }
+
+  bp-frag-two:
+    uplink:
+      delay: 25ms
+      jitter: 18ms
+      distribution: field-20260817
+      distribution_file: dist/field-20260817.dist
+      loss_gemodel: { p: 1.938%, r: 47.5%, loss_bad: 13.5%, loss_good: 0.49% }
+    downlink: { delay: 7ms, jitter: 5ms }
+
+  bp-frag-four:
+    uplink:
+      delay: 25ms
+      jitter: 18ms
+      distribution: field-20260817
+      distribution_file: dist/field-20260817.dist
+      loss_gemodel: { p: 0.969%, r: 23.75%, loss_bad: 13.5%, loss_good: 0.49% }
+    downlink: { delay: 7ms, jitter: 5ms }
+
+  bp-frag-six:
+    uplink:
+      delay: 25ms
+      jitter: 18ms
+      distribution: field-20260817
+      distribution_file: dist/field-20260817.dist
+      loss_gemodel: { p: 0.646%, r: 15.83%, loss_bad: 13.5%, loss_good: 0.49% }
+    downlink: { delay: 7ms, jitter: 5ms }
+
+  bp-frag-twelve:
+    uplink:
+      delay: 25ms
+      jitter: 18ms
+      distribution: field-20260817
+      distribution_file: dist/field-20260817.dist
+      loss_gemodel: { p: 0.323%, r: 7.917%, loss_bad: 13.5%, loss_good: 0.49% }
+    downlink: { delay: 7ms, jitter: 5ms }
+
+  bp-frag-thirtyeight:
+    uplink:
+      delay: 25ms
+      jitter: 18ms
+      distribution: field-20260817
+      distribution_file: dist/field-20260817.dist
+      loss_gemodel: { p: 0.102%, r: 2.5%, loss_bad: 13.5%, loss_good: 0.49% }
+    downlink: { delay: 7ms, jitter: 5ms }

{rosotacom_dev-2.5.dev75.dist-info → rosotacom_dev-2.5.dev77.dist-info}/METADATA

@@ -1,6 +1,6 @@
 Metadata-Version: 2.4
 Name: rosotacom-dev
-Version: 2.5.dev75
+Version: 2.5.dev77
 Summary: Host CLI for ROS OTA communication sessions.
 Author: develNor
 License-Expression: BSD-3-Clause

{rosotacom_dev-2.5.dev75.dist-info → rosotacom_dev-2.5.dev77.dist-info}/RECORD

@@ -31,7 +31,7 @@ rosotacom/resources/examples/.gitignore,sha256=9FFIV42CR379XRSDOC9UdXsfJP8cGACLj
 rosotacom/resources/examples/README.md,sha256=sKq1r0NubxweJjAvoPDFDQcEk4uBbskHJW6AAfnZy-E,6629
 rosotacom/resources/examples/__init__.py,sha256=IKLiqdO5jeBX3rMkWyb_Uc3SrQZp5vkJtqoTD_NZ90E,52
 rosotacom/resources/examples/deployment.example.yaml,sha256=E3HMJhv-Ft5mA6PC8d7yVZz1uwG3OQhCD_MBnhxtvAg,450
-rosotacom/resources/examples/profiles.yaml,sha256=NDcDgdvIdI6Hn71mQCCWaqc2LhTpmAdepS7kuu_l1hc,7362
+rosotacom/resources/examples/profiles.yaml,sha256=LdlaJghhXF-KICJ6ujuWNDE26bzfS-2WgDDP8YlvGPI,13136
 rosotacom/resources/examples/ros2docker.json,sha256=Gd_g1P_OA-_7-nM8-KmTTX2cRUyoNCpaPj9MCgxld3M,2499
 rosotacom/resources/examples/ros2docker.lyrical.json,sha256=fE5Hlx6O6q7gRyHdFXGdClFyFxN-uxPGICkYbJ42xG4,1775
 rosotacom/resources/examples/rosotacom.yaml,sha256=lpFnRNJv9kjS3Pd6dJAG1PXF-UP-YbSOK8dNcUe68hY,351
@@ -205,9 +205,9 @@ rosotacom/resources/ws/session/creation/generate_session_files.py,sha256=3Sx4xTS
 rosotacom/resources/ws/session/creation/run_session.py,sha256=G2hJhrmLp11gm3JZ6_C-zZcqu_reXlE_wmobB7BiCfU,16849
 rosotacom/resources/ws/session/creation/run_session_in_external_terminal.py,sha256=Ub_5f-ttUUc-rAPrZmg_Op34s8Z4C91hTyEn8fgyt-E,2633
 rosotacom/resources/ws/session/creation/strip_ansi.py,sha256=vNjpemcq4xHr0VG4x0bZqvgwEBEfOgN-b4PzbrM5nfM,851
-rosotacom_dev-2.5.dev75.dist-info/licenses/LICENSE.txt,sha256=FDB3-fao3lqZ94wsJHKAH7U88kAnfvZhZC8Hm5rN__g,1459
-rosotacom_dev-2.5.dev75.dist-info/METADATA,sha256=cLNp2U1eq-i_1EDopfNHgojPjInLExP5-4I7957dmS4,58884
-rosotacom_dev-2.5.dev75.dist-info/WHEEL,sha256=YVMoNqKzERt-wjUZwJ33xBGAwnFl-4cqbYkTtWa4itE,91
-rosotacom_dev-2.5.dev75.dist-info/entry_points.txt,sha256=im11ZWqBbgjQUBz2Ik2RNfMu54wlMwgiVpsBKeI7dCI,49
-rosotacom_dev-2.5.dev75.dist-info/top_level.txt,sha256=BZrtQcIVDWn_pQZR3Mlssqy5SaRXHjOa6B-1D9Fy4Ao,10
-rosotacom_dev-2.5.dev75.dist-info/RECORD,,
+rosotacom_dev-2.5.dev77.dist-info/licenses/LICENSE.txt,sha256=FDB3-fao3lqZ94wsJHKAH7U88kAnfvZhZC8Hm5rN__g,1459
+rosotacom_dev-2.5.dev77.dist-info/METADATA,sha256=z4J9DpBaWOe8CkIr_PzKl_NoF5sTmfMFsEu9awq4XwE,58884
+rosotacom_dev-2.5.dev77.dist-info/WHEEL,sha256=YVMoNqKzERt-wjUZwJ33xBGAwnFl-4cqbYkTtWa4itE,91
+rosotacom_dev-2.5.dev77.dist-info/entry_points.txt,sha256=im11ZWqBbgjQUBz2Ik2RNfMu54wlMwgiVpsBKeI7dCI,49
+rosotacom_dev-2.5.dev77.dist-info/top_level.txt,sha256=BZrtQcIVDWn_pQZR3Mlssqy5SaRXHjOa6B-1D9Fy4Ao,10
+rosotacom_dev-2.5.dev77.dist-info/RECORD,,