Model:CEM: Difference between revisions
No edit summary |
m (removed old questionnaire information. Replaced with form) |
||
Line 1: | Line 1: | ||
{{ | {{Modeler information | ||
| | |First name=A. Brad | ||
| | |Last name=Murray | ||
| | |Type of contact=Project manager | ||
| | |Institute / Organization=Duke University | ||
| | |Postal address 1=Box 90230 | ||
|Town / City=Durham | |||
|Postal code=27708-0230 | |||
|State=North Carolina | |||
|Country=USA | |||
|Email address=abmurray@duke.edu | |||
|Phone=919 681-5069 | |||
|Fax=919 684-5833 | |||
}} | }} | ||
{{Additional modeler information | |||
|First name=Andrew | |||
|Last name=Ashton | |||
|Type of contact=Model developer | |||
|Institute / Organization=Woods Hole Oceanographic Institution | |||
|Postal address 1=360 Woods Hole Rd. | |||
|Postal address 2=Clark 257 MS #22 | |||
|Town / City=Woods Hole | |||
|Postal code=02543 | |||
|State=Massachusetts | |||
|Country=USA | |||
|Email address=aashton@whoi.edu | |||
|Phone=508-289-3751 | |||
}} | |||
{{Additional modeler information | |||
|First name=Jordan | |||
|Last name=Slott | |||
|Type of contact=Model developer | |||
}} | |||
{{Model identity | |||
|Model type=Single | |||
|Categories=Coastal | |||
|Spatial dimensions=1D | |||
|Spatialscale=Landscape-Scale | |||
|One-line model description=Coastal evolution model | |||
|Extended model description=The Coastline Evolution Model (CEM) addresses predominately sandy, wave-dominated coastlines on time-scales ranging from years to millenia and on spatial scales ranging from kilometers to hundreds of kilometers. Shoreline evolution results from gradients in wave-driven alongshore sediment transport. At its most basic level, the model follows the standard 'one-line' modeling approach, where the cross-shore dimension is collapsed into a single data point. However, the model allows the plan-view shoreline to take on arbitrary local orientations, and even fold back upon itself, as complex shapes such as capes and spits form under some wave climates (distributions of wave influences from different approach angles). The model can also represent the geology underlying the sandy coastline and shoreface in a simplified manner and enables the simulation of coastline evolution when sediment supply from an eroding shoreface may be constrained. CEM also supports the simulation of human manipulations to coastline evolution through beach nourishment or hard structures. | |||
}} | |||
{{Model technical information | |||
|Supported platforms=Unix, Linux, Mac OS | |||
|Programming language=C | |||
|Code optimized=Single Processor | |||
|Start year development=2000 | |||
|Does model development still take place?=Yes | |||
|Model availability=As code | |||
|Source code availability=Through CSDMS repository | |||
|Program license type=BSD or MIT X11 | |||
|OpenMI compliant=No but planned | |||
|CCA component=No but planned | |||
|IRF interface=Yes | |||
|Memory requirements=20 Mb | |||
|Typical run time=days | |||
}} | |||
{{Input - Output description | |||
|Describe input parameters=The input parameters to a model run consist of an initial shoreline, a wave file, and a set of configuration parameters. The initial shoreline is stored within a custom binary formatted-file. Since CEM has been used for abstract simulations of coastline evolution, the initial model condition consists either of a mostly-smooth shoreline with initial perturbations to the shoreline position (generated by a tool provided with the model), or using a shoreline that resulted from a previous model run. The wave file consists of a set of wave approach angles and wave heights that are used during the model run. This wave file is also generated by a tool provided with the model, and takes as input the statistical distribution of wave-approach angles. Finally, basic model parameters (e.g. number of time steps to simulate, etc.) are specified within an XML-formatted text file. An example is provided with the model. | |||
|Input format=Binary | |||
|Other input format=XML | |||
|Describe output parameters=The output of the model consists of snapshots of the coastline during its evolution. The model can be configured to write the resulting coastline at any point during the simulation. The output format of the coastline file is a custom binary formatted-file (the same format as the initial model input). Also, for convenience using with other software tools such as MATLAB, an ASCII-based file of the coastline shape can be written too. The model can also directly generate JPEG-formatted pictures of the coastline shape at any time during the simulation. | |||
|Output format=ASCII, Binary | |||
|Other output format=JPEG | |||
|Pre-processing software needed?=No | |||
|Post-processing software needed?=Yes | |||
|Describe post-processing software=Post-processing software is sometimes necessary: In some instances (if not just using the JPEGs generated by the model code), some post-processing of the results is desired, e.g. to compare the position of the shoreline between two different times. The model code comes with simple tools to perform simple post-processing. The model also outputs the shoreline in an ASCII format and further post-processing may be achieved using tools such as MATLAB. | |||
|Visualization software needed?=Yes | |||
|If above answer is yes=Matlab | |||
|Other visualization software=Note: if using the JPEGs automatically generated, the answer to the visualization question is 'no.' | |||
}} | |||
{{Process description model | |||
|Describe processes represented by the model=A continuity equation, representing the conservation of sediment in the nearshore zone, relates gradients in alongshore sediment flux to horizontal shoreline changes, given a depth over which erosion or accretion are distributed—the depth of the shoreface. This treatment embodies the assumption that cross-shore sediment fluxes across base of the shoreface are small compared to gradients in alongshore flux. However, cross-shore sediment fluxes landward of the shoreline, associated with overwash, are treated, allowing barriers to migrate and maintain elevation relative to a rising sea level. See Ashton and Murray (2006a) for a full treatment of these model dynamics. | |||
The material underlying the shoreline and shoreface converted to mobile sediment as it is exposed by shoreline erosion. The lithology is parameterized by two quantities that can vary across the model domain: the maximum weathering rate (which occurs when the shoreface is bare of sediment) and the composition of the resulting sediment (percentage coarse enough to stay in the nearshore system. See Valvo et al. (2006) for a full explanation of how underlying geology is treated. | |||
Where beach nourishment is deemed by the user to be occurring, if the gradients in sediment flux would cause the shoreline to erode landward of a pre-determined location, sediment is added at the rate required to prevent such shoreline change. Hard structures are treated as if the lithology has a maximum weathering rate of 0. | |||
|Describe key physical parameters and equations=The evolution of the coastline is governed by a continuity equation; the rate of horizontal shoreline change in the local cross-shore direction is proportional to the divergence of alongshore sediment flux. Alongshore sediment transport is computed via the common CERC formula, which relates alongshore sediment flux to breaking-wave approach angle and breaking wave height. Breaking-wave characteristics in each shoreline location are calculated by starting with the deep-water height and propagation direction (obtained for each time slice from the input wave file), and refracting and shoaling the waves over assumed shore-parallel contours until breaking occurs. The CERC equation also involves an empirical constant K, which can be configured by the model user. Other equations for sediment flux can easily be substituted. See Ashton and Murray (2006a) for details. | |||
|Describe length scale and resolution constraints=Kilometers to hundreds of kilometers. Numerically, the model can be discretized with much smaller spatial resolution. However, the assumptions of approximately shore-parallel shoreface contours becomes unreasonable at scales smaller than kilometers. | |||
|Describe time scale and resolution constraints=Years to millenia. Typically, the model is run with timesteps on the order of a day. However, the assumptions that the shoreface progrades or erodes while maintaining its cross-shore shape prevents model results from being interpreted as meaningful over time scales shorter than years to decades. (Storm and post storm cross-shore shifting of sediment within the shoreface causes shoreline fluctuations on event timescales that are implicitly averaged out in this model.) | |||
|Describe any numerical limitations and issues=The model handles complex-shaped coastlines, such as cuspate-capes and spits. However, where the shoreline curvature becomes extreme (radius of curvature comparable to the cross-shore shoreface extent), as at the ends of spits, the assumptions of a locally rectilinear coordinate system break down, and sediment is conserved less rigorously locally. See Ashton and Murray (2006a) for details. | |||
}} | |||
{{Model testing | |||
|Describe available calibration data sets=In one application, the rate of change in the model has been calibrated to a state data set averaging shoreline change over 50 years (from the North Carolina Department of Transportation; see Slott et al., 2007). Numerous other shoreline change data sets are available, based on surveys of various sorts, aerial photography, and recently LIDAR (e.g. Lazarus and Murray, 2007). | |||
|Describe available test data sets=See answer above; many shoreline data sets exist. Comparing model results to detailed records of coastline change will become more appropriate as the model is used to investigate shoreline change in more detail in a particular location and time period. | |||
However, to date the model has been used chiefly for relatively abstract explorations of how coastline evolution works: how emergent coastline structures such as capes, spits, and alongshore sand waves form and interact; how heterogeneity in underlying geology affects coastline evolution; how scenarios of changing storm and wave climates would affect coastline change; and how human manipulations alter large-scale coastline change). Ashton and Murray (2006b) compared robust model predictions concerning the way local wave climates vary along a coastline with emergent structures (capes and flying spits) to hindcast wave climates along actual shorelines. As opposed to testing whether model parameters can be adjusted to reproduce observations in detail, testing a robust prediction like this, which does not depend on the formal details of the model ingredients, can falsify the hypothesis that the interactions in the model capture the basic aspects of the interactions that are important in the actual system (see Murray, 2003; 2007). | |||
|Describe ideal data for testing=See answer above and Ashton and Murray (2006a, b). Data sets spanning large spatial scales are most appropriate, and if model behaviors are going to be compared to shoreline change, long temporal scales are best (see ‘limitations’ above). | |||
}} | |||
{{Users groups model | |||
|Do you have current or future plans for collaborating with other researchers?=Collaborations are underway within Duke University (an interdisciplinary project involving human shoreline manipulations) and Woods Hole Oceanographic Institution (where the model is being used to explore delta dynamics). Various collaborations involving researchers in the US and abroad are in various stages. | |||
}} | |||
{{Documentation model | |||
|Provide key papers on model if any=The following papers: | |||
* Ashton, A, A.B. Murray, and O. Arnoult. 2001. "Formation of coastline features by large-scale instabilities induced by high-angle waves." Nature 414: 296-300. | |||
* Ashton, A. D. and A. B. Murray. 2006a. "High-angle wave instability and emergent shoreline shapes: 1. Modeling of sand waves, flying spits, and capes. Journal of Geophysical Research 111. F04011, doi:10.1029/2005JF000422. | |||
* Ashton, A. D. and A. B. Murray. 2006b. "High-angle wave instability and emergent shoreline shapes: 2. Wave climate analysis and comparisons to nature. Journal of Geophysical Research 111. F04012, doi:10.1029/2005JF000423. | |||
* Lazarus, E.D., and Murray, A.B., 2007, Process Signatures in regional patterns of shoreline change on annual to decadal timescales, Geophysical Research Letters 34, L19402, doi:10.1029/2007GL031047. | |||
* Slott, J., Murray, A.B., Ashton, A., and Crowley, T., 2006 Coastline responses to changing storm patterns, Geophysical Research Letters, 33, L18404, doi:10.1029/2006GL027445. | |||
* Valvo, L. M., A. B. Murray, and A. Ashton. 2006. How does underyling geology affect coastline change? An initial modeling investigation. Journal of Geophysical Research 111. F02025, doi:10.1029/2005JF000340. | |||
== | |||
Papers on Modeling and Model Testing Strategies: | |||
* Murray, A.B., 2007, Reducing model complexity for explanation and prediction, Geomorphology, 90, 178-191. | |||
* Murray, A.B., 2003, Contrasting the goal, strategies, and predictions associated with simplified numerical models and detailed simulations, in Prediction in Geomorphology, Dick Iverson and Peter Wilcock Eds, Geophysical Monograph 135, American Geophysical Union, 151-165. | |||
|Manual model available=No | |||
}} | |||
{{Additional comments model | |||
|Comments=This entry, with the name 'Coastline Evolution Model' should replace the 'Murray model' currently listed. Thanks Albert! | |||
}} | |||
<!-- PLEASE USE THE "EDIT WITH FORM" BUTTON TO EDIT ABOVE CONTENTS; CONTINUE TO EDIT BELOW THIS LINE --> | |||
==Introduction== | |||
'''NOTE: This page is still under development. Some information may be incorrect. When we believe everything is correct, we'll remove this message.''' | '''NOTE: This page is still under development. Some information may be incorrect. When we believe everything is correct, we'll remove this message.''' | ||
==Coastline Evolution Model: Introduction== | |||
This site hosts the source code for the Coastline Evolution Model (CEM) from Duke University. To find out more technical details of this model, please visit the [[Model: | This site hosts the source code for the Coastline Evolution Model (CEM) from Duke University. To find out more technical details of this model, please visit the [[Model:Test_CEM#Metadata]] page. This purpose of the instructions on this page are to explain how to download, compile, and use the model. | ||
Please keep in mind this is an open-source project, not shrink-wrapped software. So it may require a bit of effort to get running on your own system. The source code is very-well documented however, and we'd encourage you to extend it for your own purposes. | Please keep in mind this is an open-source project, not shrink-wrapped software. So it may require a bit of effort to get running on your own system. The source code is very-well documented however, and we'd encourage you to extend it for your own purposes. | ||
Line 23: | Line 122: | ||
The source code is licensed under the Berkeley Standard Distribution (BSD) license. | The source code is licensed under the Berkeley Standard Distribution (BSD) license. | ||
==Supported Systems & Requirements== | |||
Currently, the source code has only been run on Linux CentOS (which is a variation of RedHat Linux). It has also been successfully used on Mac OSX and Solaris, but the Makefiles will need slight tweaks on those systems. We'd appreciate any help getting the model to run on systems other than Linux! | Currently, the source code has only been run on Linux CentOS (which is a variation of RedHat Linux). It has also been successfully used on Mac OSX and Solaris, but the Makefiles will need slight tweaks on those systems. We'd appreciate any help getting the model to run on systems other than Linux! | ||
Line 36: | Line 135: | ||
You may need to tweak the Makefile to compile if you have these two libraries installed in a non-standard location; contact us for help. | You may need to tweak the Makefile to compile if you have these two libraries installed in a non-standard location; contact us for help. | ||
==Download needs to get the Source Code== | |||
To download the source code, you must use Subversion (svn), which you can get at http://subversion.tigris.org/.<br> | To download the source code, you must use Subversion (svn), which you can get at http://subversion.tigris.org/.<br> | ||
Line 43: | Line 142: | ||
For help on how to use Subversion, an excellent manual is available online at [http://svnbook.red-bean.com/ http://svnbook.red-bean.com/] | For help on how to use Subversion, an excellent manual is available online at [http://svnbook.red-bean.com/ http://svnbook.red-bean.com/] | ||
=== Source Code ''CEM''=== | |||
''CEM'' is a stand-alone subroutine. | ''CEM'' is a stand-alone subroutine. | ||
To browse the repository, point your browser to: [http://csdms.colorado.edu/viewvc/?root=cem http://csdms.colorado.edu/viewvc/?root=cem] | To browse the repository, point your browser to: [http://csdms.colorado.edu/viewvc/?root=cem http://csdms.colorado.edu/viewvc/?root=cem] | ||
=== Command-Line Access === | |||
If you plan to make changes, use this command to check out the code as yourself using HTTPS: | If you plan to make changes, use this command to check out the code as yourself using HTTPS: | ||
< | <syntaxhighlight lang=bash> | ||
# Project members authenticate over HTTPS to allow committing changes. | # Project members authenticate over HTTPS to allow committing changes. | ||
svn checkout https://csdms.colorado.edu/svn/cem/ | svn checkout https://csdms.colorado.edu/svn/cem/ | ||
</ | </syntaxhighlight> | ||
When prompted, enter your CSDMS Subversion password. | When prompted, enter your CSDMS Subversion password. | ||
Line 64: | Line 163: | ||
=== Source-Code Snapshots === | |||
Source-code snapshots are available via ftp at: | Source-code snapshots are available via ftp at: | ||
Line 73: | Line 172: | ||
:[http://csdms.colorado.edu/pub/models/cem-latest.tar.gz cem-latest.tar.gz] | :[http://csdms.colorado.edu/pub/models/cem-latest.tar.gz cem-latest.tar.gz] | ||
==Compiling the Source Code== | |||
Once you have downloaded the source code, you can compile it using the UNIX/Linux 'make' utility (which should come standard with your Operating System). It is probably worthwhile to edit the Makefile in the cem/ and cem/tools/ directories to set the options you want. There are further instructions there. | Once you have downloaded the source code, you can compile it using the UNIX/Linux 'make' utility (which should come standard with your Operating System). It is probably worthwhile to edit the Makefile in the cem/ and cem/tools/ directories to set the options you want. There are further instructions there. | ||
Line 79: | Line 178: | ||
To compile from the cem/ directory, simply enter the 'make' command. It compiles the model into an executable named 'cem'. It also compiles the tools/ subdirectory. | To compile from the cem/ directory, simply enter the 'make' command. It compiles the model into an executable named 'cem'. It also compiles the tools/ subdirectory. | ||
==Running the CEM Model== | |||
The CEM model is a command-line driven program. It has no GUI (Graphical User Interface). It takes several inputs: | The CEM model is a command-line driven program. It has no GUI (Graphical User Interface). It takes several inputs: | ||
Line 98: | Line 197: | ||
Note that the 'cem' executable must be in your path, and <path to config file> is the directory in which the XML configuration file is located. | Note that the 'cem' executable must be in your path, and <path to config file> is the directory in which the XML configuration file is located. | ||
==The XML-based Configuration File== | |||
A text-based XML-formatted file sets configuration options for CEM. You can find an example in the xml/ subdirectory. Please use that example config.xml for your own purposes. The configuration options are relatively straight forward with brief explanations below. | A text-based XML-formatted file sets configuration options for CEM. You can find an example in the xml/ subdirectory. Please use that example config.xml for your own purposes. The configuration options are relatively straight forward with brief explanations below. | ||
Line 117: | Line 216: | ||
# '''ast_rate''': To scale the rate of alongshore sediment transport constant. | # '''ast_rate''': To scale the rate of alongshore sediment transport constant. | ||
==Creating an Initial Shoreline (SPX) File== | |||
There is a utility program in the tools/ directory, called 'spxcreate' to create an initial shoreline. This utility creates model shorelines that are initially straight or have small initial perturbations. The utility works off a set number of predefined shorelines; you have the ability to override any individual attribute of the initial shoreline. | There is a utility program in the tools/ directory, called 'spxcreate' to create an initial shoreline. This utility creates model shorelines that are initially straight or have small initial perturbations. The utility works off a set number of predefined shorelines; you have the ability to override any individual attribute of the initial shoreline. | ||
Line 131: | Line 230: | ||
Please see the source code (tools/spxcreate.c) for more documentation. Typically, cells in the shoreline have widths of either 100 m or 1000 m. | Please see the source code (tools/spxcreate.c) for more documentation. Typically, cells in the shoreline have widths of either 100 m or 1000 m. | ||
==Creating a Wave Forcings (WVX) File== | |||
There is a utility program in the tools/ directory, called 'wvxcreate' to create an initial shoreline. This utility creates waves according to two parameters: the proportion of waves approaching from high angles and the proportion of the waves approach from the left (looking off-shore). | There is a utility program in the tools/ directory, called 'wvxcreate' to create an initial shoreline. This utility creates waves according to two parameters: the proportion of waves approaching from high angles and the proportion of the waves approach from the left (looking off-shore). | ||
Line 143: | Line 242: | ||
Note that you must generate enough waves for your simulation. The number of waves is simply the number of timesteps of your simulation divided by the number of timesteps per wave as set in your config.xml file. | Note that you must generate enough waves for your simulation. The number of waves is simply the number of timesteps of your simulation divided by the number of timesteps per wave as set in your config.xml file. | ||
==Processing the Output== | |||
The CEM model lets you generate both shoreline (SPX) files and picture (JPEG) files at any point during the simulation. If you wish to generate a text file of the positions of the beach (the dividing line between the ocean and land), you may use the 'spxposition' utility located in the tools/ directory. You can then import this text file into other programs (e.g. MATLAB). The usages of the 'spxposition' utility is simple: | The CEM model lets you generate both shoreline (SPX) files and picture (JPEG) files at any point during the simulation. If you wish to generate a text file of the positions of the beach (the dividing line between the ocean and land), you may use the 'spxposition' utility located in the tools/ directory. You can then import this text file into other programs (e.g. MATLAB). The usages of the 'spxposition' utility is simple: | ||
Line 149: | Line 248: | ||
% spxposition <spx file> | % spxposition <spx file> | ||
== Issues == | |||
== Help == | |||
== Input Files == | |||
== Output Files == | |||
== Download == | |||
== Source == | |||
[[Category:Coastal]] | [[Category:Coastal]] |
Revision as of 15:05, 18 September 2009
Contact
Name | A. Brad Murray |
Type of contact | Project manager |
Institute / Organization | Duke University |
Postal address 1 | Box 90230 |
Postal address 2 | |
Town / City | Durham |
Postal code | 27708-0230 |
State | North Carolina |
Country | USA"USA" is not in the list (Afghanistan, Albania, Algeria, Andorra, Angola, Antigua and Barbuda, Argentina, Armenia, Australia, Austria, ...) of allowed values for the "Country" property. |
Email address | abmurray@duke.edu |
Phone | 919 681-5069 |
Fax | 919 684-5833 |
Name | |
Type of contact | |
Institute / Organization | |
Postal address 1 | |
Postal address 2 | |
Town / City | |
Postal code | |
State | |
Country | |
Email address | |
Phone | |
Fax |
Name | |
Type of contact | |
Institute / Organization | |
Postal address 1 | |
Postal address 2 | |
Town / City | |
Postal code | |
State | |
Country | |
Email address | |
Phone | |
Fax |
CEM
Metadata
Summary
Technical specs
In/Output
Process
Testing
Other
IntroductionNOTE: This page is still under development. Some information may be incorrect. When we believe everything is correct, we'll remove this message. Coastline Evolution Model: IntroductionThis site hosts the source code for the Coastline Evolution Model (CEM) from Duke University. To find out more technical details of this model, please visit the Model:Test_CEM#Metadata page. This purpose of the instructions on this page are to explain how to download, compile, and use the model. Please keep in mind this is an open-source project, not shrink-wrapped software. So it may require a bit of effort to get running on your own system. The source code is very-well documented however, and we'd encourage you to extend it for your own purposes. The source code is licensed under the Berkeley Standard Distribution (BSD) license. Supported Systems & RequirementsCurrently, the source code has only been run on Linux CentOS (which is a variation of RedHat Linux). It has also been successfully used on Mac OSX and Solaris, but the Makefiles will need slight tweaks on those systems. We'd appreciate any help getting the model to run on systems other than Linux! The model code is written in C and requires the GNU Compiler Collection (GCC), preferably under version 4.0.2 or greater. It has also been run under GCC v2.9.6. Please do not use the GCC v3.x.x compiler series; we have run into issues with them. The model code requires two libraries to be installed on your system:
You may need to tweak the Makefile to compile if you have these two libraries installed in a non-standard location; contact us for help. Download needs to get the Source CodeTo download the source code, you must use Subversion (svn), which you can get at http://subversion.tigris.org/. For help on how to use Subversion, an excellent manual is available online at http://svnbook.red-bean.com/ Source Code CEMCEM is a stand-alone subroutine. To browse the repository, point your browser to: http://csdms.colorado.edu/viewvc/?root=cem Command-Line AccessIf you plan to make changes, use this command to check out the code as yourself using HTTPS: # Project members authenticate over HTTPS to allow committing changes.
svn checkout https://csdms.colorado.edu/svn/cem/
When prompted, enter your CSDMS Subversion password. Non-members may only check out a read-only working copy of the project source. To obtain a CSDMS Subversion account or to become a member of this project, please email csdms@colorado.edu.
Source-Code SnapshotsSource-code snapshots are available via ftp at: The latest version: Compiling the Source CodeOnce you have downloaded the source code, you can compile it using the UNIX/Linux 'make' utility (which should come standard with your Operating System). It is probably worthwhile to edit the Makefile in the cem/ and cem/tools/ directories to set the options you want. There are further instructions there. To compile from the cem/ directory, simply enter the 'make' command. It compiles the model into an executable named 'cem'. It also compiles the tools/ subdirectory. Running the CEM ModelThe CEM model is a command-line driven program. It has no GUI (Graphical User Interface). It takes several inputs:
It generates several outputs:
Once you have generated the configuration file, the initial shoreline, and the set of wave forcings (described below), you can run the model on the command-line as follows: % cem --config=<path to config file>/config.xml Note that the 'cem' executable must be in your path, and <path to config file> is the directory in which the XML configuration file is located. The XML-based Configuration FileA text-based XML-formatted file sets configuration options for CEM. You can find an example in the xml/ subdirectory. Please use that example config.xml for your own purposes. The configuration options are relatively straight forward with brief explanations below.
Creating an Initial Shoreline (SPX) FileThere is a utility program in the tools/ directory, called 'spxcreate' to create an initial shoreline. This utility creates model shorelines that are initially straight or have small initial perturbations. The utility works off a set number of predefined shorelines; you have the ability to override any individual attribute of the initial shoreline. For example, % spxcreate "Rough Beach 100m" will create an initially straight shoreline with small perturbations that is 150 cells alongshore, 100 cells cross-shore, where each cell is 100 m on each side. If you want to make an initial shoreline with an alongshore length of 300 cells instead, you can do something like % spxcreate "Rough Beach 100m" ALONG=300 Please see the source code (tools/spxcreate.c) for more documentation. Typically, cells in the shoreline have widths of either 100 m or 1000 m. Creating a Wave Forcings (WVX) FileThere is a utility program in the tools/ directory, called 'wvxcreate' to create an initial shoreline. This utility creates waves according to two parameters: the proportion of waves approaching from high angles and the proportion of the waves approach from the left (looking off-shore). For example, % wvxcreate -n 5000 -d 0.60 -h 0.55 -w 1.7 -f waves.wvx will create a file named 'waves.wvx' that contains 5000 waves. Each wave has a height of 1.7m and 60% of the wave influences approach from the left (looking off-shore) and 55% of the wave influences approach from high-angle. Note that you must generate enough waves for your simulation. The number of waves is simply the number of timesteps of your simulation divided by the number of timesteps per wave as set in your config.xml file. Processing the OutputThe CEM model lets you generate both shoreline (SPX) files and picture (JPEG) files at any point during the simulation. If you wish to generate a text file of the positions of the beach (the dividing line between the ocean and land), you may use the 'spxposition' utility located in the tools/ directory. You can then import this text file into other programs (e.g. MATLAB). The usages of the 'spxposition' utility is simple: % spxposition <spx file> IssuesHelpInput FilesOutput FilesDownloadSource |