rubem.configuration.raster_series_resolver

Resolution of the raster series to one file path per simulated step.

A resolver answers “which raster does step n read?” for one series. The legacy configuration only has directory series (one 8.3-named file per step); format 1.0 adds dated entries and monthly sets. A step without a raster is answered with a MissingStep marker rather than an exception, so that the run can decide: the NDVI and land use series fall back to the previous raster, the precipitation, ETP and Kp series cannot.

Functions

`check_coverage`	Report the steps each series cannot provide within the simulated window.
`check_series_member_crs`	A GeoTIFF series member must share the reference coordinate reference system.
`date_to_step`	The step whose month contains `day`.
`resolvers_from_legacy`	Directory resolvers for a legacy `InputRasterSeries`.
`resolvers_from_v1`	Resolvers for a `ModelConfigurationFileV1`, one per series.
`step_to_date`	The first day of the month simulated at `step` (step 1 is the alignment month).
`validate_resolved_series`	Validate the rasters the resolvers answer over the simulated window.

Classes

`DatedSeriesResolver`	Rasters valid over date ranges (both bounds inclusive, whole months).
`DirectorySeriesResolver`	One raster per step in a directory: PCRaster 8.3 names or GeoTIFF files.
`MissingStep`	A step the series has no raster for.
`MonthlySeriesResolver`	Twelve rasters repeated every year, optionally replaced from a year on.