Skip to content
Merged
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 0 additions & 2 deletions docs/md/dfnspec.md
Original file line number Diff line number Diff line change
Expand Up @@ -942,8 +942,6 @@ fk = { path = "diversions.idv", scope = "ifno" }

Likewise `gwf-lak`'s `connectiondata.iconn` and `gwf-maw`'s `connectiondata.icon` are scoped by `ifno`. MAW's `angledata.icon` and the LAK and MAW observations' connection numbers reference them, with the same scope.

The observations' keys are deliberately stricter than MODFLOW 6, which doesn't check a connection number against the feature. It counts from the feature's first connection across the package (`lak_rp_obs`, `maw_rp_obs`), so `lak 1 58` on a lake with 57 connections runs, and observes the next lake's first connection. What the key rejects is almost certainly a mistake reported as another feature's value.

#### Key sets

A normal `fk` is written as a path because the referrer knows the target's type: `gwf-mvr`'s `pname1` always names a row of its own `packages`. When the referenced instance is picked at runtime and may be one of several component types, the referrer can't write a path. Instead, it names a **role**, and each component type that can play it says what it means, like an interface or protocol. A component declares its roles in [`keys`](#keys):
Expand Down
Loading