pyforestry.sweden.simulation.policy package#

Submodules#

pyforestry.sweden.simulation.policy.management_rulesets module#

Management-side policy rulesets for Sweden scenario configurations.

What is Swedish here is the table. The accessors around it – supported_management_scenarios, management_intensity, management_plan – are ManagementRuleset’s, because they were identical to Norway’s apart from this table and the label in the error a bad scenario id raises.

pyforestry.sweden.simulation.policy.scenario_rulesets module#

Scenario forcings for Sweden configurations: none, by design.

A forcing is an external factor imposed on a projection – a weather correction, a disturbance rate, a price index – and every one is a claim about the world. This package has no basis for such a number, so it ships none; a caller supplies them to run_scenario() and they are recorded in the run manifest with their citations.

A storm_risk_high scenario was deleted from here for carrying growth and disturbance multipliers that were invented, with no source behind them. pyforestry.simulation.forcing now enforces what that removal established.

Module contents#

Scenario and management policy rulesets for Sweden.

The values are Sweden’s; what the fields mean and how an unknown scenario id is handled is pyforestry.simulation.policy, because the two regions had answered both questions differently.