Constraint Shift Factor Runs

One row per COMPLETED nightly estimation of MISO constraint shift factors, and the only record that a run finished.

Congestion & Constraints data

Download data

Native record

one completed estimation run

nightly (one row per completed run) publication cadence

Evidence

Reference data

Stable context used to interpret other datasets

Time basis

Point-in-time records

UTC · computed_at

Overview

Resolve the latest usable run here — computed_at = (SELECT max(computed_at) FROM atg.miso_constraint_sensitivity_runs) — and never off max(computed_at) of the sensitivities themselves, because a run writes its rows in blocks that all carry the new timestamp and an unfinished or abandoned run would otherwise look like the newest one. Each row also carries how much evidence that run had: interval_coverage is the fraction of published dispatch intervals that survived admission, intervals_refused_unexplained counts intervals showing congestion with no constraint recorded as binding (an unobserved binding set), constraint_feed_lag_minutes is how far the constraint feed trailed the price feed, and constraints_seen / constraints_in_fit / constraints_reported show how many constraints bound, how many were good enough to control for, and how many earned a published estimate.

Query contract

The newest row is the newest COMPLETE run: computed_at = (SELECT max(computed_at) FROM atg.miso_constraint_sensitivity_runs). Use that value to filter atg.miso_constraint_sensitivities.

Analysis rules

One row per run. Counting rows counts runs, not constraints, nodes or intervals — those are columns on each row.

Interpretation

A run appears here only after every one of its node blocks has landed. That is the point of the table: rows go into the sensitivities table block by block, all carrying the new computed_at, so a run still being written — or one that died halfway — would otherwise look like the newest. Absence of a row means the run did not finish, not that it did not happen.
This is provenance about an estimation job. Nothing in it measures the grid: it says how much evidence a run had, not what congestion occurred.

Access

Need the full history of this dataset in Snowflake, Databricks or your own storage? Data services delivers it on a schedule.

Schema18

Column

Type

computed_atDateTime64(3, 'UTC')

run_idString

isoLowCardinality(String)

window_startDateTime64(3, 'UTC')

window_endDateTime64(3, 'UTC')

rows_writtenUInt64

rows_estimatedUInt64

constraints_seenUInt32

constraints_in_fitUInt32

constraints_reportedUInt32

nodesUInt32

n_intervalsUInt32

intervals_publishedUInt32

intervals_refused_thinUInt32

intervals_refused_unexplainedUInt32

interval_coverageFloat32

constraint_feed_lag_minutesFloat32

method_versionLowCardinality(String)

Sample data

