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.

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

Use `uniform_lon_lat` from modules `input_ssh_m` or `read_grid_m` to
compute actual argument of `shpc_create`.

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.

In program `examine_eddy`.

Change order of command line arguments of program
`examine_eddy`. Preparing to allow a variable number of NetCDF file
arguments.

Do not always specify uv-file when it is the same as ssh-file.

`MAX_RADIUS_deg` is not general enough for a non longitude latitude
grid. The variable `max_radius` moves from module `input_ssh_m` to
module `config_m`. The variable `MAX_RADIUS_deg` disappears. The
constraint `2 * max_radius_deg(1) < 180` becomes `4 * max_radius(1) <
nlon` but is only applied to the periodic case because we do not have
the general equivalent of 180° in number of points.

`Region_1_20454_cyclone_3/config_nml.txt` is a symlink to
`Extraction_eddies_region_1_noise/config_nml.txt`.

Call `input_ssh` from main program `test_mean_speed`. This is
necessary because procedure `mean_speed` uses variable corner from
module `input_ssh_m`. Note that we have to call config before
`input_ssh` since `input_ssh` uses a variable from module `config_m`.

In program `test_set_max_speed`, read `cont_list_proj` instead of
computing it. Computing it is not possible with a non
longitude-latitude grid.

Read the same NetCDF files than those used to create `cont_list`. It
does not change anything since the window is going to be created
inside `test_set_max_speed`, so it is an unnecessary complication to
have input NetCDF files on a restricted domain. Furthermore, if we
want to use `test_set_max_speed` on a non longitude-latitude grid,
then it would be a problem to convert x, y corresponding to the grid
of `cont_list` to x, y corresponding to a restricted grid.

For `Test_compare` version > 0.4.

Rather than from current series of tests.

This variable was already used in other tests.

Because some tests require results from other tests in this series of
tests.

Because it can be created by analysis scripts.

It must be the same than the one used for other input files of the test.

Remove input file `outside_points_get_1_outerm.csv`. Use result from
test `Region_1_20454_cyclone_3` instead. There is one less point in
the file `outside_points.csv` from the test `Region_1_20454_cyclone_3`
but this does not change the results of the two impacted tests:
`Get_1_outerm` and `Extr_proj`.

The only difference in the test specification of
`Get_1_outerm_noise_2` with test `Get_1_outerm` is the input file
`outside_points.csv`. This difference in specification leads to no
difference in results of the two tests. The input file
`outside_points.csv` for `Get_1_outerm` is problematic because it has
an extra point at (9.375, -35.857) which corresponds to a cyclone for
an old version of SSH data. So we are going to change the input file
of `Get_1_outerm` to take
`$tests_old_dir/Region_1_20454_cyclone_3/outside_points.csv`, the same
one than for `Get_1_outerm_noise_2`, so there is really no use for
`Get_1_outerm_noise_2`.