Sediment Transport Capacity

[TDy]

Hello,
I’m trying to use “Sediment Transport Capacity” option under “Run/Hydraulic Design Functions”. I have a problem, which I don’t understand. Everything seems to be prepared well, the computations run, but there is nothing in results. Sometimes the results are zero independently on the conditions. I have to add that “SIAM” option configured in the same way works well and gives reasonable results. The same way means with the same sediment reaches and sediment samples, using the same sediment transport formulas.
Supposedly I did some mistake during the preparation of my project, which I don’t understand. I would like to compare my project with any working example of “Sediment Transport Capacity” application. Unfortunately, there is no such project in “Example Projects” copied to the disk during HEC-RAS installation. Could somebody give me a link to or send me working example with application of “Sediment Transport Capacity”? I’ll appreciate

[Chris G.]

Where are you looking for output? There are special output plots for sediment transport capacity. Please have a look through both the Users Manual and Hydraulic Reference Manual. They describe the process fairly well.

[TDy]

I’m checking output by pushing one of two buttons located near options Compute for This Sediment Reach/Compute for all Sediment Reaches. These are on the left in window Hydraulic Design Functions, if the type is Sediment Transport Capacity. Another window with plot of results is opened after that. In this window I don’t see much, only single point.
Then I’ll push the Report button located in the top of the window. And there is some information about the data provided. In the section, where results should be written, there are no numbers/digits in the column for results. Only empty place.
If you see something wrong in this procedure, please write it to me.

[Virgilio Anselmo]

I am just finding that same obstacle. It looks like data have been properly supplied, but clicking on both buttons, results are zero. The report summarizes tha data but zero bedload.
A quick evaluation of the transport capacity according to Shields’ criterion shows that bedload should exist.

[Anonymous]

Be sure that you have the “Sediment Output Options” (under “Sediment Transport Analysis”) set to 2 or higher. There’s an example data set included with the RAS 4.1 download (Euclid Sediment Transport Example) that might be useful.

[Virgilio Anselmo]

Working with the “Euclid” sediment transport example, Hec-Ras runs, but at the request of “View/sediment Spatial Plot”, the file EuclidExample.sed08 cannot be opened because or “Typemismatch” error. The file does exist. What can I do ?

[Anonymous]

Hello SIAM users. I am creating a SIAM model and cannot find a way around this problem: I am creating new sediment reaches and filling in all of the appropriate data. I am copying each reach moving downstream and updating the XS’s to define the bounds of the next downstream reach. By the time I arrive to the third sediment reach, the annualized flow duration values to not copy over, that is, the Hydro tab is totally blank with no discharge values in it. SIAM brings these discharge values over from the RAS hydraulic model and you cannot enter them manually, only the days/year and temperature values. When I try to Apply the changes to the new sediment reach I receive an “Error Saving Duration Curve Data” message.

Anyone else run into this problem? I’ve tried to work around it by entering the flow duration data manually into the SIAM input file, but SIAM doesn’t read it for some reason.

Thanks,
Joel

[TDy]

