BUG - CoDICE

[laspsandoval]

Description of the issue

The CoDICE team anticipates frequently changing their LUT in FSW. They have a spreadsheet that we have used to create a json. When they update their FSW we need to have a process in place to automatically create a new LUT (imap_codice_l1a-sci-lut_20251007_v004.json) based on their LUT spreadsheet and then upload that LUT to s3.

Some of the changes from their spreadsheet are listed as constants in our code. These constants need to be migrated to the LUT.

There are two tasks for this ticket:

1. Identify how imap_codice_l1a-sci-lut_20251007_v004.json is created using the spreadsheet that the CoDICE team uses for FSW. Make certain we have code created to automate it.
2. Migrate the following constants to the LUT since these will also change periodically:

# Lookup table for CoDICE-Lo despinning pixel orientations
# See section 9.3.4 of the algorithm document for further information
PIXEL_ORIENTATIONS = {
    0: "A",
    1: "B",
    2: "A",
    3: "B",

# Lookup table for mapping half-spin (keys) to esa steps (values)
# This is used to determine geometry factors L2
HALF_SPIN_LUT = {
    0: [0],
    1: [1],
    2: [2],
    3: [3],
    4: [4, 5],
    5: [6, 7],
    6: [8, 9],
    7: [10, 11],
    8: [12, 13, 14],
    9: [15, 16, 17],

[laspsandoval]

I'm adding Greg, Luisa, and Tenzin for visibility. Note that new changes are anticipated based on conversations that the Instrument Team will have today (12/12/25) so the details of the LUT data may be updated.