HEC-RAS

[Gerald Lonon]

Have you ever combined reaches, looks good in Geometric Data Viewer, runs
with reasonable results, but the reaches are separated on the Profile Plot
? One is above the other, not abbutted.

Any ideas?

Gerald

Also, RAS asks for a downstream boundary for the upstream reach – will not carry on the calculated data for the upstream-most section of the downstr reach. What to do?

Gerald.

—
*Gerald Lonon*

PACE Engineering
P.O. Box 7561
Columbia, SC 29202
(803) 467-2853

[Anonymous]

I’m assuming you have the reaches joined at a junction? Or they should be.

If so, you have to specify the flow going through each reach. By default the water surface may not be equal at the junction on either side, you can fix this using flow optimizations in the options dropdown before running the simulation. Also there are tolerances in the same dropdown.

[Gerald Lonon]

Return-Path:
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
by sloti1d2t14 (Cyrus 3.1.6-731-g19d3b16-fmstable-20190627v1) with LMTPA;
Wed, 03 Jul 2019 23:14:43 -0400
X-Cyrus-Session-Id: sloti1d2t14-1562210083-723330-2-8991936152670494392
X-Sieve: CMU Sieve 3.0
X-Spam-known-sender: no
X-Spam-score: 0.1
X-Spam-hits: FREEMAIL_FROM 0.001, HTML_MESSAGE 0.001, ME_ZS_CLEAN -0.001,
RCVD_IN_DNSWL_NONE -0.0001, SPF_HELO_NONE 0.001, SPF_PASS -0.001,
URI_HEX 0.1, LANGUAGES en, BAYES_USED none, SA_VERSION 3.4.2
X-Spam-source: IP=’209.85.160.180′, Host=’mail-qt1-f180.google.com’, Country=’US’,
FromHeader=’com’, MailFrom=’com’
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 mx6 ([10.202.2.205])
by compute1.internal (LMTPProxy); Wed, 03 Jul 2019 23:14:43 -0400
Received: from mx6.messagingengine.com (localhost [127.0.0.1])
by mailmx.nyi.internal (Postfix) with ESMTP id DFA7BA20115
for ; Wed, 3 Jul 2019 23:14:42 -0400 (EDT)
Received: from mx6.messagingengine.com (localhost [127.0.0.1])
by mx6.messagingengine.com (Authentication Milter) with ESMTP
id B698920FEAE;
Wed, 3 Jul 2019 23:14:42 -0400
ARC-Seal: i=1; a=rsa-sha256; cv=none; d=messagingengine.com; s=fm3; t=
1562210082; b=UTLDqFA8GeK99j+B0021u+Umw9eJvgc0jBlu/L1dhqrUv81ler
GqkQbhNxzL7MPgO5oyYUlCLcyfjDbsFnLZ3F4Ox1rq+dA5f+FFp8C8Y+k/Mb+2UO
9cTka3S3wGpwJTt9e5qh5q2TEK6RsDLhIXbA6+pECjz/274UAD1qgnV1EVMIb1s/
BK2eKD7frvRyc05RDxuZuefwvG5X3GIzLZ6Sg/QnSLU76wnwfAiFjglaZcookao8
4egsNIXKqo9KCj6i5T3/PXWeZ6HeqFlvOEDVPb6m80JNETj/QMYVWZU+pjOJKw5Q
i7DsCa6Nxxmy39uLt0/qZYZyUKnDj/WKWwkQ==
ARC-Message-Signature: i=1; a=rsa-sha256; c=relaxed/relaxed; d=
messagingengine.com; h=mime-version:references:in-reply-to:from
:date:message-id:subject:to:content-type; s=fm3; t=1562210082;
bh=VOTLB0Oz4y5fn9g5FCV2KUUZsGrlzajGCWy4yJA0XDE=; b=C2vHOSROIvQ5
K3/PKcWQpslo6X2PXTe+79R+i5d/xsy6wSg5ixgd89UwwNzjI+L3LwpSOmFBWk0B
aCMg/YUSc6HZb6AV7kfVQJ9TMctlKJizVxcJLI6gux0SJWpksKY7sIUfkSaHvMpQ
rj1JTnoo/oqApAG789n8ufYTY6cZrwsTvpFvzT3UEXPp9/pMKh/awOehyjhyclzl
rMK6dqLbTJ+wzSvY7U3ausVdZvFXIe/PdiL+ldhCPDbrUOJRkiAAQgLhNS3g58k8
T6kjkVGAyvd5gjcyIhe2YxcWZXWF3sOUyPVbZTj6efphrhTNxBtywGr8E6NQZOZz
Rb9u+Tl51w==
ARC-Authentication-Results: i=1; mx6.messagingengine.com; arc=none (no signatures found);
dkim=pass (2048-bit rsa key sha256) header.d=gmail.com
[email protected] header.b=Pn4DbIOE header.a=rsa-sha256
header.s=20161025 x-bits=2048;
dmarc=pass policy.published-domain-policy=none
policy.published-subdomain-policy=quarantine
policy.applied-disposition=none policy.evaluated-disposition=none
(p=none,sp=quarantine,d=none,d.eval=none) policy.policy-from=p
header.from=gmail.com;
iprev=pass smtp.remote-ip=209.85.160.180 (mail-qt1-f180.google.com);
spf=pass [email protected]
smtp.helo=mail-qt1-f180.google.com;
x-aligned-from=pass (Address match);
x-google-dkim=pass (2048-bit rsa key) header.d=1e100.net
[email protected] header.b=FokjMq8g;
x-ptr=pass smtp.helo=mail-qt1-f180.google.com
policy.ptr=mail-qt1-f180.google.com;
x-return-mx=pass header.domain=gmail.com policy.is_org=yes
(MX Records found: alt4.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com);
x-return-mx=pass smtp.domain=gmail.com policy.is_org=yes
(MX Records found: alt4.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com);
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: mx6.messagingengine.com;
arc=none (no signatures found);
dkim=pass (2048-bit rsa key sha256) header.d=gmail.com
[email protected] header.b=Pn4DbIOE header.a=rsa-sha256
header.s=20161025 x-bits=2048;
dmarc=pass policy.published-domain-policy=none
policy.published-subdomain-policy=quarantine
policy.applied-disposition=none policy.evaluated-disposition=none
(p=none,sp=quarantine,d=none,d.eval=none) policy.policy-from=p
header.from=gmail.com;
iprev=pass smtp.remote-ip=209.85.160.180 (mail-qt1-f180.google.com);
spf=pass [email protected]
smtp.helo=mail-qt1-f180.google.com;
x-aligned-from=pass (Address match);
x-google-dkim=pass (2048-bit rsa key) header.d=1e100.net
[email protected] header.b=FokjMq8g;
x-ptr=pass smtp.helo=mail-qt1-f180.google.com
policy.ptr=mail-qt1-f180.google.com;
x-return-mx=pass header.domain=gmail.com policy.is_org=yes
(MX Records found: alt4.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com);
x-return-mx=pass smtp.domain=gmail.com policy.is_org=yes
(MX Records found: alt4.gmail-smtp-in.l.google.com,alt3.gmail-smtp-in.l.google.com,alt1.gmail-smtp-in.l.google.com,gmail-smtp-in.l.google.com,alt2.gmail-smtp-in.l.google.com);
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
NjkzJmNvZGU9WjJWc2IyNXZia0JuYldGcGJDNWpiMjE4TnpZNU0zd3RPRGd6TlRJeE1qUT
U
X-ME-VSCause: gggruggvucftvghtrhhoucdtuddrgeduvddrfedugdeikecutefuodetggdotefrodftvf
curfhrohhfihhlvgemucfhrghsthforghilhdpggftfghnshhusghstghrihgsvgdpuffr
tefokffrpgfnqfghnecuuegrihhlohhuthemuceftddtnecunecujfgurhepgghfjgfhff
fkuffvtgesrgdtreertddtjeenucfhrhhomhepifgvrhgrlhguucfnohhnohhnuceoghgv
lhhonhhonhesghhmrghilhdrtghomheqnecuffhomhgrihhnpehnrggssghlvgdrtghomh
enucfkphepvddtledrkeehrdduiedtrddukedtnecurfgrrhgrmhepihhnvghtpedvtdel
rdekhedrudeitddrudektddphhgvlhhopehmrghilhdqqhhtuddqfhdukedtrdhgohhogh
hlvgdrtghomhdpmhgrihhlfhhrohhmpeeoghgvlhhonhhonhesghhmrghilhdrtghomheq
ucfukfgkgfepjedvfeelnecuvehluhhsthgvrhfuihiivgeptd
X-ME-VSScore: 0
X-ME-VSCategory: clean
X-ME-ZSResult: clean
Received-SPF: pass
(gmail.com … _spf.google.com: Sender is authorized to use ‘[email protected]’ in ‘mfrom’ identity (mechanism ‘include:_netblocks.google.com’ matched))
receiver=mx6.messagingengine.com;
identity=mailfrom;
envelope-from=”[email protected]”;
helo=mail-qt1-f180.google.com;
client-ip=209.85.160.180
Received: from mail-qt1-f180.google.com (mail-qt1-f180.google.com [209.85.160.180])
(using TLSv1.2 with cipher ECDHE-RSA-AES128-GCM-SHA256 (128/128 bits))
(No client certificate requested)
by mx6.messagingengine.com (Postfix) with ESMTPS
for ; Wed, 3 Jul 2019 23:14:40 -0400 (EDT)
Received: by mail-qt1-f180.google.com with SMTP id h21so4434313qtn.13
for ; Wed, 03 Jul 2019 20:14:40 -0700 (PDT)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20161025;
h=mime-version:references:in-reply-to:from:date:message-id:subject:to;
bh=VOTLB0Oz4y5fn9g5FCV2KUUZsGrlzajGCWy4yJA0XDE=;
b=Pn4DbIOEdzdKijjgv7gjGnUWxRVApGF0j9QY5PtvXNMGKaGFL7a0YkvS3OWUUpjBvf
uiCP0vDlCDWwnpDa3gR4ieNqBPz0MLgk6Pq5Ss5uqyQ3+fkseXY+YJjtXTRj2in5WW9Y
s9cm9im3Kzz4lVLQXYsPFl+E0Zmm3RuKHF9uhu35JtBQxv/MyKl8C7zpxT489bG7KAM4
0MuKZgfep92IZe0zWz0ilD6tEJJInm8kwnJBHIQLSGHpqv+ZECza9GXmuRx+zLP317Iq
rr9jFwi/T1WK+2UrqVZuVukcT/lE9CpQm2vZRFVudWmz7OEzK1funOqg8f9AAUg8u/HX
iL+A==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20161025;
h=x-gm-message-state:mime-version:references:in-reply-to:from:date
:message-id:subject:to;
bh=VOTLB0Oz4y5fn9g5FCV2KUUZsGrlzajGCWy4yJA0XDE=;
b=FokjMq8gj/NuqTaBsyAcn/PlRmHd0MxK7EsQi2sOGklqeZWzzzzHLZPJMwp3Mm4WY2
RTo3MH6PqP9A1/Mo+f3dIgscIFSi6J+3beR+DWm5yEDbhpCu8TuCRR1PtQ81unfoY7yn
CUNXSYS7D+zcfdhF/KQeeVPVutTM4V1oNYO20SmX8jV5w3BWFOZbGgsUYWf1VZFfP5Ji
2RwvTCnu26WQB9FeU5aK24rsVQ43a3FS/fzZ2AYJD0o/OYg81KvxlX7IzkNlHDyjy8Uq
/8C6hNdVLGT9I4lWUOPE+oBUyei7bY934ZVMikmW+QB3jjuQ21FTAA2jP+nKp+yexudK
EqIQ==
X-Gm-Message-State: APjAAAWrxERRMdP4nfcazhd8U6ZCLuoKnU7TR0ZvPMVKcyBiEr0aDDN1
FfR+aw5lLBZGl1bvnQebw9dJuFsArWtDI/+qmB4rWQ==
X-Google-Smtp-Source: APXvYqyQ8EPISXj1vvzj3yzXv5js+ZOlkh2ogyX0aTLaMXE9hxf2zjgxpc/yRHEvydPSj5BIOcl6f24IgHq9k9ohlvw=
X-Received: by 2002:ac8:1888:: with SMTP id s8mr33139073qtj.190.1562210078278;
Wed, 03 Jul 2019 20:14:38 -0700 (PDT)
MIME-Version: 1.0
References:
<[email protected]>
In-Reply-To: <[email protected]>
From: Gerald Lonon
Date: Wed, 3 Jul 2019 23:14:24 -0400
Message-ID:
Subject: Re: HEC-RAS
To: “Derek [via HEC-RAS Help]”
Content-Type: multipart/alternative; boundary=”000000000000c7c9e6058cd260dc”