Return-Path: X-Original-To: [email protected]
Delivered-To: [email protected]
Received: from mail-lf0-f48.google.com (mail-lf0-f48.google.com [209.85.215.48])
by mbob.nabble.com (Postfix) with ESMTP id 048381F0D69F
for ; Mon, 25 Jan 2016 00:34:20 -0800 (PST)
Received: by mail-lf0-f48.google.com with SMTP id m198so79973318lfm.0
for ; Mon, 25 Jan 2016 00:38:27 -0800 (PST)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=gmail.com; s=20120113;
h=subject:to:references:from:message-id:date:user-agent:mime-version
:in-reply-to:content-type;
bh=WVuTbKxHTepw3L8pEiOsQbijXHD3s8PxEHyayMdbZWA=;
b=q6fwgTSfh13LmSfgmfHQuiL15ngTVyKq+RTnvy7MLg8owXVyp+vBm99Gm7nDIyM70q
90oOYTEd0aqUkN7pcYipMgyO0sVQUM5kLtQOWSnBl9/jL+DEKU7/o7LICkynPKpkORO3
Nat3tEJkeZG5TD4RgHqLXF5+K9jPihxIMlbQNXz2gAN+IA+QFA07YYT3+bh6v9JRac1a
r2WuSzdu5dWucsYzxOeVEVEFQp/17KDWbvvtjTi2dwtU8uPRkykpnF2KYqu553m8zFAj
fXjmi9m6FjaLq7BZoRLgeCmp4Sge/kkr1HYJQH5WlM0ZW56lhtxJ2hg1ZROhQCeN69HT
O1lw==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
d=1e100.net; s=20130820;
h=x-gm-message-state:subject:to:references:from:message-id:date
:user-agent:mime-version:in-reply-to:content-type;
bh=WVuTbKxHTepw3L8pEiOsQbijXHD3s8PxEHyayMdbZWA=;
b=kO9WYZMCZzltmlm6FDgq0NWvGjjlFO16CQudw+AmoWJ2rn3VUISGBSRULa3hXxEXp5
+Z2BSa4Lm3TlKbh3xYnbv1MuxQoXhPqBg3wwjp2QrryFbMb3b5MnNZ/YJlIt4NsLQxsW
9+sS73EnC5IB1K8Hut+pwUw4PuztzWEw1V4wsbeIiMoJXAqPictRrHsfOQBgbH+zMPmh
hexz28MO7tQnwGMWF5zkrDA07hnhpBq/scvmTQza8KbHusqVl8wA5tDBr2nynptLUJ+P
K9jotr1KKxsXg9E4GsGCys1YX55xoqS8nEPYwbfHo8xXGG5cRW20le+D4oD8oHabRxB+
uusw==
X-Gm-Message-State: AG10YOSxZsjsoRDaggBNl3CXfDL+5Mh3JZ8eZcPHfBzkqHgQLhc+53PaIoFshm/5N2mUTQ==
X-Received: by 10.25.209.80 with SMTP id i77mr5837487lfg.33.1453711100703;
Mon, 25 Jan 2016 00:38:20 -0800 (PST)
Received: from [127.0.0.1] ([150.254.174.203])
by smtp.googlemail.com with ESMTPSA id l67sm2636371lfi.2.2016.01.25.00.38.19
for
(version=TLSv1/SSLv3 cipher=OTHER);
Mon, 25 Jan 2016 00:38:19 -0800 (PST)
Subject: Re: Sediment Transport Capacity
To: Joel S [via HEC-RAS Help]
References: <[email protected]>
<[email protected]>
<[email protected]>
<[email protected]>
From: Tomasz Dysarz Message-ID: <[email protected]>
Date: Mon, 25 Jan 2016 09:38:17 +0100
User-Agent: Mozilla/5.0 (Windows NT 10.0; WOW64; rv:38.0) Gecko/20100101
Thunderbird/38.5.1
MIME-Version: 1.0
In-Reply-To: <[email protected]>
Content-Type: multipart/alternative;
boundary=”————080104020208010901050406″
X-Antivirus: avast! (VPS 160121-1, 2016-01-21), Outbound message
X-Antivirus-Status: Clean

This is a multi-part message in MIME format.
————–080104020208010901050406
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: quoted-printable

Hello Joel,

I saw such problems with SIAM module in HEC-RAS. I don’t know the
reason. I think you can manage this in three ways:

1. Reload the whole SIAM model – sometimes it helps, sometimes it doesn’t.

2. Insert proper data directly into input file, which is ASCII file. You
have tried this. This is very difficult, because you should be careful
as much as it possible. The structure of this file is not very
“friendly” for ordinary user. If you miss any sign or add some
unnecessary line, the file will not be read by HEC-RAS. As you saw.

3. Rebuilt the whole model once again. It sound terrible, but I did it
several times. The SIAM in HEC-RAS is not working well. If you want to
use it, you should be very patient.

The problem is also the lack of information on this algorithm and its
implementation. As I noticed there are not many people in HEC, who knows
how it works. I suppose, that somebody who prepared this element is not
working in HEC any more. So, you can use it, but expect problems.

Please, let me know if you find (1) the reason of this error or other
errors in SIAM, or (2) better solution then those listed above. I’m also
interested in application of SIAM and I experienced such errors.

Best wishes,
Tomek

Tomasz Dysarz, Ph.D., Env. Eng.
Poznan University of Life Sciences
Faculty of Reclamation and Environmental Engineering
Department of Hydraulic and Sanitary Engineering
ul. Piatkowska 94 A
60-649 Poznan
POLAND

phone: +48 61 846 65 86
fax: +48 61 848 77 26
web: http://www.up.poznan.pl/kbw/

