See example CL output of a change map attached (Pictures 1 and 2) for a section of the embankment with flow direction from bottom of image towards the top of image (erosion in blue and deposition in red). I’m curious if this might be related to model instability or some parameters choices in attached xml file. I am using a 1m resolution LiDAR derived DEM (2400 x 400m some of which has been masked out as no data) and 5-minute rainfall gage data using multiple gages across the DEM. Attached is the xml file. Please let me know if you have any suggestions or see any red flags as far as model parameters go that might help to improve this issue. Happy to provide more info if needed.
One other note is that I have modified the removal of vegetation within the erode() routine so that when tau >vegTauCrit the vegetation is completely removed as this is what we observe at our study site. However, I get similar results and erosion patterns with the distributed version using the grass now function at beginning of run so don’t believe the issue I am having is related to the modification below.
// veg components
// here to erode the veg layer..
if (veg[x, y, 1] > 0 && tau > vegTauCrit)
{
// now to remove from veg layer..
// veg[x, y, 1] -= mult_factor * time_factor * Math.Pow(tau - vegTauCrit, 0.5) * 0.00001;
veg[x, y, 1] = 0;
}
Look forward to any input.
Thanks,
Nate
Hi Nate – is flow from bottom to top on those images? If so it looks like the material is being dumped out as splays next to the channels rather than at the bottom as you expected..? That sound about right?
Eyeballing your config file, Mannings is at 0.5 – which seems really high.. 0.05 is better? (eg https://www.fsl.orst.edu/geowater/FX3/help/8_Hydraulic_Reference/Mannings_n_Tables.htm )
--
You received this message because you are subscribed to the Google Groups "caesar-lisflood" group.
To unsubscribe from this group and stop receiving emails from it, send an email to caesar-lisflo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/caesar-lisflood/01990901-1b08-4315-ba52-e9b043bd6c72n%40googlegroups.com.
You received this message because you are subscribed to a topic in the Google Groups "caesar-lisflood" group.
To unsubscribe from this topic, visit https://groups.google.com/d/topic/caesar-lisflood/21oHKVM_O-w/unsubscribe.
To unsubscribe from this group and all its topics, send an email to caesar-lisflo...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/caesar-lisflood/0c4501d9c92b%24c14ac5e0%2443e051a0%24%40gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/caesar-lisflood/CWLP265MB4515802729B09410FBFC8EB1A70DA%40CWLP265MB4515.GBRP265.PROD.OUTLOOK.COM.
Hi Nate,
Ok – here’s my thinking on this.
It looks like you’re getting erosion and deposition that suddenly switches off and on as you move downslope. Which is resulting in the ‘splays’ then incision, then splays then incision. So taking that at stage further something in the model is switching on and off – and I think this may be the erosion, where the hard thresholds are the water depth erosion threshold.. On a steep slope – the velocity of a 1cm deep flow is likely enough to move fine grained material without a problem, and when that drops below 1cm it suddenly stops… I think this may also explain the diagonal artefacts you talked about earlier in the water depth pics – its likely this may be the switching on and off… On a 10m grid cell, a 0.01m depth threshold is likely fine, but on a 1m or smaller it can make a big difference. The work we carried out on 0.2m resolution plot simulations for Australian mines, needed to have really low min depth in order to make any sensible hydraulic connections across the DEM – BUT these were pretty low gradient situations – especially compared to yours.
A couple of other hopefully helpful comments – Shear stress is not calculated by a depth slope product in the model (which I think you are doing in your message below? Sorry if not) – it’s a product of vel^2 and a drag coefficient (ci)
double ci = gravity * (temp_mannings * temp_mannings) * Math.Pow(water_depth[x, y], -0.33);
//tauvel = 1000 * ci * vel * vel;
if (slopetot > 0) slopetot = 0;
//tauvel = 1000 * ci * vel * vel * (1 + (1 * (slopetot)));
tau = 1000 * ci * vel * vel * (1 + (1 * (slopetot / vel)));
(the slopetot/vel thing is to reduce tau when there are negative bed slopes) – this will have a big effect on your depth/slope tau calcs – as reducing n will lower flow depths – but increase the velocity..
Its also worth bearing in mind that – unfortunately – things based around mannings and mannings roughness probably start to break down on steep slopes (above 0.1) so we’re at the limits of how the model should be operating – and as you are doing calibrating to get the right results with a wide range of parameters is probably the way forward.
Not sure all of this helps – sorry! But hopefully the explanations help….
Tom
To view this discussion on the web visit https://groups.google.com/d/msgid/caesar-lisflood/CAAodT4sYg3Y6zDPUJv9cM3%2Brfzm30rfxRzRZKh1otNLuD2Hnew%40mail.gmail.com.
Tau (Pa) | Ci | vel (m/s) | manning's n | water depth (m) |
54 | 0.06 | 0.99 | 0.05 | 0.085 |
153 | 7.8 | 0.14 | 0.5 | 0.030 |
To view this discussion on the web visit https://groups.google.com/d/msgid/caesar-lisflood/004401d9cb93%24caadd040%24600970c0%24%40gmail.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/caesar-lisflood/CWLP265MB45154AD216BDC85CF54C1FFDA713A%40CWLP265MB4515.GBRP265.PROD.OUTLOOK.COM.