jwst-gc pipeline monitor

Stage ladder

Products per filter

* = the product name carries no _o<obs> token and this field has more than one observation, so the count cannot be attributed to 2092/o002.

Astrometry — m2 checkpoint

“tiles ok” is not a tolerance. measure_offset_grid runs with no max_off_mas, and astrometry_offsets sets off_ok=True whenever that is None — so N/N counts tiles whose offset histogram had a coherent peak, however large the offset. The column that carries the gate is worst tile, against 15 mas.

Provenance

Queue

No jobs in the queue for this field.

Findings

• fail
  m8: products come from 2 different pipeline tags

  2026-08-26_PR543_6eb6ff9-dirty (4), 2026-08-26_PR551_59643d9-dirty (3). Image and catalog must be deployed from the SAME pipeline run; a mixed-tag set is not releasable as one product.

  catalogs/*m8*.prov.json

  what is affected, and why

  This happens when filters are re-run at different times and only some are regenerated — a partial rerun, or a merge that picked up an older per-filter product. The fix is to re-run the lagging filters at the current tag, not to re-stamp: the tag records which code wrote the numbers.

  Diagnostic writeupfull diagnostic writeup (PDF)

  pipeline tag	products
  2026-08-26_PR543_6eb6ff9-dirty	4
  2026-08-26_PR551_59643d9-dirty	3

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• fail
  F162M_o002: 64/128 exposures misaligned vs their visit consensus

  An exposure is misaligned when its offset exceeds 2.0 mas AND is significant against the peak error bars. At m2 this CORRECTS the offsets table and stops the run; the crf frames must be regenerated before cataloging continues.

  checkpoint_m2_F162M_o002_latest.json

  what is affected, and why

  Affected: 8/8 detectors — spread across detectors, so the frame as a whole moved: look at the offsets table and whether these exposures were regenerated from _cal after the table changed. fix_alignment SKIPS a frame that already has a RAOFFSET header, so correcting the table alone leaves stale frames in place; regenerate the working copy from _cal instead of re-applying on top.

  Misaligned by detector

  nrca211/16

  nrca110/16

  nrca38/16

  nrcb18/16

  nrca47/16

  nrcb37/16

  nrcb47/16

  nrcb26/16

  Diagnostic writeupD2 — internal astrometric repeatability · full diagnostic writeup (PDF)

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrca1	1.5	1.3	2.0	761.5	288536	3.0
  1	nrca1	0.1	2.3	2.3	863.3	242461	3.0
  1	nrca1	-2.4	0.1	2.4	631.5	261612	3.0
  1	nrca2	1.1	3.3	3.5	562.9	487700	3.0
  1	nrca2	0.4	2.1	2.1	363.9	482444	3.0
  1	nrca2	1.4	3.0	3.3	602.1	487769	3.0
  1	nrca2	-0.9	2.6	2.7	1,371.0	255761	3.0
  1	nrca2	-0.9	2.4	2.6	1,363.0	255356	3.0
  1	nrca2	-3.2	-0.1	3.2	617.0	265588	3.0
  1	nrca3	-0.3	-2.6	2.6	742.5	308182	3.0
  1	nrca3	2.0	-1.1	2.3	937.0	275071	3.0
  1	nrca3	-0.4	-2.4	2.4	456.8	270346	3.0
  1	nrca3	-0.6	-2.8	2.9	507.0	269815	3.0
  1	nrca4	1.8	-3.2	3.7	612.9	578154	3.0
  1	nrca4	-1.5	-3.0	3.4	624.5	568160	3.0
  1	nrcb1	1.8	-2.0	2.7	637.1	480741	3.0
  1	nrcb1	0.9	-2.3	2.4	692.7	468517	3.0
  1	nrcb2	1.2	-2.2	2.6	793.2	306366	3.0
  1	nrcb2	0.3	-2.8	2.8	556.0	308064	3.0
  1	nrcb3	-2.6	-0.5	2.7	772.6	389359	3.0
  1	nrcb4	1.4	2.2	2.6	1,145.2	286182	3.0
  2	nrca1	-5.0	3.5	6.1	1,282.0	95719	3.0
  2	nrca1	-5.6	3.1	6.3	1,300.5	96457	3.0
  2	nrca1	-3.2	2.0	3.8	1,305.5	104665	3.0
  2	nrca1	-3.2	2.2	3.9	1,326.0	103535	3.0
  2	nrca1	2.0	-0.1	2.0	1,642.0	84226	3.0
  2	nrca1	-3.7	-0.1	3.7	1,326.0	82070	3.0
  2	nrca1	-2.5	0.3	2.5	1,445.0	81763	3.0
  2	nrca2	-3.9	5.6	6.8	1,286.5	155468	3.0
  2	nrca2	-4.5	5.3	7.0	1,303.0	154406	3.0
  2	nrca2	-2.0	4.6	5.0	1,244.5	155651	3.0
  2	nrca2	-2.0	5.0	5.3	1,278.5	156568	3.0
  2	nrca2	4.1	0.5	4.1	1,148.5	125659	3.0
  2	nrca3	7.9	-7.8	11.1	2,517.0	90030	3.0
  2	nrca3	6.1	-7.8	9.9	1,294.0	92543	3.0
  2	nrca3	3.1	-7.8	8.4	2,372.0	83038	3.0
  2	nrca3	4.1	-7.4	8.4	2,373.0	83315	3.0
  2	nrca4	-2.3	0.3	2.3	743.7	202137	3.0
  2	nrca4	8.7	-4.5	9.8	999.7	184008	3.0
  2	nrca4	6.7	-4.8	8.2	1,038.3	187220	3.0

  showing 40 of 64

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• fail
  F210M_o002: 21/64 exposures misaligned vs their visit consensus

  An exposure is misaligned when its offset exceeds 2.0 mas AND is significant against the peak error bars. At m2 this CORRECTS the offsets table and stops the run; the crf frames must be regenerated before cataloging continues.

  checkpoint_m2_F210M_o002_latest.json

  what is affected, and why

  Affected: 8/8 detectors — spread across detectors, so the frame as a whole moved: look at the offsets table and whether these exposures were regenerated from _cal after the table changed. fix_alignment SKIPS a frame that already has a RAOFFSET header, so correcting the table alone leaves stale frames in place; regenerate the working copy from _cal instead of re-applying on top.

  Misaligned by detector

  nrca14/8

  nrcb44/8

  nrca23/8

  nrcb23/8

  nrca32/8

  nrca42/8

  nrcb12/8

  nrcb31/8

  Diagnostic writeupD2 — internal astrometric repeatability · full diagnostic writeup (PDF)

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrca1	2.0	-0.8	2.1	596.2	790531	3.0
  1	nrca1	-0.1	2.4	2.4	481.7	692361	3.0
  1	nrca1	0.2	2.1	2.1	566.9	687070	3.0
  1	nrca1	-2.5	-0.1	2.5	461.6	742543	3.0
  1	nrca2	-1.5	-1.7	2.2	607.4	1063982	3.0
  1	nrca2	1.5	2.1	2.6	798.8	810931	3.0
  1	nrca2	-1.6	2.0	2.6	800.0	812979	3.0
  1	nrca3	1.1	3.1	3.3	680.4	805644	3.0
  1	nrca3	-2.0	3.1	3.7	736.6	812062	3.0
  1	nrca4	1.0	3.0	3.2	606.7	1117146	3.0
  1	nrca4	-2.0	2.9	3.6	652.7	1118375	3.0
  1	nrcb1	1.2	2.3	2.6	612.4	1061593	3.0
  1	nrcb1	-1.7	2.1	2.7	621.1	1055088	3.0
  1	nrcb2	-1.4	-1.5	2.0	696.2	963873	3.0
  1	nrcb2	1.0	2.1	2.3	565.1	922162	3.0
  1	nrcb2	-1.9	2.0	2.8	659.6	922770	3.0
  1	nrcb3	-1.3	-2.0	2.4	641.0	1021729	3.0
  1	nrcb4	1.4	-2.1	2.5	662.2	788542	3.0
  1	nrcb4	0.6	2.5	2.6	696.9	685180	3.0
  1	nrcb4	0.1	2.1	2.1	504.9	686567	3.0
  1	nrcb4	-2.5	0.2	2.5	489.8	737798	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• fail
  F360M_o002: 4/16 exposures misaligned vs their visit consensus

  An exposure is misaligned when its offset exceeds 2.0 mas AND is significant against the peak error bars. At m2 this CORRECTS the offsets table and stops the run; the crf frames must be regenerated before cataloging continues.

  checkpoint_m2_F360M_o002_latest.json

  what is affected, and why

  Affected: 1/2 detectors — confined to nrcalong, which points at a detector-local defect (distortion reference, a bad filteroffset, or one chip's frames never re-aligned) rather than a whole-frame misalignment. fix_alignment SKIPS a frame that already has a RAOFFSET header, so correcting the table alone leaves stale frames in place; regenerate the working copy from _cal instead of re-applying on top.

  Misaligned by detector

  nrcalong4/8

  nrcblong0/8

  Diagnostic writeupD2 — internal astrometric repeatability · full diagnostic writeup (PDF)

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrcalong	-0.6	-2.7	2.8	2,184.3	196229	3.0
  1	nrcalong	1.8	-1.6	2.4	2,606.0	202729	3.0
  1	nrcalong	-0.5	3.7	3.7	2,027.7	203308	3.0
  1	nrcalong	-2.9	1.7	3.4	2,728.7	193564	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• fail
  F480M_o002: 5/16 exposures misaligned vs their visit consensus

  An exposure is misaligned when its offset exceeds 2.0 mas AND is significant against the peak error bars. At m2 this CORRECTS the offsets table and stops the run; the crf frames must be regenerated before cataloging continues.

  checkpoint_m2_F480M_o002_latest.json

  what is affected, and why

  Affected: 2/2 detectors — spread across detectors, so the frame as a whole moved: look at the offsets table and whether these exposures were regenerated from _cal after the table changed. fix_alignment SKIPS a frame that already has a RAOFFSET header, so correcting the table alone leaves stale frames in place; regenerate the working copy from _cal instead of re-applying on top.

  Misaligned by detector

  nrcalong3/8

  nrcblong2/8

  Diagnostic writeupD2 — internal astrometric repeatability · full diagnostic writeup (PDF)

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrcalong	0.0	-2.6	2.6	1,620.0	216859	3.0
  1	nrcalong	2.5	-1.5	2.9	2,764.0	218472	3.0
  1	nrcalong	-3.0	2.0	3.6	2,974.0	210596	3.0
  1	nrcblong	1.2	3.3	3.5	2,896.3	230945	3.0
  1	nrcblong	-1.7	3.2	3.6	3,055.0	230666	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• fail
  errors in cloudef2092-o002-m12-finalize: traceback

  Traceback (most recent call last):

  catalog_cloudef2092-o002-m12-finalize_41882789_4294967294.out

  what is affected, and why

  Diagnostic writeupfull diagnostic writeup (PDF)

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  m7: 15 product(s) stamped with a -dirty tag

  The tree had uncommitted changes, so the tag does not identify the code that ran. Fine for a development run; not for a release.

  catalogs/*m7*.prov.json

  what is affected, and why

  Diagnostic writeupfull diagnostic writeup (PDF)

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  m8: 7 product(s) stamped with a -dirty tag

  The tree had uncommitted changes, so the tag does not identify the code that ran. Fine for a development run; not for a release.

  catalogs/*m8*.prov.json

  what is affected, and why

  Diagnostic writeupfull diagnostic writeup (PDF)

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F162M: 19/64 exposures misaligned vs their visit consensus (checkpoint predates the frames)

  An exposure is misaligned when its offset exceeds 2.0 mas AND is significant against the peak error bars. At m2 this CORRECTS the offsets table and stops the run; the crf frames must be regenerated before cataloging continues. NOTE: the reduced frames are NEWER than this checkpoint, so the correction it triggered has probably already been applied — re-run the m2 checkpoint to confirm rather than treating this as current.

  checkpoint_m2_F162M_latest.json

  what is affected, and why

  Affected: 8/8 detectors — spread across detectors, so the frame as a whole moved: look at the offsets table and whether these exposures were regenerated from _cal after the table changed. fix_alignment SKIPS a frame that already has a RAOFFSET header, so correcting the table alone leaves stale frames in place; regenerate the working copy from _cal instead of re-applying on top.

  Misaligned by detector

  nrca26/8

  nrca12/8

  nrca32/8

  nrca42/8

  nrcb22/8

  nrcb32/8

  nrcb42/8

  nrcb11/8

  Diagnostic writeupD2 — internal astrometric repeatability · full diagnostic writeup (PDF)

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrca1	1.5	1.7	2.2	916.8	301779	3.0
  1	nrca1	-2.3	-0.9	2.5	1,250.3	260176	3.0
  1	nrca2	1.1	3.5	3.7	574.4	483364	3.0
  1	nrca2	0.3	2.3	2.3	365.0	482765	3.0
  1	nrca2	1.3	3.2	3.5	612.0	487686	3.0
  1	nrca2	-0.3	2.3	2.3	1,055.0	253082	3.0
  1	nrca2	-0.3	2.1	2.1	1,050.3	253811	3.0
  1	nrca2	-2.7	-0.2	2.7	748.0	262729	3.0
  1	nrca3	-0.2	-2.2	2.2	552.0	284761	3.0
  1	nrca3	-0.4	-2.6	2.7	536.5	284216	3.0
  1	nrca4	1.7	-3.0	3.4	629.2	580941	3.0
  1	nrca4	-1.5	-2.8	3.2	653.4	572354	3.0
  1	nrcb1	1.6	-1.6	2.2	662.4	479942	3.0
  1	nrcb2	1.3	-2.4	2.8	932.5	317635	3.0
  1	nrcb2	0.4	-3.0	3.0	680.8	320051	3.0
  1	nrcb3	0.6	2.2	2.3	953.4	378473	3.0
  1	nrcb3	-2.6	-0.1	2.6	673.2	389341	3.0
  1	nrcb4	-0.7	3.3	3.4	838.2	335452	3.0
  1	nrcb4	-2.5	-1.1	2.7	855.0	310202	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F210M: 20/64 exposures misaligned vs their visit consensus (checkpoint predates the frames)

  An exposure is misaligned when its offset exceeds 2.0 mas AND is significant against the peak error bars. At m2 this CORRECTS the offsets table and stops the run; the crf frames must be regenerated before cataloging continues. NOTE: the reduced frames are NEWER than this checkpoint, so the correction it triggered has probably already been applied — re-run the m2 checkpoint to confirm rather than treating this as current.

  checkpoint_m2_F210M_latest.json

  what is affected, and why

  Affected: 8/8 detectors — spread across detectors, so the frame as a whole moved: look at the offsets table and whether these exposures were regenerated from _cal after the table changed. fix_alignment SKIPS a frame that already has a RAOFFSET header, so correcting the table alone leaves stale frames in place; regenerate the working copy from _cal instead of re-applying on top.

  Misaligned by detector

  nrcb45/8

  nrca13/8

  nrcb23/8

  nrca22/8

  nrca32/8

  nrca42/8

  nrcb12/8

  nrcb31/8

  Diagnostic writeupD2 — internal astrometric repeatability · full diagnostic writeup (PDF)

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrca1	1.8	-1.0	2.1	690.3	834510	3.0
  1	nrca1	0.1	2.3	2.3	462.6	717258	3.0
  1	nrca1	-2.4	-0.2	2.4	533.8	746267	3.0
  1	nrca2	1.5	3.2	3.6	802.9	811542	3.0
  1	nrca2	-1.6	3.2	3.5	802.9	813169	3.0
  1	nrca3	1.0	2.9	3.1	693.4	820016	3.0
  1	nrca3	-2.1	2.9	3.6	774.4	825865	3.0
  1	nrca4	1.3	2.9	3.2	640.3	1116643	3.0
  1	nrca4	-1.7	2.9	3.4	649.5	1117636	3.0
  1	nrcb1	1.5	2.7	3.1	628.5	1062210	3.0
  1	nrcb1	-1.4	2.6	2.9	614.3	1055319	3.0
  1	nrcb2	1.1	3.0	3.2	664.2	896990	3.0
  1	nrcb2	0.3	2.6	2.6	477.3	894197	3.0
  1	nrcb2	-2.1	0.5	2.2	456.8	936485	3.0
  1	nrcb3	-2.2	-0.8	2.3	632.1	912849	3.0
  1	nrcb4	-0.2	-3.3	3.3	438.1	880436	3.0
  1	nrcb4	-0.2	-3.3	3.3	439.8	848585	3.0
  1	nrcb4	1.4	-3.5	3.8	682.7	841075	3.0
  1	nrcb4	0.8	2.3	2.4	731.5	722536	3.0
  1	nrcb4	-2.3	-0.1	2.3	455.8	744353	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F360M: 21/24 exposures misaligned vs their visit consensus (checkpoint predates the frames)

  An exposure is misaligned when its offset exceeds 2.0 mas AND is significant against the peak error bars. At m2 this CORRECTS the offsets table and stops the run; the crf frames must be regenerated before cataloging continues. NOTE: the reduced frames are NEWER than this checkpoint, so the correction it triggered has probably already been applied — re-run the m2 checkpoint to confirm rather than treating this as current.

  checkpoint_m2_F360M_latest.json

  what is affected, and why

  Affected: 3/3 detectors — spread across detectors, so the frame as a whole moved: look at the offsets table and whether these exposures were regenerated from _cal after the table changed. fix_alignment SKIPS a frame that already has a RAOFFSET header, so correcting the table alone leaves stale frames in place; regenerate the working copy from _cal instead of re-applying on top.

  Misaligned by detector

  nrcb8/8

  nrcblong8/8

  nrcalong5/8

  Diagnostic writeupD2 — internal astrometric repeatability · full diagnostic writeup (PDF)

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrcalong	-0.4	-2.4	2.5	2,044.7	195500	3.0
  1	nrcalong	2.0	-1.3	2.4	2,684.0	197041	3.0
  1	nrcalong	-0.0	3.2	3.2	1,531.0	194269	3.0
  1	nrcalong	-0.1	2.8	2.8	1,670.0	194400	3.0
  1	nrcalong	-2.6	0.8	2.7	2,297.0	191890	3.0
  1	nrcb	3.7	-3.5	5.1	3,852.0	76879	3.0
  1	nrcb	0.2	-5.2	5.2	3,294.0	77135	3.0
  1	nrcb	0.4	-7.1	7.1	4,054.0	77338	3.0
  1	nrcb	0.4	-5.1	5.1	3,990.0	76327	3.0
  1	nrcb	1.2	4.7	4.8	5,279.0	84101	3.0
  1	nrcb	-1.1	3.9	4.0	4,755.0	84232	3.0
  1	nrcb	-1.3	4.6	4.8	5,402.0	83466	3.0
  1	nrcb	-2.3	3.7	4.4	4,666.0	83765	3.0
  1	nrcblong	-7.6	3.6	8.4	2,672.0	154063	3.0
  1	nrcblong	-1.1	5.6	5.7	3,586.0	154411	3.0
  1	nrcblong	-0.6	10.6	10.6	3,202.0	157683	3.0
  1	nrcblong	0.8	6.8	6.8	3,299.5	157713	3.0
  1	nrcblong	-2.0	-5.0	5.4	2,885.7	202189	3.0
  1	nrcblong	1.8	-3.9	4.3	2,166.0	203304	3.0
  1	nrcblong	2.7	-7.1	7.6	2,991.3	199807	3.0
  1	nrcblong	1.6	-5.3	5.5	2,875.7	200023	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F480M: 8/24 exposures misaligned vs their visit consensus (checkpoint predates the frames)

  An exposure is misaligned when its offset exceeds 2.0 mas AND is significant against the peak error bars. At m2 this CORRECTS the offsets table and stops the run; the crf frames must be regenerated before cataloging continues. NOTE: the reduced frames are NEWER than this checkpoint, so the correction it triggered has probably already been applied — re-run the m2 checkpoint to confirm rather than treating this as current.

  checkpoint_m2_F480M_latest.json

  what is affected, and why

  Affected: 2/3 detectors — spread across detectors, so the frame as a whole moved: look at the offsets table and whether these exposures were regenerated from _cal after the table changed. fix_alignment SKIPS a frame that already has a RAOFFSET header, so correcting the table alone leaves stale frames in place; regenerate the working copy from _cal instead of re-applying on top.

  Misaligned by detector

  nrcb4/8

  nrcblong4/8

  nrcalong0/8

  Diagnostic writeupD2 — internal astrometric repeatability · full diagnostic writeup (PDF)

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrcb	-1.2	-2.4	2.7	2,951.3	214964	3.0
  1	nrcb	1.2	3.4	3.6	2,975.0	222618	3.0
  1	nrcb	0.6	3.0	3.1	2,544.0	221197	3.0
  1	nrcb	-2.0	1.0	2.2	2,513.3	221852	3.0
  1	nrcblong	-0.1	2.2	2.2	1,644.3	195628	3.0
  1	nrcblong	-0.1	2.2	2.2	1,686.3	195784	3.0
  1	nrcblong	-0.2	2.4	2.4	1,840.0	193487	3.0
  1	nrcblong	-0.3	2.3	2.3	1,861.3	191727	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F162M_o002 visit 1: reference tie recorded as could-not-verify (apply_ok=false)

  A correction is applied only when the tie is coherent AND the gross cross-check (100 mas) passes AND the per-tile map is clean. This one was not, so no correction was made — the frame keeps whatever it had.

  checkpoint_m2_F162M_o002_latest.json

  what is affected, and why

  Diagnostic writeupD3 — absolute tie to the reference frame · full diagnostic writeup (PDF)

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F480M visit 1: reference tie recorded as could-not-verify (apply_ok=false)

  A correction is applied only when the tie is coherent AND the gross cross-check (100 mas) passes AND the per-tile map is clean. This one was not, so no correction was made — the frame keeps whatever it had.

  checkpoint_m2_F480M_latest.json

  what is affected, and why

  Diagnostic writeupD3 — absolute tie to the reference frame · full diagnostic writeup (PDF)

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F162M visit 1: worst tile 24.6 mas at cell (0,2) (> 15 mas)

  36/36 tiles are reported "ok", but that counts tiles whose offset histogram had a coherent PEAK — not tiles within tolerance. The m7 cross-band gate is no significant 2" cell above 15 mas, and this cell exceeds it, so the bulk tie being ~0 does not mean the field is flat.

  checkpoint_m2_F162M_latest.json

  what is affected, and why

  17/36 cells exceed 15 mas. They are not confined to the edge, so this is an interior residual: a distortion or per-detector alignment problem, not a coverage artefact. The bulk tie for this visit is 0.45 mas — a small bulk value cannot cancel a local one.

  Diagnostic writeupD3 — absolute tie to the reference frame · full diagnostic writeup (PDF)

  cell	off (mas)	dRA	dDec	contrast	pairs
  (0,2)	24.6	-19.5	14.9	21.0	169732
  (1,3)	24.1	-22.4	8.9	12.5	285694
  (4,0)	22.8	-8.9	-21.0	21.7	210673
  (0,3)	20.3	15.2	13.5	15.0	170496
  (2,1)	19.5	-18.4	-6.5	16.3	188052
  (1,1)	19.3	-17.6	-7.8	16.0	254739
  (5,2)	19.0	14.4	12.3	26.0	39707
  (1,2)	18.6	-16.5	8.5	14.7	192393
  (5,5)	18.5	16.2	9.0	28.5	103176
  (3,0)	18.4	7.8	-16.7	21.3	232664
  (5,4)	18.2	17.4	5.3	19.0	106139
  (3,2)	18.1	16.2	8.0	18.5	160980
  (0,0)	17.7	-11.8	-13.2	17.2	305974
  (1,4)	17.3	-12.6	-11.8	14.8	300370
  (3,5)	16.9	9.8	13.8	24.5	127514
  (5,0)	15.5	-8.8	-12.7	24.0	72940
  (1,0)	15.4	-10.0	-11.7	17.0	31877

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F162M_o002 visit 1: worst tile 26.2 mas at cell (1,3) (> 15 mas)

  36/36 tiles are reported "ok", but that counts tiles whose offset histogram had a coherent PEAK — not tiles within tolerance. The m7 cross-band gate is no significant 2" cell above 15 mas, and this cell exceeds it, so the bulk tie being ~0 does not mean the field is flat.

  checkpoint_m2_F162M_o002_latest.json

  what is affected, and why

  17/36 cells exceed 15 mas. They are not confined to the edge, so this is an interior residual: a distortion or per-detector alignment problem, not a coverage artefact. The bulk tie for this visit is 0.89 mas — a small bulk value cannot cancel a local one.

  Diagnostic writeupD3 — absolute tie to the reference frame · full diagnostic writeup (PDF)

  cell	off (mas)	dRA	dDec	contrast	pairs
  (1,3)	26.2	-24.7	8.6	14.0	26209
  (0,2)	24.3	-18.9	15.3	21.5	169843
  (4,0)	23.5	-11.1	-20.7	20.0	211830
  (2,1)	21.1	-19.5	7.9	16.3	188764
  (5,2)	19.8	14.2	13.7	16.0	33059
  (0,3)	19.5	14.9	12.7	14.5	170611
  (1,1)	19.2	-17.6	-7.6	12.0	258337
  (5,5)	18.5	16.7	8.0	24.0	97889
  (5,0)	17.9	13.0	-12.3	17.0	56901
  (3,0)	17.8	7.4	-16.2	21.0	234982
  (0,0)	17.7	-11.7	-13.3	17.8	306196
  (1,2)	17.5	-15.6	7.9	14.7	193811
  (3,2)	17.1	15.5	7.3	17.5	161988
  (1,4)	16.7	-12.1	-11.6	14.8	303091
  (3,5)	16.1	10.4	12.3	25.0	127896
  (5,4)	15.3	14.5	-4.8	14.0	92738
  (2,4)	15.1	-14.5	-4.1	14.0	17539

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F162M_o002 visit 2: worst tile 215.7 mas at cell (0,4) (> 15 mas)

  36/36 tiles are reported "ok", but that counts tiles whose offset histogram had a coherent PEAK — not tiles within tolerance. The m7 cross-band gate is no significant 2" cell above 15 mas, and this cell exceeds it, so the bulk tie being ~0 does not mean the field is flat.

  checkpoint_m2_F162M_o002_latest.json

  what is affected, and why

  36/36 cells exceed 15 mas. They are not confined to the edge, so this is an interior residual: a distortion or per-detector alignment problem, not a coverage artefact. The bulk tie for this visit is 179.70 mas — a small bulk value cannot cancel a local one.

  Diagnostic writeupD3 — absolute tie to the reference frame · full diagnostic writeup (PDF)

  cell	off (mas)	dRA	dDec	contrast	pairs
  (0,4)	215.7	-212.1	39.2	9.0	44468
  (2,4)	194.7	-187.2	53.5	52.0	49587
  (1,2)	193.8	-179.7	72.5	55.0	79645
  (0,3)	191.0	-185.2	46.7	17.0	41760
  (1,4)	189.9	-183.2	50.2	33.0	115093
  (2,2)	189.4	-180.2	58.1	42.0	81840
  (1,3)	188.4	-182.1	48.2	27.5	108927
  (0,0)	187.7	-183.5	39.3	23.5	127748
  (1,0)	186.8	-181.7	43.3	22.7	184331
  (3,3)	186.4	-180.8	45.4	60.0	89580
  (2,3)	185.8	-179.7	47.2	28.0	95813
  (2,0)	184.7	-179.2	44.9	38.5	161897
  (2,1)	184.1	-176.8	51.2	36.5	138367
  (5,0)	184.1	-179.7	39.6	20.0	95886
  (1,1)	183.8	-177.4	48.4	27.0	110792
  (0,1)	183.8	-179.0	41.5	31.0	82892
  (3,0)	183.2	-178.0	43.2	34.5	176850
  (0,2)	183.0	-169.9	67.9	17.0	37692
  (2,5)	182.7	-174.5	54.1	81.0	77236
  (5,3)	182.6	-176.3	47.5	56.0	81296
  (3,4)	181.8	-172.2	58.2	57.0	43578
  (1,5)	181.6	-173.9	52.5	36.0	115358
  (4,3)	181.0	-175.0	46.4	36.0	106950
  (5,4)	180.4	-173.4	49.9	69.0	88179
  (4,0)	180.0	-175.1	41.6	30.7	219508
  (5,1)	178.7	-170.7	53.0	27.0	170570
  (3,2)	178.4	-168.1	59.8	29.5	130046
  (3,1)	178.1	-169.8	53.7	28.7	231128
  (4,2)	177.8	-168.0	58.3	24.3	199954
  (4,1)	177.5	-170.6	48.9	22.5	298460
  (4,4)	176.8	-167.6	56.5	50.0	56490
  (0,5)	174.5	-159.7	70.3	7.0	26180
  (5,2)	173.8	-164.1	57.2	22.0	143950
  (3,5)	172.3	-162.7	56.9	57.0	49135
  (5,5)	169.0	-158.4	59.1	43.0	49737
  (4,5)	168.1	-158.6	55.7	65.0	62787

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F210M visit 1: worst tile 30.7 mas at cell (4,0) (> 15 mas)

  36/36 tiles are reported "ok", but that counts tiles whose offset histogram had a coherent PEAK — not tiles within tolerance. The m7 cross-band gate is no significant 2" cell above 15 mas, and this cell exceeds it, so the bulk tie being ~0 does not mean the field is flat.

  checkpoint_m2_F210M_latest.json

  what is affected, and why

  20/36 cells exceed 15 mas. They are not confined to the edge, so this is an interior residual: a distortion or per-detector alignment problem, not a coverage artefact. The bulk tie for this visit is 0.38 mas — a small bulk value cannot cancel a local one.

  Diagnostic writeupD3 — absolute tie to the reference frame · full diagnostic writeup (PDF)

  cell	off (mas)	dRA	dDec	contrast	pairs
  (4,0)	30.7	14.4	-27.2	8.0	31720
  (1,2)	30.3	28.1	-11.1	11.0	25554
  (2,1)	27.7	-27.2	-5.3	8.2	309892
  (0,3)	25.5	18.4	17.6	9.3	224328
  (5,0)	24.6	-23.1	8.4	8.5	129098
  (3,1)	22.3	-12.1	18.7	11.0	326537
  (1,1)	21.9	-17.8	-12.7	7.6	366859
  (3,3)	21.3	13.9	-16.2	7.0	242379
  (0,4)	19.6	16.2	10.9	7.7	218466
  (1,5)	19.0	16.2	-9.9	10.0	280543
  (5,3)	18.5	-15.4	-10.3	9.5	132554
  (3,2)	17.5	-10.9	-13.7	9.7	245911
  (5,4)	17.5	12.9	-11.8	9.7	190758
  (0,5)	17.3	-2.2	-17.2	10.0	155540
  (5,1)	17.0	-14.6	8.8	8.5	108498
  (0,2)	16.5	-15.1	6.8	8.7	251882
  (1,3)	16.3	-11.0	12.0	13.0	35326
  (5,5)	16.2	13.2	-9.3	11.0	191710
  (2,5)	15.5	7.5	13.6	11.0	225997
  (4,5)	15.2	-8.7	12.5	8.3	237555

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F210M_o002 visit 1: worst tile 6235.0 mas at cell (5,0) (> 15 mas)

  36/36 tiles are reported "ok", but that counts tiles whose offset histogram had a coherent PEAK — not tiles within tolerance. The m7 cross-band gate is no significant 2" cell above 15 mas, and this cell exceeds it, so the bulk tie being ~0 does not mean the field is flat.

  checkpoint_m2_F210M_o002_latest.json

  what is affected, and why

  23/36 cells exceed 15 mas. They are not confined to the edge, so this is an interior residual: a distortion or per-detector alignment problem, not a coverage artefact. The bulk tie for this visit is 0.21 mas — a small bulk value cannot cancel a local one.

  Diagnostic writeupD3 — absolute tie to the reference frame · full diagnostic writeup (PDF)

  cell	off (mas)	dRA	dDec	contrast	pairs
  (5,0)	6,235.0	-5,237.6	-3,382.7	8.0	85793
  (4,0)	32.0	13.6	-29.0	8.0	31652
  (2,0)	27.8	26.2	9.3	9.0	36805
  (2,1)	27.4	-26.9	-5.1	8.2	309693
  (0,3)	24.8	17.9	17.1	9.7	225194
  (0,1)	22.8	18.5	-13.4	8.2	347994
  (1,1)	22.4	-18.4	-12.9	7.6	366368
  (3,1)	22.3	-12.6	18.5	10.8	326247
  (3,3)	21.1	13.9	-15.9	7.0	242300
  (5,1)	20.4	14.4	14.5	15.0	84035
  (1,5)	19.9	17.6	-9.2	9.8	280420
  (0,4)	19.5	16.5	10.5	7.7	218348
  (0,2)	19.0	-17.5	7.6	9.0	251019
  (5,5)	17.8	14.0	-10.9	9.0	179593
  (3,5)	17.3	11.9	-12.6	9.3	210106
  (3,2)	17.1	-10.9	-13.1	9.3	245802
  (0,5)	16.9	-2.0	-16.8	10.0	155540
  (5,3)	16.8	14.8	7.9	8.5	106434
  (4,3)	16.8	8.4	14.5	9.0	173422
  (2,5)	16.7	8.8	14.2	10.7	225936
  (5,4)	16.4	10.4	-12.7	12.0	162374
  (5,2)	16.4	14.4	-7.7	10.0	56280
  (1,3)	15.8	-11.0	11.3	11.0	35341

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F360M visit 1: worst tile 27937.9 mas at cell (4,5) (> 15 mas)

  20/20 tiles are reported "ok", but that counts tiles whose offset histogram had a coherent PEAK — not tiles within tolerance. The m7 cross-band gate is no significant 2" cell above 15 mas, and this cell exceeds it, so the bulk tie being ~0 does not mean the field is flat.

  checkpoint_m2_F360M_latest.json

  what is affected, and why

  15/20 cells exceed 15 mas. They are not confined to the edge, so this is an interior residual: a distortion or per-detector alignment problem, not a coverage artefact. The bulk tie for this visit is 0.41 mas — a small bulk value cannot cancel a local one.

  Diagnostic writeupD3 — absolute tie to the reference frame · full diagnostic writeup (PDF)

  cell	off (mas)	dRA	dDec	contrast	pairs
  (4,5)	27,937.9	-13,430.4	24,498.0	7.0	78518
  (0,5)	18,885.8	-18,518.5	3,706.6	6.0	31273
  (1,2)	7,541.5	-1,725.0	-7,341.6	8.0	63767
  (1,4)	7,539.6	-1,728.3	-7,338.8	12.5	160949
  (0,1)	7,531.7	-1,753.6	-7,324.7	6.0	26733
  (1,3)	7,526.1	-1,733.0	-7,323.9	13.5	155185
  (0,3)	7,524.7	-1,749.2	-7,318.5	24.0	265647
  (0,2)	7,520.4	-1,752.4	-7,313.4	25.7	221434
  (0,4)	7,517.2	-1,747.9	-7,311.2	41.0	238406
  (5,0)	22.8	-16.3	15.9	30.3	249465
  (4,4)	21.6	-18.0	11.9	10.0	16363
  (4,3)	20.9	15.5	14.0	13.0	18617
  (5,1)	20.7	-15.4	13.8	28.0	319779
  (4,1)	16.9	-9.5	14.0	18.0	43230
  (5,5)	16.0	14.4	-7.1	30.5	290222

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F360M_o002 visit 1: worst tile 48.3 mas at cell (5,0) (> 15 mas)

  36/36 tiles are reported "ok", but that counts tiles whose offset histogram had a coherent PEAK — not tiles within tolerance. The m7 cross-band gate is no significant 2" cell above 15 mas, and this cell exceeds it, so the bulk tie being ~0 does not mean the field is flat.

  checkpoint_m2_F360M_o002_latest.json

  what is affected, and why

  30/36 cells exceed 15 mas. They are not confined to the edge, so this is an interior residual: a distortion or per-detector alignment problem, not a coverage artefact. The bulk tie for this visit is 0.31 mas — a small bulk value cannot cancel a local one.

  Diagnostic writeupD3 — absolute tie to the reference frame · full diagnostic writeup (PDF)

  cell	off (mas)	dRA	dDec	contrast	pairs
  (5,0)	48.3	-43.5	20.9	9.0	28903
  (5,1)	42.4	-36.8	21.2	11.0	37876
  (5,3)	40.9	-38.0	15.2	16.0	37133
  (5,2)	38.1	-37.7	5.6	8.0	27460
  (3,1)	27.9	18.8	20.7	31.0	70942
  (0,1)	26.7	23.8	-12.1	30.0	64739
  (5,4)	26.3	16.3	-20.7	16.0	57618
  (0,3)	24.7	15.3	19.5	25.0	33557
  (0,5)	24.7	22.3	-10.6	13.0	25480
  (2,1)	24.1	23.1	-6.9	21.0	65404
  (1,1)	23.4	-22.2	-7.5	25.0	68431
  (3,0)	23.2	-17.6	-15.1	22.0	58461
  (2,0)	22.5	16.3	15.4	14.0	52123
  (1,5)	22.4	20.8	-8.4	33.0	55998
  (1,3)	22.2	-15.1	16.3	49.0	68383
  (4,0)	22.1	-16.8	-14.4	17.0	47759
  (5,5)	20.7	-20.7	-1.6	19.0	52071
  (4,4)	20.3	18.6	8.1	25.0	56830
  (2,4)	18.4	-11.7	-14.2	28.0	65018
  (3,3)	18.2	13.5	-12.2	20.0	58068
  (0,2)	17.8	-16.9	5.4	24.0	53543
  (0,0)	17.7	14.4	10.3	12.0	48081
  (4,2)	17.4	-9.0	-15.0	24.0	50142
  (2,5)	17.2	-13.7	10.5	25.0	56626
  (1,4)	17.0	12.7	-11.2	46.0	80745
  (4,1)	16.9	-14.7	8.2	24.0	63161
  (3,2)	16.4	-6.5	-15.0	23.0	56708
  (3,5)	16.0	12.1	-10.4	23.0	56763
  (0,4)	16.0	-15.5	-4.0	15.0	35428
  (4,5)	15.9	10.7	-11.7	24.0	54478

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F480M visit 1: worst tile 157.1 mas at cell (4,0) (> 15 mas)

  16/16 tiles are reported "ok", but that counts tiles whose offset histogram had a coherent PEAK — not tiles within tolerance. The m7 cross-band gate is no significant 2" cell above 15 mas, and this cell exceeds it, so the bulk tie being ~0 does not mean the field is flat.

  checkpoint_m2_F480M_latest.json

  what is affected, and why

  8/16 cells exceed 15 mas. They are not confined to the edge, so this is an interior residual: a distortion or per-detector alignment problem, not a coverage artefact. The bulk tie for this visit is 20.69 mas — a small bulk value cannot cancel a local one.

  Diagnostic writeupD3 — absolute tie to the reference frame · full diagnostic writeup (PDF)

  cell	off (mas)	dRA	dDec	contrast	pairs
  (4,0)	157.1	-151.3	42.3	43.0	39015
  (5,0)	156.5	-149.2	47.2	129.0	47731
  (5,1)	156.0	-148.2	48.9	92.0	38127
  (5,2)	154.3	-146.7	47.9	70.0	125477
  (4,2)	154.0	-139.7	64.8	18.0	61638
  (4,1)	153.5	-147.4	42.7	30.0	30369
  (1,1)	16.5	-7.0	-14.9	12.0	82743
  (1,2)	15.8	-12.6	-9.5	29.0	39805

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• warn
  F480M_o002 visit 1: worst tile 80.1 mas at cell (5,2) (> 15 mas)

  36/36 tiles are reported "ok", but that counts tiles whose offset histogram had a coherent PEAK — not tiles within tolerance. The m7 cross-band gate is no significant 2" cell above 15 mas, and this cell exceeds it, so the bulk tie being ~0 does not mean the field is flat.

  checkpoint_m2_F480M_o002_latest.json

  what is affected, and why

  8/36 cells exceed 15 mas. They are not confined to the edge, so this is an interior residual: a distortion or per-detector alignment problem, not a coverage artefact. The bulk tie for this visit is 0.24 mas — a small bulk value cannot cancel a local one.

  Diagnostic writeupD3 — absolute tie to the reference frame · full diagnostic writeup (PDF)

  cell	off (mas)	dRA	dDec	contrast	pairs
  (5,2)	80.1	-75.9	25.4	17.0	23850
  (5,0)	58.2	-54.8	19.5	19.0	29416
  (5,1)	44.2	-40.8	16.8	24.0	32210
  (5,3)	24.7	-23.1	8.6	26.0	34840
  (4,0)	18.8	-12.5	-14.1	49.0	66416
  (5,5)	18.8	16.2	-9.5	49.0	47668
  (1,3)	18.4	-11.4	14.4	79.0	78098
  (2,5)	15.6	14.9	-4.4	48.0	55585

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
• ok
  m7 present (3 file(s))

  catalogs/
• ok
  m8 present (3 file(s))

  catalogs/
• ok
  m7: single tag 2026-08-26_PR551_59643d9-dirty (15 products)

  catalogs/*m7*.prov.json