You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Currently, autocut functionality (at least PhenologicalAutocut) requires a lot of setup on the part of the linked ModvegeSite object. Some of that setup is even hidden behind private function, so it has to be carried out manually if one wishes to just get the expected cut date based on meteo.
It would be nice to be able to debug autocut routines that don't depend on the model state without having to setup the whole ModvegeSite.
Given that only a subset of autocut routines even fulfills this condition, this is a low priority issue.
The text was updated successfully, but these errors were encountered:
Currently, autocut functionality (at least
PhenologicalAutocut
) requires a lot of setup on the part of the linkedModvegeSite
object. Some of that setup is even hidden behind private function, so it has to be carried out manually if one wishes to just get the expected cut date based on meteo.It would be nice to be able to debug autocut routines that don't depend on the model state without having to setup the whole ModvegeSite.
Given that only a subset of autocut routines even fulfills this condition, this is a low priority issue.
The text was updated successfully, but these errors were encountered: