CWARHM procedure for CAMELS-spat dataset

[CyrilThebault]

/!/!/!\ These changes must not be added to the main branch but must be kept in a separate branch dedicated to be used with CAMELS-spat dataset (at least for now) /!/!/!\

Folders 0s (exemple, control file, tools):
The exemple in the folder 0 is based on a CAMELS-spat catchment and the associated control file has been extensively revised to take account of changes linked to the use of the CAMELS-spat database (mainly remove parts that are not used anymore with CAMELS-spat)

Folder 1 (create domain):
Minor change to use the name of the chosen control_file as an argument to the script

Folder 2 (install SUMMA & MizuRoute):
Remain the same

Folder 3&4 (Data processing):
Although the architecture has been designed with a logic similar to that of the main branch, it's not exactly the same.
In fact, most of the steps involved in downloading, processing and formatting data are no longer necessary when using the CAMELS-spat database. In addition, data (and their formatting) from CAMELS-spat are not identical to those that can be obtained with the classic CWARHM procedure via the main branch, and scripts have therefore been added/modified to take these differences into account (see folder 3 to 4). In addition, now the script is using rasterstats instead of QGIS.

Folder 5 (Model setup):
For SUMMA, no changes
For MizuRoute, optional remapping was deleted and the outlet id is now automatically detected. Settings and filemanager were updated.

Folder 6 (Model Run):
No changes

Folder 7 (Visualization):
Remove unused scripts (e.g. visualisation at the global or regional scale) and minor adaptations

[wknoben]

Can you change the target branch from main to something more appropriate if we don't want this merged into main?