plm-physics 0.1.0__py3-none-any.whl

plm_physics/__init__.py

@@ -0,0 +1 @@
+"""Physics and mechanical pack: level rules, tiers, claims and unit words; the rest is plm.numeric."""

plm_physics/claims.py

@@ -0,0 +1,48 @@
+"""Which tasks the physics pack claims, and how strongly.
+
+A physics calculation names something from mechanics, fluids, heat or materials
+and gives a quantity (a number with a unit) or asks for a unit. Conceptual
+questions ("Why does ice float?") have neither and go to the general pack.
+
+Physics shares its quantities with the specialist packs: speed, mass, pressure
+and density are in aerospace questions too, where aerospace counts a phrase like
+"dynamic pressure" once while physics would count "density" and "pressure"
+twice. So generic quantity words let physics claim a text but add nothing to
+its score: only words that are physics's own (pendulum, friction, buoyant, ...)
+count as evidence. A text with generic words only scores GENERIC_ONLY, below
+any specialist's claim, so physics takes it only when no specialist does. Its
+priority is the lowest of the numeric packs, so equal evidence goes to the
+specialist too. Words that mean electricity (power, energy alone, wire,
+frequency) are in neither list.
+"""
+
+import re
+
+from plm.numeric.checks import requested_unit
+from plm.pack import evidence
+
+GENERIC_ONLY = 0.5
+GENERIC = re.compile(
+    r"\b(?:mass|weight|speed|velocity|acceleration|accelerates?|density|pressure|temperature|flow rate"
+    r"|height|distance)\b", re.IGNORECASE)
+PHYSICS_TERM = re.compile(
+    r"\b(?:force|net force|decelerat\w*|momentum|kinetic energy|potential energy|elastic energy|work|friction"
+    r"|stiffness|spring(?: constant)?|pendulum|oscillat\w*|wavelength|waves?|torque|wrench|lever|flywheel"
+    r"|rotat\w*|angular|radians?|wheel|moment of inertia|rolls?|rolling|gears?|shaft|pulley|piston"
+    r"|gauge pressure|buoyan\w*|submerged|floats?|fluid|pipe|water|tank|ice|steam|heat|specific heat"
+    r"|latent heat|boil\w*|melt\w*|thermal|conductivity|expansion|ideal gas|moles?|stress|strain"
+    r"|young's modulus|tensile|cable|beam|collision|projectile|thrown|kicked|dropped|falls?|cliff|ramp"
+    r"|incline\w*|slope|crate|ball|machine|motor|elevator|crane|pump|lifts?|kettle|gravity|centripetal|tension"
+    r"|brakes?|stopping distance|air resistance)\b",
+    re.IGNORECASE)
+QUANTITY = re.compile(r"\d\s*(?:m/s²|m/s\^?2|m/s|km/h|kg/m³|kg|g|N·m|N/m|N|kN|J|kJ|MJ|Pa|kPa|MPa|GPa|K|°C|m|cm|mm"
+                      r"|km|m²|m³|s|min|h|L|rpm|mol|degrees?|%)(?![\w/])")
+
+
+def claims(text):
+    """Distinct physics terms (generic quantities don't count), when there is a quantity or a unit is asked for."""
+    if not (PHYSICS_TERM.search(text) or GENERIC.search(text)):
+        return 0
+    if not (QUANTITY.search(text) or requested_unit(text) is not None):
+        return 0
+    return evidence(PHYSICS_TERM, text) or GENERIC_ONLY

plm_physics/controller.py

