pyforestry.norway.simulation.policy package#
Submodules#
pyforestry.norway.simulation.policy.management_rulesets module#
Management-side policy rulesets for Norway scenario configurations.
What is Norwegian here is the table. The accessors around it –
supported_management_scenarios, management_intensity, management_plan
– are ManagementRuleset’s, because they
were identical to Sweden’s apart from this table and the label in the error a bad
scenario id raises.
pyforestry.norway.simulation.policy.scenario_rulesets module#
Scenario forcings for Norway 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 in Norway, so it ships none, and
ConstantForcing refuses to be built with
a non-neutral value and no source.
There was a climate_rcp45 entry here carrying {growth 1.05, disturbance
1.2}. It arrived in this package’s first commit with no source anywhere, and
the name asserts one: RCP4.5 is a specific IPCC Representative Concentration
Pathway, so a scenario called that reads as “these are the multipliers RCP4.5
implies for Norwegian Scots pine”. They were placeholders. Sweden had already
deleted a storm_risk_high for exactly this.
A caller supplies forcings to run_scenario()
directly, and they are recorded in the run manifest with their citations. When a
Norwegian climate or damage series has a paper behind it, it belongs here.
Module contents#
Scenario and management policy rulesets for Norway.
The values are Norway’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.