Page History

...

• GRB_blind_search
  1. The DataCatalog is queried for the FT1 file based on DownlinkId.
  2. The GRB_ASP_CONFIG db table is queried for blind search configuration: log-likelihood thresholds, event number partition size, effective deadtime between burst candidates, etc.
  3. The FT1 file is read in and analyzed.
  4. For each GRB candidate:
     • A working directory is created on NFS.
     • A LatGcnNotice is generated. A text version is written to cwd. A GCN packet version is added to the GCNNOTICES db table.
     • email notification is sent out
     • If the burst corresponds a burst already in the GCNNOTICES db table (via an algorithm TBD), an entry is made and it is marked as an "UPDATE" (ISUPDATE=1), otherwise it is marked as "NEW" (ISUPDATE=0) and a GRB db table entry is created with the candidate burst parameters (INITIAL_RA, INITIAL_DEC, INITIAL_ERR_RADIUS, MET(=GRB_ID)).
  5. grb_followup.py is executed to launch followup tasks for all pending GRB analyses
• GRB_refinement
  1. The DataCatalog is queried for the FT1/2 files based on a time window centered on the candidate burst time derived by GRB_blind_search.
  2. The FT1/2 files from the DataCatalog locations are merged into single FT1 and FT2 files, and these files are written to the NFS working directory created for this burst candidate by GRB_blind_search.
  3. The GRB_ASP_CONFIG table is queried for position refinement configuration parameters.
  4. The extractLatData, refinePosition, LatGrbSpectrum, and tsMap task subprocesses are run, writing their output to the burst-specific working directory on NFS.
  5. Each process writes output to the GRB db table.
  6. The tsMap process creates plots for the GRBMonitoring page.
  7. The registerPlots scriptlet registers the plots with the DataCatalog so that the GRBMonitoring page can find them.
• GRB_afterglow
  1. The DataCatalog is queried for the FT1/2 files based on a time window, nominally 5 hours (TBR), after the end of the prompt burst phase as determined by GRB_refinement.
  2. The FT1/2 files from the DataCatalog locations are merged into single FT1 and FT2 files, and these files are written to the NFS working directory created for this burst candidate by GRB_blind_search.
  3. The GRB_ASP_CONFIG table is queried for afterglow analysis configuration parameters.
  4. The afterglowData, afterglowLivetimeCube, afteglowDiffResps, afterglowExpMap, and afterglowAnalysis task subprocesses are run, writing their output to the burst-specific working directory on NFS.
  5. Each process writes output to the GRB db table. (not implemented yet)
• DRP_monitoring
  1. The DataCatalog is queried for FT1/2 files based on a daily or weekly time window. The exact start times of these windows are TBD.
  2. A local working directory on NFS is created for each day or week interval.
  3. The getIntervalData subprocess merges the FT1/2 files from the DataCatalog locations into single FT1 and FT2 files and writes them to the time interval specfic working directory on NFS.
  4. The getIntervalData subprocess reads a parameter definition file from DRPMONTIORINGROOT with the analysis configuration (i.e., the IRFs to use, etc), and creates a local copy. (This parameter file should be replaced by an appropriate configuration table in the Oracle db.)
  5. getIntervalData, livetimecube, and diffuseResponses subprocesses are run, writing their output to the working directory on NFS.
  6. The launchRoiAnalysis pipeline scriptlet loops over the ROI_IDs, and for each ROI_ID, the roiAnalysis subtask is launched:
     • The getRoiData subprocess
       • queries the SOURCEMONITORINGROI db table for the ROI parameters (RA, Dec, ROI radius, source region radius),
       • creates a subdirectory on NFS fro that ROI,
       • runs gtselect to extract events for that ROI,
       • queries the SOURCEMONITORINGPOINTSOURCE and SOURCEMONITORINGDIFFUSESOURCE db tables for sources to include in the xml model definition
       • writes the parameter file for gtexpmap.
       • exposureMap, exposureSubMap, drpExpMap, and combineExpMaps subprocess compute the unbinned exposure maps, which are written to the local NFS time interval subdirectory. (This infrastructure allows the exposure maps to be partitioned into submaps and those submaps dispatched to the batch queues to be run in parallel.)
       • sourceAnalysis