@@ -0,0 +1,44 @@
+"""Physics pack: the 4B with the calculator for calm and alert problems, escalating to the 8B.
+
+On the 50-problem eval set, PHYSICS_RULE (evals/simulate_routing.py, fixed before that
+sweep) shipped always 8B answering directly: 49/50, while the calculator lost points
+there by printing base-unit values under prefixed units ("5e+04 MPa" for 50 MPa).
+
+SciBench's physics problems (evals/bench_physics.py: Halliday and classical mechanics,
+144, written by others; PHYS_RULE, accuracy first, fixed before the runs) reversed that:
+
+    4B+calc | 8B+calc, escalating (now)     69/144 (48%) at 48% of always-8B-direct compute
+    always 8B + calculator                  68/144 at 45%
+    always 4B + calculator                  63/144 at 24%
+    always 8B, direct (shipped before)      52/144 (36%) at 100%
+
+The routed policy beats always-8B-direct by +4 to +30 problems (paired 95%), at half the
+compute: it is the electrical pack's shape. The check caught 19 of 76-94 wrong answers
+per strategy. Budgets cover the longest calculator answers seen; 5-6 of 144 hit 1024.
+
+Model names can be overridden with PLM_SMALL_MODEL and PLM_LARGE_MODEL.
+"""
+
+import os
+
+from plm.numeric import controller as numeric
+
+from plm_physics.levels import classify
+
+MODELS = {
+    "small": os.environ.get("PLM_SMALL_MODEL", "hf.co/bartowski/Qwen_Qwen3-4B-GGUF:Q4_K_M"),
+    "large": os.environ.get("PLM_LARGE_MODEL", "qwen3:8b"),
+}
+
+# Per level: token budget and the escalation chain of (model, strategy) steps.
+LEVELS = {
+    "calm": {"num_predict": 1024, "chain": [("small", "tool"), ("large", "tool")]},
+    "alert": {"num_predict": 1024, "chain": [("small", "tool"), ("large", "tool")]},
+    "intensive": {"num_predict": 1536, "chain": [("large", "tool"), ("large", "bare")]},
+}
+
+
+def solve(task, level=None, timeout=300):
+    """Answer one physics task. Returns the answer plus a record of every model call."""
+    return numeric.solve(task, pack="physics", classify=classify, levels=LEVELS, models=MODELS,
+                         level=level, timeout=timeout)

plm_physics/levels.py

@@ -0,0 +1,43 @@
+"""Physics pack: chain cues for the shared numeric level rules (plm/numeric/levels.py).
+
+Each family marks a problem where an intermediate result has to be computed and
+reused. Written from mechanics, fluids and heat practice after the eval set and
+the holdout (evals/physics/holdout_levels.jsonl) were written; the holdout is
+never used to tune them. Evaluate them with:
+    .venv/bin/python evals/eval_levels.py --pack physics
+"""
+
+from plm.numeric import levels as numeric_levels
+
+CHAIN_CUES = {
+    # flight time first, then range or landing point
+    "projectile": r"\b(?:thrown|kicked|rolls off|fired)\b.*\b(?:land|lands|returns?|how high|how far)\b"
+                  r"|horizontally from|\bin the air\b",
+    # an energy balance or an acceleration first, then the speed, height or distance
+    "energy-chain": r"from rest down|at the bottom|just before it hits|how high does .* swing|before stopping"
+                    r"|highest speed|brakes? (?:hard|from)",
+    # momentum conserved first, then the energy or the motion after
+    "collision": r"\bhits? a (?:stationary|parked)|move off together|stick together|embeds? itself|energy is lost",
+    # moment of inertia and angular speed first, then the energy
+    "rotation-energy": r"flywheel|rolls? without slipping|moment of inertia|\bsolid (?:disc|sphere|cylinder)\b"
+                       r"|\bhollow (?:cylinder|sphere)\b",
+    # continuity or Torricelli first, then pressure or flow
+    "fluid-chain": r"\bnarrows\b|bernoulli|continuity|drains? .* through a hole|outflow rate"
+                   r"|volume of the .* (?:above|below) the water",
+    # a heat balance or a phase change, then a temperature or a time
+    "heat-chain": r"\bmixed\b|final temperature|\bice\b.*\binto water\b|how long does it take|in one hour"
+                  r"|internal energy|heated at constant|thermal stress",
+    # a friction or banking limit first, then the speed it allows
+    "curve-limit": r"\bcurve\b.*\b(?:highest|maximum|top) speed|(?:highest|maximum|top) speed .*\bcurve\b|\bbanked\b",
+    # an area or a force from given sizes, then stress or extension
+    "materials-chain": r"diameter of .* (?:holds|carries|load)|clamped between",
+}
+
+
+def features(text):
+    return numeric_levels.features(text, CHAIN_CUES)
+
+
+def classify(text):
+    """Return (level, reason)."""
+    return numeric_levels.classify(text, CHAIN_CUES)

plm_physics/manifest.py

