Add INTER reduce

[RebeccaBecky]

No description provided.

[dtasev]

Some minor comments for refactoring

I also think it would be useful if the reduce scripts copies the settings.json into the output folder - that way we have a history of all the input data that will make it possible to recreate.

Very interesting case about the usage of reduce_vars.py though, or rather, the no need for it. Maybe we can change it to just have a path to a .json file for now?

That way when rerunning you can point it to a new settings.json file, that maybe you re-configured from the GUI.

Additionally, we can "teach" the webapp to retrieve the json, use the parse_json_settings function and visualise it in a table on the page. This bit just being an ideas for myself really 😄

[dtasev]

Shouldn't need those anymore - they now get appended in the container

[dtasev]

This might be easier to manage if you make a dataclass, something like

from dataclasses import dataclass

@dataclass
class INTERParams:
    analysis_mode
    first_transmission_run_list
    second_transmission_run_list
    transmission_processing_instructions
    processing_instructions
    start_overlap
    end_overlap
    monitor_integration_wavelength_min
    monitor_integration_wavelength_max
    monitor_background_wavelength_min
    monitor_background_wavelength_max
    wavelength_min
    wavelength_max: float
    i_zero_monitor_index
    detector_correction_type

that also allows you to set typed, e.g. wavelength_max: float

Then just make it at the start of the function params = INTERParams() and fill it with data as you go down

[dtasev]

You can move this into a little helper function, e.g. get_transmission_params that takes i and sets the correct fields. This would make it easier to test as well, because now a unit test can be added for the helper function to make sure it works

[dtasev]

I think row is a better name than i, you'll have to rename it in the scope below though