reVX.config.transmission_layer_creation.DryCosts
- class DryCosts(*, iso_region_tiff: Annotated[Path, PathType(path_type=file)], nlcd_tiff: Annotated[Path, PathType(path_type=file)], slope_tiff: Annotated[Path, PathType(path_type=file)], cost_configs: Annotated[Path, PathType(path_type=file)] | None = None, default_mults: IsoMultipliers | None = None, extra_tiffs: List[Annotated[Path, PathType(path_type=file)]] | None = None, attrs: Dict[str, Dict] | None = None)[source]
Bases:
BaseModelConfig items required to generate dry costs
Create a new model by parsing and validating input data from keyword arguments.
Raises [ValidationError][pydantic_core.ValidationError] if the input data cannot be validated to form a valid model.
self is explicitly positional-only to allow self as a field name.
Methods
Attributes
model_computed_fieldsmodel_fieldsFilename of ISO region GeoTIFF
File name of NLCD GeoTiff
File name of slope GeoTiff
Path to json file with Xmission cost configuration values.
Multipliers to be used for default region.
Optional list of extra GeoTIFFs to add to cost H5 file.
H5 dataset attributes keyed by layer name.
- cost_configs: Annotated[Path, PathType(path_type=file)] | None
Path to json file with Xmission cost configuration values.
Path to json file contianing dictionary with Xmission cost configuration values. Valid configuration keysare:
“base_line_costs”
“iso_lookup”
“iso_multipliers”
“land_use_classes”
“new_substation_costs”
“power_classes”
“power_to_voltage”
“transformer_costs”
“upgrade_substation_costs”
Each of these keys should point to a dictionary or a path to a separate json file contianing a dictionary of configurations for each section.
- default_mults: IsoMultipliers | None
Multipliers to be used for default region.
This input should be a dictionary with three keys:
“iso”: Thie key is ignored, but is required. Can set to “default” and move on.
“land_use”: A dictionary where keys are the land use types (e.g. “cropland”, “forest”, “wetland”, etc.) and values are the multipliers for those land uses.
“slope”: A dictionary where keys are the slope types/mults (e.g. “hill_mult”, “hill_slope”, “mtn_mult”, “mtn_slope”, etc.) and values are the slopes/multipliers.