Storage Area inline with reach

[WeimsGuy]

I have a dam breach project with a lake inline within a reach and a dam at the downstream end of the lake. There are cross sections in the area of the lake on the reach, but they to not adequately represent the storage capacity of the lake. Rather than adding and adjusting and adding more cross sections, I want to use a Storage Area with a elevation capacity curve. I need the reach to continue to supply the inflow from a flow hydrograph from upstream reach. I am currently trying to model eliminating the upstream reach, creating as storage area for the lake, and adding a lateral structure for the inflow. The problems I am having are attaching the lateral structure to the SA (I think I need another cross section in the SA), and that the inflow from the lateral structure might be affected by the backwater effect of the lake elevation rising. Once the dam breaches, I need the lake to empty while still receiving any more inflow based on the hydrograph.

Any thoughts or recommendations would by most welcome.

[Anonymous]

From what you describe, I think you want to use an inline structure, not a lateral structure. Create the storage area to represent the lake. Connect the downstream reach directly to this storage area and have an inline structure on the reach to represent the dam. There needs to be two cross sections between the storage area and the inline structure. These should be giant, ‘dam sized’ cross sections. The inflow can be put directly into the storage area.

If you find the 1D unsteady example data sets, there is a Dam Breaching data set. Open it up and look at the ‘PMF with SA and Von Thun Breach’ plan. This shows what I am trying to describe.

[WeimsGuy]

I looked at those examples, but did not really find the same situation I have. I will however go back over all the SA/Lateral Structures to try to understand the relationships better. I have attached (hopefully) screen clips of the two geometries I am trying to use. Thanks for your reply.

[Anonymous]

Ok, so it isn’t clear to me what you are having a problem with. Is the first (top) screen shot the geometry you are trying to use? You should be able to attach the inflow hydrograph directly to the storage area and the breach the inline structure that is acting at the dam.

I’m not clear on where or why you would have a lateral structure.

If you wanted/needed to model part of the reach upstream of the lake, I don’t see any immediate reason why the second (bottom) screen shot wouldn’t work.

[WeimsGuy]

