It was not convenient to read them with input function or on the
command line: too much to read this way, and not clear when saved in
JSON text file. And we already had to create a namelist file
anyway. And this way the namelists can be extended transparently.

Instead of `config_nml.txt`. Preparing to include other namelists in
this file.

Preparing to read a second input variable from stdin in procedure
`input_ssh`.

Instead of deducing it from the longitude coordinate. The deduction
could not be generalized to a non-uniform longitude-latitude
grid. Also, the test on `step(1)` and nlon was not perfectly robust.

We are trying to simplify the logic in program `inst_eddies`. Also,
the program `inst_eddies` should not write `grid_nml.txt` to the top
level of the SHPC directory since several instances could run in
parallel for several slices. So we are leaving it as a task for a
script above `inst_eddies` to create `grid_nml.txt` at the top level
of the SHPC directory. In tests, we have to move `grid_nml.txt` to
SHPC because we use `SHPC/grid_nml.txt` in other tests.

We are reverting commit d4d05bc2. It was not true that we needed two
input fluxes in the Fortran program. `inst_eddies.py` can read the
file `config_nml.txt` and merge its content to stdin for the Fortran
program.

Add argument SHPC-dir to script `inst_eddies_Aviso.py`. We want to be
able to run `inst_eddies_Aviso` in parallel for several slices. Since
we write `used_config_nml.txt` to the current directory, we need to
run the parallel instances from different directories. So the current
directory cannot always be the directory containing the SHPC to be
appended to.

Add argument `SHPC_dir` to function `loop_inst_eddies`. We want to be
able to run `loop_inst_eddies` in parallel for several slices. Since
we write `used_config_nml.txt` to the current directory, we need to
run the parallel instances from different directories. So the current
directory cannot always be the directory containing the SHPC to be
appended to.

We want to be able to run `inst_eddies` from a directory other than
the directory containing the SHPC to be appended to. Preparing to
write `grid_nml.txt` and `used_config_nml.txt` in the current
directory. To be able to do this in parallel for several slices, we
need to be running in different directories.

For `Test_compare` version > 0.4.

We rewrite `inst_eddies_Aviso.py` so it is more convenient to use. The
script is only useful for several input files. Otherwise we can
directly use `inst_eddies.py`. So instead of optional arguments
template and last date, we use positional arguments. Then there is no
point in distinguishing dirname and basename. Also, it does not make
sense any longer to read the date from the content of the first
file. The script becomes more general: we do not assume that all input
NetCDF files are in the same -directory and that the time coordinate
is in days since 1950-1-1. The interface is also clearer.

Because `test_set_all_outerm` is now essentially the same as
`inst_eddies`. Replace `test_set_all_outerm` by `inst_eddies` in
tests.

Introduce two variables `Aviso_DT_dir` and `Eurec4A_NRT_dir` to
replace the single variable `large_input_dir`. This should remove the
need to create symbolic links to the files in these directories.

Dictionary instead of list, following update of `test_compare.py`.

Instead of symbolic links. We want to avoid creating symbolic links
above SHPC because we want to run several instances of `inst_eddies`
in parallel.

So the script can write to a slice other than 0.

Bug fix: do not provide standard input for `inst_eddies_Aviso.py`, it
does not read it.

Because `$tests_old_dir/Extraction_eddies_region_5/SHPC` is opened
with `SHPC_class` in test `Plot_eddy_contours_window`, which will
create `n_slices.txt`, so there will always be this file only in
`$tests_old_dir/Extraction_eddies_region_5/SHPC`.

We import in the test infrastructure the experiment `Inst_eddies_4`
because we want to no longer keep invalid contours, so we will need to
update the experiment.

Changing my mind. In an SHPC, store shapefiles in
"Slice_{slice}/{orientation}" instead of
"{orientation}/Slice_{slice}". Two reasons: easier to store accessory
files from running `inst_eddies`, such as `perf_report` and output
from Torque submission script; clearer that a slice should contain the
same dates for both orientations.

Assume that a slice is in a directory
"{shpc_dir}/{orientation}/Slice_{slice}" where shpc_dir can be any
name, orientation is "Anticyclones" or "Cyclones" and slice is an
integer. Do not read or create any longer a file "orientation.txt" in
the slice directory. Add procedure `get_slice_dir`. Add dummy
arguments cyclone and slice to procedure `shpc_open`. Add dummy
argument slice to procedure `shpc_create`.

Rename `main_nml` to `config_nml` in module `config_m`.

Extract code from program `inst_eddies` into new procedure `input_ssh`.

Add tests for a case where the speed is not defined on a whole segment.

Following update of `test_compare.py`.

We can make a symbolic link or copy to `$large_input_dir`.

Following modifications of `CMakeLists.txt` files.

When there are more than 3 input files. We recover the convenience of
commit b34b85a8, with the underlying generality of commit d365e754.

Provide list of input files as arguments of `inst_eddies.py`,
following commit 8e0c03e1.

For programs `inst_eddies` and `test_get_1_outerm`, following commits
9a59d13 and 9dc139d.

Following commit b0e3ce55.

In commit d5e89eb9, the test was added with the useless key
"input". Now, after commit 29c37646, the useless key is the key "required".

Now that `inst_eddies` reads `main_nml` only on the first date, we do
not need to create a file `main_nml.txt` before running
`inst_eddies.py`. `inst_eddies.py` can just read `main_nml` from
standard input.