Welcome to the RAS Solution › Forums › HEC-RAS Help › 1D/2D FLOW ERROR. BUT THE COMPUTATION MESSAGES IS STILL RUNNING
- This topic has 9 replies, 1,156 voices, and was last updated 6 years, 3 months ago by DEL.
-
AuthorPosts
-
August 4, 2018 at 12:16 am #6993DELParticipant
Hello Everybody….
I tried to make 1D model which was developed 2D model. The massages list as follows. Maybe there is somebody could be help me.
……..
13MAR2014 19:38:55 1D/2D Flow error 256. Citarum All Ri Citarum All Re 103347
13MAR2014 19:39:05 Citarum All Ri2 Citarum All Re2 102 631.47 0.801
13MAR2014 19:39:05 Perimeter 1 Cell # 556 666.82 0.0159 1
13MAR2014 19:39:00 1D/2D Flow error -19265. Citarum All Ri2 Citarum All Re2 6685
13MAR2014 19:39:10 Citarum All Ri2 Citarum All Re2 102 631.47 0.777
13MAR2014 19:39:10 Perimeter 1 Cell # 874 665.27 11.2117 2
13MAR2014 19:39:05 1D/2D Flow error 346. Citarum All Ri Citarum All Re 103347
13MAR2014 19:39:15 Citarum All Ri2 Citarum All Re2 102 631.47 0.753
13MAR2014 19:39:15 Perimeter 1 Cell # 491 665.96 1.6099 2
13MAR2014 19:39:10 1D/2D Flow error 34350. Citarum All Ri2 Citarum All Re2 6685
……The computation is still process.. but so slowly. What’s the meaning? Thanks..
August 4, 2018 at 12:46 am #11597Scott MillerParticipant1D/2D errors are normal. It is the flow that does not pass between the areas, and will cause a difference in water surface elevation. By default there are no iterations across the 1D/2D boundary. The magnitude of the flow error can be reduced by adding iterations. A threshold for acceptable flow error can also be set.
2D can be very slow. Provide more information about how your model is configured – maybe a detail of the geometry.
August 4, 2018 at 2:17 am #11598DELParticipantReturn-Path:
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
by sloti1d2t14 (Cyrus 3.1.5-11-g6b5e7b6-fmstable-20180717v1) with LMTPA;
Fri, 03 Aug 2018 18:18:04 -0400
X-Cyrus-Session-Id: sloti1d2t14-416454-1533334684-2-4919043262560644344
X-Sieve: CMU Sieve 3.0
X-Spam-known-sender: no
X-Spam-score: 2.9
X-Spam-hits: FREEMAIL_FROM 0.001, HTML_MESSAGE 0.001, ME_BETA_RULES 0.01,
RCVD_IN_DNSWL_NONE -0.0001, SPF_PASS -0.001, SUBJ_ALL_CAPS 1.625,
URI_HEX 1.313, LANGUAGES en, BAYES_USED none, SA_VERSION 3.4.0
X-Spam-source: IP=’209.85.221.51′, Host=’mail-wr1-f51.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 mx2 ([10.202.2.201])
by compute1.internal (LMTPProxy); Fri, 03 Aug 2018 18:18:04 -0400
Received: from mx2.messagingengine.com (localhost [127.0.0.1])
by mailmx.nyi.internal (Postfix) with ESMTP id 7EFFAD8AAF
for; Fri, 3 Aug 2018 18:18:03 -0400 (EDT)
Received: from mx2.messagingengine.com (localhost [127.0.0.1])
by mx2.messagingengine.com (Authentication Milter) with ESMTP
id BBF7C708D64;
Fri, 3 Aug 2018 18:18:03 -0400
ARC-Seal: i=1; a=rsa-sha256; cv=none; d=messagingengine.com; s=fm3; t=
1533334683; b=ifQihsDozeq902p4F3h0cLD2unxqCRoa8FWqdSA/gzniz8NBBl
ynkYve9Dlb23R3nfeh4TztU2DYD8oeZWBIz+dMv/8c7BSPnFl50vuOmVt1Pc490I
3zm6eZasKdvKoQuHlErAu/QxOsx6PeaMmtS8CXc0Q/+0yfk4CkJ+REeTmFxA7z6h
qzRpw1ez5RX5GwovJHThChrL6Z9veL4CzP3ljjW8NrpT0PXGFEEL1flxURYIhAZe
pz2o3+9tS+PDaIntMIkFa7py/X6z07RZUYWd47IlhRUTH10Cd+ljcPmDRCzfRJ8R
r+9Nhrs2lKO4htJHJiEEbkLH7Ck9FiCct7Bg==
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=1533334683;
bh=CGI+3HsseE4Goov1McIic2Y7VQLGoSqt8+r/BY++XVQ=; b=NIWtGApVB9ti
CLLN4tfKx1ZTx+jBqRTe1SZn5a1UUSn9gNDxtwruAb0lPa1uFHq8zURSh7qanlmq
mBLIwPhVadbdPzvY1PoODuAP1uIPznNrai9L5OaCWMsIMvDG9tAo1dcZTbZ0Zfnc
jcMpsqptLC1nzKi34N83loXrojs4PV96MLNOi2pdwZi+2svuBWKIBxSdHQbh9PH3
ZQyZDAf4w7vnwv250MjdLpYstIT/nuowVbTWbU+jeT6Mwv716KHpIb9ZlqP16XLX
342lIZYCdoeSW/aGNwT7iYErZTN6EdTF6zkTjvgeQPUbedIrT0zEuwiyjie711u8
PvhEBEoJrw==
ARC-Authentication-Results: i=1; mx2.messagingengine.com; arc=none (no signatures found);
dkim=pass (2048-bit rsa key sha256) header.d=gmail.com
[email protected] header.b=T76XUsjE header.a=rsa-sha256
header.s=20161025 x-bits=2048;
dmarc=pass (p=none,sp=quarantine,d=none) header.from=gmail.com;
iprev=pass policy.iprev=209.85.221.51 (mail-wr1-f51.google.com);
spf=pass [email protected]
smtp.helo=mail-wr1-f51.google.com;
x-aligned-from=pass (Address match);
x-cm=none score=0;
x-google-dkim=pass (2048-bit rsa key) header.d=1e100.net
[email protected] header.b=ZLG7+Bt3;
x-ptr=pass smtp.helo=mail-wr1-f51.google.com
policy.ptr=mail-wr1-f51.google.com;
x-return-mx=pass header.domain=gmail.com policy.is_org=yes
(MX Record found);
x-return-mx=pass smtp.domain=gmail.com 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
Authentication-Results: mx2.messagingengine.com;
arc=none (no signatures found);
dkim=pass (2048-bit rsa key sha256) header.d=gmail.com
[email protected] header.b=T76XUsjE header.a=rsa-sha256
header.s=20161025 x-bits=2048;
dmarc=pass (p=none,sp=quarantine,d=none) header.from=gmail.com;
iprev=pass policy.iprev=209.85.221.51 (mail-wr1-f51.google.com);
spf=pass [email protected]
smtp.helo=mail-wr1-f51.google.com;
x-aligned-from=pass (Address match);
x-cm=none score=0;
x-google-dkim=pass (2048-bit rsa key) header.d=1e100.net
[email protected] header.b=ZLG7+Bt3;
x-ptr=pass smtp.helo=mail-wr1-f51.google.com
policy.ptr=mail-wr1-f51.google.com;
x-return-mx=pass header.domain=gmail.com policy.is_org=yes
(MX Record found);
x-return-mx=pass smtp.domain=gmail.com 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-ME-VSCategory: clean
X-CM-Envelope: MS4wfI2XNrjlUPyzMJLzQLrzwONCD07sgNNy2Mbz0UfKRM79I3IevRcF14E+GJ+GcG8GFamOhx/mevi0CZ+8VKm/P7qsGngp7paeAnTJCZsEHKdbBde7qUvr
h07HRHyIy+f+E1ISuFcuCBK8iHNqu27gw57tpwu1gwaCiF/SqDVSdKGQ2VeWrr7wEEwSLZLqXihkgdBfaVIaswonjQ5Xv+qN+Q6/igkl7BGM7VfRndIu+72s
X-CM-Analysis: v=2.3 cv=XYWnMrx5 c=1 sm=1 tr=0 a=dg4IilA35Stpn4h1fnSyIQ==:117
a=x7bEGLp0ZPQA:10 a=xl9-TOw3_ukA:10 a=dapMudl6Dx4A:10 a=9I5xiGouAAAA:8
a=sTQn-d-nFd7b-UR_hYIA:9 a=QEXdDO2ut3YA:10 a=spvjGQUTOj0A:10
a=iYZlb8aE7kKhmoKHCBIA:9 a=gMmJdMvzS8MvxDP_:21 a=ARFN2YZ7Uv8kHtb7LS-q:22
X-ME-CMScore: 0
X-ME-CMCategory: none
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=mx2.messagingengine.com;
identity=mailfrom;
envelope-from=”[email protected]”;
helo=mail-wr1-f51.google.com;
client-ip=209.85.221.51
Received: from mail-wr1-f51.google.com (mail-wr1-f51.google.com [209.85.221.51])
(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, 3 Aug 2018 18:18:02 -0400 (EDT)
Received: by mail-wr1-f51.google.com with SMTP id r16-v6so6677287wrt.11
for; Fri, 03 Aug 2018 15:18:02 -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=CGI+3HsseE4Goov1McIic2Y7VQLGoSqt8+r/BY++XVQ=;
b=T76XUsjEVteTv8xqPUYA/Kks+wuGn19J8Vg6ofou3fbqi1PqZS9dlUVoCO5xD8CRzq
ElyqNN2rqzkqzIzY/qjLfvj/mo3n9/eEowz2GYHvlu3StU0M5w0pSUc4TzGGA/f35i7U
p0SaSqGi1+PVazKuXOUuQlD/FT54ff/cRD8o5h5tdXyl/u01iuuWq6HuunCXJ2fcVZGA
ROQzcStWGF5rbWW1XoEecpXuulTmVKRqcA9maOSzLhBxDqGu8K78FSsZ5XvzxpKTVh6u
IDRmTqsXdJovJs+be1urlxxeLv9JAptI8e9bh97LqjsfURhUzfLW7TqQAZh7FzuN2dbd
9BnA==
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=CGI+3HsseE4Goov1McIic2Y7VQLGoSqt8+r/BY++XVQ=;
b=ZLG7+Bt3ed0nUXhFz/mcVmKvYa3SkgFL6rXJsi0Xk09NKBxzuodFFC5uqD7y4uRhye
rRWzLum8TbG9kMe7WnPN6ACyGjSHKcLZjYP4YXYYgFQ43s7BCZfuzme+DHJtM5Bv7Bpm
7sU+00BDONx4uvkMtBIK+JmDeH0zvaSnlObMGXpjlcWkJ640wfCYtT6IpPjC4URRs0Fd
EZUaroEQSSKS2JWMsVtMi0+mTu9EwXRBhIIN2M0MF4pM+Qy5BKQUWl8yer9lIOEMwFt0
tntSRTgYljM28Uza3QH4i497fdFUFa3qBlMA+wNO1sBTc6Jbfelv7rdqVIuPjOO4+JjX
9ORA==
X-Gm-Message-State: AOUpUlGmdIOnbAw3YGdMzLXEk3gov1hTjLZ9ntzof3FD1auj26BFovg5
kw0Oa87yoZHpGu9CJCa0zr6SqC/PHejoOx/nX6Qz1Q==
X-Google-Smtp-Source: AAOMgpdEall9rYztjT0szBqw2JyeDIhIDKknshKSlaJe7Z1KGnvWrEkGqHYnT2IqFj8Cxg2tBEfpjA2HJObQXCxm67s=
X-Received: by 2002:a5d:5641:: with SMTP id j1-v6mr3830094wrw.209.1533334680697;
Fri, 03 Aug 2018 15:18:00 -0700 (PDT)
MIME-Version: 1.0
References: <[email protected]> <[email protected]>
In-Reply-To: <[email protected]>
From: Fadel Khalifah Ibrahim
Date: Sat, 4 Aug 2018 05:17:43 +0700
Message-ID:
Subject: Re: 1D/2D FLOW ERROR. BUT THE COMPUTATION MESSAGES IS STILL RUNNING
To: “Scott Miller [via HEC-RAS Help]”
Content-Type: multipart/alternative; boundary=”000000000000f7030a05728f4cdf”–000000000000f7030a05728f4cdf
Content-Type: text/plain; charset=”UTF-8″
Content-Transfer-Encoding: quoted-printableThank you for your response. But before i have set the maximum iteration
between 1D and 2D=3D20. The result is same.On Sat, 4 Aug 2018 3:46 am Scott Miller [via HEC-RAS Help], < [email protected]> wrote:
> 1D/2D errors are normal. It is the flow that does not pass between the
> areas, and will cause a difference in water surface elevation. By default
> there are no iterations across the 1D/2D boundary. The magnitude of the
> flow error can be reduced by adding iterations. A threshold for acceptabl=
e
> flow error can also be set.
>
> 2D can be very slow. Provide more information about how your model is
> configured – maybe a detail of the geometry.
>
> ——————————
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://hec-ras-help.1091112.n5.nabble.com/1D-2D-FLOW-ERROR-BUT-THE-COMPUT=
ATION-MESSAGES-IS-STILL-RUNNING-tp6040p6041.html
> To unsubscribe from 1D/2D FLOW ERROR. BUT THE COMPUTATION MESSAGES IS
> STILL RUNNING, click here
> <http://hec-ras-help.1091112.n5.nabble.com/template/NamlServlet.jtp?macro=
=3Dunsubscribe_by_code&node=3D6040&code=3DZmFkZWxraGFsaWZhaEBnbWFpbC5jb218N=
jA0MHwxNDE4NDczOTAz>
> .
> 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>
>–000000000000f7030a05728f4cdf
Content-Type: text/html; charset=”UTF-8″
Content-Transfer-Encoding: quoted-printableThank you for your response. But before i have set the ma=
ximum iteration between 1D and 2D=3D20. The result is same.=C2=A0=
On Sat, 4 Aug 2018 3:46 am Scot=
t Miller [via HEC-RAS Help], <[email protected]> wrote:1D/2D errors are normal. It is the flow that does not pass between the are=
as, and will cause a difference in water surface elevation. By default ther=
e are no iterations across the 1D/2D boundary. The magnitude of the flow er=
ror can be reduced by adding iterations. A threshold for acceptable flow er=
ror can also be set.2D can be very slow. Provide more information about how your model =
is configured – maybe a detail of the geometry.=09
=09
=09
If you reply to this email, your message =
will be added to the discussion below:
=09
To unsubscribe from 1D/2D FLOW ERROR. BUT THE COMPUTATION MESSAGES IS STI=
LL RUNNING, click here.
NAML–000000000000f7030a05728f4cdf–
August 4, 2018 at 7:01 am #11599DELParticipantas information the distance between cross sections is 15-30 meters. Is that too solid?
August 4, 2018 at 6:34 pm #11600cameronParticipantWhat are you using for your weir coefficients?
August 4, 2018 at 10:47 pm #11601DELParticipantReturn-Path:
Received: from compute1.internal (compute1.nyi.internal [10.202.2.41])
by sloti1d2t14 (Cyrus 3.1.5-11-g6b5e7b6-fmstable-20180717v1) with LMTPA;
Sat, 04 Aug 2018 14:48:15 -0400
X-Cyrus-Session-Id: sloti1d2t14-2543078-1533408495-2-8435091028365117491
X-Sieve: CMU Sieve 3.0
X-Spam-known-sender: no
X-Spam-score: 2.9
X-Spam-hits: FREEMAIL_FROM 0.001, HTML_MESSAGE 0.001, ME_BETA_RULES 0.01,
RCVD_IN_DNSWL_NONE -0.0001, RCVD_IN_MSPIKE_H3 -0.01,
RCVD_IN_MSPIKE_WL -0.01, SPF_PASS -0.001, SUBJ_ALL_CAPS 1.625,
URI_HEX 1.313, LANGUAGES en, BAYES_USED none, SA_VERSION 3.4.0
X-Spam-source: IP=’74.125.82.46′, Host=’mail-wm0-f46.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 mx2 ([10.202.2.201])
by compute1.internal (LMTPProxy); Sat, 04 Aug 2018 14:48:15 -0400
Received: from mx2.messagingengine.com (localhost [127.0.0.1])
by mailmx.nyi.internal (Postfix) with ESMTP id 38140D8B52
for; Sat, 4 Aug 2018 14:48:15 -0400 (EDT)
Received: from mx2.messagingengine.com (localhost [127.0.0.1])
by mx2.messagingengine.com (Authentication Milter) with ESMTP
id 7E7F5ADB2F7;
Sat, 4 Aug 2018 14:48:15 -0400
ARC-Seal: i=1; a=rsa-sha256; cv=none; d=messagingengine.com; s=fm3; t=
1533408495; b=CIvSDLxOizGAvT8tElhpuK4SBouXXfU5EBvBTzpmJqW51Z9aPu
3mpjpQCEGaMcyjAfwiX+Kv0bxO4J8midi/Fw0M8dU1QAunRCOIDtMJqJDD7lHTwS
scGw5B2MRUWBK4UVogn2CLDyFgCPh3hF0V3+T+baV2XUO3BxioDl/AeFSYHMs868
VtHXtlaiNCLoW2yFIFXEWhkszvPO0X69E68lWgvrmtGiZK5Hu5jpBWBD36kk2WRR
o4HMaPji/A2jW3zg+S6VZdLPzgCalX2JDJsq1Fv89li7Pi+Wm7EIQqVZVtE8Na/A
//zy9DjNci0qQYu+5VaI1Yf6UGjnVN3euXbw==
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=1533408495;
bh=MxgnDroAcVuZW3DmuO6qkZOUZ28PuAsx2GhDu5wJWdc=; b=O7GHVCOZnIuv
tC+kMloEOqaa3BAWMbuT1tonBS0+B1nUO77n8E+pNvk0mDJq+1ex4wO2ToUCL5Wv
RQilryrBPT6XUYuIg9BJVOPAZB/bOgb6X5P70gSOIITILp2hc2gIN1Kr3qlvAkPR
zg2nFGgAV7ydJzMm/+5S0W0LnQwZUka7ybdV9pJCSAzP9Vt7dYMzfSAGxnW2rGY+
vomXAid7VlJdwT9sGGqPYr8n7eCiNg6L44KSV90B0W/tf3NivCnZHCW45wPZ3OzN
p0B7DRw/QsInVIdb/N5EmYUY0Zaq8p7Ca7fTONzBiio53QyV2gaTJqUTmvmBNftz
ytK7wA3ayg==
ARC-Authentication-Results: i=1; mx2.messagingengine.com; arc=none (no signatures found);
dkim=pass (2048-bit rsa key sha256) header.d=gmail.com
[email protected] header.b=C+ukiznk header.a=rsa-sha256
header.s=20161025 x-bits=2048;
dmarc=pass (p=none,sp=quarantine,d=none) header.from=gmail.com;
iprev=pass policy.iprev=74.125.82.46 (mail-wm0-f46.google.com);
spf=pass [email protected]
smtp.helo=mail-wm0-f46.google.com;
x-aligned-from=pass (Address match);
x-cm=none score=0;
x-google-dkim=pass (2048-bit rsa key) header.d=1e100.net
[email protected] header.b=ELjS8RdC;
x-ptr=pass smtp.helo=mail-wm0-f46.google.com
policy.ptr=mail-wm0-f46.google.com;
x-return-mx=pass header.domain=gmail.com policy.is_org=yes
(MX Record found);
x-return-mx=pass smtp.domain=gmail.com 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
Authentication-Results: mx2.messagingengine.com;
arc=none (no signatures found);
dkim=pass (2048-bit rsa key sha256) header.d=gmail.com
[email protected] header.b=C+ukiznk header.a=rsa-sha256
header.s=20161025 x-bits=2048;
dmarc=pass (p=none,sp=quarantine,d=none) header.from=gmail.com;
iprev=pass policy.iprev=74.125.82.46 (mail-wm0-f46.google.com);
spf=pass [email protected]
smtp.helo=mail-wm0-f46.google.com;
x-aligned-from=pass (Address match);
x-cm=none score=0;
x-google-dkim=pass (2048-bit rsa key) header.d=1e100.net
[email protected] header.b=ELjS8RdC;
x-ptr=pass smtp.helo=mail-wm0-f46.google.com
policy.ptr=mail-wm0-f46.google.com;
x-return-mx=pass header.domain=gmail.com policy.is_org=yes
(MX Record found);
x-return-mx=pass smtp.domain=gmail.com 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-ME-VSCategory: clean
X-CM-Envelope: MS4wfKyNOuVHAKQ0jWPD0Gcz7BeEkE6elJjODmKhI6r/BzLqxXjQj5B3CQGMx3ScEvNzpf4zfSKlWhgh7Dml68DqRCvmGVZjQS4zH4pEAl/41uGddzGuE9dK
yJc3gvJXHi94S2us/L8ebQSyHae+pJUFZO1bYv6GALmL71w9noRcSIiuXyR+ZAZeyfPCtDyM+r4/YNseX3N2jUq5b12l1VaNRFR17SoYs3lPQZN/cP+/JDUr
X-CM-Analysis: v=2.3 cv=XYWnMrx5 c=1 sm=1 tr=0 a=nIc0VDSzMRGb8XsmHHV1bw==:117
a=x7bEGLp0ZPQA:10 a=xl9-TOw3_ukA:10 a=dapMudl6Dx4A:10 a=9I5xiGouAAAA:8
a=wwCnWocy-HltVAetIE0A:9 a=QEXdDO2ut3YA:10 a=G9hyOcw7D30A:10
a=vV2ycgvOAmNHkcHhv8YA:9 a=qhnh2j2d5kl1Vulw:21 a=ARFN2YZ7Uv8kHtb7LS-q:22
X-ME-CMScore: 0
X-ME-CMCategory: none
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=mx2.messagingengine.com;
identity=mailfrom;
envelope-from=”[email protected]”;
helo=mail-wm0-f46.google.com;
client-ip=74.125.82.46
Received: from mail-wm0-f46.google.com (mail-wm0-f46.google.com [74.125.82.46])
(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; Sat, 4 Aug 2018 14:48:14 -0400 (EDT)
Received: by mail-wm0-f46.google.com with SMTP id y2-v6so9635140wma.1
for; Sat, 04 Aug 2018 11:48:14 -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=MxgnDroAcVuZW3DmuO6qkZOUZ28PuAsx2GhDu5wJWdc=;
b=C+ukiznkjvPCJwYNDGUA7lgNmpl9A8yDioLSC6iuSgXgKE5aNiBMAPa8yug5r5twZe
TlQj8FmmhoaPY0xkxAvkXSgJEEJlPhxZBKCEuIVmYThWKvUAtYvXm6nEbForC/3aoYux
URNNQ1x8V2A/Qrn4U0AaoZJpPE08+GWtzDGTsyUmyIIiXNp3dzaJ8YubzikaZhma2Fc9
9fQdbL3v3BQx7ZnysfH0mO2d3bMRpLbzhpqrn03zvAmczpfnG1WX0bTNT7dIGdTU+FMu
lMBkbtGbaDxltFJ/CC4/EBitLtaBSEAxJHzPyc1Q+pif8JmG+0KWutiyxdm/CzSaVMMS
pPKQ==
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=MxgnDroAcVuZW3DmuO6qkZOUZ28PuAsx2GhDu5wJWdc=;
b=ELjS8RdCvaj3ic7bNBFI0joE4vkwjC8k5GghUdYWz/Zj5Kp6iOvbxPaB6W0eXmyCR7
+mopOgC3M3pXN4WvjXVOBNgKI/wxizHTKhB7luqqqszz1axDJlK4iup2APLBFD4ktqqR
cIoadn1lIAfBnfdCFt/wcyLBKF6P7acXyg1YQ3RzrszlKhv+gha3nG2MSgEWwEi+6g8j
QzSCzP5pUZ6xBcCotF3fx6opRCm0LDPr8G0zSzNajsH/IFtpbxmbLUN3DA1QVTwH0zFt
pl7NGdG6MJook9F71Com0OFIW5zLRODiYG4s2Bc7RZPkfHJefb7h0GsVRvD8+iHhPoUE
/A4Q==
X-Gm-Message-State: AOUpUlEVvhhjTW2XqC1ZA1fcqH23/+1+8aZ9KCP5yibhUua5rTxtLQ4P
W5nxJHpUKAgEmU8cOCuvz1oO535rhkEFeXwF9pFBlA==
X-Google-Smtp-Source: AAOMgpfahLG1N2fUSEj/MpGePRSD9pLc+xtURI2WCbMzDyJAQCNp+iHcwqMAco0cIrZ3qYRwYrwlgOIff3Gfe6SWV0c=
X-Received: by 2002:a1c:b213:: with SMTP id b19-v6mr7551468wmf.141.1533408492548;
Sat, 04 Aug 2018 11:48:12 -0700 (PDT)
MIME-Version: 1.0
References: <[email protected]> <[email protected]>
<[email protected]> <[email protected]>
In-Reply-To: <[email protected]>
From: Fadel Khalifah Ibrahim
Date: Sun, 5 Aug 2018 01:47:59 +0700
Message-ID:
Subject: Re: 1D/2D FLOW ERROR. BUT THE COMPUTATION MESSAGES IS STILL RUNNING
To: “cameron [via HEC-RAS Help]”
Content-Type: multipart/alternative; boundary=”0000000000007e75a70572a07c30″–0000000000007e75a70572a07c30
Content-Type: text/plain; charset=”UTF-8″
Content-Transfer-Encoding: quoted-printableI used 1.43 for all lateral structures
On Sat, 4 Aug 2018 9:34 pm cameron [via HEC-RAS Help], < [email protected]> wrote:
> What are you using for your weir coefficients?
>
> ——————————
> If you reply to this email, your message will be added to the discussion
> below:
>
> http://hec-ras-help.1091112.n5.nabble.com/1D-2D-FLOW-ERROR-BUT-THE-COMPUT=
ATION-MESSAGES-IS-STILL-RUNNING-tp6040p6045.html
> To unsubscribe from 1D/2D FLOW ERROR. BUT THE COMPUTATION MESSAGES IS
> STILL RUNNING, click here
> <http://hec-ras-help.1091112.n5.nabble.com/template/NamlServlet.jtp?macro=
=3Dunsubscribe_by_code&node=3D6040&code=3DZmFkZWxraGFsaWZhaEBnbWFpbC5jb218N=
jA0MHwxNDE4NDczOTAz>
> .
> 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>
>–0000000000007e75a70572a07c30
Content-Type: text/html; charset=”UTF-8″
Content-Transfer-Encoding: quoted-printableI used 1.43 for all lateral structures=3D"gmail_quote" style=3D"margin:0 0 0 .8ex;border-left:1px #ccc solid;padd= ing-left:1ex">
What are you using for your weir coefficients?=20
=09
=09
=09
If you reply to this email, your message =
will be added to the discussion below:
=09
To unsubscribe from 1D/2D FLOW ERROR. BUT THE COMPUTATION MESSAGES IS STI=
LL RUNNING, click here.
NAML–0000000000007e75a70572a07c30–
August 5, 2018 at 7:29 am #11603cameronParticipantOne thing that will make the iteration go away is if you switch to the 2D solver instead of the weir equation, but you need to be careful when doing that.
Does that weir coefficient make sense for you model? Check the manual that lists values to use.
You could also adjust the lengths of the lateral structures by breaking it up into more sections.
August 5, 2018 at 3:04 pm #11604DELParticipantYes i does. I have check manual list value for weir coefficient. But it’s not works. For lateral inflow, i haven’t adjust to break lateral structures in to more sections. i will try it. but before it, Does, it has some length criteria to break it down?
Thank you so much cameron.
August 7, 2018 at 8:51 am #11605DELParticipantAugust 7, 2018 at 8:51 am #11602DELParticipant -
AuthorPosts
- You must be logged in to reply to this topic.