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

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

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

Split derived type `shpc_slice_handler` into `shpc_slice_handler` and
`shpc_slice_meta out`. Do not mix what is necessary to open, create
and close, analogous to a logical unit, with what comes from reading
the files.

Create component `unit` for `ishape_last.txt` in derived type
`shpc_slice_handler`. Open, create and close `ishape_last.txt` at the
same time we open, create and close the shapefiles. So we use
`read_opcol` instead of `read_column` when we need to read
`ishape_last.txt`.

We are more clearly separating opening files and reading from them.

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

Because it contains timing.

Following update of `test_compare.py`.

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

This `accept.py` also serves as an example for a module accept
accompanying the script `filter.py`.

The bug was introduced in commit b3615f59.

Following modifications of `CMakeLists.txt` files.

With `target_sources` rather than referring to their path from another
directory.

It was difficult to find the `CMakeLists.txt` that controlled the the
compilation of a given file from the message of a compilation error.

This did not produce an error because the mod files are also in
`${CMAKE_CURRENT_BINARY_DIR}`.

It was difficult to find the `CMakeLists.txt` that controlled the the
compilation of a given file from the message of a compilation error.

Since `NR_util` has been integrated into Jumble.

But reading from them is not here yet.

Needed by test `Set_max_speed_degenerate`.

Because the program `test_set_max_speed` in tests `Set_max_speed` and
`Set_max_speed_noise` uses the results of program
`test_get_1_outerm`. `test_set_max_speed` opens an SHPC with
`shpc_open`, so it needs ishape_last.txt.

Since `shpc_open` is called by all processes, reading d0 and
`ishape_last` in `shpc_open` implies that we do not broadcast d0 and
`ishape_last`.

Store `ishape_last` and first date in components of derived type
shpc. We then remove arguments `d_init` and `ishape_last` of procedures
`read_snapshot` and `get_snapshot`.

Preparing for components `ishape_last` and `d_init` of type shpc.

It was confusing to mix opening an SHPC with broadcasting some part of
the resulting shpc variable.

By explicit formatting.

We are reverting commit e48b7f7e. I think I did not really appreciate
then that the number of days since 1950-1-1 is another date index. It
is clearer to use just one date index, which is in the dbf files. So,
in effect, we replace everywhere the old 0-based date index k by `k -
d_init`. Note that we no longer need argument `d_init` for procedure
`dispatch_snapshot` and we no longer need to write `d_init` to file
`node_id_param.json`. Note also that the value of every node index
changes by the amount `d_init * e_overestim`.