An example EventsFilter.xml configuration file for filtering events from the list is presented below. Only the text printed in black in the example is edited.

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>
<!DOCTYPE boost_serialization>
<boost_serialization signature="serialization::archive" version="12">
<Parameters class_id="0" tracking_level="0" version="0">
       <count>7</count>
       <item_version>0</item_version>
       <item class_id="1" tracking_level="0" version="0">
             <what>Origin</what>
             <relation>?</relation>
             <value></value>
       </item>
       <item>
<what>Latitude</what>
             <relation>GE</relation>
             <value>12.5</value>
       </item>
       <item>
             <what>Latitude</what>
             <relation>LE</relation>
             <value>14.2</value>
       </item>
       <item
             <what>Longitude</what>
             <relation>GE</relation>
             <value>130.0</value>
       </item>
       <item>
             <what>Longitude</what>
             <relation>LE</relation>
             <value>133.0</value>
       </item>
       <item>
             <what>Magnitude ML</what>
             <relation>?</relation>
             <value></value>
       </item>
       <item>
             <what>Magnitude ML</what>
             <relation>GE</relation>
             <value>3.0</value>
       </item>
</Parameters>
</boost_serialization>

In the absence of a configuration file, the program creates a template file EventsFilter.tmp, which should be edited and the extension changed to '.xml'.

The description of each filtering condition is stored as the <item> field in the <Parameters> structure, where the first position contains the full description of the <item> with the definition of class_id, tracking_level, and version, while the descriptions of the remaining columns start with the shortened version of <item>.

Each condition is described by three items:

 <what> zawiera nazwę parametru zjawiska, jaki jest badany. Mogą wystąpić następujące nazwy: Latitude, Longitude, Depth, Magnitude MM, gdzie MM jest nazwą magnitudy, Origin i Picks PP, gdzie PP jest nazwą fazy. Może wystąpić więcej niż jedno pole <item> z tym samym parametrem.

<value> zawiera wartość, w stosunku, do której porównywany jest parametr wstrząsu.

<relation> zawiera typ relacji miedzy parametrem a wartością. Mogą wystąpić nazwy:

<what> contains the name of the parameter of the phenomenon being investigated. The following names can occur: Latitude, Longitude, Depth, Magnitude MM, where MM is the name of the magnitude, Origin, and Picks PP, where PP is the name of the phase. There may be more than one <item> field with the same parameter.

<value> contains the value against which the shock parameter is compared.

<relation> contains the type of relationship between the parameter and the value. It may appear:

  • GT – the parameter defined in <what> must be greater than the value defined in <value>,
  • GE – the parameter defined in <what> must be greater than or equal to the value defined in <value>,
  • LT – the parameter defined in <what> must be smaller than the value defined in <value>,
  • LE – the parameter defined in <what> must be less than or equal to the value defined in <value>.
  • ? - it has a special role and can only be used with the parameters Origin, Magnitude MM and FM. The condition must also appear at the beginning of the list of descriptions. A condition marked by ? throws out phenomena that do not have an MM magnitude, an origin, or a focal mechanism. If this condition is missing from Origin, then if there are no encountered focus parameters and a condition for Latitude, Longitude, or Depth, an error is generated and the filtration is interrupted. The same happens when there is no magnitude MM and the condition Magnitude MM is encountered.

<count>7</count>

The <count> field contains information about the number of conditions.

  • No labels