relsa-severity-assessment

Compute RELSA severity scores and forecast humane endpoints with ARIMA for laboratory animal studies.

41.1k|3.8k|Updated Oct 19, 2025
One-click install
npx skills add https://github.com/K-Dense-AI/scientific-agent-skills --skill relsa-severity-assessment
Or copy as Structured Prompt for Agent
Please help me install this Agent Skill.
Skill: relsa-severity-assessment
Source: https://github.com/K-Dense-AI/scientific-agent-skills/tree/main/skills/relsa-severity-assessment
Command: npx skills add https://github.com/K-Dense-AI/scientific-agent-skills --skill relsa-severity-assessment

SYSTEM DOCUMENTATION & REQUIREMENTS

💡 This Skill requires numpy, pandas, scipy, statsmodels, matplotlib, and includes scripts (resource) and references (resource) and assets (resource) components.

What problem does it solve?

Animal welfare monitoring typically evaluates each readout (weight loss, temperature, clinical scores) in isolation, making it hard to judge how severely an individual animal is affected or to anticipate humane endpoints before they are reached.

Core Features & Use Cases

  • RELSA scoring: Combines multiple welfare readouts into one per-animal, per-time-point severity score relative to a reference set, with baseline normalization, directionality (turned variables), and ordinal score mapping.
  • ARIMA forecasting (foRcast): Fits per-animal ARIMA models to RELSA trajectories to predict endpoint scores with 95% prediction intervals, evaluated by RMSE, PICP, and MPIW.
  • KDE severity zones: Derives candidate attention/danger thresholds from kernel density minima on the RELSA scale, with bandwidth sensitivity guidance.
  • Use Case: Given a CSV of daily mouse measurements (weight, temperature, clinical score, biomarker), compute RELSA scores against the endpoint-reaching reference group, forecast which animals will reach the humane endpoint, and report severity zones for a 3Rs or EU Directive 2010/63/EU welfare assessment.

Quick Start

Ask the agent to compute RELSA scores from your cohort CSV using scripts/relsa_score.py with the endpoint group as reference, then forecast endpoints with scripts/forecast_relsa.py.

Frequently Asked Questions about relsa-severity-assessment

High-intent search queries and answers about installing and using this skill.

FAQPage Schema
How do I combine multiple animal welfare measurements into one severity score?

Use the RELSA procedure: normalize each variable to the animal's baseline, declare rising variables as turned, build a reference set from the highest-burden group, and run scripts/relsa_score.py. It outputs one score per animal per time point with per-variable weights.

How to predict when a lab animal will reach a humane endpoint?

Fit an ARIMA model to each animal's RELSA trajectory using scripts/forecast_relsa.py, which forecasts the endpoint score with a 95% prediction interval. Report RMSE, PICP, and MPIW together, and act on the upper interval bound since ARIMA cannot foresee abrupt deterioration.

What Python packages are required for RELSA severity scoring?

The scoring and KDE threshold scripts need numpy, pandas, and scipy. Forecasting additionally requires statsmodels >= 0.14, and matplotlib is needed only for figures. Python 3.10 or later is required; no network access is needed.

Why does a variable contribute nothing to my RELSA score?

A variable whose worsening direction is rising but is not declared as turned contributes exactly zero, because deviations in the wrong direction are floored at zero. Declare rising variables like clinical scores and biomarkers with --turned, and check the reference model table for plausible max reached values.

Are RELSA KDE thresholds the same as EU Directive 2010/63/EU severity categories?

No. KDE-derived attention and danger zones are model-specific candidate thresholds on the RELSA scale, not regulatory severity gradings. EU categories such as mild, moderate, and severe are assigned prospectively by a separate process, and thresholds are sensitive to bandwidth choice.

When should I not use ARIMA forecasting for severity trajectories?

Avoid relying on ARIMA when deterioration is abrupt, since the model assumes stationarity and linearity and cannot predict a cliff from a smooth prior trajectory. For sudden changes, consider Bayesian online changepoint detection or Markov switching models instead.