Update links to example configs in documentation

[jeipollack]

Links to the example config files point in the documentation to the now deleted dummy-main branch.
data_config.yaml
training_config.yaml
metrics_config.yaml
plotting_config.yaml

Update the links to point to correct config file in the main branch (see here).

[jeipollack]

I forgot this link is also broken:

wf-psf/docs/source/configuration.md

Line 286 in 146725f

The `configs.yaml` file is the master configuration file that is used to define all of the pipeline tasks to be submitted and executed by `WaveDiff` during runtime. In this file, the user lists the processing tasks (one or more) to be performed by setting the values of the associated configuration variables `{pipeline_task}_conf` and the name of the configuration file `{pipeline_task}_config.yaml`. See an example below to configure `WaveDiff` to launch a sequence of runs to train models 1...n with their respective configurations given in the files `training_config_{id}.yaml`.

It should be replaced with this one: https://github.com/CosmoStat/wf-psf/blob/146725f2c2209bf3174c88c07a116e9ce28fff9a/config/configs.yaml

[nadamoukaddem]

In certain sections, there are missing links as illustrated below. These links need to be added ?

wf-psf/docs/source/configuration.md

Line 341 in 146725f

Note, in this version of WaveDiff produces a single plot per each metric per trained model. To display all of the metrics results for each trained model in a single plot, the user must do so in a different run following the steps defined in the section [Plot Configuration](plotting_config). The next upgrade to WaveDiff will feature options to produce independent metrics plots per trained model or a single master plot comparing the respective metric results for all trained models.

wf-psf/docs/source/configuration.md

Line 207 in 146725f

The option to generate plots of the metric evaluation results is provided by setting the value of the parameter `plotting_config` to the name of the [plotting configuration](plotting_config) file, e.g. `plotting_config.yaml`. This will trigger WaveDiff's plotting pipeline to produce plots after completion of the metrics evaluation pipeline. If the field is left empty, no plots are generated.

wf-psf/docs/source/configuration.md

Line 209 in 146725f

To compute the errors of the trained PSF model, the `metrics` package can retrieve a ground truth data set if it exists in the dataset files listed in the [data_configuration](data_config) file. If they do exist, WaveDiff can generate at runtime a `ground truth model` using the parameters in the metrics configuration file associated to the key: `ground_truth_model`. The parameter settings for the ground truth model are similar to those contained in the [training configuration](training_config) file. Currently, the choice of model, which is indicated by the key `model_name`, is currently limited to the polychromatic PSF model, referenced by the short name `poly`.

[jeipollack]

No. not from a commit state. You should add the links to the files in the main branch.