Often SET tables are not set at elevations throughout the tidal range and are focused up around MHW so you would need to estimate the other portions of the range or use a model such as MEM3 to help fill out the relationship between marsh platform elevation and predicted accretion rates.
This is a quick birds-eye view of the procedure, please ask specific questions about the spreadsheet and we will answer them ASAP.
Last post by slammdunk - October 01, 2019, 04:19:42 AM
Hello Jonathon and Marco,
I am new to SLAMM and have had some difficulties understanding how to vary accretion rates as a function of cell elevation for different NWI wetland codes. I am hoping you can provide some more guidance on how to go about this.
I would like to use surface elevation change data from SETs that were placed in marsh and mangrove regions. Rather than breaking up the dataset for subsites around each SET, I would like to have accretion rates vary with elevation and tidal range for marsh and mangroves. I'm not certain about how to input this data into SLAMM though. Could you provide a step by step overview?
I have read through the user manual and technical guides, and have tried playing with the Excel SLAMM6_Accretion file included with the download. However, I'm still confused about how to go forward. Could you also provide an overview of the SLAMM6_Accretion file- bit of an introduction on how to utilize the spreadsheet?
The DEM must have some vertical datum to which elevations are referenced -- are the elevations in terms of the 1974 datum?
The MTL-NAVD88 parameter is set up such that if you looked at a gauge and there was a referenced MTL height and a referenced NAVD88 height, the value would be the difference of the two numbers referenced.
The 64-bit version of the software should be able to accommodate nearly any map size -- the limitations are the memory of the machine (and there are also practical limitations in terms of how long it takes to load and run simulations.) We have found the maximum size that is reasonably practicable to run is approximately 26 GB of memory (~250 million cells) but that obviously requires 32 GB of memory or more.
Note the memory utilization in GB is given in the SLAMM File setup window and different optimization options are available a the bottom of the screen.
e.g. "Cells to Track 7,169,539, memory utilization in GB 0.7478"
Are you saying that data can be input at 10m resolution in 6.0.1 but that 6.7 crashes with the same data set? Have you tried converting the data to binary using the binary button? This significantly optimizes input/output and may shed light on the problem. If you cannot solve the problem, you can send me the data files and I can look at it, but I'm afraid I have not been very responsive in terms of loading other people's data lately. Sorry that the software is not giving you a more helpful error message.
Last post by andybell - September 17, 2019, 04:01:03 PM
Hi, I have just installed SLAMM 6.7 on my laptop (8GB Ramm on windows 10) I am trying to run a model that I have downscaled from 2m to 10m resolution, but get an error when it reaches 6% in reading the site characteristics. The error reads "Invalid Floating Point Operation". The error comes up when the 6% progress is met
Any clues what might cause this? Many thanks in advance