All-enhancements-on sets, per probe and engine

Generated from arrayprobe_enhancements.registry, arrayprobe_enhancements.applicability and the per-probe restriction table the driver computes these sets with; never hand-typed. Rebuilt by the documentation build.

What a run gets when every enhancement in arrayprobe_enhancements is switched on, for each of four probes (2D-S, HVPS, CIP, PIP) on the UIOOPS v3.5 engine. SODA-2 is covered separately in §5 – it has no engine axis and no per-probe registry.

Probe applicability is not enforced anywhere in the resolver. arrayprobe_enhancements.applicability gates by engine only; the probe restrictions below are read off each module's own registry.py summary and the PROTECTIVE probetype table (registry.py:750-757), not measured by a runtime check. CIP and PIP are probetype 1, read from constants.IMGPROC_CONFIG (imgProc_sm.m:138-156).

See also Enhancements · Which enhancements apply to which engine · Enhancements by stage · Probes.

1. Module x probe matrix, per engine

Cell values: on (in the all-on set), refuses (state, see §4) (applicability.check raises NotApplicableToEngine; the one-line reason and file:line are in §4), n.a. (applicable but left out of default_set by name, see §4 – a cost/benefit exclusion, not a version refusal), **excluded (probe restriction, see Probe applicability above)** (the module does not apply to this probe's probetype; the code has no probe axis to enforce it).

engine = 3.5

2. The literal all-on list, per (probe, engine)

default_set narrowed by the probe restrictions, sorted, each module linked as in §1.

3.5 / 2DS (24): analysis, arco_export, arm_export, brown_francis_1995, cf_export, distance_rejection, dmax_sensitivity (its part), effective_density, field2006_shatter (its part), hole_edge_swap (its part), intarr_policy (its part), md_relations, ml_accept_reject, overload_accounting_fix (its part), partial_image_habit (its part), particle_clustering (its part), poisson_restore, poisson_uncertainty, probe_crossover, probe_uncertainty, published_dof (its part), rollover_fix (its part), spec_artefact_filter, spot_edge_fix (its part)

3.5 / HVPS (23): analysis, arco_export, arm_export, brown_francis_1995, cf_export, distance_rejection, dmax_sensitivity (its part), effective_density, field2006_shatter (its part), hole_edge_swap (its part), intarr_policy (its part), md_relations, ml_accept_reject, overload_accounting_fix (its part), partial_image_habit (its part), particle_clustering (its part), poisson_restore, poisson_uncertainty, probe_crossover, probe_uncertainty, published_dof (its part), rollover_fix (its part), spot_edge_fix (its part)

3.5 / CIP (26): analysis, arco_export, arm_export, brown_francis_1995, cf_export, distance_rejection, dmax_sensitivity (its part), effective_density, field2006_shatter (its part), hole_edge_swap (its part), int_arr_rollback_fix (its part), intarr_policy (its part), md_relations, ml_accept_reject, partial_image_habit (its part), particle_clustering (its part), particle_time_glitch_fix (its part), pms_c6_routing_fix (its part), poisson_restore, poisson_uncertainty, probe_crossover, probe_uncertainty, published_dof (its part), rollover_fix (its part), spot_edge_fix (its part), tas_grid_fix (its part)

3.5 / PIP (26): analysis, arco_export, arm_export, brown_francis_1995, cf_export, distance_rejection, dmax_sensitivity (its part), effective_density, field2006_shatter (its part), hole_edge_swap (its part), int_arr_rollback_fix (its part), intarr_policy (its part), md_relations, ml_accept_reject, partial_image_habit (its part), particle_clustering (its part), particle_time_glitch_fix (its part), pms_c6_routing_fix (its part), poisson_restore, poisson_uncertainty, probe_crossover, probe_uncertainty, published_dof (its part), rollover_fix (its part), spot_edge_fix (its part), tas_grid_fix (its part)

3. Moves a number, or tooling / export / analysis

From all_on_sets.MOVES_A_NUMBER / TOOLING_ONLY – a correction to a written value or a derived diagnostic nothing in the port computes, against a lossless re-encode, a unit re-expression or a reference table.

Moves a number (29): analysis, diode_range_fix (its part), distance_rejection, dmax_sensitivity (its part), effective_density, field2006_shatter (its part), hole_edge_swap (its part), int16_double_fix (its part), int_arr_rollback_fix (its part), intarr_policy (its part), intarr_threshold_fix (its part), mask_presence_fix (its part), ml_accept_reject, outoffocus (its part), overload_accounting_fix (its part), partial_image_habit (its part), particle_clustering (its part), particle_number_all_fix (its part), particle_time_glitch_fix (its part), particle_time_int8_fix (its part), pms_c6_routing_fix (its part), poisson_restore, poisson_uncertainty, published_dof (its part), reshape_fix (its part), rollover_fix (its part), spec_artefact_filter, spot_edge_fix (its part), tas_grid_fix (its part)

Tooling / export / analysis (7): arco_export, arm_export, brown_francis_1995, cf_export, md_relations, probe_crossover, probe_uncertainty

4. Every module that refuses or is excluded on v3.5

Six rows: two superseded (the UIOOPS developers already fixed these in v3.5, so applying the correction again would double-correct), three variant-only (the construct exists in no stock UIOOPS release), and one excluded from default_set by name (applicable, but costly for little benefit).

5. SODA-2

SODA-2 has its own package, arrayprobe_soda2_enhancements, with a per-module registry. It differs from the UIOOPS registry on two axes: no engine matrix (SODA-2 has one source tree, so there is nothing for an applicability-shaped module to consult), and no archived-product lineage: SODA-2 has written no archived product for any probe, so its PROTECTIVE set (the corrections for data-destroying upstream defects) runs by default on every probe, per the protective-corrections rule, and a config opts out by name or with --protective off. Every other correction is opt-in, as on the UIOOPS side.

Every SODA-2 correction – the all-on set for SODA-2 on any probe:

• aspr_nan_fix – opt-in, reachability live, finding S2-d
• blank_roi_dof_fix – opt-in, reachability flagged, finding S4-v
• den_clamp_fix – opt-in, reachability live, finding S2-f
• dilation_clamp_fix – default ON (protective), reachability live, finding S4-z
• double_pi_fix – opt-in, reachability live, finding S2-c
• empty_roi_diodegaps_fix – opt-in, reachability flagged, finding S5-h
• fillholes_int_labels – opt-in, reachability latent, finding S4-u
• hk_probeid_columns – opt-in, reachability flagged, finding S5-k
• label_blobs_int_count – opt-in, reachability latent, finding S4-y
• last_buffer_index_fix – default ON (protective), reachability live, finding S4-i
• no_stuck_diode_fix – default ON (protective), reachability live, finding S4-x
• pbp_inttime_consistent – opt-in, reachability live, finding S6-i
• pbp_rejectionflag_ubyte – default ON (protective), reachability live, finding S6-k
• poisson_fill_guard – opt-in, reachability live, finding S4-t
• rejection_tally_fix – opt-in, reachability live, finding S5-a
• rollover_modulus_fix – opt-in, reachability live, finding S4-n
• run_diagnostics – opt-in, reachability flagged, finding S4-q
• same_time_buffer_fix – default ON (protective), reachability live, finding S4-o
• zero_area_return_fix – opt-in, reachability flagged, finding S3-e

No probe restriction is encoded for SODA-2 either; the port runs the SPEC chain (2D-S/HVPS) and the CIP route for SEA- and DMT-format files end to end, and every registered correction applies wherever its own consumes/entry point reaches, not narrowed by probe here.