Hi @chrisschuerz,
running the SWATfarmeR 3.2 with different climate change scenarios and the same SWATfarmer input csv file, I encontered differents problems. All of them are releated to the killing operation that in some occasion is skypped and stop the function because the SWATfarmer check if there is already a crop in the field (and yes, there is because it is not killed before!).
Part of these issues were resolved by editing the input farmer file, increasing the time window of the killing operations but in some occasion the time window is very large but probably the addictional variables (i.e. pcp and api) don't permit the execution of the operation. Here an example extractect by a not completed frm.mgts file and in particular the skipped_operation table:
(md >= 0911) * (md <= 0920) * (1 - w_log(pcp, 0, 7)) * (1 - w_log(api, 5, 20)) * (year == (year(prev_op)))
is there a way to force the killing operation inside the window?
thanks
enrico
Hi @chrisschuerz,
running the SWATfarmeR 3.2 with different climate change scenarios and the same SWATfarmer input csv file, I encontered differents problems. All of them are releated to the killing operation that in some occasion is skypped and stop the function because the SWATfarmer check if there is already a crop in the field (and yes, there is because it is not killed before!).
Part of these issues were resolved by editing the input farmer file, increasing the time window of the killing operations but in some occasion the time window is very large but probably the addictional variables (i.e. pcp and api) don't permit the execution of the operation. Here an example extractect by a not completed frm.mgts file and in particular the skipped_operation table:
(md >= 0911) * (md <= 0920) * (1 - w_log(pcp, 0, 7)) * (1 - w_log(api, 5, 20)) * (year == (year(prev_op)))is there a way to force the killing operation inside the window?
thanks
enrico