atspm-detector 1.0.0__tar.gz

atspm_detector-1.0.0/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2024 Shawn Strasser
+
+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.

atspm_detector-1.0.0/PKG-INFO

@@ -0,0 +1,186 @@
+Metadata-Version: 2.4
+Name: atspm-detector
+Version: 1.0.0
+Summary: Phase, function, lanes, setback, night speed and health of traffic-signal detectors from the controller's hi-res event log (CPU, onnxruntime).
+Author: Shawn Strasser
+License-Expression: MIT
+Project-URL: Homepage, https://github.com/ShawnStrasser/atspm-detector
+Project-URL: Documentation, https://github.com/ShawnStrasser/atspm-detector#readme
+Project-URL: Repository, https://github.com/ShawnStrasser/atspm-detector
+Project-URL: Issues, https://github.com/ShawnStrasser/atspm-detector/issues
+Project-URL: Changelog, https://github.com/ShawnStrasser/atspm-detector/blob/main/CHANGELOG.md
+Project-URL: Embedding Guide, https://github.com/ShawnStrasser/atspm-detector/blob/main/docs/embedding.md
+Keywords: traffic signal,ATSPM,detector,high-resolution data,NTCIP
+Classifier: Development Status :: 5 - Production/Stable
+Classifier: Intended Audience :: Science/Research
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3 :: Only
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Topic :: Scientific/Engineering
+Requires-Python: >=3.10
+Description-Content-Type: text/markdown
+License-File: LICENSE
+Requires-Dist: numpy>=1.24
+Requires-Dist: pandas>=2.0
+Requires-Dist: duckdb>=1.0
+Requires-Dist: onnxruntime>=1.21
+Provides-Extra: charts
+Requires-Dist: matplotlib>=3.7; extra == "charts"
+Provides-Extra: dev
+Requires-Dist: pytest>=7.0.0; extra == "dev"
+Requires-Dist: build>=1.0; extra == "dev"
+Dynamic: license-file
+
+# atspm-detector
+
+Give it a signal controller's hi-res event log; for every vehicle detector it returns the **phase**, **function**,
+**lanes**, **setback** from the stop bar and **health**. No cabinet print needed: the answers come from how each
+detector behaves. Use it to **build** a signal's ATSPM detector configuration, or to **check** the one you have.
+
+* **Tested on 115 signals it never trained on:** phase right for **98.0 %** of detectors, function **91.7 %**
+  (30 minutes or more of log).
+* **More accurate than hand-labled configuration:** phase wrong on 1.3 % of detectors, against 2.6 % by hand.
+* **Fast and light:** one second per signal on CPU.
+
+**Contents:** [Detector functions](#detector-functions) · [Install](#install) · [Usage](#usage) · [Input](#input) ·
+[How much data](#how-much-data) · [How it works](#how-it-works) · [Accuracy](#accuracy) ·
+[Detector health](#detector-health) · [License](#license)
+
+## Detector functions
+
+| Function | ATSPM | What it is |
+|---|---|---|
+| Presence | yes | Stop-bar presence zone. The presence zones used in training were about 20 ft long at the stop bar. |
+| Advance | yes | Advance count zone, upstream. Single lane or spanning several lanes. |
+| Count | yes | Stop-bar count zone. Usually set to pulse, one per lane. |
+| Yellow_Red | yes | At the stop bar; may span several lanes. Configure it in the field with a 5 mph speed threshold. |
+| Mid | no | Zone between the advance and the stop bar. A class of its own because it helps the model. |
+| Bike | no | Bicycle detection zone. |
+| Other | no | Everything else that drives operations but is not an ATSPM zone. |
+
+## Install
+
+```bash
+pip install atspm-detector   # Python 3.10 or newer
+```
+
+## Usage
+
+```python
+import pandas as pd
+from atspm_detector import predict
+
+events = pd.read_csv("events.csv")   # or pd.read_parquet (needs pyarrow)
+events.head()
+```
+
+```text
+                               DeviceId                Timestamp  EventId  Parameter
+0  d2d0de72-c8aa-45ca-ae1a-8fc626c5afc9  2024-12-03 12:00:00.000      150          7
+1  d2d0de72-c8aa-45ca-ae1a-8fc626c5afc9  2024-12-03 12:00:00.000      320          0
+2  d2d0de72-c8aa-45ca-ae1a-8fc626c5afc9  2024-12-03 12:00:00.000      318          3
+3  d2d0de72-c8aa-45ca-ae1a-8fc626c5afc9  2024-12-03 12:00:00.000      316        120
+4  d2d0de72-c8aa-45ca-ae1a-8fc626c5afc9  2024-12-03 12:00:00.600       13          6
+```
+
+```python
+results = predict(events)
+results[["Detector", "phase_pred", "phase_prob", "function_pred", "function_prob",
+         "lanes", "distance_ft", "health_status"]].round(2).head()
+```
+
+```text
+   Detector  phase_pred  phase_prob function_pred  function_prob lanes  distance_ft    health_status
+0         2           2        0.99       Advance           0.90     2        164.0               ok
+1         3           2        1.00       Advance           0.64   1,2        153.0               ok
+2         4           2        1.00      Presence           0.40   1,2          0.0               ok
+3         5           2        1.00       Advance           0.53     1        152.0               ok
+4         6        <NA>         NaN           NaN            NaN   NaN          NaN  not_enough_data
+```
+
+From the bundled 30-minute sample; detector 6 had one actuation, too few to judge. One row per detector; main columns:
+
+| Column | What |
+|---|---|
+| `phase_pred`, `phase_prob` | phase and its probability (`phase_2nd`, `phase_2nd_prob`: runner-up) |
+| `function_pred`, `function_prob` | function (table above) and its probability |
+| `lanes`, `phase_n_lanes` | lane(s) the detector covers, number of lanes on its phase |
+| `distance_ft`, `night_speed_mph` | setback from the stop bar (ft); typical night speed on the phase |
+| `health_status`, `health_reason` | ok / watch / suspect / bad / not_enough_data, and why |
+| `status`, `review_flag` | "ok", or why an answer is missing or weak; `True` = worth a look |
+
+Under 5 actuations: no answer (guess in `phase_guess`, `function_guess`). `return_phases=True` also returns a phase table.
+
+**One signal or many.** `DeviceId` separates signals. Each is processed on its own, so its answers are the same alone
+or in a batch. `predict` also takes a parquet or CSV path or glob, and `start` / `end` times. To build it into an
+application, see [docs/embedding.md](https://github.com/ShawnStrasser/atspm-detector/blob/main/docs/embedding.md).
+
+## Input
+
+One row per event, standard Indiana hi-res format: `DeviceId` (any signal id), `Timestamp` (controller local time),
+`EventId`, `Parameter`. Give it the whole log; unused event codes are dropped.
+
+## How much data
+
+| Sample length | Phase | Function | Notes |
+|---|---|---|---|
+| 5 minutes | 94.1 % | 86.4 % | works, but weaker; no lanes |
+| 30 minutes | 97.7 % | 91.7 % | **recommended minimum**; lanes from here on |
+| 1 hour | 98.0 % | 91.8 % | |
+| 3 hours | 98.2 % | 92.9 % | best for phase and function (3 to 24 hours) |
+| 24 hours | 98.4 % | 92.5 % | full health check |
+
+On the 115 test signals. Health runs on any length; time-of-day checks need a full day, night speed midnight to 5 am.
+
+## How it works
+
+* **In:** detector on / off, signal colors and phase calls. The model never sees a phase or channel number; it scores
+  each detector against every phase that turned green, from behavior alone.
+* **Models:** gradient-boosted trees and a small neural network score each detector against each phase and function.
+  A final step looks at the whole intersection to keep at most one detector of each ATSPM function per lane. Small
+  models give lanes and setback. Health is checked last, by rules, and never changes an answer. All on the CPU with
+  onnxruntime (8.5 MB of weights).
+
+## Accuracy
+
+Measured once, on the final model, on **115 locked signals** never used for training or tuning (30 minutes to 24 hours
+of log). Phase truth: controller timing (21,341 detector samples, 113 signals). Function truth: configuration export
+checked against cabinet prints (87 signals). Detectors with no actuations or no green on their phase are not scored.
+All labels come from one agency; other agencies' conventions may differ.
+
+* **Phase: 98.0 %** (95 % interval 97.0-98.9 %). Most errors are between through phases nearly always green together
+  (2 and 6, 4 and 8).
+* **Function: 91.7 %** (88.7-94.0 %), ATSPM errors only, excluding detectors whose label the model picked (print vs
+  hand label). By true class: Advance 93.9 %, Presence 95.2 %, Count 96.6 %, Yellow_Red 89.5 %, Other 81.8 %.
+* **Lanes:** lane count per phase exact for 82.5 % of phases, within one for 97.5 % (298 phases).
+* **Setback:** median error 36 ft (59.9 % within 50 ft; Advance, 25 signals); 23.9 ft in cross-validation.
+* **Night speed:** an approach speed, not the posted speed; two nights agree to a median of 1.5 mph.
+* **Speed:** 0.8 s per signal for 30 minutes of log, 1.7 s for 24 hours; 250-400 MB of memory.
+
+**Against hand labels** (signals not trained on): phase wrong on 1.3 % of 4,636 detectors (hand labels 2.6 %); function
+off the cabinet print on about 6 % of 5,254 (hand labels 9.7 %). Where model and hand label differed, the timing backed
+the model 104 times to 24, the print 398 to 177. Prints can be out of date.
+
+**Health:** flagged 19 of 20 detectors a traffic engineer judged faulty, and none of the 12 judged fine.
+Flagged (suspect or bad) per 100 detectors: 0.4 on 30 minutes, 1.2 on 3 hours, 3.9 on 24 hours. Not field-verified.
+
+## Detector health
+
+Each detector gets a status, a plain-words reason, the periods affected and the categories, judged against what is
+normal for its type (function x lanes x sample length). Checks: stuck on, goes silent, count drops, misses vehicles at
+night, erratic counts, too-fast actuations, chattering, too many for the traffic, erratic time ON, busy at night,
+unusual daily pattern, Count zone held ON. **Bad** = one strong finding, two checks agreeing, or 4+ hours of the day.
+
+![Stuck on: a Presence detector held ON three times in one day](https://raw.githubusercontent.com/ShawnStrasser/atspm-detector/main/docs/images/health_stuck_on.png)
+
+![Busy at night: a detector ON 62 % of the time from 1 to 5 am](https://raw.githubusercontent.com/ShawnStrasser/atspm-detector/main/docs/images/health_busy_at_night.png)
+
+![Unusual daily pattern: an advance loop goes quiet at midday while its partner keeps counting](https://raw.githubusercontent.com/ShawnStrasser/atspm-detector/main/docs/images/health_unusual_day.png)
+
+## License
+
+MIT

atspm_detector-1.0.0/README.md

@@ -0,0 +1,149 @@
+# atspm-detector
+
+Give it a signal controller's hi-res event log; for every vehicle detector it returns the **phase**, **function**,
+**lanes**, **setback** from the stop bar and **health**. No cabinet print needed: the answers come from how each
+detector behaves. Use it to **build** a signal's ATSPM detector configuration, or to **check** the one you have.
+
+* **Tested on 115 signals it never trained on:** phase right for **98.0 %** of detectors, function **91.7 %**
+  (30 minutes or more of log).
+* **More accurate than hand-labled configuration:** phase wrong on 1.3 % of detectors, against 2.6 % by hand.
+* **Fast and light:** one second per signal on CPU.
+
+**Contents:** [Detector functions](#detector-functions) · [Install](#install) · [Usage](#usage) · [Input](#input) ·
+[How much data](#how-much-data) · [How it works](#how-it-works) · [Accuracy](#accuracy) ·
+[Detector health](#detector-health) · [License](#license)
+
+## Detector functions
+
+| Function | ATSPM | What it is |
+|---|---|---|
+| Presence | yes | Stop-bar presence zone. The presence zones used in training were about 20 ft long at the stop bar. |
+| Advance | yes | Advance count zone, upstream. Single lane or spanning several lanes. |
+| Count | yes | Stop-bar count zone. Usually set to pulse, one per lane. |
+| Yellow_Red | yes | At the stop bar; may span several lanes. Configure it in the field with a 5 mph speed threshold. |
+| Mid | no | Zone between the advance and the stop bar. A class of its own because it helps the model. |
+| Bike | no | Bicycle detection zone. |
+| Other | no | Everything else that drives operations but is not an ATSPM zone. |
+
+## Install
+
+```bash
+pip install atspm-detector   # Python 3.10 or newer
+```
+
+## Usage
+
+```python
+import pandas as pd
+from atspm_detector import predict
+
+events = pd.read_csv("events.csv")   # or pd.read_parquet (needs pyarrow)
+events.head()
+```
+
+```text
+                               DeviceId                Timestamp  EventId  Parameter
+0  d2d0de72-c8aa-45ca-ae1a-8fc626c5afc9  2024-12-03 12:00:00.000      150          7
+1  d2d0de72-c8aa-45ca-ae1a-8fc626c5afc9  2024-12-03 12:00:00.000      320          0
+2  d2d0de72-c8aa-45ca-ae1a-8fc626c5afc9  2024-12-03 12:00:00.000      318          3
+3  d2d0de72-c8aa-45ca-ae1a-8fc626c5afc9  2024-12-03 12:00:00.000      316        120
+4  d2d0de72-c8aa-45ca-ae1a-8fc626c5afc9  2024-12-03 12:00:00.600       13          6
+```
+
+```python
+results = predict(events)
+results[["Detector", "phase_pred", "phase_prob", "function_pred", "function_prob",
+         "lanes", "distance_ft", "health_status"]].round(2).head()
+```
+
+```text
+   Detector  phase_pred  phase_prob function_pred  function_prob lanes  distance_ft    health_status
+0         2           2        0.99       Advance           0.90     2        164.0               ok
+1         3           2        1.00       Advance           0.64   1,2        153.0               ok
+2         4           2        1.00      Presence           0.40   1,2          0.0               ok
+3         5           2        1.00       Advance           0.53     1        152.0               ok
+4         6        <NA>         NaN           NaN            NaN   NaN          NaN  not_enough_data
+```
+
+From the bundled 30-minute sample; detector 6 had one actuation, too few to judge. One row per detector; main columns:
+
+| Column | What |
+|---|---|
+| `phase_pred`, `phase_prob` | phase and its probability (`phase_2nd`, `phase_2nd_prob`: runner-up) |
+| `function_pred`, `function_prob` | function (table above) and its probability |
+| `lanes`, `phase_n_lanes` | lane(s) the detector covers, number of lanes on its phase |
+| `distance_ft`, `night_speed_mph` | setback from the stop bar (ft); typical night speed on the phase |
+| `health_status`, `health_reason` | ok / watch / suspect / bad / not_enough_data, and why |
+| `status`, `review_flag` | "ok", or why an answer is missing or weak; `True` = worth a look |
+
+Under 5 actuations: no answer (guess in `phase_guess`, `function_guess`). `return_phases=True` also returns a phase table.
+
+**One signal or many.** `DeviceId` separates signals. Each is processed on its own, so its answers are the same alone
+or in a batch. `predict` also takes a parquet or CSV path or glob, and `start` / `end` times. To build it into an
+application, see [docs/embedding.md](https://github.com/ShawnStrasser/atspm-detector/blob/main/docs/embedding.md).
+
+## Input
+
+One row per event, standard Indiana hi-res format: `DeviceId` (any signal id), `Timestamp` (controller local time),
+`EventId`, `Parameter`. Give it the whole log; unused event codes are dropped.
+
+## How much data
+
+| Sample length | Phase | Function | Notes |
+|---|---|---|---|
+| 5 minutes | 94.1 % | 86.4 % | works, but weaker; no lanes |
+| 30 minutes | 97.7 % | 91.7 % | **recommended minimum**; lanes from here on |
+| 1 hour | 98.0 % | 91.8 % | |
+| 3 hours | 98.2 % | 92.9 % | best for phase and function (3 to 24 hours) |
+| 24 hours | 98.4 % | 92.5 % | full health check |
+
+On the 115 test signals. Health runs on any length; time-of-day checks need a full day, night speed midnight to 5 am.
+
+## How it works
+
+* **In:** detector on / off, signal colors and phase calls. The model never sees a phase or channel number; it scores
+  each detector against every phase that turned green, from behavior alone.
+* **Models:** gradient-boosted trees and a small neural network score each detector against each phase and function.
+  A final step looks at the whole intersection to keep at most one detector of each ATSPM function per lane. Small
+  models give lanes and setback. Health is checked last, by rules, and never changes an answer. All on the CPU with
+  onnxruntime (8.5 MB of weights).
+
+## Accuracy
+
+Measured once, on the final model, on **115 locked signals** never used for training or tuning (30 minutes to 24 hours
+of log). Phase truth: controller timing (21,341 detector samples, 113 signals). Function truth: configuration export
+checked against cabinet prints (87 signals). Detectors with no actuations or no green on their phase are not scored.
+All labels come from one agency; other agencies' conventions may differ.
+
+* **Phase: 98.0 %** (95 % interval 97.0-98.9 %). Most errors are between through phases nearly always green together
+  (2 and 6, 4 and 8).
+* **Function: 91.7 %** (88.7-94.0 %), ATSPM errors only, excluding detectors whose label the model picked (print vs
+  hand label). By true class: Advance 93.9 %, Presence 95.2 %, Count 96.6 %, Yellow_Red 89.5 %, Other 81.8 %.
+* **Lanes:** lane count per phase exact for 82.5 % of phases, within one for 97.5 % (298 phases).
+* **Setback:** median error 36 ft (59.9 % within 50 ft; Advance, 25 signals); 23.9 ft in cross-validation.
+* **Night speed:** an approach speed, not the posted speed; two nights agree to a median of 1.5 mph.
+* **Speed:** 0.8 s per signal for 30 minutes of log, 1.7 s for 24 hours; 250-400 MB of memory.
+
+**Against hand labels** (signals not trained on): phase wrong on 1.3 % of 4,636 detectors (hand labels 2.6 %); function
+off the cabinet print on about 6 % of 5,254 (hand labels 9.7 %). Where model and hand label differed, the timing backed
+the model 104 times to 24, the print 398 to 177. Prints can be out of date.
+
+**Health:** flagged 19 of 20 detectors a traffic engineer judged faulty, and none of the 12 judged fine.
+Flagged (suspect or bad) per 100 detectors: 0.4 on 30 minutes, 1.2 on 3 hours, 3.9 on 24 hours. Not field-verified.
+
+## Detector health
+
+Each detector gets a status, a plain-words reason, the periods affected and the categories, judged against what is
+normal for its type (function x lanes x sample length). Checks: stuck on, goes silent, count drops, misses vehicles at
+night, erratic counts, too-fast actuations, chattering, too many for the traffic, erratic time ON, busy at night,
+unusual daily pattern, Count zone held ON. **Bad** = one strong finding, two checks agreeing, or 4+ hours of the day.
+
+![Stuck on: a Presence detector held ON three times in one day](https://raw.githubusercontent.com/ShawnStrasser/atspm-detector/main/docs/images/health_stuck_on.png)
+
+![Busy at night: a detector ON 62 % of the time from 1 to 5 am](https://raw.githubusercontent.com/ShawnStrasser/atspm-detector/main/docs/images/health_busy_at_night.png)
+
+![Unusual daily pattern: an advance loop goes quiet at midday while its partner keeps counting](https://raw.githubusercontent.com/ShawnStrasser/atspm-detector/main/docs/images/health_unusual_day.png)
+
+## License
+
+MIT

atspm_detector-1.0.0/pyproject.toml

@@ -0,0 +1,69 @@
+[build-system]
+requires = ["setuptools>=77.0"]
+build-backend = "setuptools.build_meta"
+
+[project]
+name = "atspm-detector"
+dynamic = ["version"]
+description = "Phase, function, lanes, setback, night speed and health of traffic-signal detectors from the controller's hi-res event log (CPU, onnxruntime)."
+readme = "README.md"
+license = "MIT"
+license-files = ["LICENSE"]
+requires-python = ">=3.10"
+authors = [
+    {name = "Shawn Strasser"}
+]
+keywords = ["traffic signal", "ATSPM", "detector", "high-resolution data", "NTCIP"]
+classifiers = [
+    "Development Status :: 5 - Production/Stable",
+    "Intended Audience :: Science/Research",
+    "Operating System :: OS Independent",
+    "Programming Language :: Python :: 3",
+    "Programming Language :: Python :: 3 :: Only",
+    "Programming Language :: Python :: 3.10",
+    "Programming Language :: Python :: 3.11",
+    "Programming Language :: Python :: 3.12",
+    "Programming Language :: Python :: 3.13",
+    "Topic :: Scientific/Engineering",
+]
+
+dependencies = [
+    "numpy>=1.24",
+    "pandas>=2.0",
+    "duckdb>=1.0",
+    "onnxruntime>=1.21",
+]
+
+[project.optional-dependencies]
+charts = ["matplotlib>=3.7"]
+dev = [
+    "pytest>=7.0.0",
+    "build>=1.0",
+]
+
+[project.scripts]
+atspm-detector = "atspm_detector.pipeline:main"
+atspm-detector-check = "atspm_detector.check:cli"
+
+[project.urls]
+Homepage = "https://github.com/ShawnStrasser/atspm-detector"
+Documentation = "https://github.com/ShawnStrasser/atspm-detector#readme"
+Repository = "https://github.com/ShawnStrasser/atspm-detector"
+Issues = "https://github.com/ShawnStrasser/atspm-detector/issues"
+Changelog = "https://github.com/ShawnStrasser/atspm-detector/blob/main/CHANGELOG.md"
+"Embedding Guide" = "https://github.com/ShawnStrasser/atspm-detector/blob/main/docs/embedding.md"
+
+[tool.setuptools.dynamic]
+version = {attr = "atspm_detector.__version__"}
+
+[tool.setuptools]
+include-package-data = false
+
+[tool.setuptools.packages.find]
+where = ["src"]
+
+[tool.setuptools.package-data]
+atspm_detector = ["weights/*.json", "weights/*.onnx", "weights/*/*.json", "weights/*/*.onnx", "data/*.parquet", "reference/*.parquet"]
+
+[tool.pytest.ini_options]
+testpaths = ["tests"]

atspm_detector-1.0.0/setup.cfg

@@ -0,0 +1,4 @@
+[egg_info]
+tag_build = 
+tag_date = 0
+

atspm_detector-1.0.0/src/atspm_detector/__init__.py

@@ -0,0 +1,20 @@
+"""atspm_detector: phase, function, lanes, setback, night speed and health of every detector of a traffic signal,
+from the controller's high-resolution event log alone (CPU, onnxruntime; no channel-to-phase table).
+
+    from atspm_detector import predict, to_atspm_config
+    out = predict("events.parquet")                  # one row per detector
+    out, phases = predict(df, return_phases=True)    # + the per-phase lane table
+    config = to_atspm_config(out)                    # detector configuration for the atspm package
+
+Check an install with `python -m atspm_detector.check` (or the `atspm-detector-check` command).
+"""
+from __future__ import annotations
+
+__version__ = "1.0.0"
+
+from .atspm_export import atspm_coverage, to_atspm_config  # noqa: E402
+from .pipeline import (DEFAULT_MODEL_DIR, EXTRA_COLS, OUT_COLS, PHASE_COLS, PROB_COLS,  # noqa: E402
+                      list_signals, main, predict, run)
+
+__all__ = ["predict", "list_signals", "run", "main", "to_atspm_config", "atspm_coverage", "OUT_COLS", "EXTRA_COLS",
+           "PHASE_COLS", "PROB_COLS", "DEFAULT_MODEL_DIR", "__version__"]

atspm_detector-1.0.0/src/atspm_detector/__main__.py

@@ -0,0 +1,4 @@
+"""python -m atspm_detector --events ... --out ... (the predict command line)."""
+from .pipeline import main
+
+main()