Array Manager - Matlab graphical user interface for RR processing for an array of MT sites
Copyright (c) 2002-2011 Oregon State University AUTHOR Gary Egbert College of Atmospheric and Oceanic Sciences
"Array Manager" is a matlab graphical user interface for handling data from an array of MT sites. It was written to handle data from the EarthScope array, but it should be useful for other long period MT surveys as well. The basic interface displays all runs, collected into sites, with a graphical display of times when the site was running. It makes it easy to see which sites overlap, and for how long. A principal use of the interface is for picking pairs of sites for remote reference, or groups of sites for multiple station processing. It also provides an interface for loading time series files for plotting (including simultaneous plotting of data at two or more site), and it can be used to select impedance files for display.
First, set up a directory structure for your survey, say "Cascadia".
Create a directory, say C:\MT\surveys\Cascadia\original and place
all raw NIMS data there.
Then, create directory C:\MT\surveys\Cascadia\CF and place your EMTF
configuration files there. Process all raw data using SS.
Before using ArrayManager, your directory structure MUST include:
original/Here your raw data,*.matand*.xmlfiles are located;CF/These are dnff and tranmt configuration files;data/Contains*.binfiles for all data (output of nimsread or SS).
Array Manager uses matlab functions from: TSplot, EMTF/matlab/UTIL, EMTF/matlab/Zplt, and SS. For full functionality (i.e., for time
series processing) it calls executables dnff, tranmtlr, and multmtrn.
Fortran source codes for these routines are in EMTF.
For ArrayManager to work, you need to set the Matlab environment
variable MTdata, which is the path to where your data is processed:
setenv('MTdata', 'C:\MT\surveys\')
You can add it to your Matlab startup file or call it manually.
The main driver is a matlab function ArrayManager(Survey).
Survey gives the path (relative to MTdata) of the specific survey
being processed (e.g., "Cascadia"). This is the directory
which contains subdirectories data, XML, original, MT, FC, tmp, etc.
Optionally, can call ArrayManager(Survey,maxSites): here,
maxSites is used to control how many sites are displayed initially.
This is useful when there are a large number of sites in the survey
(e.g., in Cascadia, there were 80 sites, too many to display in
a single window at useful resolution). Given a list
of available data runs is generated from the list of *.xml files
in /XML, and the associated metaData is retrieved. Using
the list, NIMSinfo is created (on the fly) by checking which of
the files (*.bin, *.sp, *.f5, *.br) exist in the appropriate
survey subdirectories. This information is passed to function
dataTimes, which initializes the ArrayManager GUI, with the input
information saved as "UserData" for the ArrayManager main figure.
At this point control of the ArrayManager essentially passes to
dataTimesCB, a script which implements callbacks for all user
interface objects in the ArrayManager. Note that all (or at least
almost all!) of the symbols used by the callbacks refer to data
that is retrieved from GUI UserData.
Additional information on other matlab functions and scripts, and their dependencies, is given in ArrayManagerNotes.
Some other notes ... documentation, such as it is, for now.
Transfer functions: Single site, remote reference, and multiple site transfer function computations are supported by the array manager interface. To use, select files to process by clicking on the run letter boxes (a, b, c, etc., to the left of the site name). If the total number of sites selected is 1, the SS button (for single site processing) is enabled. If > 1 the RR (remote reference) and MMT (multiple station) buttons are enabled. Clicking the buttons opens an interface with the selected file names displayed for local, remote, etc., as well as a default "options" file. The list of selected files can be edited, as can the name of the options file. Then by clicking "process" the appropriate fortran program is started.
The default options file names are taken from the last three lines of the local (survey) paths.cfg file (the first six lines of paths.cfg are read by dnff to set paths for I/O for this program. The last three lines are read by dataTimes.m. If these extra lines of input are found, they are used, respectively, to initialize
- options file for single site processing; (2) options file for remote reference processing; (3) band setup file for MMT processing. If not read succesfully the names default to
CF/options_SS.cfg;(2)CF/options_RR.cfg;(3)CF/bs_1hzNIMS.cfg. Once read (or set to default) the file names are stored as user data in the corresponding GUI pushbotton (SS, RR, MMT, respectively). If edited, the edited config file name is stored in user data, so subsequent uses of the processing button (in the same session, until changed by editing again through the processing interface) will default to the new name.