Reason for Change
Several relatively minor issues have arisen in GRB processing so far in LEO. Jiras are posted below. ASP-8 resulted from unexpectedly small (zero to one event) FT1 files delivered by L1Proc. ASP-3 and ASP-10 were uncovered by trying to process the test GCN Notices from GBM.
Test Procedure
Tested by hand on flight data associated with the identified failures. Tested in dev on data in /ASP/TestSims and /ASP/TestSims2.
Rollback Procedure
Revert to ASP v2r5p1 + ASP/pyASP v3r5p1 + ASP/asp_pgwave v1r5
CCB JIRA
Details
- ASP/grbASP v4r3
- ASP-3@JIRA GRB_refinement_launcher fails when no FT1 data are available. Modified launchRefinementStreams.py to exit in this case.
- ASP-8@JIRA GRB_blind_search crashes if there is only one event in the FT1 file for a given run. As a short term solution, will skip files with a single event in BlindSearch.py.
- ASP-10@JIRA GRB refinement process crashes when there are no photons returned from the data selection for the candidate GRB. For the short term there is no convenient way to avoid a failed process. The best short term fix is to have the extractLatData process report that no events for this burst were found, and if appropriate, that the burst was too far off-axis to be seen. The long term fix will be to find a way to exit the train of processes in the xml task definition without setting a failure condition. Also, the info regarding the off-axis angle of the burst or lack of photons will need to be propagated to the data processing page somehow. AFAIK, there are no mechanisms for implementing either of these last two items.
Complete set of tags for ASP v2r6 (* indicates a revision for this CCB)
- ASP/AspHealPix v0r0p1
- ASP/AspLauncher v1r3p1
- ASP/AspPolicy v0r6
- ASP/BayesianBlocks v0r2
- ASP/asp_pgwave v1r5
- ASP/drpMonitoring v1r3p2
- ASP/grbASP v4r3 *
- ASP/pyASP v3r5p1
- ASP/sourceDet v0r0p1