W dniu 22-Jan-16 o 8:57 PM, Joel S [via HEC-RAS Help] pisze:
> Hello SIAM users. I am creating a SIAM model and cannot find a way
> around this problem: I am creating new sediment reaches and filling
> in all of the appropriate data. I am copying each reach moving
> downstream and updating the XS’s to define the bounds of the next
> downstream reach. By the time I arrive to the third sediment reach,
> the annualized flow duration values to not copy over, that is, the
> Hydro tab is totally blank with no discharge values in it. SIAM brings
> these discharge values over from the RAS hydraulic model and you
> cannot enter them manually, only the days/year and temperature values.
> When I try to Apply the changes to the new sediment reach I receive an
> “Error Saving Duration Curve Data” message.
>
> Anyone else run into this problem? I’ve tried to work around it by
> entering the flow duration data manually into the SIAM input file, but
> SIAM doesn’t read it for some reason.
>
> Thanks,
> Joel
>
> ————————————————————————
> If you reply to this email, your message will be added to the
> discussion below:
> http://hec-ras-help.1091112.n5.nabble.com/Sediment-Transport-Capacity-tp4=
1p2261.html
>
> To unsubscribe from Sediment Transport Capacity, click here
> <http://hec-ras-help.1091112.n5.nabble.com/template/NamlServlet.jtp?macro=
=3Dunsubscribe_by_code&node=3D41&code=3DdGR5c2FyekBnbWFpbC5jb218NDF8MzgzMDU=
3MDA0>.
> 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.n=
aml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-nabb=
le.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamespace-=
nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNamesp=
ace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.NabbleNa=
mespace-nabble.naml.namespaces.BasicNamespace-nabble.view.web.template.Nabb=
leNamespace-nabble.view.web.template.NodeNamespace&breadcrumbs=3Dnotify_sub=
scribers%21nabble%3Aemail.naml-instant_emails%21nabble%3Aemail.naml-send_in=
stant_email%21nabble%3Aemail.naml>
>

—
Ta wiadomo=C5=9B=C4=87 zosta=C5=82a sprawdzona na obecno=C5=9B=C4=87 wirus=
=C3=B3w przez oprogramowanie antywirusowe Avast.
https://www.avast.com/antivirus

————–080104020208010901050406
Content-Type: text/html; charset=UTF-8
Content-Transfer-Encoding: 8bit

Hello Joel,

I saw such problems with SIAM module in HEC-RAS. I don’t know the
reason. I think you can manage this in three ways:

1. Reload the whole SIAM model – sometimes it helps, sometimes it
doesn’t.

2. Insert proper data directly into input file, which is ASCII file.
You have tried this. This is very difficult, because you should be
careful as much as it possible. The structure of this file is not
very “friendly” for ordinary user. If you miss any sign or add some
unnecessary line, the file will not be read by HEC-RAS. As you saw.

3. Rebuilt the whole model once again. It sound terrible, but I did
it several times. The SIAM in HEC-RAS is not working well. If you
want to use it, you should be very patient.

The problem is also the lack of information on this algorithm and
its implementation. As I noticed there are not many people in HEC,
who knows how it works. I suppose, that somebody who prepared this
element is not working in HEC any more. So, you can use it, but
expect problems.

Please, let me know if you find (1) the reason of this error or
other errors in SIAM, or (2) better solution then those listed
above. I’m also interested in application of SIAM and I experienced
such errors.

Best wishes,
Tomek

Tomasz Dysarz, Ph.D., Env. Eng.
Poznan University of Life Sciences
Faculty of Reclamation and Environmental Engineering
Department of Hydraulic and Sanitary Engineering
ul. Piatkowska 94 A
60-649 Poznan
POLAND

phone:	+48 61 846 65 86
fax:	+48 61 848 77 26
web:	http://www.up.poznan.pl/kbw/

W dniu 22-Jan-16 o 8:57 PM, Joel S [via
HEC-RAS Help] pisze:

type="cite"> Hello SIAM users.  I am creating a SIAM model and
cannot find a way around this problem:  I am creating new sediment
reaches and filling in all of the appropriate data. I am copying
each reach moving downstream and updating the XS’s to define the
bounds of the next downstream reach. By the time I arrive to the
third sediment reach, the annualized flow duration values to not
copy over, that is, the Hydro tab is totally blank with no
discharge values in it. SIAM brings these discharge values over
from the RAS hydraulic model and you cannot enter them manually,
only the days/year and temperature values. When I try to Apply the
changes to the new sediment reach I receive an “Error Saving
Duration Curve Data” message.

Anyone else run into this problem?  I’ve tried to work around it
by entering the flow duration data manually into the SIAM input
file, but SIAM doesn’t read it for some reason.

Thanks,

Joel

---

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

http://hec-ras-help.1091112.n5.nabble.com/Sediment-Transport-Capacity-tp41p2261.html

To unsubscribe from Sediment Transport Capacity, click
here.
NAML

---

Ta wiadomość została sprawdzona na obecność wirusów przez oprogramowanie antywirusowe Avast. http://www.avast.com

————–080104020208010901050406–

[Anonymous]

TDy,

Thanks for the suggestions. It turns out that when you create a new sediment reach, if you go to the “Plan Name” drop-down box in the SIAM window and select the appropriate steady flow plan again then it will trigger SIAM to import the flow data into the Hydrology tab. A weird quirk, but seems to work.

Joel

[Author]

Posts