–000000000000c7c9e6058cd260dc
Content-Type: text/plain; charset=”UTF-8″
Content-Transfer-Encoding: quoted-printable

Derek,

Joined them at a new junction, then deleted the junction.

It is steady flow, same discharge both reaches. So the water surface
calculated for the upstreammost section of the downstream reach can’t be
carried on to the upstream reach?

Thanks, Gerald

On Wed, Jul 3, 2019 at 9:29 PM Derek [via HEC-RAS Help] < [email protected]> wrote:

> I’m assuming you have the reaches joined at a junction? Or they should be=
.
>
> If so, you have to specify the flow going through each reach. By default
> the water surface may not be equal at the junction on either side, you ca=
n
> fix this using flow optimizations in the options dropdown before running
> the simulation. Also there are tolerances in the same dropdown.
>
> ——————————
> If you reply to this email, your message will be added to the discussion
> below:
> http://hec-ras-help.1091112.n5.nabble.com/HEC-RAS-tp7693p7731.html
> To unsubscribe from HEC-RAS, click here
> <http://hec-ras-help.1091112.n5.nabble.com/template/NamlServlet.jtp?macro=
=3Dunsubscribe_by_code&node=3D7693&code=3DZ2Vsb25vbkBnbWFpbC5jb218NzY5M3wtO=
DgzNTIxMjQ5>
> .
> NAML
> <http://hec-ras-help.1091112.n5.nabble.com/template/NamlServlet.jtp?macro=
=3Dmacro_viewer&id=3Dinstant_html%21nabble%3Aemail.naml&base=3Dnabble.naml.=
namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabble.v=
iew.web.template.NodeNamespace&breadcrumbs=3Dnotify_subscribers%21nabble%3A=
email.naml-instant_emails%21nabble%3Aemail.naml-send_instant_email%21nabble=
%3Aemail.naml>
>