computed_at	run_id	iso	window_start	window_end	rows_written	rows_estimated	constraints_seen	constraints_in_fit	constraints_reported	nodes	n_intervals	intervals_published	intervals_refused_unexplained	interval_coverage	constraint_feed_lag_minutes	method_version
2026-10-22 09:41:19.343	6dece46c-7d01-4eb8-b730-cd44727bb583	MISO	2026-08-23 09:41:19.000	2026-10-22 09:41:19.000	141382	61815	446	418	195	317	16260	16512	252	0.98473835	0	ols-blockboot-v2+solo-median-dayboot-v1
2026-10-21 09:41:20.013	4d90c385-7923-48be-b3c8-efbd140b4dfb	MISO	2026-08-22 09:41:20.000	2026-10-21 09:41:20.000	141382	61498	446	420	194	317	16223	16509	286	0.9826761	0	ols-blockboot-v2+solo-median-dayboot-v1
2026-10-20 09:41:19.962	0adae2b1-c719-429b-a317-17b93ddf5f86	MISO	2026-08-21 09:41:19.000	2026-10-20 09:41:19.000	139163	60547	439	414	191	317	16186	16495	309	0.98126704	0	ols-blockboot-v2+solo-median-dayboot-v1
2026-10-19 09:41:20.273	0e8f7b39-c9f9-4dd0-8357-907fd6ee6727	MISO	2026-08-20 09:41:20.000	2026-10-19 09:41:20.000	138529	60230	437	412	190	317	16157	16477	320	0.980579	5	ols-blockboot-v2+solo-median-dayboot-v1
2026-10-18 09:41:20.315	33421d38-b355-4de5-b4b0-c656cf67dc26	MISO	2026-08-19 09:41:20.000	2026-10-18 09:41:20.000	138846	59596	438	412	188	317	16134	16475	341	0.979302	0	ols-blockboot-v2+solo-median-dayboot-v1
2026-10-17 09:41:19.934	9320d46b-7ce2-4519-9236-d805509ee758	MISO	2026-08-18 09:41:19.000	2026-10-17 09:41:19.000	137895	58962	435	408	186	317	16101	16465	364	0.9778925	5	ols-blockboot-v2+solo-median-dayboot-v1
2026-10-16 09:41:18.443	4a65a7df-a7b2-4454-b94c-7ad79f01a5f4	MISO	2026-08-17 09:41:18.000	2026-10-16 09:41:18.000	133774	57377	422	397	181	317	15786	16470	684	0.9584699	5	ols-blockboot-v2
2026-10-15 09:41:21.082	e28f4d50-738a-4a07-9e0d-60422500a2c4	MISO	2026-08-16 09:41:21.000	2026-10-15 09:41:21.000	128702	57060	406	381	180	317	15762	16474	712	0.9567804	0	ols-blockboot-v2
2026-10-14 09:41:19.768	3e2acfb0-30ec-4d5f-b751-c67017e7426b	MISO	2026-08-15 09:41:19.000	2026-10-14 09:41:19.000	129019	57377	407	381	181	317	15758	16486	728	0.9558413	5	ols-blockboot-v2
2026-10-13 09:41:19.905	7ac5584c-7bb8-4fd8-9a25-981e43464844	MISO	2026-08-14 09:41:19.000	2026-10-13 09:41:19.000	128385	57377	405	380	181	317	15756	16488	732	0.9556041	5	ols-blockboot-v2
2026-10-12 09:41:20.722	f9c02b15-256d-447d-bd65-eedcdd2ca4bd	MISO	2026-08-13 09:41:20.000	2026-10-12 09:41:20.000	125215	57060	395	370	180	317	15745	16492	747	0.9547053	5	ols-blockboot-v2
2026-10-11 09:41:19.858	175eee24-0f16-48cc-8de8-f0eb6c731dd9	MISO	2026-08-12 09:41:19.000	2026-10-11 09:41:19.000	126166	56109	398	373	177	317	15609	16357	748	0.95427036	5	ols-blockboot-v2
2026-10-10 09:41:20.004	a488b1c8-00f6-4d51-8c90-29749349fe5f	MISO	2026-08-11 09:41:20.000	2026-10-10 09:41:20.000	124898	53890	394	369	170	317	15331	16079	748	0.9534797	5	ols-blockboot-v2
2026-10-09 09:41:19.882	d279e5fe-9652-4bbe-b1a7-c0a8bf5a292e	MISO	2026-08-10 09:41:19.000	2026-10-09 09:41:19.000	121411	51988	383	358	164	317	15054	15802	748	0.9526642	5	ols-blockboot-v2
2026-10-08 09:41:22.276	b2a4e76c-a15f-4741-ad3b-6885e4acedd9	MISO	2026-08-09 09:41:22.000	2026-10-08 09:41:22.000	119509	51988	377	352	164	317	14778	15526	748	0.95182276	5	ols-blockboot-v2
2026-10-07 09:41:36.851	0f8c5a09-c813-4894-9478-5f4e0d24fb4a	MISO	2026-08-08 09:41:36.000	2026-10-07 09:41:36.000	118875	51354	375	351	162	317	14514	15260	746	0.951114	0	ols-blockboot-v2
2026-10-06 09:41:20.050	a5cfef19-d007-4002-a093-b1a7350bbaa2	MISO	2026-08-07 09:41:20.000	2026-10-06 09:41:20.000	114754	50086	362	335	158	317	14241	14987	746	0.9502235	0	ols-blockboot-v2
2026-10-05 09:41:19.600	cedab493-db1e-4afd-90a4-986428e48642	MISO	2026-08-06 09:41:19.000	2026-10-05 09:41:19.000	110633	49452	349	327	156	317	13973	14709	736	0.9499626	5	ols-blockboot-v2
2026-10-04 09:41:19.107	e150e311-0274-4a93-b0a7-b77338db3d73	MISO	2026-08-05 09:41:19.000	2026-10-04 09:41:19.000	110633	49135	349	326	155	317	13713	14435	722	0.9499827	5	ols-blockboot-v2
2026-10-03 09:41:21.804	a9361ff8-7359-4f04-a2e2-bf798f81227a	MISO	2026-08-04 09:41:21.000	2026-10-03 09:41:21.000	109048	48184	344	320	152	317	13439	14162	723	0.9489479	5	ols-blockboot-v2
2026-10-02 09:41:24.392	6a565254-be44-4cc3-94fa-c1c5a1717d73	MISO	2026-08-03 09:41:24.000	2026-10-02 09:41:24.000	107463	47233	339	316	149	317	13171	13894	723	0.9479632	5	ols-blockboot-v2
2026-10-01 09:41:19.365	ef5af5d7-3a74-4d72-9fc9-c471ad0b6a4d	MISO	2026-08-02 09:41:19.000	2026-10-01 09:41:19.000	103342	46599	326	303	147	317	12895	13618	723	0.9469085	5	ols-blockboot-v2
2026-09-30 09:41:21.424	a4e5910d-f686-4e10-8cdd-bb7626924153	MISO	2026-08-01 09:41:21.000	2026-09-30 09:41:21.000	101440	45965	320	297	145	317	12620	13343	723	0.9458143	5	ols-blockboot-v2
2026-09-29 09:41:20.701	bdcbbed6-1453-46c7-96f1-0a99c84b336d	MISO	2026-07-31 09:41:20.000	2026-09-29 09:41:20.000	97953	44063	309	288	139	317	12346	13069	723	0.94467825	5	ols-blockboot-v2
2026-09-28 09:41:20.968	72d32741-c3c5-4143-a7a3-1188d54ffdbc	MISO	2026-07-30 09:41:20.000	2026-09-28 09:41:20.000	95100	42478	300	278	134	317	12069	12791	722	0.94355404	0	ols-blockboot-v2

