Reason for Change

The non-ASP specific parts of the pgwave package was added to ST v9r5p2 so that the Catalog group can have prebuilt binaries. The ASP package has been renamed asp_pgwave to avoid CMT-related naming conflicts, and the compiled executables (now in ST/pgwave) have been removed. UpperLimit code from pyLikelihood v1r5p4 will be used instead of replicated code in grbASP v4 and drpMonitoring v1r2. Some minor, unrelated changes to the ASP code will also be included.

Testing Procedure

ST v9r5p2 passed the standard RM tests. Tested on dev pipeline using /ASP/TestSims data.

Rollback Procedure

Revert to ST v9r5, ASP/pgwave v1r2, ASP/grbASP v4, ASP/drpMonitoring v1r2, ASP/AspLauncher v1r1

CCB JIRA

ssc-36@Jira

Details

  • ST v9r5p2
  • ASP/AspLauncher v1r2
    • use asp_pgwave v* in req file
    • pass streamId to PGWave task (unrelated to ST v9r5p2 change)
    • use afs installation of catalog files (unrelated to ST v9r5p2 change)
    • use ST v9r5p2 in xml def
  • ASP/asp_pgwave v1r3
    • Names for flaring sources have been changed to use Catalog group convention based on IAU standards. (unrelated to ST v9r5p2 change)
    • xml task def and os.environ references in python scripts were updated to point to ASP_PGWAVEROOT. (unrelated to ST v9r5p2 change)
  • ASP/grbASP v4r0p1
    • use UpperLimits from pyLikelihood v1r5p4 instead of local version
    • save time history log-probability evaluations for each data delivery epoch (unrelated to ST v9r5p2 change)
  • ASP/drpMonitoring v1r2p1
    • use UpperLimits from pyLikelihood v1r5p4 instead of local version
    • make folder containing pgwave output configurable via pipeline command line argument (unrelated to ST v9r5p2 change)