Return-Path:
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
by sloti1d2t14 (Cyrus 3.1.5-832-gba113d7-fmstable-20190201v1) with LMTPA;
Fri, 08 Feb 2019 14:32:06 -0500
X-Cyrus-Session-Id: sloti1d2t14-1549654326-3609367-2-12233008012389471502
X-Sieve: CMU Sieve 3.0
X-Spam-known-sender: no
X-Spam-score: 1.3
X-Spam-hits: FREEMAIL_FROM 0.001, HTML_MESSAGE 0.001, ME_ZS_CLEAN -0.001,
RCVD_IN_DNSWL_NONE -0.0001, URI_HEX 1.313, LANGUAGES en, BAYES_USED none,
SA_VERSION 3.4.2
X-Spam-source: IP=’66.163.191.206′, Host=’sonic312-25.consmr.mail.ne1.yahoo.com’,
Country=’US’, FromHeader=’net’, MailFrom=’net’
X-Spam-charsets: plain=’UTF-8′, html=’UTF-8′
X-Resolved-to: [email protected]
X-Delivered-to: [email protected]
X-Mail-from: [email protected]
Received: from mx2 ([10.202.2.201])
by compute1.internal (LMTPProxy); Fri, 08 Feb 2019 14:32:06 -0500
Received: from mx2.messagingengine.com (localhost [127.0.0.1])
by mailmx.nyi.internal (Postfix) with ESMTP id AC213D8C71
for ; Fri, 8 Feb 2019 14:32:05 -0500 (EST)
Received: from mx2.messagingengine.com (localhost [127.0.0.1])
by mx2.messagingengine.com (Authentication Milter) with ESMTP
id 6876321BEC8;
Fri, 8 Feb 2019 14:32:05 -0500
ARC-Seal: i=1; a=rsa-sha256; cv=none; d=messagingengine.com; s=fm2; t=
1549654325; b=Lx8EDX9X8jK7kiCiJ8zV5pflY+bWRUUxJrdOkzI8Bdp9KNv+Sy
sdHsdynaCr1vHARcElV3usXwN69c2j0T0Sfx9rVOOMrTo7ibrXn+EHkLUpQDWb42
UPcr/pFbKhk59tg9t35Wtnn9t/Y6rWXh44FKgsB3xif+Hr2dhc9gMewO+Ka4japy
+h/8ndaiBuwkPJlVwAhKQZM/nd12itO4PuJnzWDlkGMm8S/Mmz66/Q2W/JUM5VnJ
oijzpZF9OM9kOD0ssgOaQQIhrPd4VdRt0Vo8RTm3IzViXIkSGuRV0dGKATW/lSPX
V+1UMEAvHQBi980LqS4Ad8ZlYzhfJtUvkCkQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=date:from:reply-to:to:message-id
:in-reply-to:references:subject:mime-version:content-type; s=
fm2; t=1549654325; bh=KVNazXolKsCu1BD8FFh84zOqifvbd8D8YBhJVBy+q1
M=; b=Avd2YhjzuSIttbcX0LeW1ua/98v+9voFttMYCN3mNIK3HqbOPfba6WYgoF
fNxNdH5RKHO0wgoaKsCcvb0eZxUCkBMSxIJhHMhxOOV00PYxtIZGUM7Hs0484tL8
lZcB0L0n6QcMUuDkDQBqGgeEj48rStQ7P9yvbHbJWm2+WrZ9mVjhpVTSJkR/WIdi
Omh/CI28aNibBTd5YKF74bRVdV4YLB5FFjOTAlu2M+8nEp7RwDPXtGXtXVRDf+hE
PLHAAvst2ZC6p+TkkhutSumF8T2fXv9l3bm/lUhS2uqIWjdA1m0Sg8RIc7bHrVGg
lmL58kyEDxxzjrzviyg9twMU7jGQ==
ARC-Authentication-Results: i=1; mx2.messagingengine.com; arc=none (no signatures found);
dkim=pass (1024-bit rsa key sha256) header.d=att.net [email protected]
header.b=A9Gj0YCe header.a=rsa-sha256 header.s=s1024 x-bits=1024;
dmarc=none policy.published-domain-policy=none
policy.applied-disposition=none policy.evaluated-disposition=none
(p=none,d=none,d.eval=none) policy.policy-from=p header.from=att.net;
iprev=pass smtp.remote-ip=66.163.191.206
(sonic312-25.consmr.mail.ne1.yahoo.com);
spf=none [email protected]
smtp.helo=sonic312-25.consmr.mail.ne1.yahoo.com;
x-aligned-from=pass (Address match);
x-ptr=pass smtp.helo=sonic312-25.consmr.mail.ne1.yahoo.com
policy.ptr=sonic312-25.consmr.mail.ne1.yahoo.com;
x-return-mx=pass header.domain=att.net policy.is_org=yes
(MX Record found);
x-return-mx=pass smtp.domain=att.net policy.is_org=yes
(MX Record found);
x-tls=pass smtp.version=TLSv1.2 smtp.cipher=ECDHE-RSA-AES128-GCM-SHA256
smtp.bits=128/128;
x-vs=clean score=0 state=0;
x-zs=clean
Authentication-Results: mx2.messagingengine.com;
arc=none (no signatures found);
dkim=pass (1024-bit rsa key sha256) header.d=att.net [email protected]
header.b=A9Gj0YCe header.a=rsa-sha256 header.s=s1024 x-bits=1024;
dmarc=none policy.published-domain-policy=none
policy.applied-disposition=none policy.evaluated-disposition=none
(p=none,d=none,d.eval=none) policy.policy-from=p header.from=att.net;
iprev=pass smtp.remote-ip=66.163.191.206
(sonic312-25.consmr.mail.ne1.yahoo.com);
spf=none [email protected]
smtp.helo=sonic312-25.consmr.mail.ne1.yahoo.com;
x-aligned-from=pass (Address match);
x-ptr=pass smtp.helo=sonic312-25.consmr.mail.ne1.yahoo.com
policy.ptr=sonic312-25.consmr.mail.ne1.yahoo.com;
x-return-mx=pass header.domain=att.net policy.is_org=yes
(MX Record found);
x-return-mx=pass smtp.domain=att.net policy.is_org=yes
(MX Record found);
x-tls=pass smtp.version=TLSv1.2 smtp.cipher=ECDHE-RSA-AES128-GCM-SHA256
smtp.bits=128/128;
x-vs=clean score=0 state=0;
x-zs=clean
X-ME-VSSU: VW5zdWI9aHR0cDovL2hlYy1yYXMtaGVscC4xMDkxMTEyLm41Lm5hYmJsZS5jb20vdGVtcG
xhdGUvTmFtbFNlcnZsZXQuanRwP21hY3JvPXVuc3Vic2NyaWJlX2J5X2NvZGUmbm9kZT03
MTQ1JmNvZGU9UjI5dlpHVklaV3h3UUdGMGRDNXVaWFI4TnpFME5YdzJOVGczTXpVd05ETT
0
X-ME-VSCause: gggruggvucftvghtrhhoucdtuddrgedtledrledvgdduvdekucetufdoteggodetrfdotf
fvucfrrhhofhhilhgvmecuhfgrshhtofgrihhlpdggtfgfnhhsuhgsshgtrhhisggvnecu
uegrihhlohhuthemuceftddtnecunecujfgurhepfffhrhfvkfgjfhfugggtofesrgdtsg
gsredtjeenucfhrhhomhepifhoohguvgcujfgvlhhpuceoghhoohguvghhvghlphesrght
thdrnhgvtheqnecuffhomhgrihhnpehnrggssghlvgdrtghomhenucfkphepieeirdduie
efrdduledurddvtdeinecurfgrrhgrmhepihhnvghtpeeiiedrudeifedrudeluddrvddt
iedphhgvlhhopehsohhnihgtfeduvddqvdehrdgtohhnshhmrhdrmhgrihhlrdhnvgdurd
ihrghhohhordgtohhmpdhmrghilhhfrhhomhepoehgohhouggvhhgvlhhpsegrthhtrdhn
vghtqeenucevlhhushhtvghrufhiiigvpedt
X-ME-VSScore: 0
X-ME-VSCategory: clean
X-ME-ZSResult: clean
Received-SPF: none
(att.net: No applicable sender policy available)
receiver=mx2.messagingengine.com;
identity=mailfrom;
envelope-from=”[email protected]”;
helo=sonic312-25.consmr.mail.ne1.yahoo.com;
client-ip=66.163.191.206
Received: from sonic312-25.consmr.mail.ne1.yahoo.com (sonic312-25.consmr.mail.ne1.yahoo.com [66.163.191.206])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by mx2.messagingengine.com (Postfix) with ESMTPS
for ; Fri, 8 Feb 2019 14:32:04 -0500 (EST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=att.net; s=s1024; t=1549654322; bh=KVNazXolKsCu1BD8FFh84zOqifvbd8D8YBhJVBy+q1M=; h=Date:From:Reply-To:To:In-Reply-To:References:Subject:From:Subject; b=A9Gj0YCeYSKeRILqGZcv31198N3EBaNH/RjhGAp6ncFX/HkMVEBRdZ8/0iienQfkp/iCjqwtQb1tVfDOziT2mrxrio78TlzdR/C3p/rrYIDq74Iro+fqqMIB7m0ap0DI6Zfy7jzmL1TxW0wJwrEdYKgI72cGPr9lfC8SKt2kF1U=
X-YMail-OSG: jI._qk4VM1lflnMRSdvYCvFbTKf7nQBowmkXyOVIKocUguFPWutVYjIgq8qHvBb
z2xXVQJ2dLWMnHORhkyHboSZmm08P1zK7libwuaJxLllf_aN_svOI0GBGJv1tYve3fXs4OC3xOOz
rsNxvPclGisOpK2PJmyC2PuP39Ky7DjiU6VmnQkckAbjZse9v4Kd2pVGp3z7C4ZswaJIIJF7udJJ
z40IJsA9oikeLvpgIbAfWGToxLiEH_qVlved.nxAjW9um6qhdCDnDE2uJP4r.PWngxUdMyl355n8
uKC9i6M9t.aXJH1LUAO4OHelnB2fT5gfCHjoxnpGCMrQXfHifAqZAjbmHoksHz3UxapWeqLviIWO
UGI64_2aZV1ZBLYtCMc5dIB7hHLgjZaodZXZ1prg5lugFXCeYKnkq0O6FMxQDVNv.xjRoUFLODNR
Eufb3sxRNduTFPIALNjAMssSns1_7LB4uDyJk75E1YDE2oGoANi.Tk8WupBM7N3Bep6KkHT14.LN
A8Fln5CmQtxflOOjBcNykQAcyTC16zP4z2Rd.W_ZS5uUZqD0TVMJWTVFbM5r.7YDg4OX7A_qk3Xu
CkCRtmQ4KBVrnbR492Z2_AIhn9SZQxQ0b8FFs8Gl609Vas1_LAVfzc.yY3UC65vW6Kn0qk3lfEES
._rJ6xjbMpPhUZn9oItgu5EYXUdbZ3_VZG9tRhBdFzV9zcqYsY8xgfHsU1A2D8hLffhCo_wzYrzc
sLZxpo_.Rb1AoePeOBoi7aV8yioPW8LRQu8HTas2KzgQCUFZoL2rlSDig20x8jsmRHeBn6rTSLu4
zuMOsBLmUirnJ2ERnRavG.3IFesGypxrI6665W_EsNqv9TFkottcuj8YkPKZxAKv4qIyTX3Hghl8
xbq.utHgbX3Fhvu_J6ytq7wsmW4GNoUinBz9A7I6lPd0z1tm9Jzu5_6z_MevCRPjV2HMZaXcFK8o
Sf87S.4FnH8XK5kNzv2maSGR2FF09Ev8XMrLXbRM9w06AD.xm7nIJyHt49RnxFiwW_oBYRPDCbnI
XNJIyJzcKhZky6wD6J0yi9rntGfcHapwymd.j8cTBUHsC9hLYczTU
Received: from sonic.gate.mail.ne1.yahoo.com by sonic312.consmr.mail.ne1.yahoo.com with HTTP; Fri, 8 Feb 2019 19:32:02 +0000
Date: Fri, 8 Feb 2019 19:31:17 +0000 (UTC)
From: Goode Help
Reply-To: Goode Help
To: “jarvus [via HEC-RAS Help]”
Message-ID: <[email protected]>
In-Reply-To: <[email protected]>
References: <[email protected]> <[email protected]> <[email protected]> <[email protected]>
Subject: Re: Storage Area inline with reach
MIME-Version: 1.0
Content-Type: multipart/alternative;
boundary=”—-=_Part_562775_900057652.1549654277063″
X-Mailer: WebService/1.1.13027 YMailNorrin Mozilla/5.0 (Windows NT 6.1; Win64; x64; rv:65.0) Gecko/20100101 Firefox/65.0

——=_Part_562775_900057652.1549654277063
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: quoted-printable

I confused the lateral inflow hydrograph with the lateral structure.=C2=A0 =
I found a reference to a good article elsewhere in the forum that explained=
it very well.=C2=A0 The article was from the State of Colorado Department =
of Natural Resources Division of Water Resources – Office of the State Engi=
neer Dam Safety Branch – “Guidelines for Dam Breach Analysis”, February 10,=
2010.
Thanks for your advise.=C2=A0 I am working with the first one for now to se=
e if I can get a stable dam breach and will use the second one if required.
=20

On Friday, February 8, 2019, 1:12:14 PM CST, jarvus [via HEC-RAS Help] =
wrote: =20
=20
Ok, so it isn’t clear to me what you are having a problem with. =C2=A0Is =
the first (top) screen shot the geometry you are trying to use? =C2=A0You s=
hould be able to attach the inflow hydrograph directly to the storage area =
and the breach the inline structure that is acting at the dam.

I’m not clear on where or why you would have a lateral structure.

If you wanted/needed to model part of the reach upstream of the lake, I don=
‘t see any immediate reason why the second (bottom) screen shot wouldn’t wo=
rk.=20
=20
If you reply to this email, your message will be added to the discussion=
below: http://hec-ras-help.1091112.n5.nabble.com/Storage-Area-inline-with-=
reach-tp7145p7153.html To unsubscribe from Storage Area inline with reach=
, click here.
NAML =20
——=_Part_562775_900057652.1549654277063
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 7bit

I confused the lateral inflow hydrograph with the lateral structure.  I found a reference to a good article elsewhere in the forum that explained it very well.  The article was from the State of Colorado Department of Natural Resources Division of Water Resources – Office of the State Engineer Dam Safety Branch – “Guidelines for Dam Breach Analysis”, February 10, 2010.

Thanks for your advise.  I am working with the first one for now to see if I can get a stable dam breach and will use the second one if required.

On Friday, February 8, 2019, 1:12:14 PM CST, jarvus [via HEC-RAS Help] <[email protected]> wrote:

Ok, so it isn’t clear to me what you are having a problem with.  Is the first (top) screen shot the geometry you are trying to use?  You should be able to attach the inflow hydrograph directly to the storage area and the breach the inline structure that is acting at the dam.

I’m not clear on where or why you would have a lateral structure.

If you wanted/needed to model part of the reach upstream of the lake, I don’t see any immediate reason why the second (bottom) screen shot wouldn’t work.

---

If you reply to this email, your message will be added to the discussion below:

http://hec-ras-help.1091112.n5.nabble.com/Storage-Area-inline-with-reach-tp7145p7153.html

To unsubscribe from Storage Area inline with reach, click here.
NAML

——=_Part_562775_900057652.1549654277063–

[Author]

Posts