You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 2 Next »

Overview

  • Task triggers
    • Availability of Level 1 (FT1/2) Data from L1Proc
    • GCN Notices and GCN Server
  • DataCatalog querying and task launching
  • Individual Task Data Processing
    • GRB_blind_search
    • GRB_refinement
    • GRB_afterglow
    • DRP_monitoring
    • flareDetection
    • PGwave

Task triggers

Availability of Level 1 (FT1/2) Data from L1Proc

  1. At the end of each L1Proc stream (for OktoberTest there was one stream per DownlinkId), ASP tasks are launched. GRB_blind_search, flareDetection, and PGwave are designed to process each downlink and are launched unconditionally. For tasks that are designed to run on specific time intervals (in MET), a task launcher stream is submitted first, it does a query to the datacatalog to ascertain if the FT1/2 files covering the desired interval are available and if so, it launches the desired stream.
  2. GCN Notices will arrive asynchronously via the GCN socket connection and these notices will be entered into the GCNNOTICES db table. If the Notice refers to a new GRB, a GRB_ID is assigned and a new entry in the GRB db table is created. When the next L1Proc delivery of FT1/2 data is made, the GRB_refinement_launcher task consults the GRB db table to find entries that have not had the GRB_refinement task launched. For those, the desired time interval of data to extract is computed, the datacatalog is queried, and if the FT1/2 data are available, it launches the GRB_refinement task and updates the entry in the GRB table that it has been launched. Similar logic is implemented for the GRB_afterglow_launcher and GRB_afterglow tasks.
  • No labels