docs: describe solution T through the levelised cost, ownership and scale
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
parent
ad0be79fdc
commit
79a00f3464
3 changed files with 29 additions and 11 deletions
12
CHANGELOG.md
12
CHANGELOG.md
|
|
@ -96,3 +96,15 @@ All notable changes to this project will be documented in this file.
|
|||
refuse solution T and a loss of demand until chapter 17 is taken through them. No result has been computed.
|
||||
- Present values are now exactly rounded sums. As dot products the same computation did not give the same last
|
||||
digit every time, for every solution. A test runs the same computation six times and requires equal numbers.
|
||||
- Solution T and the loss of demand through the levelised cost, the business economics, the ownership forms
|
||||
and scale (`nivaaisert.py`, `eierskap.py`, `skala.py`): the power cost per module, with a renewable module's
|
||||
own portfolio as in C and the nuclear modules of T-K on shared units as in B; tariff, building, IT hardware
|
||||
and residual value per module; and the factor of S51 per vintage in S19, S27, S31 and S42. For the five
|
||||
solutions of chapters 0 to 16 without a loss every figure is unchanged to the last digit. A new independent
|
||||
reader coded the same from the specification alone: 1 760 made-up paths through both codes, 6.6 million
|
||||
figures compared, without a difference. Six clarifications (82–87) in chapter 16 say how the text is read
|
||||
and name one property the reader found that is in favour of nuclear power on the grid in the business
|
||||
economics (`modell/fagfellevurdering-utkast-2-og-3.md`, part 12). M5 and the verdicts do not know solution T yet. No
|
||||
result has been computed.
|
||||
- The technologies of a facility are kept in a fixed order. As a set of names their order differed from run to
|
||||
run, and the last digit of the figures for solution C with it.
|
||||
|
|
|
|||
17
CLAUDE.md
17
CLAUDE.md
|
|
@ -19,8 +19,8 @@ carousel, Python code, and a Claude plugin (own repo, later).
|
|||
Every model parameter must trace to an entry here.
|
||||
- `FORHANDSREGISTRERING.md`: the approved direction and pre-registered criteria (M1–M7). Committed.
|
||||
- `modell/spesifikasjon.md`: the model specification (equations S1–S54; of chapter 17,
|
||||
the addition to the direction, solution T is coded through the build-out, the power system and the cash
|
||||
flow, and S48–S54 are coded; T through the levelised cost, ownership, scale and verdicts is not).
|
||||
the addition to the direction, solution T is coded through the build-out, the power system, the cash
|
||||
flow, the levelised cost, ownership and scale, and S48–S54 are coded; T through M5 and the verdicts is not).
|
||||
`modell/parametere.json`: the frozen
|
||||
parameters (value, range, distribution, source entries); its checksum is recorded in the pre-registration
|
||||
(version 1.1 after the one deviation of 2026-11-12, which added the quantities of chapter 17.8).
|
||||
|
|
@ -47,17 +47,21 @@ carousel, Python code, and a Claude plugin (own repo, later).
|
|||
cost of capital before tax), approved by the operator 2026-11-12; 67 lists what remains. Clarification 68
|
||||
holds the sources' figures for M5 (i), mirrored in `miljo.KILDEVERDIER_M5`. Clarifications 70 to 75 hold the
|
||||
readings of chapter 17 made when its build-out was coded, and 76 to 81 those made when T was taken through
|
||||
the power system and the cash flow, both settled against an independent reader's code.
|
||||
the power system and the cash flow, and 82 to 87 those made when T and the loss of demand were taken through
|
||||
the levelised cost, ownership and scale, all settled against an independent reader's code.
|
||||
Solution T (`Losning.T_F`, `Losning.T_K`) goes through `lag_plan` (a `Trinnvisplan`) and `regn_program`
|
||||
with a module in the place of a facility (`Programresultat.P_enhet`): renewable modules have their own
|
||||
portfolio as in C, the nuclear modules of T-K share the programme's units as in B
|
||||
(`paa_felles_kjernekraft`), and S41 counts to the first unit. The factor of S51 enters the revenue and the
|
||||
disconnection arm of S47 through `regn_program(..., bortfall=...)` (`Programresultat.mu_d`; exactly one
|
||||
without a loss). `miljo.py` puts S53 (`unngaatt_utslipp`, `utslipp_med_fradrag`) and S54 (`kjolevann`)
|
||||
together over a programme for all solutions. `nivaaisert.py`, `eierskap.py` and `skala.py` refuse a result
|
||||
for T or with a loss of demand (`ks.krev_uten_tillegget`) until part 5T-4c takes chapter 17 through them.
|
||||
together over a programme for all solutions. `nivaaisert.py`, `eierskap.py` and `skala.py` take T per
|
||||
module (`res.P_enhet`, `res.reaktoreffekt(k)`, `res.antall_paa_felles(t, ...)`) and carry the factor of
|
||||
S51 per vintage in S19, S27, S31 and S42; the rules of M5 in `miljo.py` and the verdicts in `dommer.py`
|
||||
do not know five solutions yet (part 5T-4d).
|
||||
Present values are exactly rounded sums (`math.fsum`), never numpy dot products: those are not repeatable
|
||||
to the last digit. The run over the draws, the sensitivities and the tools of chapter 12 are not coded yet.
|
||||
to the last digit. Sums over technologies go in the plants' own order, never over a set of names: its order
|
||||
differs from run to run. The run over the draws, the sensitivities and the tools of chapter 12 are not coded yet.
|
||||
- `data/trekninger.npy` and `data/trekninger.json`: the 10 000 draws of the 91 drawn quantities, in the parameter
|
||||
file's units. `data/aarshendelser.npy` and `.json`: one uniform number per draw and year 2028–2100 for the
|
||||
export rule (own seed). Committed; every later computation reads them.
|
||||
|
|
@ -67,6 +71,7 @@ carousel, Python code, and a Claude plugin (own repo, later).
|
|||
environment. The verdicts are tested on invented outcomes per draw. `test_trinnvis.py` holds chapter 17:
|
||||
hand-computed build-outs for T-F and T-K, and S48 to S54. `test_trinnvis_kontantstrom.py` holds T through
|
||||
the power system and the cash flow, the loss of demand, and S53 and S54 over a programme.
|
||||
`test_trinnvis_nivaaisert.py` holds T and the loss of demand through the levelised cost, ownership and scale.
|
||||
- `requirements.txt` (numpy, scipy) and `requirements-dev.txt` (pytest, ruff, mypy) pin exact versions;
|
||||
`pyproject.toml` only configures the tools (ruff `ALL`, mypy strict).
|
||||
|
||||
|
|
|
|||
11
README.md
11
README.md
|
|
@ -26,11 +26,12 @@ skal si når satsingen lønner seg, og når den ikke gjør det.
|
|||
datasenteret og inntekten (kapittel 1–3), utbyggingen (kapittel 4), kraftsystemet (kapittel 5), kontantstrømmen
|
||||
med netto nåverdi for Norge (kapittel 6), bedriftsøkonomien, eierformene, skala, miljø og dommene (kapittel
|
||||
7–11), og innlesing av parameterne og trekningene. Den trinnvise løsningen (kapittel 17) er kodet til og med
|
||||
kontantstrømmen og netto nåverdi for Norge: når hver modul starter, hvilken kraft den går på, og hva
|
||||
programmet koster og tjener år for år. Utslipp «med fradrag» og kjølevann regnes for alle løsningene, og
|
||||
lavere etterspørsel etter regnekraft kan legges inn i inntekten. Kraftkostnaden per årgang, eierformene,
|
||||
skala og dommene er ikke ført gjennom for den trinnvise løsningen ennå. Kjøringen over trekningene,
|
||||
følsomhetene og verktøyene er ikke kodet, og ingen resultater er regnet.
|
||||
skala: når hver modul starter, hvilken kraft den går på, hva programmet koster og tjener år for år, hva
|
||||
regnekrafta koster per årgang, bedriftsøkonomien, eierformene og bidraget til Norges inntekt. Utslipp «med
|
||||
fradrag» og kjølevann regnes for alle løsningene, og lavere etterspørsel etter regnekraft kan legges inn i
|
||||
alle disse størrelsene for alle løsningene. Miljømålet og dommene er ikke ført gjennom for den trinnvise
|
||||
løsningen ennå. Kjøringen over trekningene, følsomhetene og verktøyene er ikke kodet, og ingen resultater
|
||||
er regnet.
|
||||
- `data/trekninger.npy`: de 10 000 trekningene av parameterne, laget med fast frø. `data/trekninger.json` sier hva
|
||||
kolonnene er. `data/aarshendelser.npy` er en egen strøm av tilfeldige tall for eksportregelen, ett tall per
|
||||
trekning og år.
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue