Currently this code requires the user to generate their own GLOW look-up tables based on date, time, and geophysical conditions at the observation time. It might be nice to have a better/easier way to handle this automatically. Some possibilities that have been discussed:
- A single large look-up table that covers all relevant geophysical conditions (would require a sensitivity analysis to understand the necessary parameter space to cover)
- Inversion code generates the look-up tables it requires automatically at run time
- Include GLOW directly in inversion iteration and avoid look-up tables
Currently this code requires the user to generate their own GLOW look-up tables based on date, time, and geophysical conditions at the observation time. It might be nice to have a better/easier way to handle this automatically. Some possibilities that have been discussed: