EPISODES Platform Documentation

Application User Guides > Reconstruction tools

Catalog Editor user guide ​

TIP

This document contains instructions for running application Catalog Editor within the EPISODES Platform. T**he application is a tool for editing Data Catalog. It allows to add a new entry to the catalog or edit an existing one.
To obtain more general information about working with applications within the Platform, see Applications Quick Start Guide.

NOTE

CATEGORY Reconstruction tools

KEYWORDS Data merging

CITATION If you use the results or visualizations retrieved from this application in a publication, then you must cite the data source as follows: Orlecka-Sikora, B., Lasocki, S., Kocot, J. et al. (2020) An open data infrastructure for the study of anthropogenic hazards linked to georesource exploitation., Sci Data 7, 89, doi: 10.1038/s41597-020-0429-3.

Input file specification ​

The application requires a single file in the format of a Matlab catalog (type Data Catalog). This may be a Catalog (a seismic events catalog), Ground Motion Catalog or any other similar type - check other possible catalog data formats, including also catalogs that are produced by joining two different catalog types (products of the Parameters Catalog builder user guide). For the purpose of this guide, we use the seismic catalog (Catalog), but most of the functionality is the same for other types.

Figure 1. Application input file specification.
Figure 1. Application input file specification.

Filling form values ​

The application form contains entries for each column present in the input catalog file (marked with (1) in Figure 2). The values might be filled by hand or populated from an event present in the input catalog or from another catalog or event properties file. For the second option, use the Select entry from catalog button (marked with (2) in Figure 2) and choose the event to be modified (Figure 3). To load external event values, use the Load values from file button (marked with (3) in Figure 2) and choose the file from which the event should be loaded (Figure 4) - it might be a file of one the following types: Catalog, Seismic Event (can be obtained as a result of the Signal download tool application) or Extracted relocalized event properties (can be obtained as a result of the Localization application). Note, that if the chosen file is a seismic catalog, you will be also prompted to choose a single event from that file (similarly as in Figure 3).

Figure 2. Application form with entries for catalog columns filled.
Figure 2. Application form with entries for catalog columns filled.
Figure 3. Dialog allowing for choosing an event from the input catalog.
Figure 3. Dialog allowing for choosing an event from the input catalog.
Figure 4. Dialog allowing for choice of an external file to load the values from.
Figure 4. Dialog allowing for choice of an external file to load the values from.

Depending on the ID specified in the form (marked with (4) in Figure 2), an event will either be modified or added to the input catalog. If the specified ID already exist in the catalog, the event with this ID will be modified by setting the provided values. If the ID didn't already exist in the catalog, a new event with the provided values will be added. Note, that the resulting catalog will be sorted by time, therefore, the event will not be added at the end, but at the right place considering its time. In case of an event modification, if its time changes, it will also be moved within the catalog, to retain the correct sorting.

Apart from setting values for the properties that already exist within the input catalog, we can also add new properties - using the part of the form Add new values (marked with (5) in Figure 2 and demonstrated in Figure 5).

Figure 5. Adding properties that were not yet present in the catalog.
Figure 5. Adding properties that were not yet present in the catalog.

Produced output

The result file will have the same name as the input with additional _mod suffix (e.g., if the input catalog file was called sample_catalog.mat, the result catalog will be named sample_catalog_mod.mat), and it will be visualized within the application outputs.

Figure 6. Result file visualization.
Figure 6. Result file visualization.

With the settings presented in Figure 2, the event CZORSZTYN_CIBIS_100010 from the input catalog will be changed, so that its time and magnitude ML is updated. Due to the time change, and the fact that the catalog is always sorted, the event in the resulting catalog was moved after event CZORSZTYN_CIBIS_100011. The comparison of the relevant part of the input and the result catalog is shown in Figure 7 and Figure 8.

Figure 7. The seismic event CZORSZTYNCIBIS100010 in the input catalog.
Figure 7. The seismic event CZORSZTYNCIBIS100010 in the input catalog.
Figure 8. The seismic event CZORSZTYNCIBIS100010 in the result catalog.
Figure 8. The seismic event CZORSZTYNCIBIS100010 in the result catalog.