Dear developers, we are applying CWatM to a basin in the United States. It seems that Ln 491 of "calibration_single.py" has a minor glitch. The "streamflow_simulated_best.csv" file that we get is labeled from the ForcingStart instead of ForcingStart + Spin-up dates.
Y.
----------------------------------------------
Hi Y.,
in the settings.txt (for calibration) there are some lines:
ForcingStart = 1/1/2003
ForcingEnd = 31/12/2013
-> ForcingStart and End should be the calibration period
Therefore:
ForcingStart = SpinUp (in the CWATM settings.ini)
ForcingEnd = StepEnd
I hope your problem gets solved if you put in the SpinUp date as ForcingStart
Regards,
Peter
--------------------------------------
Hi Peter,
Thank you. So, even if I set ForcingStart = the SpinUp date, the model will perform the spinup during calibration?
Y.
-------------------------------------
Hi Y.
yes the model will perform the spin up.
The calibration module is only triggering the CWATM model each time with
different calibration parameters. The model itself performs what is
writen in the settings.ini for the model (in the template folder) and
if you put a spin up there it will be performed.