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 2221/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
  F182M_o002 visit 1: consensus not formed

  The exposures of this visit could not be brought into a common frame, so nothing downstream of m2 is trustworthy for it.

  checkpoint_m2_F182M_o002_latest.json

  what is affected, and why

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

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• fail
  F182M_o002 visit 2: consensus not formed

  The exposures of this visit could not be brought into a common frame, so nothing downstream of m2 is trustworthy for it.

  checkpoint_m2_F182M_o002_latest.json

  what is affected, and why

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

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• fail
  F212N visit 1: consensus not formed

  The exposures of this visit could not be brought into a common frame, so nothing downstream of m2 is trustworthy for it.

  checkpoint_m2_F212N_latest.json

  what is affected, and why

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

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• fail
  F182M_o002: lowest offset-peak contrast 4.50 < 5

  A low peak contrast means the offset histogram found no real tie. It does NOT mean "no offset": a shift larger than the search window has zero true pairs inside it, so a gross misalignment reads as low contrast (the brick-1182 v001 signature).

  checkpoint_m2_F182M_o002_latest.json

  what is affected, and why

  Diagnostic writeupfull diagnostic writeup (PDF)

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• fail
  F212N: lowest offset-peak contrast 4.00 < 5

  A low peak contrast means the offset histogram found no real tie. It does NOT mean "no offset": a shift larger than the search window has zero true pairs inside it, so a gross misalignment reads as low contrast (the brick-1182 v001 signature).

  checkpoint_m2_F212N_latest.json

  what is affected, and why

  Diagnostic writeupfull diagnostic writeup (PDF)

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• fail
  F182M_o002: 38/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_F182M_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

  nrca412/16

  nrca38/16

  nrca16/16

  nrca26/16

  nrcb22/16

  nrcb32/16

  nrcb11/16

  nrcb41/16

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrca1	2.4	0.1	2.4	528.0	370296	3.0
  1	nrca1	2.0	-0.1	2.0	547.8	361673	3.0
  1	nrca1	2.6	0.1	2.6	536.8	364581	3.0
  1	nrca2	2.6	0.4	2.6	919.3	219010	3.0
  1	nrca2	2.9	0.5	3.0	1,000.7	229449	3.0
  1	nrca2	2.5	0.4	2.5	902.0	221909	3.0
  1	nrca2	2.9	0.5	3.0	1,012.0	233615	3.0
  1	nrca3	-3.2	0.1	3.2	612.2	393270	3.0
  1	nrca3	-3.2	0.1	3.2	632.0	393462	3.0
  1	nrca3	-3.3	0.1	3.3	607.4	390999	3.0
  1	nrca3	-3.2	0.2	3.2	640.4	386574	3.0
  1	nrca4	0.0	-2.1	2.1	539.7	426846	3.0
  1	nrca4	0.5	-2.1	2.1	842.0	424081	3.0
  1	nrca4	0.1	-2.1	2.1	593.0	413944	3.0
  1	nrca4	0.4	-2.0	2.1	780.8	412431	3.0
  1	nrca4	-2.7	-0.5	2.7	826.0	261112	3.0
  1	nrca4	-2.6	-0.4	2.6	787.2	266161	3.0
  1	nrca4	-2.8	-0.6	2.9	885.0	262286	3.0
  1	nrca4	-2.8	-0.6	2.9	851.0	270148	3.0
  2	nrca1	1.0	-1.8	2.1	823.6	356199	3.0
  2	nrca1	1.1	-2.2	2.4	845.2	360670	3.0
  2	nrca1	0.8	-2.2	2.3	826.6	359544	3.0
  2	nrca2	0.7	-2.1	2.2	776.3	409802	3.0
  2	nrca2	0.8	-2.3	2.5	803.0	416587	3.0
  2	nrca3	-1.2	2.5	2.8	924.4	374890	3.0
  2	nrca3	-1.1	2.7	2.9	951.6	372800	3.0
  2	nrca3	-1.3	2.7	3.0	975.8	386502	3.0
  2	nrca3	-1.2	2.3	2.6	965.8	378391	3.0
  2	nrca4	-1.0	2.3	2.5	819.7	430034	3.0
  2	nrca4	-0.9	2.7	2.8	790.3	420748	3.0
  2	nrca4	-1.1	2.8	3.0	870.5	445166	3.0
  2	nrca4	-1.1	2.3	2.6	824.8	435453	3.0
  2	nrcb1	2.1	0.8	2.2	952.8	290037	3.0
  2	nrcb2	2.0	1.2	2.3	807.5	428483	3.0
  2	nrcb2	1.4	1.5	2.1	833.7	439917	3.0
  2	nrcb3	-2.9	-0.4	2.9	767.2	297992	3.0
  2	nrcb3	-2.0	0.0	2.0	617.0	278373	3.0
  2	nrcb4	-2.4	-0.8	2.5	756.0	451879	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• fail
  F187N_o002: 29/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_F187N_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

  nrcb25/16

  nrca14/16

  nrca24/16

  nrca34/16

  nrca44/16

  nrcb14/16

  nrcb32/16

  nrcb42/16

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  2	nrca1	1.2	-2.4	2.7	786.0	9692	3.0
  2	nrca1	1.3	-2.7	3.0	813.0	9883	3.0
  2	nrca1	1.1	-2.9	3.1	825.0	10368	3.0
  2	nrca1	0.7	-2.3	2.5	752.0	10423	3.0
  2	nrca2	0.7	-2.3	2.4	990.0	13989	3.0
  2	nrca2	0.7	-2.4	2.5	942.0	13682	3.0
  2	nrca2	0.8	-2.8	2.9	1,013.0	14648	3.0
  2	nrca2	0.2	-2.2	2.2	732.0	14752	3.0
  2	nrca3	-0.8	3.5	3.6	732.0	10182	3.0
  2	nrca3	-0.6	3.7	3.8	755.0	10643	3.0
  2	nrca3	-0.8	3.6	3.7	744.0	10757	3.0
  2	nrca3	-0.6	3.3	3.4	728.0	10812	3.0
  2	nrca4	-0.6	3.6	3.6	981.0	15119	3.0
  2	nrca4	-0.5	3.9	4.0	916.0	14678	3.0
  2	nrca4	-0.6	4.0	4.1	1,035.0	16234	3.0
  2	nrca4	-0.6	3.6	3.7	922.0	15401	3.0
  2	nrcb1	-0.6	2.9	3.0	779.0	10751	3.0
  2	nrcb1	-0.6	4.0	4.1	763.0	10240	3.0
  2	nrcb1	-0.9	3.8	3.9	880.0	11006	3.0
  2	nrcb1	0.1	3.1	3.1	545.0	10185	3.0
  2	nrcb2	-2.0	0.8	2.2	974.0	15768	3.0
  2	nrcb2	-0.9	3.3	3.4	1,075.0	20287	3.0
  2	nrcb2	-1.1	4.7	4.8	1,209.0	20401	3.0
  2	nrcb2	-1.2	4.2	4.4	1,161.0	19625	3.0
  2	nrcb2	-0.2	3.7	3.7	758.0	19946	3.0
  2	nrcb3	0.9	-2.2	2.4	945.0	11357	3.0
  2	nrcb3	1.3	-2.1	2.4	972.0	11214	3.0
  2	nrcb4	1.2	-2.8	3.0	1,236.0	20716	3.0
  2	nrcb4	1.4	-2.5	2.9	1,254.0	20109	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• fail
  F212N_o002: 28/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_F212N_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

  nrca46/16

  nrca35/16

  nrcb34/16

  nrca13/16

  nrca23/16

  nrcb23/16

  nrcb12/16

  nrcb42/16

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  2	nrca1	0.5	-2.1	2.2	833.0	18497	3.0
  2	nrca1	-0.2	2.1	2.1	1,361.0	37717	3.0
  2	nrca1	-0.3	2.2	2.3	1,494.0	37630	3.0
  2	nrca2	0.4	-4.5	4.5	1,080.0	23214	3.0
  2	nrca2	-0.3	2.2	2.3	1,402.0	33748	3.0
  2	nrca2	-0.4	2.2	2.3	1,493.0	33447	3.0
  2	nrca3	-0.9	3.2	3.3	934.0	12300	3.0
  2	nrca3	-1.3	3.2	3.5	975.0	11991	3.0
  2	nrca3	-0.8	3.1	3.2	882.0	11913	3.0
  2	nrca3	-1.2	3.3	3.5	1,125.0	19127	3.0
  2	nrca3	-1.0	3.4	3.6	1,147.0	19741	3.0
  2	nrca4	-1.5	1.9	2.4	1,263.0	18187	3.0
  2	nrca4	-1.8	2.0	2.7	1,297.0	17976	3.0
  2	nrca4	-1.4	1.9	2.3	1,247.0	17687	3.0
  2	nrca4	-1.1	-2.1	2.4	996.0	17213	3.0
  2	nrca4	0.8	-2.1	2.2	1,291.0	24245	3.0
  2	nrca4	0.8	-2.1	2.2	1,369.0	25671	3.0
  2	nrcb1	-0.6	3.9	4.0	1,057.0	18829	3.0
  2	nrcb1	0.3	4.0	4.0	849.0	17192	3.0
  2	nrcb2	-2.0	0.8	2.2	1,521.0	30179	3.0
  2	nrcb2	-0.5	4.0	4.0	1,211.0	32329	3.0
  2	nrcb2	0.4	4.3	4.3	1,104.0	32558	3.0
  2	nrcb3	1.1	-2.1	2.4	1,242.0	19887	3.0
  2	nrcb3	1.3	-2.0	2.4	1,274.0	19385	3.0
  2	nrcb3	1.0	-2.3	2.5	1,135.0	16860	3.0
  2	nrcb3	1.1	-2.5	2.8	1,178.0	18109	3.0
  2	nrcb4	1.5	-2.3	2.7	1,564.0	33538	3.0
  2	nrcb4	1.6	-2.1	2.6	1,575.0	32759	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• fail
  F405N_o002: 1/32 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_F405N_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

  nrcalong1/16

  nrcblong0/16

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  2	nrcalong	-3.9	-1.1	4.0	3,421.0	45573	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• fail
  F410M_o002: 26/32 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_F410M_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

  nrcblong16/16

  nrcalong10/16

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrcalong	4.6	4.0	6.1	4,202.5	171343	3.0
  1	nrcalong	4.3	4.1	6.0	4,216.5	171965	3.0
  1	nrcblong	-4.6	-0.0	4.6	2,171.5	166330	3.0
  1	nrcblong	-4.6	-0.0	4.6	2,158.0	167061	3.0
  1	nrcblong	-4.6	-0.0	4.6	2,193.0	168902	3.0
  1	nrcblong	-4.6	-0.0	4.6	2,168.0	169208	3.0
  1	nrcblong	-0.5	3.6	3.6	3,045.5	168127	3.0
  1	nrcblong	-0.1	3.6	3.6	2,323.0	166348	3.0
  1	nrcblong	0.1	3.5	3.5	2,346.0	168346	3.0
  1	nrcblong	0.5	3.7	3.7	3,178.0	166404	3.0
  2	nrcalong	-2.1	-2.6	3.3	4,076.5	175211	3.0
  2	nrcalong	-2.0	-2.7	3.4	4,109.5	177711	3.0
  2	nrcalong	-2.1	-2.6	3.3	4,095.0	175040	3.0
  2	nrcalong	-2.4	-2.4	3.4	4,132.5	175739	3.0
  2	nrcalong	-4.5	1.7	4.8	3,862.0	155641	3.0
  2	nrcalong	-4.5	1.9	4.9	3,928.0	155765	3.0
  2	nrcalong	-4.6	1.9	5.0	3,898.0	153779	3.0
  2	nrcalong	-4.6	1.9	5.0	3,870.0	152361	3.0
  2	nrcblong	2.9	-1.8	3.4	4,059.0	167609	3.0
  2	nrcblong	2.9	-1.9	3.5	4,103.0	169121	3.0
  2	nrcblong	2.9	-1.8	3.4	4,126.5	169910	3.0
  2	nrcblong	2.6	-1.7	3.1	4,042.5	170005	3.0
  2	nrcblong	2.1	1.8	2.8	4,053.0	178322	3.0
  2	nrcblong	2.1	2.0	2.9	4,072.0	176207	3.0
  2	nrcblong	2.0	2.1	2.9	4,047.0	177266	3.0
  2	nrcblong	2.1	2.0	2.9	4,054.0	176802	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• fail
  F466N_o002: 5/32 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_F466N_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

  nrcalong4/16

  nrcblong1/16

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  2	nrcalong	-2.8	-0.3	2.8	1,684.0	22761	3.0
  2	nrcalong	-2.6	-1.0	2.8	2,150.0	22601	3.0
  2	nrcalong	-2.7	-0.8	2.8	2,061.0	22882	3.0
  2	nrcalong	-3.8	-0.7	3.8	2,002.0	22582	3.0
  2	nrcblong	3.2	2.0	3.8	3,273.0	35625	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  m7: 21 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
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  m8: 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/*m8*.prov.json

  what is affected, and why

  Diagnostic writeupfull diagnostic writeup (PDF)

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F182M: 49/128 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_F182M_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

  nrca28/16

  nrca38/16

  nrca16/16

  nrca46/16

  nrcb36/16

  nrcb46/16

  nrcb15/16

  nrcb24/16

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  1	nrca1	2.7	-0.1	2.7	577.8	350640	3.0
  1	nrca1	3.2	0.0	3.2	552.0	354941	3.0
  1	nrca1	2.6	-0.1	2.6	570.6	347812	3.0
  1	nrca1	3.2	0.0	3.2	548.4	349698	3.0
  1	nrca2	3.2	0.4	3.2	997.3	206380	3.0
  1	nrca2	3.6	0.6	3.7	1,081.3	215397	3.0
  1	nrca2	3.1	0.4	3.2	987.0	208909	3.0
  1	nrca2	3.6	0.6	3.7	1,102.7	219800	3.0
  1	nrca3	-2.2	0.1	2.2	615.0	377980	3.0
  1	nrca3	-2.2	0.1	2.2	637.4	377294	3.0
  1	nrca3	-2.3	0.1	2.3	623.6	376466	3.0
  1	nrca3	-2.2	0.1	2.2	644.0	370278	3.0
  1	nrca4	-2.1	-0.5	2.1	1,169.3	248402	3.0
  1	nrca4	-2.0	-0.5	2.1	1,092.0	255618	3.0
  2	nrca1	0.9	-2.0	2.2	838.6	344126	3.0
  2	nrca1	0.7	-2.1	2.2	827.6	345591	3.0
  2	nrca2	0.6	-2.0	2.1	929.2	386063	3.0
  2	nrca2	0.7	-2.5	2.6	977.4	391629	3.0
  2	nrca2	0.7	-2.7	2.8	994.8	396563	3.0
  2	nrca2	0.3	-2.1	2.1	802.4	396750	3.0
  2	nrca3	-1.2	2.6	2.9	997.6	359756	3.0
  2	nrca3	-1.1	2.8	3.0	1,015.2	356761	3.0
  2	nrca3	-1.4	2.8	3.1	1,047.4	369087	3.0
  2	nrca3	-1.2	2.3	2.7	1,028.8	360841	3.0
  2	nrca4	-1.0	2.1	2.3	860.5	408352	3.0
  2	nrca4	-0.9	2.4	2.6	1,004.8	400015	3.0
  2	nrca4	-1.1	2.5	2.7	911.2	423675	3.0
  2	nrca4	-1.1	2.1	2.3	872.2	415255	3.0
  2	nrcb1	-1.7	1.1	2.0	1,236.5	297094	3.0
  2	nrcb1	-2.9	0.6	2.9	1,100.5	284756	3.0
  2	nrcb1	3.5	1.4	3.7	1,147.0	281785	3.0
  2	nrcb1	-3.1	2.1	3.7	1,171.8	276652	3.0
  2	nrcb1	3.5	1.5	3.8	1,131.8	272193	3.0
  2	nrcb2	-2.5	0.6	2.6	959.6	343722	3.0
  2	nrcb2	4.5	2.0	4.9	916.3	413843	3.0
  2	nrcb2	-2.2	2.7	3.5	926.5	414512	3.0
  2	nrcb2	4.4	2.1	4.9	926.7	419868	3.0
  2	nrcb3	-2.8	-0.4	2.8	896.8	291129	3.0
  2	nrcb3	-1.3	-2.1	2.4	1,178.8	293280	3.0
  2	nrcb3	-0.9	-2.0	2.2	1,105.5	281878	3.0

  showing 40 of 49

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F187N: 30/128 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_F187N_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/16

  nrca24/16

  nrca34/16

  nrca44/16

  nrcb14/16

  nrcb24/16

  nrcb44/16

  nrcb32/16

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  2	nrca1	1.2	-3.1	3.3	763.0	9530	3.0
  2	nrca1	1.3	-3.4	3.7	791.0	9690	3.0
  2	nrca1	1.1	-3.6	3.7	804.0	10088	3.0
  2	nrca1	0.7	-3.0	3.1	720.0	10113	3.0
  2	nrca2	0.8	-2.9	3.0	974.0	13676	3.0
  2	nrca2	0.8	-3.3	3.4	930.0	13263	3.0
  2	nrca2	0.8	-3.5	3.6	1,012.0	14436	3.0
  2	nrca2	0.3	-3.1	3.1	789.0	14361	3.0
  2	nrca3	-0.8	2.5	2.6	697.0	9923	3.0
  2	nrca3	-0.6	2.6	2.7	701.0	10317	3.0
  2	nrca3	-0.8	2.8	2.9	708.0	10481	3.0
  2	nrca3	-0.6	2.4	2.4	696.0	10520	3.0
  2	nrca4	-0.5	2.7	2.7	904.0	14637	3.0
  2	nrca4	-0.4	2.9	2.9	830.0	14239	3.0
  2	nrca4	-0.5	2.9	3.0	953.0	15781	3.0
  2	nrca4	-0.5	2.5	2.6	844.0	15039	3.0
  2	nrcb1	-0.4	2.4	2.4	653.0	10292	3.0
  2	nrcb1	-0.4	3.5	3.5	653.0	9889	3.0
  2	nrcb1	-0.7	3.4	3.5	795.0	10597	3.0
  2	nrcb1	0.3	2.7	2.7	630.0	9863	3.0
  2	nrcb2	2.1	-0.6	2.2	910.0	15101	3.0
  2	nrcb2	-0.8	3.0	3.1	1,034.0	19865	3.0
  2	nrcb2	-0.9	2.5	2.7	1,006.0	19196	3.0
  2	nrcb2	0.2	2.1	2.1	710.0	19261	3.0
  2	nrcb3	1.1	-2.5	2.7	932.0	11022	3.0
  2	nrcb3	1.5	-2.3	2.7	937.0	10837	3.0
  2	nrcb4	0.4	-3.0	3.0	839.0	19840	3.0
  2	nrcb4	1.5	-4.2	4.4	1,226.0	20085	3.0
  2	nrcb4	1.6	-3.9	4.2	1,229.0	19649	3.0
  2	nrcb4	-0.7	-3.1	3.2	1,068.0	20274	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F212N: 39/128 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

  nrca48/16

  nrcb38/16

  nrca14/16

  nrca24/16

  nrcb14/16

  nrcb24/16

  nrcb44/16

  nrca33/16

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  2	nrca1	1.1	-3.3	3.5	1,007.0	17447	3.0
  2	nrca1	1.3	-3.9	4.1	1,028.0	17398	3.0
  2	nrca1	1.0	-4.1	4.2	1,077.0	18004	3.0
  2	nrca1	0.8	-3.5	3.6	946.0	17869	3.0
  2	nrca2	0.5	-3.4	3.5	1,101.0	21806	3.0
  2	nrca2	0.7	-3.8	3.9	1,208.0	21998	3.0
  2	nrca2	0.6	-3.9	4.0	1,187.0	22186	3.0
  2	nrca2	0.2	-3.4	3.4	872.0	22727	3.0
  2	nrca3	-0.4	2.1	2.1	839.0	18553	3.0
  2	nrca3	-0.6	2.3	2.4	900.0	19009	3.0
  2	nrca3	-0.6	2.0	2.1	907.0	19167	3.0
  2	nrca4	-2.6	0.1	2.6	721.0	17469	3.0
  2	nrca4	-2.5	-0.2	2.5	782.0	17470	3.0
  2	nrca4	-2.6	-0.3	2.6	917.0	16920	3.0
  2	nrca4	-3.0	0.2	3.0	811.0	16496	3.0
  2	nrca4	-0.5	2.6	2.7	1,131.0	23872	3.0
  2	nrca4	-0.1	2.7	2.7	802.0	23336	3.0
  2	nrca4	-0.4	2.8	2.9	1,074.0	24861	3.0
  2	nrca4	-0.3	2.5	2.6	977.0	24261	3.0
  2	nrcb1	-0.5	2.0	2.0	930.0	18233	3.0
  2	nrcb1	-0.3	2.8	2.9	784.0	17238	3.0
  2	nrcb1	-0.7	2.7	2.8	998.0	18100	3.0
  2	nrcb1	0.5	2.2	2.2	891.0	16674	3.0
  2	nrcb2	-0.5	3.0	3.1	1,131.0	31531	3.0
  2	nrcb2	-0.5	4.1	4.1	1,214.0	31773	3.0
  2	nrcb2	-0.6	3.8	3.9	1,234.0	31162	3.0
  2	nrcb2	0.4	3.3	3.3	1,103.0	31712	3.0
  2	nrcb3	0.4	-3.2	3.2	954.0	19289	3.0
  2	nrcb3	1.2	-4.2	4.4	1,227.0	19061	3.0
  2	nrcb3	1.5	-4.1	4.4	1,255.0	18826	3.0
  2	nrcb3	-1.0	-3.3	3.4	1,125.0	18615	3.0
  2	nrcb3	3.0	-0.6	3.1	988.0	16728	3.0
  2	nrcb3	2.8	0.2	2.8	813.0	16252	3.0
  2	nrcb3	2.5	-0.0	2.5	630.0	17479	3.0
  2	nrcb3	3.6	-0.5	3.6	958.0	16995	3.0
  2	nrcb4	0.6	-2.2	2.3	1,172.0	31632	3.0
  2	nrcb4	1.5	-3.2	3.6	1,512.0	32336	3.0
  2	nrcb4	1.6	-3.0	3.4	1,528.0	31653	3.0
  2	nrcb4	-0.7	-2.3	2.4	1,339.0	32711	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F405N: 1/32 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_F405N_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

  nrcalong1/16

  nrcblong0/16

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  2	nrcalong	-3.8	-1.0	4.0	3,265.0	42922	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F410M: 16/32 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_F410M_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/16

  nrcblong8/16

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  2	nrcalong	36.2	-733.6	734.5	4,096.5	181994	3.0
  2	nrcalong	36.5	-734.6	735.5	4,117.0	185373	3.0
  2	nrcalong	36.5	-734.5	735.4	4,132.0	180535	3.0
  2	nrcalong	35.4	-734.0	734.8	4,152.5	180345	3.0
  2	nrcalong	33.5	-729.9	730.7	4,010.5	150023	3.0
  2	nrcalong	33.6	-729.1	729.8	4,043.5	150954	3.0
  2	nrcalong	33.3	-729.0	729.8	4,015.5	147863	3.0
  2	nrcalong	33.4	-729.4	730.2	3,995.0	147100	3.0
  2	nrcblong	-36.2	732.2	733.1	4,227.5	163012	3.0
  2	nrcblong	-34.0	729.0	729.8	4,257.0	164263	3.0
  2	nrcblong	-33.2	729.2	730.0	4,279.5	165739	3.0
  2	nrcblong	-38.9	731.5	732.5	3,825.5	164964	3.0
  2	nrcblong	-36.1	734.8	735.6	2,810.3	187095	3.0
  2	nrcblong	-36.9	736.7	737.7	4,119.5	184737	3.0
  2	nrcblong	-37.5	736.8	737.8	2,701.0	187210	3.0
  2	nrcblong	-35.2	735.1	735.9	2,782.3	187266	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F466N: 5/32 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_F466N_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

  nrcalong4/16

  nrcblong1/16

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

  visit	detector	dRA (mas)	dDec (mas)	off (mas)	contrast	pairs	window ("")
  2	nrcalong	-2.8	-0.3	2.8	1,557.0	20724	3.0
  2	nrcalong	-2.6	-1.0	2.7	1,995.0	20668	3.0
  2	nrcalong	-2.7	-0.8	2.8	1,967.0	20878	3.0
  2	nrcalong	-3.7	-0.7	3.8	1,857.0	20504	3.0
  2	nrcblong	3.2	1.9	3.8	3,103.0	32729	3.0

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F182M_o002: 8 exposure tie(s) needed a swept search window

  measure_offset widens the window (3->10->30->60") when a narrow window finds no peak. A swept tie means the frame is grossly shifted; check that the peak reproduces at an independent window rather than sitting on the window edge.

  checkpoint_m2_F182M_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
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F212N: 4 exposure tie(s) needed a swept search window

  measure_offset widens the window (3->10->30->60") when a narrow window finds no peak. A swept tie means the frame is grossly shifted; check that the peak reproduces at an independent window rather than sitting on the window edge.

  checkpoint_m2_F212N_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
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F410M visit 2: 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_F410M_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
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F182M_o002: 8 exposure(s) could not be verified

  Recorded as could-not-verify: the reference tie was not coherent, or the gross cross-check (100 mas) failed, so no correction was applied.

  checkpoint_m2_F182M_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
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F212N: 4 exposure(s) could not be verified

  Recorded as could-not-verify: the reference tie was not coherent, or the gross cross-check (100 mas) failed, so no correction was applied.

  checkpoint_m2_F212N_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
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F182M visit 1: worst tile 46.9 mas at cell (0,4) (> 15 mas)

  34/34 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_F182M_latest.json

  what is affected, and why

  3/34 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
  (0,4)	46.9	45.6	11.1	10.0	66918
  (5,1)	18.3	14.3	-11.4	7.0	14226
  (3,2)	16.1	13.2	-9.2	40.5	151943

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F182M visit 2: worst tile 23.5 mas at cell (0,4) (> 15 mas)

  34/34 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_F182M_latest.json

  what is affected, and why

  7/34 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.56 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)	23.5	23.1	-4.6	7.0	17046
  (5,1)	22.3	-19.0	11.6	8.0	18134
  (1,0)	21.1	-17.8	-11.4	50.5	165628
  (4,0)	18.0	-15.3	-9.6	28.3	210515
  (1,5)	17.6	17.1	4.3	20.7	253393
  (1,1)	17.5	-17.0	4.4	28.3	232302
  (0,1)	16.2	-15.4	5.2	22.7	205390

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F182M_o002 visit 1: worst tile 17931.6 mas at cell (5,1) (> 15 mas)

  32/32 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_F182M_o002_latest.json

  what is affected, and why

  3/32 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,1)	17,931.6	-11,721.7	13,570.0	8.0	84811
  (3,2)	15.1	11.8	-9.4	37.5	161626
  (0,4)	15.0	-13.7	-6.3	18.0	39291

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F182M_o002 visit 2: worst tile 21272.6 mas at cell (3,0) (> 15 mas)

  34/34 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_F182M_o002_latest.json

  what is affected, and why

  8/34 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.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
  (3,0)	21,272.6	-7,069.2	20,063.7	5.0	28497
  (4,0)	15,642.3	-14,119.7	-6,731.8	6.0	155511
  (5,1)	23.4	-20.3	11.8	8.0	19588
  (0,4)	21.4	21.2	-2.3	6.0	15072
  (1,5)	18.0	17.5	4.3	20.7	249418
  (1,1)	17.3	-16.8	4.0	26.0	228937
  (5,3)	15.9	-11.6	-10.8	23.0	65262
  (0,1)	15.7	-15.3	3.4	22.0	195060

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F187N visit 2: worst tile 56759.7 mas at cell (0,4) (> 15 mas)

  34/34 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_F187N_latest.json

  what is affected, and why

  2/34 cells exceed 15 mas, and every one of them is on the mosaic EDGE — that is usually thin coverage (few exposures, so few pairs per cell) rather than a distortion error. Check the pair counts in the table before treating it as a defect. The bulk tie for this visit is 0.91 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)	56,759.7	8,219.7	56,161.3	9.0	86206
  (0,3)	15.5	-15.1	3.3	29.0	13052

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F187N_o002 visit 2: worst tile 52301.4 mas at cell (0,4) (> 15 mas)

  34/34 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_F187N_o002_latest.json

  what is affected, and why

  2/34 cells exceed 15 mas, and every one of them is on the mosaic EDGE — that is usually thin coverage (few exposures, so few pairs per cell) rather than a distortion error. Check the pair counts in the table before treating it as a defect. The bulk tie for this visit is 0.51 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)	52,301.4	-50,559.4	-13,386.1	8.0	86207
  (0,3)	15.3	-14.9	3.5	29.0	13272

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F212N visit 1: worst tile 16.4 mas at cell (5,1) (> 15 mas)

  32/32 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

  1/32 cells exceed 15 mas, and every one of them is on the mosaic EDGE — that is usually thin coverage (few exposures, so few pairs per cell) rather than a distortion error. Check the pair counts in the table before treating it as a defect. The bulk tie for this visit is 0.48 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,1)	16.4	0.7	-16.4	8.0	25218

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F212N visit 2: worst tile 15.1 mas at cell (3,0) (> 15 mas)

  34/34 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

  1/34 cells exceed 15 mas, and every one of them is on the mosaic EDGE — that is usually thin coverage (few exposures, so few pairs per cell) rather than a distortion error. Check the pair counts in the table before treating it as a defect. The bulk tie for this visit is 0.48 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)	15.1	-7.0	-13.4	101.0	81911

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F212N_o002 visit 2: worst tile 16.7 mas at cell (0,3) (> 15 mas)

  34/34 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_o002_latest.json

  what is affected, and why

  2/34 cells exceed 15 mas, and every one of them is on the mosaic EDGE — that is usually thin coverage (few exposures, so few pairs per cell) rather than a distortion error. Check the pair counts in the table before treating it as a defect. The bulk tie for this visit is 1.06 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,3)	16.7	-15.6	6.0	34.0	16457
  (5,1)	15.3	12.0	-9.5	15.0	59145

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F405N visit 2: worst tile 19.7 mas at cell (1,5) (> 15 mas)

  34/34 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_F405N_latest.json

  what is affected, and why

  6/34 cells exceed 15 mas, and every one of them is on the mosaic EDGE — that is usually thin coverage (few exposures, so few pairs per cell) rather than a distortion error. Check the pair counts in the table before treating it as a defect. The bulk tie for this visit is 1.01 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,5)	19.7	19.1	5.0	77.0	34078
  (0,4)	19.6	19.4	3.2	9.0	25086
  (0,3)	17.0	-15.7	6.6	31.0	13559
  (3,5)	15.3	15.3	-1.1	80.0	47782
  (4,5)	15.3	14.5	-4.9	102.0	45480
  (5,5)	15.1	13.5	-6.8	95.0	44479

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F405N_o002 visit 2: worst tile 19.4 mas at cell (0,4) (> 15 mas)

  34/34 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_F405N_o002_latest.json

  what is affected, and why

  5/34 cells exceed 15 mas, and every one of them is on the mosaic EDGE — that is usually thin coverage (few exposures, so few pairs per cell) rather than a distortion error. Check the pair counts in the table before treating it as a defect. The bulk tie for this visit is 1.01 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)	19.4	19.3	-1.1	11.0	25754
  (1,5)	19.1	18.4	5.1	77.0	34943
  (0,3)	17.2	-16.1	6.2	31.0	13633
  (3,5)	15.3	15.3	-1.1	80.0	48433
  (4,5)	15.3	14.5	-4.9	101.0	45719

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F410M visit 1: worst tile 19.1 mas at cell (5,1) (> 15 mas)

  34/34 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_F410M_latest.json

  what is affected, and why

  5/34 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.63 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,1)	19.1	-2.5	-19.0	6.0	28115
  (0,4)	18.2	-17.1	-6.2	9.0	32888
  (1,0)	17.6	16.2	6.9	64.0	76703
  (3,4)	16.6	13.6	9.5	79.0	89463
  (3,2)	15.8	13.3	-8.4	64.0	68358

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F410M visit 2: worst tile 3329.4 mas at cell (2,2) (> 15 mas)

  32/32 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_F410M_latest.json

  what is affected, and why

  32/32 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 731.47 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
  (2,2)	3,329.4	1,379.2	3,030.3	117.0	88050
  (4,2)	3,329.3	1,380.5	3,029.6	56.0	91137
  (0,2)	3,328.2	1,375.2	3,030.8	47.0	27343
  (1,1)	3,328.2	1,374.7	3,031.0	68.5	90334
  (0,1)	3,328.0	1,372.2	3,031.9	107.0	69865
  (3,1)	3,326.3	1,379.6	3,026.7	69.0	92973
  (0,0)	3,326.1	1,382.8	3,025.0	101.0	70264
  (4,1)	3,326.0	1,375.9	3,028.1	83.0	102209
  (1,2)	3,326.0	1,375.4	3,028.2	94.0	62810
  (2,1)	3,325.5	1,377.1	3,026.9	110.0	68977
  (3,2)	3,325.1	1,380.3	3,025.1	59.0	91116
  (2,0)	3,325.0	1,382.4	3,024.0	94.0	56960
  (5,2)	3,324.1	1,379.9	3,024.2	27.0	20093
  (1,0)	3,323.1	1,370.4	3,027.3	108.0	67763
  (4,0)	3,320.9	1,374.1	3,023.3	100.0	54299
  (3,0)	3,316.8	1,374.9	3,018.4	103.0	83932
  (1,3)	746.9	-39.8	745.9	52.5	90747
  (0,3)	742.2	-52.2	740.4	23.0	21234
  (2,5)	740.9	-31.0	740.3	106.0	88413
  (2,3)	739.0	-38.8	738.0	81.0	64786
  (1,4)	738.9	-31.8	738.3	95.0	84551
  (1,5)	738.9	-28.0	738.4	61.0	46545
  (3,5)	736.0	-29.9	735.4	88.0	79110
  (3,4)	730.5	-36.8	729.5	79.0	71167
  (4,3)	729.8	-38.4	728.7	63.0	60020
  (4,5)	727.9	-29.8	727.3	107.0	73169
  (3,3)	726.3	-36.9	725.3	71.0	63159
  (4,4)	726.0	-37.9	725.0	100.0	68589
  (5,5)	725.7	-30.7	725.0	108.0	69604
  (2,4)	723.6	-33.3	722.9	94.0	81604
  (5,3)	722.7	-39.9	721.6	31.0	20024
  (5,4)	720.8	-37.8	719.8	97.0	60310

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F410M_o002 visit 1: worst tile 19.9 mas at cell (5,1) (> 15 mas)

  34/34 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_F410M_o002_latest.json

  what is affected, and why

  7/34 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.04 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,1)	19.9	-4.0	-19.5	6.0	27356
  (0,4)	19.7	-18.5	-6.7	9.0	32938
  (1,0)	17.5	15.3	8.5	63.0	77361
  (2,2)	15.6	-11.7	-10.3	69.0	75679
  (4,0)	15.5	-9.5	-12.2	40.0	50297
  (3,2)	15.5	12.6	-8.9	60.0	69422
  (3,4)	15.4	12.5	8.9	37.5	91393

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F410M_o002 visit 2: worst tile 20.8 mas at cell (0,3) (> 15 mas)

  34/34 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_F410M_o002_latest.json

  what is affected, and why

  10/34 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.20 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,3)	20.8	-19.1	8.3	31.0	21326
  (0,4)	19.4	18.7	5.3	7.0	3843
  (3,5)	17.6	17.3	-2.9	71.0	78058
  (1,5)	17.3	16.1	6.3	60.0	50028
  (1,0)	17.1	-16.6	4.2	68.0	68117
  (3,0)	16.9	-10.6	-13.1	73.0	84821
  (0,1)	16.7	-15.0	7.4	65.0	69758
  (2,5)	16.1	13.3	9.1	96.0	88076
  (1,1)	15.3	-13.6	7.0	85.0	89508
  (1,3)	15.0	-5.2	14.1	77.0	77982

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F466N visit 2: worst tile 17.9 mas at cell (0,3) (> 15 mas)

  32/32 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_F466N_latest.json

  what is affected, and why

  3/32 cells exceed 15 mas, and every one of them is on the mosaic EDGE — that is usually thin coverage (few exposures, so few pairs per cell) rather than a distortion error. Check the pair counts in the table before treating it as a defect. The bulk tie for this visit is 1.23 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,3)	17.9	-15.8	8.4	42.0	84015
  (1,5)	16.8	16.4	3.3	69.0	30985
  (3,0)	15.8	-8.8	-13.1	104.0	49239

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F466N_o002 visit 1: worst tile 15.8 mas at cell (5,1) (> 15 mas)

  34/34 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_F466N_o002_latest.json

  what is affected, and why

  1/34 cells exceed 15 mas, and every one of them is on the mosaic EDGE — that is usually thin coverage (few exposures, so few pairs per cell) rather than a distortion error. Check the pair counts in the table before treating it as a defect. The bulk tie for this visit is 0.54 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,1)	15.8	15.6	-2.8	10.0	86709

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• warn
  F466N_o002 visit 2: worst tile 19.2 mas at cell (0,3) (> 15 mas)

  33/33 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_F466N_o002_latest.json

  what is affected, and why

  4/33 cells exceed 15 mas, and every one of them is on the mosaic EDGE — that is usually thin coverage (few exposures, so few pairs per cell) rather than a distortion error. Check the pair counts in the table before treating it as a defect. The bulk tie for this visit is 1.37 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,3)	19.2	-17.4	8.0	45.0	88383
  (0,4)	16.6	16.5	-1.0	11.0	24403
  (1,5)	16.3	16.3	-0.4	68.0	31765
  (3,0)	15.6	-8.5	-13.2	105.0	50179

  Existing figures

  • astrometry_offsets_2026-07-10.png audit_plots
  • 12CO10_PV_BostonACES.png figures
  • 12CO_mom0_contour_filament.pdf figures
  • 13CO_mom0_contour_filament.pdf figures
• ok
  m7 present (3 file(s))

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

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

  logs/
• ok
  m7: single tag 2026-09-01_PR612_f4ebf47-dirty (21 products)

  catalogs/*m7*.prov.json
• ok
  m8: single tag 2026-09-01_PR612_f4ebf47-dirty (3 products)

  catalogs/*m8*.prov.json