Last modified 14 months ago Last modified on 2019-04-29 10:48:49

Welcome to the Coastal Marine Geology (CMG) Trac Site

This is the site for distribution of the M_CMG SVN repository of software written by USGS Coastal Marine Geology Program scientists and collaborators. Bug reports, fixes, new features and related content will be logged in the "tickets" section of this site.


This is a working, changing compilation of programs we find useful. You may catch them in a state of change, where they either don't work or produce wrong answers. No warranty is made or implied.


This WIKI contains various kinds of documentation about using svn, using Matlab with NetCDF,data processing, review, and philosophy. Short descriptions of the contents of each directory in the repository are provided, but may not be up to date. In Matlab, typing "help DirectoryName" or "help MfileName" is the best way to view documentation

For more documentation of our practices and the approved database and what goes into our netCDF files that are released on see: A graphical display of our workflow is available by downloading the file in the attachments at the bottom of this page.

We use these guiding principals to work with and treat our data. The general workflow applied to our data is diagrammed and the processing steps described here. Check the list of what to do and what to avoid for more detail of things we use to maintain consistency in our files.

The first steps

  • Field Activity planning, Data management and COMPASS
  • What is the workflow for dealing with oceanographic data
  • Shorthand notation for naming our instruments (in file names and such)

data review, release, access topics

programming topics

Instruments and experiments


WIKI notes:
You can embed images in WIKI pages and trac tickets! Here's a way to do it.
Here's a page showing how to remove an attachment.

Planning Documents

Here are two things that Marinna uses for group planning - if you don't see something you expect on here, it's not on Marinna's radar.
There is a planning calendar for STG operations as a USGS Google Calendar here:STG Operations Calendar
The list of instruments and reservations is a USGS internal Google Doc page here: Instrument Reservations

Required Tools for using this svn repository

This site uses Subversion (svn for short) to manage software version control. The public site for accessing the code (open access, no passphrase, but no write permission, using a svn client) is :[[BR]]

If you have a user name and passphrase, checkout the code from here :

If your are a registered user and are logged in, you may view the code by clicking the "Browse Source" tab in the black horizontal bar under the banner and follow the directory structure to the software desired. Eventually, you can drill down to individual pages with Matlab code. You can view the changes in specired versions of a program from this interface.

Although you can browse the source code using Trac, to download the code you really should use the Subversion revision control system software. There is no alternate FTP or HTTP access to tar.gz or zip files. More information on the tools used (Trac and Wiki) to implement this site are described here.

Want to Log In?

This site is open to all to read, and we also provide access (read and write) to collaborators interested in improving specific directories. USGS users are invited to establish their own subdirectories in the repository. The access control of each directory is up to individual owners, and the repository is backed up nightly, so it is a safe and convenient spot to save your code.

Starting Points

To use subversion, the client must be installed on the user's computer (often pre-installed on linux). PC users may try installing Tortoise SVN, a nice GUI interface to svn commands.

Whats New

If your installation of these tools gives weird messages or stops working, there might be a recent change (e.g., naming convention, calling parameters, etc) in the software. These changes should be documented in the Whats New but often are not. You might get some clues by looking at the svn history.

Here is an update on the way our file names are assembled in the new world with mooring IDs > 1000.
Here is an update on the proposed new instrument name abbreviations.