[BUG]: SWMF-GITM coupling is broken

[abukowski21]

[BUG]: We cannot check if indices times are valid

Since GITM cannot check if file_time is < end_time and file_time > start_time, we have to read in entire indices files. And then of course cannot check that the entire run is covered by indices.

• Please fill out any of the sections below which are relevant to the bug.
• Feel free to edit, delete, or re-order the sections included in the template.
• Please attach any input files necessary to reproduce the bug. If GITM maintainers cannot reproduce the bug, it may cause delays.

Fixing options:

• Currently, this is hacked around. Commit 04085aa says to use old readers (without any time info) and then don't check anything.
• We can possibly pass start/end times over from the SWMF
• in-situ checks of whether indices are valid? but then runs will fail midway through. Sub-optimal!
• something else?

[abukowski21]

We will need to modify how GITM reads indices and parses the UAM/PARAM.in files (set_inputs.f90)

From Gabor:

The inputs are read in two phases in the SWMF. First phase is “READ” and the second phase is “CHECK”. The start and end time are available in the “CHECK” phase from the CON_time module, which can be accessed from the UA_wrapper and passed to GITM variables. This is the point where these files could be read (or even later in init_session). I just checked the code, and it seems that the TimeEnd variable is set right after the component “CHECK” calls:

    do lComp=1,n_comp()
       iComp = i_comp(lComp)
       if(use_comp(iComp))then
    [...]
          call set_param_comp(iComp,'CHECK')
       end if
    end do
   [...]
       ! If not set in PARAM, set TimeEnd using tSimulationMax
      TimeEnd % Time = TimeStart % Time + tSimulationMax
       call time_real_to_int(TimeEnd)

The order can be reversed, so the CHECK phase has the TimeStart and TimeEnd set. The UA_init_session is called even later.

Alternatively we could assume that these times are available already during the READ phase. That would rely on the ordering of commands. We typically we provide the #STARTTIME at the very beginning of the PARAM.in file. The #ENDTIME or #STOP commands, however, are usually put after the BEGIN_COMP … END_COMP sections, so that will not be known yet. So if we force the user to set #STOP before the UA section, it would work. Not ideal.

[abukowski21]

We also want to switch GITM to using the SWMF's share/ and util/ folders.