Coverage

100.0% complete0 gap days45 days with data

Show coverage history

Coverage: 100.0%Days with data: 45Gaps: 0

2026

gaplessmore

Related congestion & constraints data

Related congestion & constraints data
Dataset	Description
Annual real-time constraint historyMISO · year publication	MISO's Annual real-time constraint history. Each row preserves a publisher record, workbook row, or report document with its source member and row index. Source timestamps, units, geographic scope, and revision qualifiers are retained in record_json; event_time is collection time; completed_at is when the entire document became available.
Constraint Shift Factors (Estimated)MISO · nightly (60-day rolling estimation window)	Estimated sensitivity of every MISO pricing location's price to every binding transmission constraint: one row per constraint, contingency, and location, recomputed nightly over a rolling 60-day window. This is what answers 'which nodes drive this constraint' and 'which constraints is this node exposed to'. Covers MISO's binding real-time constraints over its hub and zone roll-up of roughly 325 pricing locations, so the answers are coarser than a full nodal set. MISO publishes no contingency or terminal names, so contingency_name, from_station and to_station are always empty. shift_factor is in the ISO's orientation — POSITIVE means an incremental MW injected at that node increases loading on the constraint and the node is paid below system lambda while it binds; NEGATIVE means generation there relieves the constraint and earns a premium. These are ESTIMATES recovered from the price identity LMP = energy - sum(shift_factor x shadow_price), not a published PTDF matrix. They are measured RELATIVE TO THE MARKET'S REFERENCE — the identity yields SF(node) - SF(reference), so a single absolute value should be quoted as 'relative to the system reference' rather than as the node's PTDF, while DIFFERENCES between nodes are exact because the reference term cancels. Three further differences from a published matrix: they describe a NODE (a generator at that node inherits its location's value, and two units at one node are indistinguishable), they reflect the topology actually in effect across the window including outages rather than a stated base case, and every one carries a std_error from a 200-draw block bootstrap that resamples whole days. Read std_error before quoting shift_factor: an estimate whose absolute value is not at least twice its standard error is not distinguishable from zero. estimation_status says why a row has no number — 'thin_support' (in the fit, so it is controlled for, but under 12 binding intervals or under 3 distinct binding days), 'no_support' (under 3 binding intervals; not a regressor), or 'collinear' (it bound in lockstep with another constraint, so the two cannot be separated). Where from_station and to_station are populated they identify the monitored element and are NOT the constrained direction — the sign of shift_factor is what says which way. Every read must pin computed_at to one run, and must resolve that run through the companion atg.<iso>_constraint_sensitivity_runs ledger rather than off max(computed_at) here — rows are written in blocks that all carry the new timestamp, so an unfinished or abandoned run would otherwise look like the newest. Mixing runs averages a node across different network topologies.
Daily day-ahead binding constraintsMISO · day publication	MISO's Daily day-ahead binding constraints. Each row preserves a publisher record, workbook row, or report document with its source member and row index. Source timestamps, units, geographic scope, and revision qualifiers are retained in record_json; event_time is collection time; completed_at is when the entire document became available.
Day-Ahead Binding ConstraintsMISO · hourly (day-ahead)	The named transmission constraints that bound in MISO's day-ahead market, one row per constraint per operating hour, with the signed shadow price in dollars per MWh. constraint_name describes the flowgate as a monitored element under a contingency; branch_name is the monitored element itself, with branch_type LN for a line and XF for a transformer, and from_ca and to_ca its control areas. A row establishes that the constraint bound in the cleared day-ahead solution for that hour and its marginal system cost. It does not, by itself, identify which pricing node the constraint affected or whether it also bound in real time; those claims require shift-factor or direct attribution evidence. Distinct from miso.binding_constraint, which counts real-time binding constraints and names none of them. MISO restates this history, so read the latest load per constraint and hour.