docs: describe M5 and the verdicts for five solutions and the sensitivities that are switches
Co-Authored-By: Claude Fable 5.2 <noreply@anthropic.com>
This commit is contained in:
parent
88dfb1ce03
commit
64d24c7800
3 changed files with 40 additions and 14 deletions
13
CHANGELOG.md
13
CHANGELOG.md
|
|
@ -108,3 +108,16 @@ All notable changes to this project will be documented in this file.
|
|||
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.
|
||||
- M5 and the verdicts for five solutions (`miljo.py`, `dommer.py`): T-F meets M5 (i) and (ii) by definition
|
||||
and T-K is judged as nuclear power; the ladder, part I and M7 cover A, B, C, T-F and T-K, and in M7 A must
|
||||
beat each of the four others that can be built. Three sensitivities of chapter 17.8 are switches: full
|
||||
displacement in the first stage (`regn_program(..., full_fortrengning_i_forste_trinn=True)`), new renewable
|
||||
power first from 2031 for C and T (`lag_plan(..., ny_kraft_fra=2031)`), and modules of 50 and 200 MW
|
||||
(`Inndata.med`). Next to S54 the withdrawal of water is also given with sea water only for the nuclear
|
||||
production the data centres themselves use. With the switches off every figure for all seven solutions is
|
||||
unchanged to the last digit. A new independent reader coded the same from the specification alone: about
|
||||
400 000 comparisons of M5 and the verdicts on invented outcomes per draw, and 2 523 made-up paths with
|
||||
10.1 million figures through both codes for the sensitivities, without a difference. Seven clarifications
|
||||
(88–94) in chapter 16 say how the text is read; one of them (93, what the condition is when M5 holds under
|
||||
conditions) is a proposal put to the project owner and not settled
|
||||
(`modell/fagfellevurdering-utkast-2-og-3.md`, part 13). No result has been computed.
|
||||
|
|
|
|||
26
CLAUDE.md
26
CLAUDE.md
|
|
@ -18,9 +18,9 @@ carousel, Python code, and a Claude plugin (own repo, later).
|
|||
avoided emissions and cooling water).
|
||||
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, the cash
|
||||
flow, the levelised cost, ownership and scale, and S48–S54 are coded; T through M5 and the verdicts is not).
|
||||
- `modell/spesifikasjon.md`: the model specification (equations S1–S54; chapter 17, the addition to the
|
||||
direction, is coded all the way: solution T through the build-out, the power system, the cash flow, the
|
||||
levelised cost, ownership, scale, M5 and the verdicts, and S48–S54).
|
||||
`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).
|
||||
|
|
@ -48,7 +48,10 @@ carousel, Python code, and a Claude plugin (own repo, later).
|
|||
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, 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.
|
||||
the levelised cost, ownership and scale, and 88 to 94 those made when M5 and the verdicts were coded for
|
||||
five solutions and three sensitivities of chapter 17.8 as switches, all settled against an independent
|
||||
reader's code. Clarification 93 (which conditions can be named when M5 holds under conditions) is a proposal
|
||||
the operator has not decided; `dommer.del_I` takes the answer as an argument.
|
||||
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
|
||||
|
|
@ -57,11 +60,18 @@ carousel, Python code, and a Claude plugin (own repo, later).
|
|||
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` 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).
|
||||
S51 per vintage in S19, S27, S31 and S42. The ladder, part I and M7 in `dommer.py` cover the five
|
||||
solutions of `DOMSLOSNINGER` (A, B, C, T-F, T-K; `a_er_best` and `dom_m7` take the net present values per
|
||||
solution); M5 in `miljo.py` holds by definition for T-F and judges T-K as nuclear power. Three
|
||||
sensitivities of chapter 17.8 are switches: `regn_program(..., full_fortrengning_i_forste_trinn=True)`
|
||||
(`Programresultat.delta_V(inn, k)` is then one for the first-stage modules), `lag_plan(...,
|
||||
ny_kraft_fra=2031)` for C and T, and `inn.med({"P_m": 50.0})` for the module size. With the switches off
|
||||
every figure is unchanged to the last digit. `miljo.kjolevann` also gives the withdrawal with sea water
|
||||
only for the nuclear production the data centres themselves use (`uttak_egen_bruk`, clarification 92).
|
||||
Present values are exactly rounded sums (`math.fsum`), never numpy dot products: those are not repeatable
|
||||
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.
|
||||
differs from run to run. The run over the draws, the other 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.
|
||||
|
|
@ -72,6 +82,8 @@ carousel, Python code, and a Claude plugin (own repo, later).
|
|||
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.
|
||||
`test_trinnvis_dommer.py` holds M5 and the verdicts for five solutions on invented outcomes, the three
|
||||
sensitivities that are switches (hand-computed build-outs), and the water for the data centres' own use.
|
||||
- `requirements.txt` (numpy, scipy) and `requirements-dev.txt` (pytest, ruff, mypy) pin exact versions;
|
||||
`pyproject.toml` only configures the tools (ruff `ALL`, mypy strict).
|
||||
|
||||
|
|
|
|||
15
README.md
15
README.md
|
|
@ -25,13 +25,14 @@ skal si når satsingen lønner seg, og når den ikke gjør det.
|
|||
- `src/tokenfabrikker/`: koden. Én funksjon per ligning, med samme nummer som i spesifikasjonen: kraftverket,
|
||||
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
|
||||
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.
|
||||
7–11), og innlesing av parameterne og trekningene. Den trinnvise løsningen (kapittel 17) er kodet gjennom
|
||||
hele modellen: 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, bidraget til Norges inntekt, miljømålet
|
||||
og dommene, som nå gjelder fem løsninger. 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. Tre av
|
||||
følsomhetene for den trinnvise løsningen er kodet som brytere: full fortrengning i første trinn, moduler på
|
||||
50 og 200 MW, og ny fornybar kraft først fra 2031. Kjøringen over trekningene, resten av 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