News:

Due to SPAM attacks, new members must be approved before posting.  Please email jclough@warrenpinnacle.com when registering and your account will be approved.

Main Menu
Menu

Show posts

This section allows you to view all posts made by this member. Note that you can only see posts made in areas you currently have access to.

Show posts Menu

Messages - MSub

#1
We are using SLAMM version 6.7 and wanted to make sure the following holds on this version:
  • this version considers historical SLR rate or Uplift/Subsidence raster and marsh accretion rate in order to calculate the marsh elevations in relation to sea level as explained in Accretion or surface elevation change. So, it means the elevation output of SLAMM incorporates both these rates in marsh area and the first rate (historic SLR rate or Uplift/Subsidence raster) in open water and upland area?
  • unlike mentioned on Elevation output, the elevation output is converted back into NAVD88 on this version?

Thank you!
#2
Using SLAMM / Re: SLAMM in Linux
January 12, 2016, 02:10:40 PM
Thanks Jonathan. By "a parallel-processing version", do you mean SLAMM parallel-processing version? If so, do we need to modify code to make it run as a parallel-processing version? Can you please elaborate more about it?

I have also thought about wine, but am not sure if it will be able to take an advantage of parallel processing in HPC. I'll take a look on the paper. 
#3
Using SLAMM / SLAMM in Linux
January 06, 2016, 09:06:21 AM
We are working on a large study area and are thinking of making use of High Performance Computing (HPC) cluster that we have in campus. The operating system in the HPC is Linux. So, we need to compile SLAMM on Linux. I wanted to get some idea about the possibility of using SLAMM in Linux before I start digging into the Delphi compiler in Linux. Has anyone tried SLAMM on Linux? What would be the best approach to get started for it to make it work?

Thank you for your help.
#4
Hi Marco,
Thank you for your suggestion. I do see the erosion being triggered now after I redefine AdjMaxFetch <= 1 km. However, I see that the maximum erosion is 10 m on the legend of both marsh and beach erosion maps. For this run, the marsh erosion, swamp erosion and tidal flat erosion was 0.589788, 0.997603 and 1.26461 m/yr respectively. For another test run, we increased the erosion rate to 10 m/yr for all three erosion types. But, we get the same legend again for marsh and beach erosion with the maximum of 10 m. While we compare the output csv files of these two runs, we see significant changes in the marsh area.

Actually, we have not seen the legend going beyond 10 m in any of our test runs. However, I found that it has gone to 30 m in the report that Warren Pinnacle had prepared for TNC on Galveston Bay (http://www.slammview.org/slammview2/reports/Galveston_Report_6_30_2011_w_GBEP_reduc.pdf). Do you think it's something we should be worried about?

Thanks again.
#5
Erosion is still not occurring in all places where we presume it should be even after I made the following changes in the code:
1. defined Erosion = Moderate if AdjMaxFetch <= 9 and got rid of "Erosion = Little" as I did not see the use of "Little" in the code
2. changed the line Convert(Cell,Clss,Tidalflat,-99) to Convert(Cell,Clss,EstuarineWater,-99) in the Procedure ErodeMarsh based on your suggestion

I could not attach the pdf file due to size limitation here but have uploaded it on dropbox (https://app.box.com/s/rm83kqlfoxi06slr7oqvd4jlmnvm64g1). The pdf file has the resulting maps and figures before and after making changes in the code. E.g. we think there should be erosion in an area shown by purple rectangle on page # 3 of the pdf file . For our test run, we've used A1T max SLR scenario with 25 years time step. There's also a screenshot of the site parameters that we've used in our test run. Can you please take a look on the maps and help us understand if we are are overseeing or missing something? Thank you.
#6
In Transfer.inc, I found a procedure called Procedure Erode(Cell: PCompressedCell; Var Erosion: ErosionScale) where erosion is defined based on Knutson et al. 1981 (I also could not understand why SLAMM has used those ranges for the fetch from the paper.) I tried changing the range of the fetch within the procedure, but it did not make any difference in the erosion map of my study area. I am wondering if there is any other procedure where I need to make changes. Thank you in advance.
#7
Model Formulation & Parameters / Erosion issue
May 11, 2015, 12:19:33 PM
We are having an issue with Erosion in SLAMM that we are running in Galveston Bay. SLAMM is not triggering marsh and beach erosion in areas where wetlands are adjacent to water and the maximum fetch threshold is reached. We ran a sensitivity analysis varying erosion rates (marsh, swamp, and tidal flat) by +/- 15%, which resulted in no change to model output from the base case. Following the post in SLAMM forum, we attempted to force SLAMM to trigger erosion by converting the Estuarine Open Water class to Open Ocean since SLAMM will assume max fetch is infinite when the last cell on the edge of the map is Open Ocean, but erosion still isn't occurring. Similarly, we also tried to run the model with the reclassified water and run the sensitivity analysis with the reclassified water, but it also does not make much difference. We wanted to make changes on SLAMM code to see if decreasing the fetch length from 9 km may be useful. Can you please point me to the place in the code where I can make changes to it?

Thank you for your help.