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
It would be nice to be able to get the list of variables that a forcing source needs to succesfully be able to generate a forcing object. I'm thinking something like:
forcing['genericLumped'].get_variables()
would return a list: ["tas","pr"]
The text was updated successfully, but these errors were encountered:
@classmethoddefget_input_variables(
cls: type["DefaultForcing"],
) ->tuple[str, ...] |None:
return ("pr", "tas", "rsds") # for example
tuple is immutable: better for returning here.
UserForcings have "variables" as input argument, so we cannot know which ones are required based on the class definition. Therefore the possibility of the method returning None.
I like that. Should we add that as a template in the central repos and implement it in the model repos?
I'll add it as an abstractmethod to the base forcing class, which will force plugin maintainers (i.e. us) to implement it for any implementations of the forcing.
It would be nice to be able to get the list of variables that a forcing source needs to succesfully be able to generate a forcing object. I'm thinking something like:
would return a list:
["tas","pr"]
The text was updated successfully, but these errors were encountered: