Skip to main content

Priorityx: Entity prioritization and escalation detection using GLMM statistical models

PyPI version Downloads Tests Python License

Entity prioritization and escalation detection using GLMM statistical models

Installation

Requires Python 3.12 or later.

On macOS/Linux:

python3 -m venv .venv
source .venv/bin/activate
python -m pip install priorityx

On Windows PowerShell:

py -3.12 -m venv .venv
.\.venv\Scripts\python.exe -m pip install priorityx
.\.venv\Scripts\python.exe -m priorityx app

The Windows command uses the environment directly; activation is optional.

AutoViz: interactive saved-results workspace

Explore a linked quadrant matrix → YTD transition timeline → trajectories and regenerate layouts through browser controls. AutoViz reads saved results; opening charts or changing their layout does not fit models.

Start the workspace:

python -m priorityx app

The app opens in your browser and runs locally on macOS, Windows and Linux. Keep the terminal running while using the app; press Ctrl+C to stop it.

  1. Open results: choose a saved result bundle, or Import CSV files and assign your saved matrix, movement and transition CSVs. Supply the type label, cadence, coverage and source metadata. These are PriorityX result tables; source-specific raw data must be transformed by your own adapter first.
  2. Choose Type and cadence: labels come from your results. Quarterly opens when available. The timeline shows YTD through the latest saved period; full history is retained for event classification and trajectories.
  3. Inspect and adjust: select an entity to link the charts, zoom or Reset view, and open View data for exact values. Use Layout to adjust equal panel sizes and apply the changes. Save settings and Load settings inside Layout preserve a portable view configuration.
  4. Export: Export → Save offline HTML saves an interactive view that reopens without Python or a network connection. Matrix SVG also works offline; print PNG/SVG exports require the running local app. The HTML contains the full saved data, so share it with the same care as the source results.

To open a bundle directly:

python -m priorityx app --bundle results.json
Create a bundle from existing saved CSVs
from priorityx.results import ResultBundle, import_results_csv

dataset = import_results_csv(
    entity_type="work_unit", type_label="Work units",
    cadence="quarterly", source_id="saved-analysis",
    coverage_start="2025-Q1", as_of="2025-Q4",
    matrix_path="priority_matrix.csv",
    movement_path="movement.csv",
    transitions_path="transitions.csv",
)
ResultBundle([dataset]).save("results.json")

Use your actual file paths and coverage dates. Quarterly dates use YYYY-Qn; monthly dates use YYYY-MM with cadence="monthly". A bundle can hold multiple types and cadences by including more datasets in ResultBundle([...]).

See the workspace guide for controls, layout, state and exports, and the saved-result contract for import validation and trajectory selection.

Which identity and date columns? For the analysis API, set entity_col="your_identifier" and timestamp_col="your_date"; these refer to your own input columns. AutoViz imports the saved result columns, where entity is both the linked identifier and the displayed name. Movement dates use quarter (YYYY-Qn) or month (YYYY-MM); transitions use transition_quarter (or transition_month for Monthly). The matrix is a single snapshot, dated by the bundle's as_of metadata. The import dialog does not map arbitrary source columns or select a separate name column. See the exact column table and mapping example before importing files with different headers.

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

  • AutoViz local workspace with linked interactive charts, automatic layout and offline HTML export
  • 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.7.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for priorityx 0.7.0
File Size Uploaded Provenance Actions
priorityx-0.7.0.tar.gz 675.4 kB With provenance Details for priorityx-0.7.0.tar.gz

Built distribution (wheel)

Table of built distributions (wheels) for priorityx 0.7.0
File Interpreter ABI Platform Actions
priorityx-0.7.0-py3-none-any.whl Python 3 none any Details for priorityx-0.7.0-py3-none-any.whl

Total release size: 1.2 MB

Release files / priorityx-0.7.0.tar.gz

Download URL priorityx-0.7.0.tar.gz
Size 675.4 kB
Tags Source
SHA-256 checksum
How to use checksums
b318291810ac5d674727fac9aa379aeeebde866ae21e02e7f15cf076bf0598bf
BLAKE2b-256 checksum
How to use checksums
e0ebdead94706f914b916e933d0b4be213383e4fe82d7155d37207f7f1a054a8
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 18, 2026.

Transparency log

Release files / priorityx-0.7.0-py3-none-any.whl

Download URL priorityx-0.7.0-py3-none-any.whl
Size 507.9 kB
Tags Python 3
SHA-256 checksum
How to use checksums
c4daef6590cecab7a5c06566a9d7951e6e4eb880d0cc203c85dc6391f4cce169
BLAKE2b-256 checksum
How to use checksums
4ce6731aaf8cbbcca63f7d079b2e694c812187096eb7a7e5eef168851612c663
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 18, 2026.

Transparency log

Security for priorityx 0.7.0

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.

Full provenance

Both files in this release have been uploaded with provenance metadata.

Select from 2 files

Attestation for priorityx-0.7.0.tar.gz

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 18, 2026.

Transparency log

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page