@@ -0,0 +1,26 @@
+"""The physics pack's manifest: what the router needs to know about it."""
+
+from plm.pack import Pack
+
+from plm_physics import controller
+from plm_physics.claims import claims
+
+# Mechanics, fluids, heat and materials. Words other packs also declare (newtons,
+# pascals, meters per second, ...) are repeated here so this pack works without them;
+# a word two packs declare must mean the same unit.
+UNIT_WORDS = {
+    "newtons": "N", "kilonewtons": "kN", "newton-meters": "N*m", "newtons per meter": "N/m",
+    "newton-seconds": "N*s", "kilogram meters per second": "kg*m/s",
+    "meters per second": "m/s", "kilometers per hour": "km/h", "meters per second squared": "m/s^2",
+    "radians per second": "rad/s", "revolutions per minute": "rpm", "hertz": "Hz",
+    "centimeters": "cm", "millimeters": "mm", "cubic meters": "m^3", "liters": "L",
+    "liters per second": "L/s", "cubic meters per second": "m^3/s",
+    "grams": "g", "kilograms per cubic meter": "kg/m^3",
+    "kilojoules": "kJ", "megajoules": "MJ",
+    "pascals": "Pa", "kilopascals": "kPa", "megapascals": "MPa", "gigapascals": "GPa",
+    "kelvin": "K", "degrees celsius": "degC",
+}
+
+PACK = Pack(name="physics", version="0.1.0", claims=claims, priority=40, solve=controller.solve,
+            levels=controller.LEVELS, models=controller.MODELS, unit_words=UNIT_WORDS,
+            eval_set="evals/physics/problems.jsonl")

plm_physics-0.1.0.dist-info/METADATA

@@ -0,0 +1,20 @@
+Metadata-Version: 2.5
+Name: plm-physics
+Version: 0.1.0
+Summary: plm pack: Physics and mechanical calculations, checked by units and sanity rules
+Project-URL: Homepage, https://github.com/ro-rbl/plm-orchestrator
+Project-URL: Source, https://github.com/ro-rbl/plm-orchestrator
+Project-URL: Issues, https://github.com/ro-rbl/plm-orchestrator/issues
+Author: ro-rbl
+License-Expression: MIT
+License-File: LICENSE
+Requires-Python: >=3.13
+Requires-Dist: plm-core<0.2,>=0.1
+Description-Content-Type: text/markdown
+
+# plm-physics
+
+Plm pack: Physics and mechanical calculations, checked by units and sanity rules.
+
+A domain pack for [plm-core](https://github.com/ro-rbl/plm-orchestrator): install it with `plm packs install physics`, which also pulls the
+models it needs into Ollama. Documentation, benchmark results and caveats: https://github.com/ro-rbl/plm-orchestrator

plm_physics-0.1.0.dist-info/RECORD

@@ -0,0 +1,10 @@
+plm_physics/__init__.py,sha256=Us084AoBlEazUzqCHSOlHkPaI8I6NBVyryqJrTSY8N0,103
+plm_physics/claims.py,sha256=hZiFNOjqW-7ztfxVv2minFxSrbAmh2-Y6VXFyF_6kjQ,2688
+plm_physics/controller.py,sha256=bdJczQTft_rRHIeHQFK9HuKjvw-b1TpblzUk1DUc5mc,2042
+plm_physics/levels.py,sha256=OIi5OFnS4VkemPrh-4CiN2boRUB9yKhn6nHMF6NWgY4,2380
+plm_physics/manifest.py,sha256=MHLWMVkHsd3NwJhLiF7YFitJaxq6yByMAdrYaBVR4ps,1384
+plm_physics-0.1.0.dist-info/METADATA,sha256=nlAC8K3ujqfoYNs_gbGIwqYyO6KWV8xEg_gypj8z3T4,862
+plm_physics-0.1.0.dist-info/WHEEL,sha256=2iZrJkDIkeDh0k9SikKMqFuRP-ua6mb4Ir1AsER4BEw,87
+plm_physics-0.1.0.dist-info/entry_points.txt,sha256=oYLov-o-POB-43Ix8Wz4jeOD7YV_H2qfOqO82WN3lfo,48
+plm_physics-0.1.0.dist-info/licenses/LICENSE,sha256=KcrxZgcJO8eG0MOaibWc_3Pxvh6U_KruTKPaGwV6-vA,1063
+plm_physics-0.1.0.dist-info/RECORD,,

plm_physics-0.1.0.dist-info/WHEEL

@@ -0,0 +1,4 @@
+Wheel-Version: 1.0
+Generator: hatchling 1.33.0
+Root-Is-Purelib: true
+Tag: py3-none-any

plm_physics-0.1.0.dist-info/entry_points.txt

@@ -0,0 +1,2 @@
+[plm.packs]
+physics = plm_physics.manifest:PACK

plm_physics-0.1.0.dist-info/licenses/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 ro-rbl
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.