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 2045/o001.

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
  m7: products come from 2 different pipeline tags

  2026-08-22_PR468 (6), 2026-08-27_PR574_3bdf55f-dirty (3). Image and catalog must be deployed from the SAME pipeline run; a mixed-tag set is not releasable as one product.

  catalogs/*m7*.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-22_PR468	6
  2026-08-27_PR574_3bdf55f-dirty	3

• fail
  m8: products come from 3 different pipeline tags

  2026-08-23_PR508_87d7fbd-dirty (6), 2026-08-22_PR468 (2), 2026-08-27_PR574_3bdf55f-dirty (1). 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-23_PR508_87d7fbd-dirty	6
  2026-08-22_PR468	2
  2026-08-27_PR574_3bdf55f-dirty	1

• fail
  F212N_o001: 37/88 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_F212N_o001_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

  nrca17/11

  nrca47/11

  nrcb26/11

  nrcb15/11

  nrcb35/11

  nrca33/11

  nrca22/11

  nrcb42/11

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrca1	3.0	-0.3	3.1	802.0	369088	3.0
  1	nrca1	3.3	0.4	3.3	797.0	369441	3.0
  1	nrca1	1.4	1.5	2.1	1,017.8	365980	3.0
  1	nrca1	-3.3	-0.0	3.3	566.6	356396	3.0
  1	nrca1	-3.5	1.4	3.8	1,061.0	355832	3.0
  1	nrca1	3.1	-0.5	3.2	906.2	370593	3.0
  1	nrca1	-0.2	-3.3	3.3	670.8	372242	3.0
  1	nrca2	3.6	1.6	3.9	883.4	511029	3.0
  1	nrca2	-1.3	2.0	2.4	862.9	511254	3.0
  1	nrca3	3.0	1.4	3.3	1,105.2	402128	3.0
  1	nrca3	-1.7	2.2	2.8	1,110.6	389610	3.0
  1	nrca3	-1.8	1.3	2.2	1,096.2	402957	3.0
  1	nrca4	2.4	0.2	2.4	550.0	579873	3.0
  1	nrca4	2.7	0.8	2.9	747.4	575430	3.0
  1	nrca4	0.5	2.3	2.3	686.8	581075	3.0
  1	nrca4	-3.9	0.4	3.9	607.4	563706	3.0
  1	nrca4	2.1	-0.2	2.1	545.5	569186	3.0
  1	nrca4	2.4	-1.8	3.0	833.0	576109	3.0
  1	nrca4	-1.1	-3.0	3.2	775.8	572159	3.0
  1	nrcb1	2.4	-0.7	2.5	1,088.0	334833	3.0
  1	nrcb1	3.0	-0.1	3.0	534.6	337692	3.0
  1	nrcb1	-3.7	-0.3	3.7	678.4	336211	3.0
  1	nrcb1	1.8	-1.0	2.1	928.2	349924	3.0
  1	nrcb1	2.0	-2.4	3.2	1,013.2	351747	3.0
  1	nrcb2	2.6	0.2	2.6	616.4	341831	3.0
  1	nrcb2	3.2	0.9	3.3	931.8	347442	3.0
  1	nrcb2	0.2	2.0	2.0	613.6	345082	3.0
  1	nrcb2	-3.5	0.5	3.5	863.0	361777	3.0
  1	nrcb2	2.2	-1.7	2.8	1,030.6	354100	3.0
  1	nrcb2	-1.1	-2.9	3.1	951.2	353079	3.0
  1	nrcb3	2.2	0.9	2.4	870.2	444349	3.0
  1	nrcb3	-0.6	2.4	2.4	786.5	447004	3.0
  1	nrcb3	-2.3	-0.6	2.3	759.2	421259	3.0
  1	nrcb3	1.6	-1.5	2.2	902.3	433296	3.0
  1	nrcb3	-1.8	-2.8	3.3	937.8	431434	3.0
  1	nrcb4	-1.5	1.9	2.4	1,222.2	325355	3.0
  1	nrcb4	-3.3	-0.4	3.4	936.0	304738	3.0

• fail
  F323N_o001: 14/22 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_F323N_o001_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

  nrcalong8/11

  nrcblong6/11

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrcalong	3.6	-1.2	3.8	3,199.0	136846	3.0
  1	nrcalong	4.0	-0.6	4.0	2,714.5	135545	3.0
  1	nrcalong	1.9	0.8	2.0	2,766.5	136090	3.0
  1	nrcalong	-3.0	1.1	3.2	3,117.5	135774	3.0
  1	nrcalong	-2.5	-1.1	2.7	3,128.0	136027	3.0
  1	nrcalong	-2.8	0.3	2.8	2,219.5	135376	3.0
  1	nrcalong	-0.4	-2.1	2.1	2,341.0	136065	3.0
  1	nrcalong	3.7	-1.5	4.0	3,340.5	136331	3.0
  1	nrcblong	2.9	-1.3	3.2	3,231.0	133409	3.0
  1	nrcblong	3.4	-0.7	3.5	2,848.0	133623	3.0
  1	nrcblong	-3.2	-0.9	3.4	3,155.0	135477	3.0
  1	nrcblong	-3.7	0.5	3.7	2,661.5	134356	3.0
  1	nrcblong	-1.0	-1.9	2.1	3,075.5	135088	3.0
  1	nrcblong	2.6	-1.6	3.0	3,360.5	134725	3.0

• warn
  m7: 3 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)
• 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)
• warn
  F212N: 42/88 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_F212N_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

  nrca47/11

  nrcb27/11

  nrca16/11

  nrcb36/11

  nrcb15/11

  nrca24/11

  nrca34/11

  nrcb43/11

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrca1	3.0	-0.5	3.1	893.8	369133	3.0
  1	nrca1	3.3	0.2	3.3	697.8	369487	3.0
  1	nrca1	-3.2	-0.2	3.2	711.2	356250	3.0
  1	nrca1	-3.5	1.2	3.7	1,047.6	355981	3.0
  1	nrca1	3.1	-0.7	3.2	972.2	370489	3.0
  1	nrca1	-0.1	-3.5	3.5	668.8	372165	3.0
  1	nrca2	3.0	1.7	3.5	885.9	510750	3.0
  1	nrca2	-1.9	2.2	2.9	881.7	511442	3.0
  1	nrca2	-2.0	1.4	2.4	880.7	519373	3.0
  1	nrca2	1.2	-3.5	3.7	884.3	520443	3.0
  1	nrca3	2.9	1.5	3.3	1,113.4	402132	3.0
  1	nrca3	-1.8	2.4	3.0	1,111.0	389580	3.0
  1	nrca3	-1.9	1.4	2.3	1,108.2	403021	3.0
  1	nrca3	1.3	-3.7	3.9	918.8	413546	3.0
  1	nrca4	2.4	0.2	2.4	569.9	580056	3.0
  1	nrca4	2.8	0.8	2.9	754.2	575472	3.0
  1	nrca4	0.5	2.3	2.4	692.8	581231	3.0
  1	nrca4	-3.8	0.4	3.9	622.1	563541	3.0
  1	nrca4	2.1	-0.2	2.1	530.4	569395	3.0
  1	nrca4	2.4	-1.7	3.0	833.0	576146	3.0
  1	nrca4	-1.1	-3.0	3.2	774.6	572158	3.0
  1	nrcb1	2.4	-0.6	2.5	1,063.5	334788	3.0
  1	nrcb1	3.0	0.1	3.0	542.0	337627	3.0
  1	nrcb1	-3.7	-0.2	3.7	644.0	336130	3.0
  1	nrcb1	1.9	-0.9	2.1	918.0	349896	3.0
  1	nrcb1	2.0	-2.4	3.2	1,012.8	351662	3.0
  1	nrcb2	2.6	0.2	2.6	643.2	341756	3.0
  1	nrcb2	3.2	0.9	3.3	936.8	347290	3.0
  1	nrcb2	0.2	2.1	2.1	630.2	345125	3.0
  1	nrcb2	-3.4	0.6	3.5	872.6	361705	3.0
  1	nrcb2	2.0	-0.1	2.0	611.6	355189	3.0
  1	nrcb2	2.2	-1.7	2.8	1,030.4	354089	3.0
  1	nrcb2	-1.1	-2.8	3.0	949.0	353065	3.0
  1	nrcb3	2.3	0.1	2.3	563.2	450063	3.0
  1	nrcb3	2.8	0.7	2.9	842.2	444468	3.0
  1	nrcb3	0.1	2.2	2.2	540.0	446920	3.0
  1	nrcb3	-3.8	0.3	3.8	670.0	419032	3.0
  1	nrcb3	2.2	-1.6	2.7	926.7	433348	3.0
  1	nrcb3	-1.1	-2.9	3.1	901.5	431394	3.0
  1	nrcb4	-1.5	1.9	2.4	1,212.2	325299	3.0

  showing 40 of 42

• warn
  F323N: 13/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_F323N_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

  nrcalong7/12

  nrcblong6/12

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrcalong	3.0	-1.4	3.3	3,421.5	139079	3.0
  1	nrcalong	3.3	-0.8	3.3	3,044.5	138499	3.0
  1	nrcalong	-3.7	0.9	3.8	3,178.0	138504	3.0
  1	nrcalong	-3.2	-1.3	3.5	3,415.5	138096	3.0
  1	nrcalong	-3.5	0.1	3.5	1,958.0	138014	3.0
  1	nrcalong	-1.2	-2.3	2.6	3,295.0	138738	3.0
  1	nrcalong	2.9	-1.7	3.4	3,520.0	138374	3.0
  1	nrcblong	2.4	-1.5	2.9	3,409.0	136138	3.0
  1	nrcblong	3.0	-0.8	3.1	3,156.5	136580	3.0
  1	nrcblong	-3.7	-1.1	3.9	3,390.0	137762	3.0
  1	nrcblong	-4.2	0.3	4.2	2,470.0	137394	3.0
  1	nrcblong	-1.5	-2.0	2.5	3,471.5	137757	3.0
  1	nrcblong	2.1	-1.8	2.8	3,475.5	137720	3.0

• warn
  F212N visit 1: worst tile 27.7 mas at cell (3,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_F212N_latest.json

  what is affected, and why

  19/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 3.50 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
  (3,0)	27.7	-21.7	17.2	20.0	296586
  (0,0)	27.0	-11.7	24.3	24.5	174013
  (4,0)	26.0	-23.5	-11.2	16.5	320315
  (3,1)	23.0	-19.1	12.7	15.5	278431
  (5,5)	22.6	16.4	-15.5	17.5	174914
  (3,2)	21.4	-14.6	-15.7	14.7	201536
  (2,0)	20.5	-14.4	14.6	23.0	245968
  (1,4)	20.1	14.6	-13.8	20.0	201271
  (5,4)	19.0	-11.1	-15.3	19.7	233452
  (0,5)	18.8	11.3	-15.0	14.7	213972
  (2,3)	18.7	14.3	-12.0	18.5	135340
  (5,2)	17.5	-12.6	-12.1	13.7	203535
  (0,2)	16.7	11.4	-12.3	16.0	114619
  (2,4)	16.2	10.4	12.4	13.7	219027
  (0,4)	16.0	10.4	-12.2	21.0	16680
  (5,3)	15.4	-7.6	-13.4	16.5	140438
  (1,2)	15.1	6.1	-13.8	17.5	139852
  (3,5)	15.1	-7.4	-13.1	25.5	161795
  (4,2)	15.0	-10.8	-10.4	15.3	229529

• warn
  F212N_o001 visit 1: worst tile 27.2 mas at cell (0,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_F212N_o001_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.17 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,0)	27.2	-8.7	25.7	24.0	174098
  (3,0)	25.7	-19.3	17.0	22.0	296768
  (4,0)	24.2	-21.8	-10.4	15.2	320297
  (3,1)	21.9	-17.2	13.7	16.0	278320
  (2,3)	20.9	16.0	-13.4	18.5	135329
  (1,4)	20.6	16.6	-12.1	21.0	201277
  (5,5)	20.2	14.2	-14.3	19.0	174810
  (0,5)	20.1	14.2	-14.3	15.0	214063
  (2,0)	19.5	-11.7	15.6	22.7	246040
  (3,2)	19.4	-12.6	-14.7	13.7	201415
  (2,4)	18.9	13.0	13.8	14.7	218987
  (5,3)	18.7	8.0	-16.8	16.0	140442
  (1,1)	17.3	12.6	11.9	15.2	273819
  (3,4)	17.3	13.8	10.3	20.7	222550
  (0,2)	17.2	13.2	-11.0	16.5	114540
  (1,5)	16.9	13.8	9.7	15.3	191202
  (5,4)	16.7	-8.5	-14.3	19.0	233436
  (1,2)	16.1	-9.5	-13.0	16.5	139938
  (5,2)	16.1	-10.2	-12.4	12.0	203539
  (3,3)	16.0	9.4	13.0	16.0	97619
  (3,5)	15.9	6.8	-14.4	25.0	161981
  (2,5)	15.8	13.9	-7.6	27.0	150080
  (0,4)	15.8	11.5	-10.8	21.0	16687

• warn
  F323N visit 1: worst tile 27.9 mas at cell (3,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_F323N_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 1.87 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
  (3,0)	27.9	-23.9	14.5	71.0	79047
  (4,0)	27.6	-24.2	-13.2	55.0	83588
  (0,0)	27.3	-13.7	23.5	41.0	52106
  (2,0)	23.0	-14.8	17.6	65.0	69658
  (1,0)	22.6	-14.7	17.2	70.0	76100
  (3,1)	21.1	-16.4	13.2	54.0	71189
  (5,0)	20.0	-17.0	-10.6	46.0	68599
  (4,1)	19.4	-17.0	-9.4	67.0	73000
  (5,3)	19.1	9.9	-16.4	33.0	32487
  (1,4)	18.9	15.3	-11.1	57.0	69585
  (1,1)	18.1	-13.0	12.5	53.0	75060
  (5,1)	17.7	-12.4	-12.7	67.0	74768
  (2,2)	17.6	-14.8	9.5	38.0	39937
  (0,1)	17.3	-6.4	16.1	49.0	57702
  (0,4)	17.1	9.8	-14.0	44.0	55351
  (3,4)	17.0	14.0	9.7	53.0	64418
  (5,4)	17.0	9.2	-14.3	47.0	56458
  (0,5)	16.8	12.3	-11.5	37.0	51849
  (3,2)	16.6	13.2	-10.0	37.0	41819
  (0,2)	16.4	-9.1	13.6	24.0	28687
  (2,3)	16.2	11.0	-11.9	33.0	39783
  (1,2)	16.2	-6.2	15.0	30.0	35271
  (5,5)	16.0	13.3	-9.0	31.0	46063

• warn
  F323N_o001 visit 1: worst tile 27.0 mas at cell (3,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_F323N_o001_latest.json

  what is affected, and why

  24/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.46 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
  (3,0)	27.0	-22.3	15.2	67.0	80039
  (0,0)	26.6	-12.5	23.5	41.0	51426
  (4,0)	26.5	-23.3	-12.6	53.0	84716
  (2,0)	22.5	-13.4	18.0	66.0	70302
  (1,0)	21.6	-13.0	17.2	72.0	76104
  (3,1)	20.5	-15.4	13.6	55.0	71276
  (5,3)	20.0	10.0	-17.4	35.0	32413
  (5,0)	19.9	-17.1	-10.0	45.0	68683
  (2,3)	18.5	14.8	-11.1	34.0	39255
  (3,4)	18.3	15.4	9.8	57.0	64580
  (4,1)	18.1	-16.1	-8.2	61.0	72777
  (5,5)	17.9	14.8	-10.1	32.0	45683
  (1,4)	17.9	14.5	-10.5	57.0	69401
  (2,4)	17.9	12.9	12.3	37.0	75956
  (5,4)	17.6	10.4	-14.2	49.0	56329
  (3,2)	17.2	14.4	-9.4	42.0	42257
  (0,4)	17.1	10.7	-13.3	43.0	55389
  (1,2)	16.7	-5.8	15.6	28.0	35257
  (0,1)	16.5	-4.3	16.0	47.0	57528
  (2,2)	16.3	-13.3	9.5	35.0	40134
  (5,1)	16.3	-11.3	-11.7	61.0	74305
  (1,1)	16.0	9.1	13.1	53.0	74866
  (0,5)	15.5	14.4	5.9	39.0	52052
  (1,5)	15.2	12.8	8.2	41.0	51566

• ok
  m7 present (3 file(s))

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

  catalogs/
• ok
  8 recent log(s), no error signatures

  logs/