Priorityx: Entity prioritization and escalation detection using GLMM statistical models
Entity prioritization and escalation detection using GLMM statistical models
Installation
pip install priorityx
Quick Start
import pandas as pd
import priorityx as px
df = pd.read_csv("data.csv")
# Default: volume x growth (single GLMM)
results = px.fit_priority_matrix(
df,
entity_col="service",
timestamp_col="date",
temporal_granularity="quarterly",
)
# Returns: entity, x_score, y_score, count, quadrant
px.plot_priority_matrix(results, entity_name="Service", save_plot=True)
Custom Axes
# Custom Y axis: volume × resolution_days (two GLMMs)
results = px.fit_priority_matrix(
df,
entity_col="service",
timestamp_col="date",
y_metric="resolution_days",
)
# Custom both axes: disputed_amount × paid_amount
results = px.fit_priority_matrix(
df,
entity_col="service",
timestamp_col="date",
x_metric="disputed_amount",
y_metric="paid_amount",
)
Composite Indices
# Add entity metrics
metrics = px.aggregate_entity_metrics(
df,
entity_col="service",
duration_start_col="opened_at",
duration_end_col="closed_at",
primary_col="exposure",
secondary_col="recovery",
)
results = results.merge(metrics, left_on="entity", right_on="service", how="left")
# Add weighted indices: RI (Risk), SQI (Service Quality), EWI (Early Warning)
results = px.add_priority_indices(
results,
volume_col="count",
growth_col="y_score",
severity_col="total_primary",
resolution_col="mean_duration",
recovery_col="secondary_to_primary_ratio",
# customize weights (default shown)
w_volume=0.4, w_growth=0.4, w_severity=0.2,
w_resolution=0.5, w_recovery=0.5,
w_risk=0.7, w_quality=0.3,
)
# Top priority entities
top_risks = results.nlargest(10, "EWI")
Features
- GLMM-based priority matrix (Q1–Q4) with entity-level intercept/slope insights
- Priority-based transition timeline (Crisis / Investigate / Monitor / Low) with spike markers (
*X,*Y,*XY) - Cumulative movement tracking and trajectory visualizations
- Transition driver analysis that surfaces top subcategories causing quadrant shifts with spike summaries
- Deterministic seeding option for reproducible GLMM runs (set
PRIORITYX_GLMM_SEED)
Use Cases
IT incidents, software bugs, compliance violations, performance monitoring.
Documentation
Metadata
Release files for priorityx 0.6.2
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| priorityx-0.6.2.tar.gz | 278.4 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| priorityx-0.6.2-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 339.1 kB
Release files / priorityx-0.6.2.tar.gz
| Download URL | priorityx-0.6.2.tar.gz |
|---|---|
| Size | 278.4 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
27151f595bf71586230823359997c463737cf9f21bf76ff6bed3f8acd486c28e
|
|
BLAKE2b-256 checksum How to use checksums |
1fcd1fb8579a736d0afd8b486f9a0da5ab65c7920efced59c7b21e3af7f5ee62
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency logRelease files / priorityx-0.6.2-py3-none-any.whl
| Download URL | priorityx-0.6.2-py3-none-any.whl |
|---|---|
| Size | 60.7 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
6d76dc3cbf73fb01f29377388e825de217ea5472df9994793f5406393d9bc056
|
|
BLAKE2b-256 checksum How to use checksums |
7d8c1fff8fdb69cf49fa90599098245c77afedcc70fecead5032d5e7b049be50
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/7.0.0 CPython/3.13.14
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 12, 2026.
Transparency log