The `overview.html`, `overview_meta.html`, and `overview_recent.html` files are interactive plots with a shared time axis (i.e., panning or zooming in one panel will update the rest) that can be opened in a web browser. `overview_recent.html` shares the same format as `overview.html` but for only the last [`recplot`](Inputs-and-Settings#configuration-file) days, and shows all families active within that period in the occurrence timeline (instead of families with at least [`minplot`](Inputs-and-Settings#configuration-file) members). Meanwhile, `overview_meta.html` condenses all plots into tabs so many runs can appear on a `meta.html` page at once. This plot shows the last [`mrecplot`](Inputs-and-Settings#configuration-file) days with at least [`mminplot`](Inputs-and-Settings#configuration-file) members. The ending time of the plots is set to the time of the latest trigger by default, but can also be set to the time the timeline was rendered by setting [`bokehendtime=now`](Inputs-and-Settings#configuration-file).
The `overview.html`, `overview_meta.html`, and `overview_recent.html` files are interactive plots with a shared time axis (i.e., panning or zooming in one panel will update the rest) that can be opened in a web browser. `overview_recent.html` shares the same format as `overview.html` but for only the last [`recplot`](Inputs-and-Settings#configuration-file) days, and shows all families active within that period in the occurrence timeline (instead of families with at least [`minplot`](Inputs-and-Settings#configuration-file) members). Meanwhile, `overview_meta.html` condenses all plots into tabs so many runs can appear on a `meta.html` page at once. This plot shows the last [`mrecplot`](Inputs-and-Settings#configuration-file) days with at least [`mminplot`](Inputs-and-Settings#configuration-file) members. The ending time of the plots is set to the time of the latest trigger by default, but can also be set to the time the timeline was rendered by setting [`bokehendtime=now`](Inputs-and-Settings#configuration-file).
Below is an annotated screenshot of the `overview_recent.html` output of the suggested default run:
Below is an annotated screenshot of the `overview_recent.html` output of the suggested default run:
1.**Title** (here, 'REDPy Catalog') is set in [`title`](Inputs-and-Settings#configuration-file). It is also used for the `<title>` of the page.
1.**Title** (here, 'REDPy Catalog') is set in [`title`](Inputs-and-Settings#configuration-file). It is also used for the `<title>` of the page.
...
@@ -79,7 +79,7 @@ The `overview_meta.html` version of these plots is roughly the same (varies by s
...
@@ -79,7 +79,7 @@ The `overview_meta.html` version of these plots is roughly the same (varies by s
Each family has its own detailed page with statistics and plots that can be opened in a web browser. Nominally, these are meant to be opened from a timeline page, but can be accessed directly within the `families/` folder, and are simply named with the family number (e.g., `0.html`).
Each family has its own detailed page with statistics and plots that can be opened in a web browser. Nominally, these are meant to be opened from a timeline page, but can be accessed directly within the `families/` folder, and are simply named with the family number (e.g., `0.html`).
Below is an annotated screenshot of the `families/0.html` output of a lightly modified default run:
Below is an annotated screenshot of the `families/0.html` output of a lightly modified default run:
<imgsrc="https://code.usgs.gov/ahotovec-ellis/REDPy/-/raw/main/img/output-family.png"alt="Annotated family page for default run Family 0"/>
<imgsrc="https://code.usgs.gov/vsc/REDPy/-/raw/main/img/output-family.png"alt="Annotated family page for default run Family 0"/>
1.**Navigation** links to the previous and next families (ordered by starting time). You can skip to a specific family by changing the number in the address bar.
1.**Navigation** links to the previous and next families (ordered by starting time). You can skip to a specific family by changing the number in the address bar.
...
@@ -132,7 +132,7 @@ changes the appearance of members of the `default1` family to be yellow to stand
...
@@ -132,7 +132,7 @@ changes the appearance of members of the `default1` family to be yellow to stand
Some families (especially large ones) may have interesting features that a user might want to investigate in more detail. A "report" can be generated with [`redpy-create-report`](Console-Scripts#redpy-create-report) for a given family (or list of families) that has more information than the standard family page.
Some families (especially large ones) may have interesting features that a user might want to investigate in more detail. A "report" can be generated with [`redpy-create-report`](Console-Scripts#redpy-create-report) for a given family (or list of families) that has more information than the standard family page.
Below is an annotated screenshot of the `reports/report-0.html` output for a Family 0 report with no flags (`redpy-create-report 0`) after the default run completes:
Below is an annotated screenshot of the `reports/report-0.html` output for a Family 0 report with no flags (`redpy-create-report 0`) after the default run completes:
<imgsrc="https://code.usgs.gov/ahotovec-ellis/REDPy/-/raw/main/img/output-reports.png"alt="Annotated report page for Family 0"/>
<imgsrc="https://code.usgs.gov/vsc/REDPy/-/raw/main/img/output-reports.png"alt="Annotated report page for Family 0"/>
1. Instead of a navigation bar, the **time** that the report was rendered is listed. For runs that update on a schedule, this can help remind the user that the report may be out of date.
1. Instead of a navigation bar, the **time** that the report was rendered is listed. For runs that update on a schedule, this can help remind the user that the report may be out of date.
...
@@ -156,7 +156,7 @@ These interactive timelines can be accessed by themselves in `reports/0-report-b
...
@@ -156,7 +156,7 @@ These interactive timelines can be accessed by themselves in `reports/0-report-b
If you use the `-o` flag, the waveform plots in 4 and correlation matrices in 8 and/or 9 will be ordered with OPTICS, which is used to pick the core event. This ordering is based on similarity from the correlation matrix, such that similar events will be close to each other in the order, allowing visualization of possible sub-families within the family. The ordering is applied to both the waveform images and the correlation matrices. Note the tight groups of dark colors surrounded by lighter colors in the matrix on the right:
If you use the `-o` flag, the waveform plots in 4 and correlation matrices in 8 and/or 9 will be ordered with OPTICS, which is used to pick the core event. This ordering is based on similarity from the correlation matrix, such that similar events will be close to each other in the order, allowing visualization of possible sub-families within the family. The ordering is applied to both the waveform images and the correlation matrices. Note the tight groups of dark colors surrounded by lighter colors in the matrix on the right:
<imgsrc="https://code.usgs.gov/ahotovec-ellis/REDPy/-/raw/main/img/output-reports-ordered.png"alt="Comparison of ordering by time vs. ordering by OPTICS"/>
<imgsrc="https://code.usgs.gov/vsc/REDPy/-/raw/main/img/output-reports-ordered.png"alt="Comparison of ordering by time vs. ordering by OPTICS"/>
If you use the `-m` flag, two .npy (numpy format) files will be output: `reports/0-cmatrix.npy` with the values of the cross-correlation matrix (full by default, or only the stored matrix if `-s`) and `reports/0-evtimes.npy` with the corresponding event times. If using `-o`, these two files will reflect the ordering with OPTICS.
If you use the `-m` flag, two .npy (numpy format) files will be output: `reports/0-cmatrix.npy` with the values of the cross-correlation matrix (full by default, or only the stored matrix if `-s`) and `reports/0-evtimes.npy` with the corresponding event times. If using `-o`, these two files will reflect the ordering with OPTICS.
