@@ -119,7 +119,7 @@ Management operation inputs in a SWAT+ model setup can be very complex and compr
Function `report_mgt()` can be applied to identify discrepancies between management operations in model input files and what operations are actually triggered in the model. If `write_report` parameter is set to TRUE, function also provides a report in *"schedule_report.txt"* text file.
```{r}
mgt_report <- report_mgt(sim_nostress, TRUE)
mgt_report <- report_mgt(sim_nostress)
mgt_report
print(paste("Issues were identified in", length(mgt_report$schedule), "schedules."))
print(paste("Table of issues for selected management", sel_mgt))
create_dt(mgt_report$schedule_report[[sel_nb]])
} else {
id <- get_hru_id_by_attribute(sim_nostress)
}
```
...
...
@@ -211,17 +213,19 @@ The next step includes activating potential sources for plant growth stresses, s
Setting `nostress = 0` while running `run_swat_verification()` function will activate all stresses, however turning off the nutrient plant stress only can as well be a useful option for analyses (`nostress = 2`). This is particularly useful for eliminating the fertilization impact on the plant growth and focusing only on the weather/climate and structural setting of the plant. Particularly, the aeration, temperature, and water stress, alongside yields are relevant outputs to be analyzed. A simulation with inactive nutrient stress will provide a good approximation of possible yields with an optimal fertilization and ideal plant nutrient supply. All other stresses will indicate the need of irrigation, drainage or plant-specific parameter adjustments for a plant to grow.
It is possible to plot each case side-by-side for examination with same functions applied. For instance `plot_variable_at_harvkill()` could be run to check how much stress factors affect in each case.