Add fourth aruco (ID 220, batch4 coefficients)

[dzermas]

Add fourth aruco

What?

• Add sg3144_batch4_coefficients to imgcorrect/zenith_co.py (wavelengths 250-2450 nm)
• Map ArUco ID 287 220 (edit: ZT) to batch4 coefficients in imgcorrect/corrections.py
• Update imgcorrect/detect_panel.py to use DICT_6X6_1000 (backward-compatible superset of DICT_6X6_250) and recognize ID 287 220 (edit: ZT)
• Add tests/aruco_markers/aruco_220.png (edit: ZT) test marker image
• Update tests/test_corrections.py to cover ID 287 (edit: ZT) and batch4

Why?

Need support for another aruco code.

Notes

DICT_6X6_1000 produces identical bit patterns for IDs 0-249 as DICT_6X6_250, so existing panels (23, 63, 217) are unaffected.

PR Checklist

• Merged latest master
• Updated version number
• All private git packages are at their newest version in both pyproject.toml and environment.yml
• All git package version numbers match between pyproject.toml and environment.yml
• [?] dist/ImageryCorrector.exe and dist/GetCorrectionsCsv.exe have been rebuilt

Breaking Changes

[zthorson]

I'd like to collect a dataset of in field data for final verification before approval, as we need this set anyway to share with Pix4D to get them to add the marker to their software.

[zthorson]

Sent a sample of the code and a test dataset to Pix4D to get their feedback on whether their Aruco codes work. We still have the option to change the ID if Pix4D comes back and says they won't support it, so I'll wait until I hear back.

[zthorson]

The new ID is 220, I've made the required changes.

Running it on flight test data with the new Aruco 220 is still pending.

[dzermas]

@zthorson changes look good. Did we get an update on the testing?

[zthorson]

I just created a test panel yesterday, just need to find time to fly a short test flight to collect data. The PR should be fine, but want to check it against real world data since we need it anyway for Pix4D to update their ocde. Panels aren't shipping for a bit, so we have some time to merge

[zthorson]

New 220 panel looks good. We flew a test set using the 6X Thermal Pro and the panel was properly detected and corrections performed. This is the same marker on the stickers for production, so we should be good to go.

Test dataset:
\as-taurus.jdnet.deere.com\Production\Sensors\21216-XX -- 6X Sensor (Thermal)\21216-03\037\RMA 47908

Log:

2026-06-23_16-12-47-calibrated_radiometric_corrections.log

Test dataset will be shared with Pix4D to get it added to Fields in the future. Keep an eye on their field support site here for details: