Last post by JackieRaw - April 14, 2019, 01:41:46 AM
I have found the solution to this problem. It was a simple default setting that needed to be changed on my computer. My Windows 10 machine was set up with US English as the default language, with a comma to be used as a decimal point instead of a full stop. This prevented the ASCII files from being loaded because the decimals were being read as commas, even if the original files were correctly formatted.
Hello, I would like some clarity with some of the new input parameters in SLAMM 6.7.
1) The Marsh Erosion Fetch (km) - is this a maximum value to input instead of the default 9km that was previously in the other versions? If this is left "0", will it use the 9km default, or do I need to input a max value?
2) H1-H5 inundation Parameters - since these relate to infrustructure, if I am not including roads etc., then can I leave these inputs as "0" ?
3) Irreg-Flood Collapse and Reg-Flood Collapse (m) - do these parameters need to be put in for SLAMM to run correctly? I'm not sure how to calculate these values, or if there are default values that can be used here. Any references or material on how to calculate these would be great.
I guess we've never run with just an 010 and not also a 100 year storm. I think it's fair to say that this portion of the model has only been utilized by our team and is not deeply user friendly. I'll look into the code to understand the requirements.
Yes, if you have no correction factor for NAVD88 then using the MTL datum would be correct. This is because, while the model will try to convert data from NAVD88 (which has been the format we generally received data in) it would use the zero conversion factor, so there would be no change.
Sorry about the deficiency in documentation. This is from some metadata we created when running the model:
Inundation maps were created by running SLAMM for 5 different inundation elevations (H1-H5 in the subsite parameters)
Raster values are: 0 (zero) - open water, 1 - inundated at H1 level (we often set this to the 30-day inundation level), 2 - inundated at H2 (we have used 60 days), 3 - inundated at H3 (90 days) 4 - inundated by H4 (we often set this to the 10 years storm), 5 - inundated at H5 (100 years storm), 6 - above H5, 7 - below H5 but not connected, 8 - protected by dikes, -99 no data/blank
Last post by pjsnyder - March 19, 2019, 12:45:36 PM
Okay, one more question and then I should be done.
Is there any documentation of the legend for the inundation frequency output? There doesn't appear to be an option to look at this map (and therefore its legend) in the during-run mapping window analysis tools, and I can't find any mention in documentation aside from 30, 60, and 90 days. The GIS output has 0, 1, 4, 5, 6, and 7. 0 is clearly always-wet and 6 appears to be always-dry, but the other numbers are unclear.
Last post by pjsnyder - March 18, 2019, 10:21:34 PM
When I use a storm surge raster that ends in 00_010.ASC, the program still searches for an 00_100 file. Will SLAMM only run the 10-year if there's also a 100-year to run? Does it run through both? It's not totally clear to me how this is implemented. I was thinking that I could run separate runs: one with the 100-year surge over the SLR period, and one with the 10-year over the SLR period (actually, and one more just using the spring tide over the SLR period) and these would give me what those storms would look like in future years. Is that not what the model is doing?
Last post by pjsnyder - March 15, 2019, 08:00:09 AM
The user manual calls for the storm surge raster to be in NAVD88. However, I already have my DEM in MTL, so I am not using a datum correction for the DEM elevation. I assume that the surge should be in the same datum as the DEM, but the manual gives me pause since it calls for NAVD. I just wanted to make sure there isn't some additional behind-the-scenes datum conversion going on for the surge (beyond what you might input in the VDATUM file or MTL-NAVD conversion factor)
I can view the sample Santa Ynez files as rasters in GIS with no problems. I have also tried using my own .asc files for a new simulation but the files are still not valid (showing in red and the Ncols, Nrows are not being shown) in the File Setup Window.
Last post by JackieRaw - March 08, 2019, 01:36:51 AM
Thanks for your reply. I uninstalled and re-downloaded the executable and the sample files to ensure there were no problems in the file path. However, I am still getting the same error. I have changed the installation folder to avoid using C/Program Files.
I have unzipped the folder to a new location and I have loaded the Santa Ynez SLAMM6 file from this new location. If I press the "Set Map Attributes" I first get a blank window with the heading SLAMM 6.7 beta but there is no text, just an "OK" button. Then the error is returned 'Error Reading Headers for "Santa_Ynez_NWI_5m_531.asc" and I can click "OK" again. Then it opens a window Reading Site Characteristics but there is no progress from 0% and I can click on "Halt Execution".
When I go to the File Setup window then the files are shown with a red background. This remains the same when I let the files be picked up from the folder where the SLAMM6 file is or when I browse and select them through a file path. Pressing "Execute" generates the same error as above after the SLR parameters have been selected.
I might try download it on a different machine and see if I still encounter the same problem.