Cool and very useful functionality. Thank-you for sharing. NOTE: The only way I was able to get it to run in v6.5 was to make the inflow boundary an external condition.
Yes, that's right. Internal flow boundary conditions do not work with sediment. And since we added internal flow boundary conditions, older models that defined the the boundary condition within the mesh read as internal bcs.
I remember in the past you've mentioned to cap the gradations between zero and 100. What happens under the hood when you leave them blank and let RAS guess the gradations either side of the curve? Does it automatically cap them at the adjacent gradations ranges or does it interpolate to 0/100 including all the available gradations in the list (I.e. from non-cohesives to massive boulders)?
Good question...using 0 and 100 is best practice when you are using the cumulative input. But when you use the histogram input, it should just add up to 100.
Cool and very useful functionality. Thank-you for sharing.
NOTE: The only way I was able to get it to run in v6.5 was to make the inflow boundary an external condition.
Yes, that's right. Internal flow boundary conditions do not work with sediment. And since we added internal flow boundary conditions, older models that defined the the boundary condition within the mesh read as internal bcs.
It was great and insightful thank you Dr. Gibson
Dr. Gibson, please help me. I cant visualize “bed change” in RAS Mapper
I remember in the past you've mentioned to cap the gradations between zero and 100.
What happens under the hood when you leave them blank and let RAS guess the gradations either side of the curve? Does it automatically cap them at the adjacent gradations ranges or does it interpolate to 0/100 including all the available gradations in the list (I.e. from non-cohesives to massive boulders)?
Good question...using 0 and 100 is best practice when you are using the cumulative input. But when you use the histogram input, it should just add up to 100.