Skip to content

fix(dfns): accept boundname as ID2 for LAK/MAW connection observations - #382

Merged
wpbonelli merged 1 commit into
MODFLOW-ORG:developfrom
wpbonelli:obs-id2-boundname
Oct 6, 2026
Merged

wpbonelli merged 1 commit into
MODFLOW-ORG:developfrom
wpbonelli:obs-id2-boundname

Conversation

@wpbonelli

Copy link
Copy Markdown
Member

MF6 accepts ID BOUNDNAME for LAK's lak, wetted-area and conductance and MAW's maw and conductance obstypes, observing the boundname and ignores the number. The test042 and test045 lake models use this form (e.g. L2WA WETTED-AREA 2 ELAKE02)

  • add _connection_or_name, a union of three forms: feature and connection, feature and boundname, or boundname alone
  • keep the two-form union for LKT, MWT and MWE
  • name records after all their fields (ifno_iconn, ifno_boundname) so arms of the same union get distinct names

…vations

MF6 accepts a feature number followed by a boundname for LAK's lak,
wetted-area and conductance and MAW's maw and conductance obstypes,
observing the boundname and ignoring the number. Add that form as a
third union arm. LKT, MWT and MWE read ID2 as a number only, so they
keep the two-form union.

Name records after all their fields (e.g. ifno_iconn, ifno_boundname)
so records that are arms of the same union get distinct names.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@wpbonelli wpbonelli added this to the 1.10.0 milestone Oct 6, 2026
@wpbonelli wpbonelli added the bug Something isn't working label Oct 6, 2026
@wpbonelli
wpbonelli marked this pull request as ready for review October 6, 2026 13:46
@wpbonelli
wpbonelli merged commit 9745da2 into MODFLOW-ORG:develop Oct 6, 2026
15 checks passed
@wpbonelli
wpbonelli deleted the obs-id2-boundname branch October 6, 2026 13:47
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bug Something isn't working

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant