.. _toast_importing_creating: Import events and create incidents in |appname| =============================================== There are various ways for creating or loading :term:`incidents ` in |appname|: * |scname| events are received via an active messaging connection and new incidents are created automatically, see: :ref:`toast_receive_events`. * Events are imported manually by user interaction, see: :ref:`toast_import_event_manually`. * The user creates an incident manually, see: :ref:`toast_artificial_incidents`. * Incidents are loaded from the |appname| database, see: :ref:`toast_import_incidents`. See also: :ref:`toast_simulations` on how to add simulations to an :term:`incident `. .. _toast_receive_events: Receive events automatically via messaging ------------------------------------------ If a connection to a |scname| system is configured, new events (and event updates) are received via messaging and incidents can be created automatically. This is the case if the magnitude of the event is larger than :confval:`incidentMinimumMagnitude` and if the depth is shallower than :confval:`incidentMaximumDepth`. See also: :ref:`toast_sim_automatic`. .. _toast_import_event_manually: Import events from a |scname| database manually ----------------------------------------------- To import an event from a |scname| database and create an :term:`incident `, use :menuselection:`Menu --> File --> Import --> From SeisComP` or press *F4*. Load events by choosing appropriate time span settings and clicking the refresh button. Filter the list using the *funnel* icon. Double click an event to create an incident which then is displayed in |appname|. .. _fig-import_event: .. figure:: media/toast/gui/import_event.png :align: center :width: 16 cm Import an event from a |scname| database To trigger simulations for the new incident, press *CTRL+N*. See also :ref:`toast_sim_manual`. .. _toast_artificial_incidents: Create artificial incidents --------------------------- :term:`Incidents ` can also be created manually, for example for testing or in case a specific earthquake isn't available in the connected |scname| database. In case of manual creation, there exists no event associated with the incident. Click the middle mouse button or use the context menu in the :ref:`toast_map_perspective`. Adapt the required settings in the dialog and click *Ok*. The new incident appears on the map and in the :ref:`toast_database_panel`. .. _fig-artificial_incident: .. figure:: media/toast/gui/artificial_incident.png :align: center :width: 10 cm Artificial incident dialog .. _toast_import_incidents: Load incidents from |appname| database -------------------------------------- In order to load :term:`incidents ` from the |appname| database, click the settings-icon in the :ref:`toast_database_panel`, specify a time span either by dates or by *Last days* and hit the corresponding refresh button. Using: :program:`scconfig` :menuselection:`--> Modules --> gempa --> toast --> toast --> tsunami --> database` you can set :confval:`tsunami.database.loadLastDays` to automatically load incidents after starting |appname|. .. _toast_create_gnss: Import displacement amplitudes and create observed displacements ================================================================ Analogous to events and incidents, there are also various ways to create or import :term:`displacements ` in |appname|: * |scname| displacement amplitudes are received via an active messaging connection and new displacements are :ref:`created automatically`. * Displacement amplitudes are :ref:`imported manually from an XML file`. * The user :ref:`creates a displacement manually for a GNSS station`. .. _toast-note-amps: .. note:: Technically, an *amplitude* is a |scname| object, while a *displacement* is a |appname|-specific object. The automatic amplitudes (received by messaging) and those imported from an XML file are converted to displacements and are referenced in the displacement components, analogous to event and incident. Required amplitude attributes are type ('Gd'), amplitude value and waveformID. The public IDs of the amplitudes can be looked up in the :ref:`toast_gnss_perspective`. A manually entered displacement does not reference an amplitude. The priority of the displacements is: manual, automatic, imported (manual displacements overwrite automatic and imported etc.). For more information on Displacements functionality see: :ref:`toast_gnss_perspective`. .. _toast-gnss-messaging: Receive displacements via messaging ----------------------------------- If a connection to a |scname| system is configured, displacements are automatically created and updated upon receiving displacement amplitudes from GNSS observations. .. note:: Automatically created displacements overwrite :ref:`imported` displacements, but never :ref:`manually created` ones. .. _toast-gnss-import: Import displacement amplitudes from an XML file ----------------------------------------------- GNSS displacements can be imported from a file in XML format containing displacement amplitudes via :menuselection:`File --> Import --> Displacements amplitudes...`. This is an example for a file containing such amplitudes. It was created by the *gdisp* plugin: .. include:: media/toast/gnss_import/gnss_amplitudes.xml :literal: Upon import, the amplitudes are converted to displacements for the currently active |appname| incident. .. note:: Imported displacements can be overwritten by :ref:`manually` or :ref:`automatically` created displacements. .. _toast-manual-gnss: Create observed displacements manually -------------------------------------- It is possible to enter or override the observed displacement for a GNSS station manually. This is useful if there are no automatic displacements available or for training purposes. To do so, right-click on a GNSS station in :ref:`toast_map_perspective` or in :ref:`toast_gnss_perspective` and select: :menuselection:`Observed displacement --> Set manually...`. Note that it is not necessary to enter all components. The horizontal contribution to the displacement residual is computed if both East and North components are present and the vertical contribution if the Up component is present. .. _fig-gnss_custom: .. figure:: media/toast/gui/gnss_custom_dialog.png :align: center :width: 7 cm Manual displacement input dialog A user icon on the left side of the displacement columns in :ref:`toast_gnss_perspective` indicates manually entered values. .. note:: Manually displacements can never be overwritten, neither by :ref:`automatically` received or :ref:`imported` ones. .. note:: If all components are not set in the manual setting dialog, the displacement will be removed. Receiving updates from the |scname| system ========================================== As long as |appname| is connected to a |scname| messaging system, incidents and displacements are updated automatically. If event updates, like origin and magnitude, or displacement amplitudes were send via messaging connection while |appname| was offline, they can be loaded from the |scname| system by clicking on the *Update* button in the :ref:`toast_incident_summary`. A short click updates both incident information (origin, magnitude and nodal planes) and displacements, while a long left mouse click allows to update them separately. .. _fig-update_button: .. figure:: media/toast/gnss_import/update_button.png :align: center :width: 18 cm Incident and displacement update button