–=20
*Gerald Lonon*

PACE Engineering
P.O. Box 7561
Columbia, SC 29202
(803) 467-2853

–000000000000c7c9e6058cd260dc
Content-Type: text/html; charset=”UTF-8″
Content-Transfer-Encoding: quoted-printable

Derek,

Joined them at a new junction, t=
hen deleted the junction.

It is steady flow, same di=
scharge both reaches.=C2=A0 So the water surface calculated for the upstrea=
mmost section of the downstream reach can't be carried on to the upstre=
am reach?

Thanks, Gerald

On Wed, Jul 3, 2019 at 9:29 PM Derek [via HEC-RAS Help]=
<ml+s1091112n773=
[email protected]> wrote:

" style=3D"margin:0px 0px 0px 0.8ex;border-left:1px solid rgb(204,204,204);= padding-left:1ex">

I'm assuming you have the reaches joined at a junction? Or they should=
be.

If so, you have to specify the flow going through each reach. By de=
fault the water surface may not be equal at the junction on either side, yo=
u can fix this using flow optimizations in the options dropdown before runn=
ing the simulation. Also there are tolerances in the same dropdown.

=09
=09
=09

---

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

http://hec-ras-help.1091112.n5.nabble.com/HEC-RAS-t=
p7693p7731.html

=09
To unsubscribe from HEC-RAS, click here.
NAML

—

Gerald Lonon

PACE Engineering
P.O. Box 7561
Columbia=
, SC 29202
(803) 467-2853

–000000000000c7c9e6058cd260dc–

[Author]

Posts