Update README.md
Browse files
README.md
CHANGED
|
@@ -1,3 +1,233 @@
|
|
| 1 |
-
---
|
| 2 |
-
|
| 3 |
-
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| 1 |
+
---
|
| 2 |
+
language: en
|
| 3 |
+
license: mit
|
| 4 |
+
task_categories:
|
| 5 |
+
- text-classification
|
| 6 |
+
tags:
|
| 7 |
+
- clinical-trials
|
| 8 |
+
- five-node-cascade
|
| 9 |
+
size_categories:
|
| 10 |
+
- 1K<n<10K
|
| 11 |
+
pretty_name: Clinical Five Node Shock Cascade Boundary Forecast
|
| 12 |
+
---
|
| 13 |
+
|
| 14 |
+
# What this repo does
|
| 15 |
+
|
| 16 |
+
This dataset models shock cascade boundary approach using a Clarus five-node coupling framework combined with trajectory and system dynamics.
|
| 17 |
+
|
| 18 |
+
The goal is to predict whether a patient is approaching the shock cascade boundary.
|
| 19 |
+
|
| 20 |
+
The dataset introduces a dynamic forecasting layer that allows models to reason about motion through the stability manifold rather than relying only on static physiological snapshots.
|
| 21 |
+
|
| 22 |
+
# Core five-node cascade
|
| 23 |
+
|
| 24 |
+
hemodynamic_stress
|
| 25 |
+
buffer_capacity
|
| 26 |
+
intervention_delay
|
| 27 |
+
organ_coupling
|
| 28 |
+
perfusion_stability
|
| 29 |
+
|
| 30 |
+
These five variables represent the interacting physiological state controlling shock stability.
|
| 31 |
+
|
| 32 |
+
hemodynamic_stress
|
| 33 |
+
Represents circulatory burden such as falling pressure reserve, rising vasopressor demand, tissue hypoperfusion, or escalating shock load.
|
| 34 |
+
|
| 35 |
+
buffer_capacity
|
| 36 |
+
Represents patient reserve including metabolic resilience, cardiovascular compensation, and remaining tolerance to hemodynamic stress.
|
| 37 |
+
|
| 38 |
+
intervention_delay
|
| 39 |
+
Represents the delay between deterioration onset and effective clinical response.
|
| 40 |
+
|
| 41 |
+
organ_coupling
|
| 42 |
+
Represents cross-system interaction such as cardio-renal stress, inflammatory spillover, respiratory-hemodynamic linkage, or multi-organ destabilization.
|
| 43 |
+
|
| 44 |
+
perfusion_stability
|
| 45 |
+
Represents the remaining stability of tissue perfusion, circulatory adequacy, and microvascular resilience under shock stress.
|
| 46 |
+
|
| 47 |
+
The five-node structure models how these variables interact to produce either recoverable dynamics or cascade deterioration.
|
| 48 |
+
|
| 49 |
+
# Trajectory layer
|
| 50 |
+
|
| 51 |
+
drift_gradient represents the direction of motion in the system state space.
|
| 52 |
+
|
| 53 |
+
Values near +1 indicate motion toward instability.
|
| 54 |
+
|
| 55 |
+
Values near −1 indicate motion toward recovery.
|
| 56 |
+
|
| 57 |
+
This variable captures trajectory alignment with the instability boundary.
|
| 58 |
+
|
| 59 |
+
# Dynamic forecasting layer
|
| 60 |
+
|
| 61 |
+
Three additional variables describe how the system moves through the stability manifold.
|
| 62 |
+
|
| 63 |
+
drift_velocity — speed of motion through state space
|
| 64 |
+
drift_acceleration — change in velocity across consecutive time steps
|
| 65 |
+
boundary_distance — proximity to the instability boundary
|
| 66 |
+
|
| 67 |
+
Together these variables allow models to estimate how rapidly instability is approaching rather than simply identifying its direction.
|
| 68 |
+
|
| 69 |
+
This converts the dataset from trajectory detection into dynamic cascade forecasting.
|
| 70 |
+
|
| 71 |
+
# Dynamic variable definitions
|
| 72 |
+
|
| 73 |
+
drift_velocity
|
| 74 |
+
|
| 75 |
+
Magnitude of state change between consecutive time steps.
|
| 76 |
+
|
| 77 |
+
Definition
|
| 78 |
+
|
| 79 |
+
drift_velocity(t) = ||x(t) − x(t−1)||
|
| 80 |
+
|
| 81 |
+
Interpretation
|
| 82 |
+
|
| 83 |
+
Higher values indicate faster movement through the stability manifold.
|
| 84 |
+
|
| 85 |
+
Lower values indicate slower system evolution.
|
| 86 |
+
|
| 87 |
+
drift_acceleration
|
| 88 |
+
|
| 89 |
+
Rate of change of drift velocity across three consecutive snapshots.
|
| 90 |
+
|
| 91 |
+
Definition
|
| 92 |
+
|
| 93 |
+
drift_acceleration(t) = drift_velocity(t) − drift_velocity(t−1)
|
| 94 |
+
|
| 95 |
+
where
|
| 96 |
+
|
| 97 |
+
drift_velocity(t) = ||x(t) − x(t−1)||
|
| 98 |
+
|
| 99 |
+
Interpretation
|
| 100 |
+
|
| 101 |
+
Positive values indicate accelerating movement toward instability.
|
| 102 |
+
|
| 103 |
+
Negative values indicate deceleration or stabilization.
|
| 104 |
+
|
| 105 |
+
boundary_distance
|
| 106 |
+
|
| 107 |
+
Weighted metric distance between the current system state and the instability boundary.
|
| 108 |
+
|
| 109 |
+
Definition
|
| 110 |
+
|
| 111 |
+
Computed as weighted Euclidean distance from the current state vector to the nearest point on the instability boundary, normalized to the range 0 to 1.
|
| 112 |
+
|
| 113 |
+
Interpretation
|
| 114 |
+
|
| 115 |
+
0 indicates the system has reached the cascade boundary.
|
| 116 |
+
|
| 117 |
+
Lower values indicate minimal remaining stability margin.
|
| 118 |
+
|
| 119 |
+
Higher values indicate greater separation from collapse.
|
| 120 |
+
|
| 121 |
+
# Prediction target
|
| 122 |
+
|
| 123 |
+
label_shock_cascade_boundary
|
| 124 |
+
|
| 125 |
+
Binary classification.
|
| 126 |
+
|
| 127 |
+
1 indicates the system is entering the shock cascade boundary regime.
|
| 128 |
+
|
| 129 |
+
0 indicates the system remains recoverable.
|
| 130 |
+
|
| 131 |
+
# Binary simplification note
|
| 132 |
+
|
| 133 |
+
Real shock deterioration unfolds as a continuous physiological process.
|
| 134 |
+
|
| 135 |
+
This dataset encodes boundary approach as a binary classification problem to simplify model evaluation and benchmarking.
|
| 136 |
+
|
| 137 |
+
# False stability example
|
| 138 |
+
|
| 139 |
+
The central challenge in this dataset is detecting cases that appear stable when viewed only through the five-node state variables.
|
| 140 |
+
|
| 141 |
+
Example
|
| 142 |
+
|
| 143 |
+
hemodynamic_stress 0.44
|
| 144 |
+
buffer_capacity 0.72
|
| 145 |
+
intervention_delay 0.21
|
| 146 |
+
organ_coupling 0.27
|
| 147 |
+
perfusion_stability 0.70
|
| 148 |
+
drift_gradient +0.66
|
| 149 |
+
drift_velocity 0.18
|
| 150 |
+
drift_acceleration +0.08
|
| 151 |
+
boundary_distance 0.07
|
| 152 |
+
label_shock_cascade_boundary 1
|
| 153 |
+
|
| 154 |
+
This row appears relatively safe if only the static state variables are considered.
|
| 155 |
+
|
| 156 |
+
However:
|
| 157 |
+
|
| 158 |
+
drift_gradient shows motion toward deterioration
|
| 159 |
+
drift_velocity shows active movement through state space
|
| 160 |
+
drift_acceleration shows increasing momentum
|
| 161 |
+
boundary_distance shows very little remaining stability margin
|
| 162 |
+
|
| 163 |
+
This is a false stability case.
|
| 164 |
+
|
| 165 |
+
The patient appears stable in a static snapshot but is dynamically close to deterioration.
|
| 166 |
+
|
| 167 |
+
# Row structure
|
| 168 |
+
|
| 169 |
+
scenario_id
|
| 170 |
+
hemodynamic_stress
|
| 171 |
+
buffer_capacity
|
| 172 |
+
intervention_delay
|
| 173 |
+
organ_coupling
|
| 174 |
+
perfusion_stability
|
| 175 |
+
drift_gradient
|
| 176 |
+
drift_velocity
|
| 177 |
+
drift_acceleration
|
| 178 |
+
boundary_distance
|
| 179 |
+
label_shock_cascade_boundary
|
| 180 |
+
|
| 181 |
+
# Files
|
| 182 |
+
|
| 183 |
+
data/train.csv
|
| 184 |
+
data/tester.csv
|
| 185 |
+
scorer.py
|
| 186 |
+
readme.md
|
| 187 |
+
|
| 188 |
+
# Evaluation
|
| 189 |
+
|
| 190 |
+
Models are evaluated using binary classification metrics.
|
| 191 |
+
|
| 192 |
+
accuracy
|
| 193 |
+
precision
|
| 194 |
+
recall_cascade_detection
|
| 195 |
+
false_safe_rate
|
| 196 |
+
f1
|
| 197 |
+
confusion_matrix
|
| 198 |
+
|
| 199 |
+
Primary metric
|
| 200 |
+
|
| 201 |
+
recall_cascade_detection
|
| 202 |
+
|
| 203 |
+
Secondary diagnostic metric
|
| 204 |
+
|
| 205 |
+
false_safe_rate
|
| 206 |
+
|
| 207 |
+
The primary goal is detecting cascade onset rather than maximizing overall accuracy.
|
| 208 |
+
|
| 209 |
+
# License
|
| 210 |
+
|
| 211 |
+
MIT
|
| 212 |
+
|
| 213 |
+
# Structural Note
|
| 214 |
+
|
| 215 |
+
Clarus datasets encode cascade instability through interacting system variables rather than isolated predictors.
|
| 216 |
+
|
| 217 |
+
Collapse emerges from coupled system dynamics rather than from any single measurement crossing a threshold.
|
| 218 |
+
|
| 219 |
+
# Production Deployment
|
| 220 |
+
|
| 221 |
+
These datasets support early warning models designed to detect deterioration trajectories before irreversible cascade occurs.
|
| 222 |
+
|
| 223 |
+
Such models may assist clinical monitoring systems by identifying dynamic instability patterns earlier than threshold-based alerts.
|
| 224 |
+
|
| 225 |
+
# Enterprise & Research Collaboration
|
| 226 |
+
|
| 227 |
+
The Clarus dataset framework can be applied across multiple domains including clinical medicine, infrastructure monitoring, complex AI systems, and other environments where cascade instability must be detected before boundary crossing.
|
| 228 |
+
|
| 229 |
+
For dataset expansion, custom coherence scorers, or deployment architecture:
|
| 230 |
+
team@clarusinvariant.com
|
| 231 |
+
|
| 232 |
+
Instability is detectable.
|
| 233 |
+
Governance determines whether it propagates.
|