Forum Replies Created

Viewing 12 posts - 1 through 12 (of 12 total)
  • Author
    Posts
  • LorenAmelang
    Participant

    So in my post at
    http://hec-ras-help.1091112.n5.nabble.com/Terrain-from-EPSG-3310-file-is-475-south-of-Web-Imagery-td6257.html

    Is the key:

    Here is what RAS Mapper GDAL sees in the 3310 file it imported incorrectly:

    Pixel Size = (1.030469526568122,-0.969388829487901)

    vs:

    RAS Mapper importing original USGS DEM:

    Pixel Size = (1.000000000000000,-1.000000000000000)

    It must know about non-square pixels, since the features aligned perfectly once manually displaced to matching positions. I guess it just calculates the Origin without considering pixel shape?

    in reply to: Chris- The Forum Interface Needs Help #11581
    LorenAmelang
    Participant

    This problem seems to appear randomly! Sometimes I have to click “More” for each screen height of new data, in a long post or even in the list of topics. And other times I can scroll to the bottom of any page. Same computer, same browser…

    This is a good test page:
    http://hec-ras-help.1091112.n5.nabble.com/Do-tiny-mountain-streams-make-spiky-plots-td6288.html#a6326

    (Sorry, I did see the recommendation to keep posts short, but it isn’t a simple issue…)

    I just re-opened it from the list of my user posts, and it not only didn’t require “More”, it opened scrolled to the bottom! The system must remember each user’s last reading position in each post? But a few days ago I opened it from a saved URL and had to click “More” about 20 times to get to the bottom.

    When I began reading posts today, I had to click “More” several times to get through page 1 of the topic list. After that none of the other pages showed any “More” pauses.

    in reply to: After Importing DGM in RasMapper Terrain is dislocated #10833
    LorenAmelang
    Participant

    I just noticed your report. Sounds a bit like mine:
    http://hec-ras-help.1091112.n5.nabble.com/Terrain-from-EPSG-3310-file-is-475-south-of-Web-Imagery-tp6257.html

    The terrain I had pre-processed and re-projected in QGIS was displaced. RAS Mapper (from 5.0.5) was able to import the original DEM directly – in the correct location.

    See also:
    http://hec-ras-help.1091112.n5.nabble.com/Terrain-layer-not-aligned-with-other-layers-td6130.html#a6354

    Looks like a real bug somewhere between QGIS and RAS Mapper. They aren’t kidding about “BETA”! The Release Notes ask for reports, but I’ve received no acknowledgement for sending them…

    in reply to: Terrain layer not aligned with other layers #11625
    LorenAmelang
    Participant

    I just noticed your report. Sounds a bit like mine:
    http://hec-ras-help.1091112.n5.nabble.com/Terrain-from-EPSG-3310-file-is-475-south-of-Web-Imagery-tp6257.html

    The terrain I had pre-processed and re-projected in QGIS was displaced. RAS Mapper (from 5.0.5) was able to import the original DEM directly – in the correct location.

    in reply to: Do tiny mountain streams make spiky plots? #11712
    LorenAmelang
    Participant

    > This is your issue. HEC-RAS and the equations that govern solutions have slope limitations (if i remember its due to the cos(X) portion of the eqaution)

    I’ve been wondering if the steep part was a problem. So I saved a modified Geometry, where I deleted the XS above 5640 – the steep part is gone from “-spillway” plans.
    Compute is not slowing down as it hits the serious flows – maybe the wild spiking is gone? Still took 5 minutes, though…

    Now the initial pileup is down on the more level part, and it is taller as I expected:

    ***** Warning! Extrapolated above Cross Section Table at: *****
    Walker Creek Reach 1 from R.S. 5640 to 5493
    The maximum xsec wsel error was 4.259
    Walker Creek Reach 1 1437 at 13SEP2018 01:13:51

    The Stage and Flow Hydrograph plot shows the new plan and geometry names, but the only top plot option is the old 5715 top XS. All other plots have the new 5640 top. Reselecting Plan doesn’t help. Bottom stage looks just as spiky as before. Flow at bottom never gets above 2 cfs – something is way wrong! Large Flow at top stops between 5512 and 5349… Hydraulic Depth seems to have flow all the way down???

    So I tried dividing the Flow Hydrograph by 10 – for 40 cfs max…

    No extrapolation with the lower flow:
    The maximum xsec wsel error was 2.754
    Walker Creek Reach 1 25 at 13SEP2018 04:02:44

    Guess I need a different Normal Depth at the bottom, it is sloping way up in the last segment.

    Stage and Flow Hydrograph is still stuck showing 5715. Bottom flow never goes above 3 cfs, stage still just as spiky.

    Flow plot goes -380 to +200 cfs in spikes, Initial Conditions plot exactly 1 as expected.

    Depth plot peaks at 3.2′, never below 0.3′, follows terrain, looks good! Depth Initial Conditions plot also follows the terrain.

    But the Flow Initial Conditions plot is a straight line… I guess overall flow has to be the same all along, for a steady input flow… But the Flow plot during simulation changes so wildly + and -, even in the Profiles for the last two hours of steady 1 cfs input. It never settles back down to the “Initial Conditions” straight line. I don’t understand…

    Have to quit for now, another project needs attention today!

    in reply to: Do tiny mountain streams make spiky plots? #11710
    LorenAmelang
    Participant

    Thank you Luis for another day’s suggestions!

    > Copy inverts is your starting point yes. Now for vertical select all the values and set them all at 100, and also set the Increment to “0.1” Horizontal mapping set them all as well to “500”

    Looks like 100 is the maximum Horizontal it can save, even though it says in the header that the vertical count can go to 500.

    > In your failed runs, or runs with erroneous stage elevations, click the profile button and select the “plot initial conditions” button at the top right. This should show the solution of your model after initial conditions have finished computing. Are there any issues with this?

    The very first cross section had a second dip way out past the bank line, and apparently it was dumping about 40% of the flow over there instead of in the spillway channel. It would end up in the main channel at the third cross section, but fixing that has made all the plots a bit smoother.

    > What’s the maximum slope or elevation change between cross sections? What’s the total slope from the first to last cross section?

    The worst drop near the top was 30′, a few more around 20′. Below the spillway there is way less than one foot drop between cross sections. I added some at the top, to keep the drop under ten feet. Some results are smoother, but now the stage jumps up 70′ in the 4′ drop of the first XS distance, instead of up 9′ in the previous 25′ drop distance. After that first extreme, the rest of the stages and elevations looked reasonable.

    Total drop from the bottom of the spillway to end of model is 90′ in 5600′. Above there the spillway drops 30′ in 75′.

    But that brings me to a new insight… In the YouTube videos I’ve seen, people just dump a flow hydrograph at the top of a river and watch what happens. But in a dam failure that starts down from the top, the elevation where the water is pouring out will keep dropping as the dam fails. In order to dump 5000 cfs, the dam will have to be washed away almost down to the bottom of the spillway.

    So maybe trying to model dumping huge flows at the top of the spillway is just wrong? But it seems dumping the same flows down at the beginning of the shallow slope would lead to even higher initial spikes… I see people saying to create a storage area at the top of the stream, but it seems that would also require a fixed elevation for the connection between storage and stream. How do you model a failure that washes away your top cross sections?

    > Yea, if you can smooth out that hydrograph in HMS if possible or within a data editor like excel to give HEC-RAS more computation points to use

    Haven’t tried that yet. Actually there are lots of points, they just fall in straight lines with corners instead of a smooth curve.

    > the point here is to keep the model from ever drying out.

    Difficult when the stage seems to be mostly tiny spikes, and the flow bounces from positive to negative constantly.

    > The 2D layer or computational mesh will use the assigned mannings value in the data entry location in RAS mapper. The 1D cross sections will always use the data from the geometry data editor n table only.

    That’s what I thought. I haven’t begun to think about 2D yet…

    So here are today’s whines about probable bugs:

    Tons of errors about left bank Manning’s n not set. Totally set in Geometric Data Editor table. In cross section profiles, channel and right n was shown, left was either missing or to right of right n width. Looked in RAS Mapper, noticed those cross section Edge Lines were not at the XS ends.
    -> Cross Section -> Edge Lines -> [right click] Edit -> Compute Edge Lines at XS Limits -> Stop Editing (Save) fixed this, and it ran!

    But then I added some cross sections in the steep initial spillway…

    Bank Lines, Edge Lines, and Flow Paths would zoom to feature properly, but Bank Stations, Cross sections, and Rivers would zoom way out to show coordinate 0,0 to the southwest. Mapper’s Recalculate didn’t fix this… Flow Hydrograph entry dialog showed an unnamed reach of unnamed river…
    Geometric Data Editor -> Edit -> Delete -> Reaches …

    Also must manually fix Htab Param and Manning’s n tables after adding XS in Mapper.

    And once again Mapper Recalculate has added a bunch of those “zero width walls” to be manually fixed.

    Definitely still deserves the “Beta” label.

    in reply to: Do tiny mountain streams make spiky plots? #11708
    LorenAmelang
    Participant

    Luis, thanks again for giving me things to think about!

    > Your issues are a common instability problem solving exercise. Htab parameters for cross sections are VERY important for stability. If its a 1D cross sections it is located in the geometry data editor on the left tool bar just above the “View Picture” Button. All minimum WSELs or starting points should be at the cross sectional minimum and max out everything else with small intervals both vertically and horizontally.

    I’ve done the “Copy Invert” button there. Shows 30 to 80 vertical points, I guess RAS Mapper has chosen those numbers individually as I drew them? Can I tell it to use more?

    But the “Horizontal” columns there are all zero. In the screenshots in the manual, those columns don’t seem to exist… I’ve tried to find out what they should show. A count of horiz points? In the Cross Section editor, each line has between 250 and 500 horizontal points.

    Image search found me http://www.hec.usace.army.mil/software/hec-ras/documentation/HTab_Parameters_Error.pdf which shows those columns. Doesn’t talk about them, but theirs are all “5”…

    > Change your mapping interval to only double your computational time step.

    So Computation Interval 1 second, Mapping Output Interval 2 Second?

    That may be better… Stage and Flow Hydrograph looks just as spiky, but the surface profile spikes are at possible levels instead of stratospheric. Will have to try more plans.

    > How many cross sections is this model?

    There are 122, in 5715 feet of channel. Some as far as 80′ apart, but much closer in “interesting” spots. If my spikes matched certain spots, I’d definitely add some, but the spikes seem unrelated to cross section spacing.

    > When you said you changed your input flow hydrographs you changed it in HEC-HMS? or interpolated down to 1-minute and re-entered the data in the flow editor?

    I changed the interval in the flow editor, and used its interpolate button. I realize now that doesn’t smooth out the flow corners in the Stage and Flow Hydrograph plot… But it (or something…) certainly changed the detail of the stage part.

    > Since there are 1D cross sections what’s your initial flow?

    This little stream spends most of the year under 1 cfs. Average flow at the first gauge, 19 miles downstream after four other rivers join this one, is around 16 cfs. But this is California, so a few winter storms can make huge spikes… I start each model at 1 cfs, and I’ve tried peaks of 20, 200, 400 (dump the dam in six hours), 800, and 5000 cfs (dump the dam in one hour). Somehow 400 spread most across the wider floodplains downstream.

    I’m thinking maybe I need to put way more detail into Manning’s n for the wildly varying terrains here. If I draw the 2D layer or import a land use file, can the 1D model use that info, or are they totally separate?

    > You green flow hydrograph looked very odd as it is showing data points every 6 hours or so.

    Yes, I realize now my “interpolation” strategy just draws the same straight lines.

    > Stage should never vary that much though so you are correct in assuming your model is unstable to say the least

    Something big and obvious must be wrong, but I certainly haven’t spotted it yet.

    in reply to: Do tiny mountain streams make spiky plots? #11706
    LorenAmelang
    Participant

    I’ve now extended a few cross sections it occasionally complained about, changed my input Flow Hydrographs to 1-minute intervals (instead of 10-minutes or 1 hour), tweaked the lower end Normal Depth to avoid any slant on the last segment of plots, speeded up my calculation time interval to 1 second and all reporting times to 1 minute – and everything is as spiky as before – but in randomly different places.

    I had been setting the input Flow Hydrograph – Critical Boundary Condition – Max Change in Flow value to 1, and it had obviously slowed down calculations in the parts where the flow was changing rapidly. I tried it as low as 0.1, which turned a 1-minute calc into 8 minutes, but didn’t reduce the spikiness.

    I still see occasional “EG Max WS” values that are 200000 feet above my real surface – never in the same places twice. The “WS Max WS” values are sometimes a bit odd, but always at least physically possible.

    The only explanation Google finds:
    “EG Max WS: elevación máxima de la superficie de agua. Crit. Max WS: elevación crítica de superficie de agua. WS Max WS: elevación de la superficie de agua.”

    I guess that means “EG” is the maximum ever seen in calculations? Do we care, if the average value settles on a more reasonable “WS”?

    As for “maximum headwaters and tailwaters in the htba parameters”, I’m completely lost. I can’t find anything like that in any of my Htab Parm or Cross Section dialogs. But I suspect it doesn’t matter – my wild spikes are never at the same cross section twice.

    To compare with the earlier Stage and Flow Hydrographs plot, here’s essentially the same thing with all the factors speeded up:

    Actually puts less water up on the flat bank areas, as I’d guess from less area under the curve. How can the flow be so wrong at the very first cross section where the hydrograph is dumping it into the system?

    Thanks, Luis, for giving me things to try, and someone to try to explain this to…

    in reply to: RAS Mapper – Velocity output layer not displaying #11700
    LorenAmelang
    Participant

    Interesting… “Out of memory” is what the QGIS devs blame for many of my problems. As far as Windows 10 Task Manager or Resource Monitor can see, Ras.exe uses under 50 MB for display, and is very good at clearing that back to ~12 MB when idle. PipeServer.exe (the visible name for RAS Mapper) uses about 160 MB (105 MB of it private…) for my current project.

    While Firefox easily claims over a GB for itself, and there are another 5 GB unused. Maybe GIS apps play by different rules?

    in reply to: RAS Mapper – Velocity output layer not displaying #11698
    LorenAmelang
    Participant

    Sorry I have no answer to your issue, only another question…

    I (also in 5.0.5) have the red asterisk next to Geometries -> Manning’s n -> Final n values. I just tried all the mousing tricks I can think of, and can’t connect the popup message with anything I’ve done (maybe there is a huge delay?), but a few times a message has popped up for an instant about “Geometry is not associated…” That’s all I’ve been able to read before it disappears again.

    What did you do to be able to copy your long message?

    I haven’t explicitly created a Geometry layer for Manning’s n, I just filled in the table in Geometric Data Editor. I guess that doesn’t automatically import? I’m concerned because in my results View -> General Profile Plot – Weighted n plots, the channel n value is always continuous and correct, but the L/R values are mostly missing and sometimes totally wrong. The original table is still perfect. Maybe that explains my randomly spiky depth and flow results? Velocity can jump from 16 to 600fps for no apparent width or slope reason.

    LorenAmelang
    Participant

    Thank you Luis for the reply! A lot has happened since I wrote my post… I wanted to check the example projects, and noticed HEC-RAS 5.0.5 was there, so I installed it. Can’t find any examples of junctions.

    But I did discover RAS Mapper’s editing functions! The Release Notes document announced them like a finished addition, but I notice the Menu choices all still say “BETA”. And rightly so – I saw at least ten “exceptions” yesterday. They randomly re-order a few Cross Sections, or move a couple of them way out in the mid-Pacific on “River (Missing), Reach (Missing)” – and then redraw all your bank lines zigzagging up and down the reach, or flipping around to the other end of it. If you can get through fixing those without generating any new ones, it will automatically fix all your bank lines… If they ever make editing reliable it will be wonderful!

    So I was able to edit those junctions with the Terrain visible under them, and cleaned up several places where my original river lines didn’t match the new 1-meter LIDAR DEM.

    There is still a pileup of water ahead of junctions, but it is now ~5 feet instead of ~32 feet. But the “Max WS” levels still wildly overreact to every little bump in the streambed! A 2′ rise to a downstream cross section can make a 100′ spike in the Max WS. I guess that’s what they mean by “unstable”?

    All my junctions have less than 2′ drop across the adjacent cross sections, similar to differences between other cross sections. Does that require a “direct drop”?

    The cross sections joining the reaches are as close to the junction as they can be without being a star of arrow points. Maybe that’s what I need, a really short perpendicular line with splayed tails barely avoiding each other?

    But I’m now seeing worse pile-ups midstream than at the junctions, so I think my scenario is just way too sensitive all over. Maybe little ~1 cfs and ~2 cfs wandering mountain streams are just tricky to model?

    in reply to: Is RAS Mapper saying my cross sections are backward? #11620
    LorenAmelang
    Participant

    Thank you gerar200 for pointing me to the right menu!

    I started with this – QGIS on the left, Geometric Data Editor on the right, showing cutline 19380 extending well beyond the bank line to the (screen left) west on the “right” side of my stream looking downstream. HEC-RAS shows all cutlines L-R reversed:
    Cross 19380 original QGIS, with HEC xyz plot.JPG

    I used this on 19380 (in HEC-RAS 5.0.4):
    HEC_RAS -> Edit -> Geometric Data Editor -> GIS Tools -> GIS Cut Lines -> Reverse Cut Lines -> (select river and reach – “all” shows no items! But see below…)

    –> Check the “Node Types …” button before selecting lots of items! Sometimes it has all node types selected, even though you triggered it from a Cross Section specific menu item.

    And while it reversed the XS left right arrow as expected, it also reversed the geometry, moving the whole channel westward and reversing the shape of it, leaving the wide bank area on the (screen right) east, “left” side of the stream:
    Cross 19380 original QGIS, with Reverse Cut Lines.JPG

    So I reversed that back and tried the other option:
    HEC_RAS -> Edit -> Geometric Data Editor -> GIS Tools -> GIS Cut Lines -> Reverse XS Stationing and Cut Line Data
    (For a single XS line, in Geometric Data Editor, left click the line, select “Reverse XS Stationing and Cut Line”, which does the same thing.)

    These options reverse the HEC-RAS idea of left and right, _without_ moving the stream channel or spoiling the elevation profile.
    Cross 19380 original QGIS, with Reverse XS Stationing and Cut Line Data.JPG

    If you’re flipping your entire reach, you can click “All RS” to have the right arrow select all of the stations (you won’t see any action until you click the right arrow…) If you’re flipping your entire project, you can click “All Rivers” when the dialog first opens to have the right arrow select everything.

    To see handy XS direction arrows in Geometric Data Editor, View -> View Options … -> Cross Section Properties -> XS Direction Arrows

    To see map coordinates in Geometric Data Editor, hold Ctrl key, click a point.

    P. 6-187 “Reverse Cut Lines” in the HEC-RAS “User’s Manual” Version 5.0 February 2016 sort-of describes the first function. I guess P. 6-166 “Reverse Stationing Data” must be trying to describe the other option, but it doesn’t match my HEC-RAS 5.0.4 at all, and isn’t very helpful.

    Does anyone have a PDF manual that allows copying text? I can hardly believe it, but all the ones I’ve found are “protected”.

    So I think my left-right issue is solved! I wonder what I get to learn next…



Viewing 12 posts - 1 through 12 (of 12 total)