Page History

Overview

• Conditions for Task Launching Task triggers Availability of
  1. GCN Notices
  1. Level 1 (FT1/2) Data
  from L1Proc
• GCN Notices and GCN Server
DataCatalog querying and task launching
1. availability
2. GRB task launcher process and DataCatalog querying
• Individual Task Data Processing
  • GRB_blind_search
  • GRB_refinement
  • GRB_afterglow
  • DRP_monitoring
  • flareDetection
  • PGwave

Conditions for Task

...

Launching

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 data time intervals, a task launcher stream is submitted first, it queries 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 arrive asynchronously via the GCN socket connection and these notices will be
   • On arrival, each Notice is 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.
   On the next delivery of FT1/2 data by L1Proc,
   • For each new entry in the GRB db table, two flags are set to false (0): L1_DATA_AVAILABLE and ANALYSIS_VERSION. L1_DATA_AVAILABLE is set to true if L1 data are available for the GRB_refinement
   _launcher
   • task
   queries the GRB db table for entries that have not had
   • and the task has been submitted. ANAYLSIS_VERSION is set to true if 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, the GRB_refinement task is launched and the entry in the GRB table is updated. Similar logic is followed for the GRB_afterglow_launcher and GRB_afterglow tasks except that the GRB_refinement task must also have been run first before the initial datacatalog query
   • has run and if the L1 data are available for the GRB_afterglow task. (The names and conditions for altering fields will need to be reviewed.)
3. When new L1 (FT1/2) data are available, ASP tasks are launched.
   • GRB_blind_search, flareDetection, and PGwave are designed to process each downlink and are launched unconditionally.
   • GRB_refinement, GRB_afterglow, and DRP_monitoring require data from specific data time intervals to be available in order to run.
4. GRB task launcher process and DataCatalog querying
   • In the BlindSearch process, a script (grb_followup.py) is run that
     queries the GRB db table for entries satisfying two sets of conditions:
     • L1_DATA_AVAILABLE=0: These are GRB candidates that require the GRB_refinement task to be run.
     • L1_DATA_AVAILABLE=1 and ANALYSIS_VERSION=0: These are GRB candidates that have had GRB_refinement task run, but still require GRB_afterglow to be run.
   • Based on the data in those queries, grb_followup.py computes the time intervals to be considered and queries the DataCatalog for the required FT1/2 files.
   • If those files are available, the corresponding tasks are launched.
   • GRB the table entries are updated by the launched tasks.