MLOC Output


This section describes the various output files (including plots) that may be generated by a successful run of mloc. There is a set of basic output files that are always produced and many additional files that are controlled by commands, either directly or because of the type of relocation specified by certain commands. The four types of relocation are:

The terminal window will contain some information that is not repeated in any output file but all information that has been found to be worth retaining is written to at least one output file. It is not necessary to save the terminal window after a run of mloc.

Default Output

The following files and plots are always created, whether a cluster is to be calibrated or not. Some of the more complex file types are described on their own page.

  • ~_base.pdf: Base Plot (map of final locations)
  • ~.dat0: Input Data Bulletin (record of all input data)
  • ~.depth_phases: Depth Phase File (all data relevant to depth constraint)
  • ~.hdf: HDF File (hypocenter data summary)
  • ~.kml: KML File (for plotting in Google Earth or equivalent)
  • ~.log: Log File
  • ~.phase_data: Phase Data File (complete list of phase data and usage)
  • ~.plog: Phase Identification Log (information related to changing phase names)
  • ~.rderr: Empirical Reading Error File (for each station-phase with 2 or more instances)
  • ~.stn: Station Data File (especially useful when there are supplemental station files)
  • ~.summary: Summary File (summary of the input parameters, progress through iterations and final locations)
  • ~.ttsprd: Travel Time Spread File (for each observed phase)

Every run of mloc also creates a folder named ~_gmt_scripts containing the GMT scripts used to create any plots (the ~_base.bash script at minimum). These are preserved for cases where the user may wish to modify a script for research or publication purposes.

Input Data Bulletin

As each event’s data file is read it is added line-for-line to a bulletin in MNF format. This is the only reliable record of the input data to a specific run of mloc, since event data files are constantly being edited during the course of a relocation analysis. If necessary the ~.dat0 file could be unpacked into event files using the mnf_search utility program, in order to recover the initial state of a particular run. This has almost never been necessary but it is simply good practice to retain the capability. Differential time data cannot be retained in the ~.dat0 file since each datum references two events.

KML File

The final locations of the cluster are written in Keyhole Markup Language (KML) for plotting in Google Earth or compatible programs. The file references symbols that vary in size according to magnitude, and in color according to focal depth:

  • 0-9 km: red
  • 10-19 km: green
  • 20-29 km: skyblue
  • 30+ km: blue

A yellow icon is used for events set to the cluster default depth. The image files are stored in the tables/kml subdirectory of the working directory. The paths to the image files are hard-wired in the code, so if the ~.kml file is moved from its original location, the plot will display generic icons for the events.

Log File

The log file is used to collect information about the relocation that is normally of little interest, but may be helpful if mloc is behaving strangely or giving unexpected results. The main sections deal with:

  • Events that were killed (commands memb and kill) in the command file
  • Convergence limits (command shcl)
  • The local velocity model (command lmod)
  • Starting locations read from a previous run (command rhdf)
  • If the bdps command has been set “on”, the list of stations read from the file bdps.dat
  • Reading the input data file for each event and the number of phases re-identified
  • Depth phase readings converted to relative depth phases (e.g., pP-P)
  • For each iteration, statistics on the number of readings used for hypocentroid, the number lost because of epicentral distance, the number lost because of large residual
  • For each iteration, the change in hypocentroid, weighted epicentroid, bias correction (command bias)
  • For each iteration, the changes in cluster vector parameters for each event
  • For a calibrated relocation, a list of events with hypocentral data written in the form needed for the cal_ command, so that they could be used for indirect calibration of a different cluster
  • A simplified list of hypocentral parameters for each event
  • For direct calibration, statistics on mean residuals of readings used for the hypocentroid and their use for indicating the need for depth adjustment. Outliers from this list are listed in the terminal output.

Phase Identification Log

This log file is not, technically, part of the “default” set of output files, because it could be turned off using the phid command. The default state is to do phase re-identification, however, and it is extremely unusual to turn it off.

The standard content of the phase identification log is a list of cases where the name of a phase read from the event file has been changed. Phase re-identification is done several times so there are usually several passes through the event list that have been logged, normally with decreasing numbers of changed phases as the relocation settles down.

Last Updated on