home.md

@@ -202,6 +202,23 @@ For example, if the extremes (1/10, 9/10) are requested, the output will be:
 
 The Saving module contains several functions that export the data (the calibrated hindcast and forecast, the corresponding observations, the skill metrics, percentiles and probabilities) to netCDF files and save them.
 
+save_data() serves as the main wrapper function for this module.`recipe` (the recipe),  `data` (the list obtained from the Loading module) and `archive` (the archive) are mandatory arguments. The rest of the arguments (calibrated_data, skill_metrics and probabilities) are optional. 
+
+Therefore, all the data can be saved at once:
+
+`save_data(recipe, archive, data, calibrated_data, skill_metrics, probabilities)
+
+Or, one can choose to save only some of it. For example,
+saving the calibrated hcst/fcst and corresponding observations only:
+
+`save_data(recipe, archive, data, calibrated_data = calibrated_data)`
+
+Or saving the skill metrics only:
+
+`save_data(recipe, archive, data, skill_metrics = skill_metrics)`
+
+### The structure of the output directory
+
 Several subdirectories are created in the output directory specified in the recipe. Their structure is as follows:
 
 If fcst_year has been requested:
@@ -210,8 +227,12 @@ If fcst_year has been requested:
 
 If fcst_year is empty:
 
+- For seasonal data:
 `output_dir/<calibration_method>-<frequency>/hcst-<mmdd>/<var>/`
 
+- For decadal data:
+`output_dir/<calibration_method>-<frequency>/hcst-<yyyy>_<yyyy>/<var>/`
+
 Please take this structure into account when defining Run:output_dir, to avoid unintentionally rewriting previous data.
 For example, in our example recipe, the final output directory will be: