Is there an option to write ASCii maps of simulated MTL depths for each timestep specified ?

The steps above resulted in completed simulations. I guess jacking up the virtual memory past 4 GB will not do anything in the near future. By footprint, do you mean the "Memory Utilization in GB" ? I am new to this and don't quite understand all of the jargon yet, so thanks for your patience.

Thanks for addressing my questions and insight. Regarding irrelevant cells (blank), I would expect some landscape with no wetland designation to become wetland with SLR. By not tracking blank raster cells, is this possibility removed - unless the cell has a SLAMM code >= 2.

Hope the 32b to 64b port smooths out soon.


-Justin

Hello,

We are having trouble with out of memory errors in version 6.0.1 using Windows XP. The pilot datasets are quite a bit smaller than the successful examples described in this thread, but still large (~1:48,000 scale at 1 meter resolution, but with elevations over 50m masked out with limited wetland class coverage). Our first attempts are to:

1. Reduce the spatial extent of the analysis
2. Increase the virtual memory on the D: drive (non OS) to 5-10 GB. 

I do not yet understand how the "Do Not Track ""Blank"" Cells" option makes processing more efficient. Also, can you gain efficiency by populating the "Sites" parameter?

Any tips for increasing efficiency of processing are appreciated. 

Justin A. Saarinen, GISP
Geographer
USGS-Western Fisheries Research Center
at Hatfield Marine Science Center
2111 SE Marine Science Drive
Newport, OR 97365
Phone: 541-867-5022
FAX: 541-867-4049
EMAIL: jsaarinen@usgs.gov