Outputs - ahotovec/REDPy GitHub Wiki

Output File Structure

REDPy/
    default/
        clusters/
            0.html
            0.png
            fam0.jpg
            map0.png (if checkComcat is True)
            0-report.html (if createReport.py was run)
            0-report-bokeh.html (if createReport.py was run)
            0-report.png (if createReport.py was run)
            0-reportcmat.png (if createReport.py was run)
            0-reportwaves.png (if createReport.py was run)
            ...
        junk/ (if plotJunk.py was run)
            2018-01-01T00/00/00.000000Z-0.png (if plotJunk.py was run)
            ...
        catalog.txt
        cores.txt
        dailycounts.txt
        junk.txt (if plotJunk.py was run)
        orphancatalog.txt
        overview_recent.html
        overview.html
        swarm.csv

Bokeh Plots

overview.html and overview_recent.html are interactive plots with a shared time axis (i.e., panning or zooming in one window will update the rest). overview_recent.html shares the same format as overview.html but for only the last recplot days, and shows all families active within that period in the occurrence timeline (instead of clusters with at least minplot members).

Navigation bar at top right has options to pan, zoom, tap, reset, and save. Title (here, 'REDPy Catalog') is set in title.

The Repeaters vs. Orphans plot is a histogram with number of both types of events within bins defined by binhr and binday; the total number of triggers in that hour will be the sum of these two.

The Frequency Index plot has a point for every repeating event related to its frequency content. Tectonic-type events usually have FI>0 and 'long period' earthquakes have FI<0 with the default settings. This plot is useful for quickly identifying the character of repeating seismicity.

The Occurrence Timeline has horizontal lines corresponding to individual clusters/families, with endpoints at the times of the first and last events in that cluster. Colored bars correspond to hours with activity within that cluster, colored by the number of events within that hour (see color scale at top left). The number to the right of the bars corresponds to the number of total members within the cluster. Hovering the mouse over a cluster will display a preview waveform (core event at plotsta station) and the cluster's ID number. Clicking here will open a more detailed page about the cluster.

The Cluster Longevity plot orders the clusters in the occurrence timeline by the length of time they are active, and can be useful for identifying times when many clusters die or are created. If the starting time of a cluster is before the date of the start of overview_recent.html, an arrow will indicate that the cluster extends off the plot.

Below is the overview_recent.html output of the suggested default run:

Cluster Pages

Each cluster has its own detailed page with statistics and plots. At the very top are links to the previous and next clusters (ordered by starting time) for navigation between subsequent clusters (though you may always change the number just before .html manually, if you wish). The preview waveform is the same as the occurrence plot on overview.html, and some quick statistics are listed below it.

Top left plot shows the core (black) and stacked (red) waveforms at each station/channel used, and at right is the sum of the Fourier amplitude spectra over all stations. Below those are three timelines. First, the amplitude (on the same preview station only) of each event with time. Next, the time between successive members of the cluster in hours (note the logarithmic scale). Last is the cross-correlation coefficient relative to the best correlated event. Open circles at the bottom mean that no value is stored for that pair (either not computed or below cmin). This is intended to help visualize how the waveforms are changing with time. Note that the coefficient plotted here is what is stored in the table, which is the maximum across all stations used.

Below is the page for Cluster 1 from the suggested default run:

Text Files

catalog.txt: Dates of all repeaters in the catalog and their associated cluster number. If verbosecatalog is True, then frequency index, amplitude, time since previous event in hours, and correlation coefficient with respect to the best correlated event are also included.

cores.txt: Dates of core events and their cluster number. Could be used to create templates from core events.

dailycounts.txt: Tabulated daily 'histogram' of occurrence of each cluster.

junk.txt: If plotJunk.py was run, dates of all triggers and associated type code.

orphancatalog.txt: Dates of current orphans.

swarm.csv: This file can be read by Swarm v2.8.5+ using the tagging feature to annotate the interactive helicorders. It marks each repeating event with a label that has the groupName and the cluster it belongs to (so for the default run, family 1 would be labeled as 'default1'). The station listed is the one referenced by printsta in the configuration, and can be changed using global find/replace in a text editor to change which station or channel the tags will appear on. Finally, colors can be chosen for clusters of interest by adding lines to the EventClassifications.config file in the Swarm folder. For example, adding the line:

default1, #ffff00

changes the appearance of members of the default1 family to be yellow to stand out against the default red-orange of the rest of the catalog.