-
Notifications
You must be signed in to change notification settings - Fork 7
Time representations #243
Copy link
Copy link
Open
Labels
backendRelated to the in-memory data model/storeRelated to the in-memory data model/storefrontendRelated to the user-facing APIRelated to the user-facing APIrequirementCore requirementCore requirement
Milestone
Description
Metadata
Metadata
Assignees
Labels
backendRelated to the in-memory data model/storeRelated to the in-memory data model/storefrontendRelated to the user-facing APIRelated to the user-facing APIrequirementCore requirementCore requirement
Type
Fields
Give feedbackNo fields configured for issues without a type.
We currently use the builtin
datetime.datetimefor type hinting component fields and implementing converters.The one exception at the moment is in the utilities we've already rehomed from imod-python, e.g. the head and budget file readers in https://github.com/modflowpy/pyphoenix-project/tree/develop/flopy4/mf6/utils.
We may need some utilities like imod-python's for more flexible handling of dates/times and converting between representations. Ideally we can be lenient in what we accept, then convert internally into a consistent representation.
Relevant reading