Reason for change
Add Lat Catalog data to db view ASSOCIATIONCATALOGSDATA.
This view is used by ASPDataViewer to produce XML model on page http://glast-ground.slac.stanford.edu/ASPDataViewer/xmlModel.jsp
and it shows tentative association sources in flare events tables.
Test Procedure
Tested on dev space
Rollback procedure
The package can be rolled backreplace old version db view (ASSOCIATIONCATALGSDATA)
CCB Jira
Reason for change
Bug fix for GCR crash in recon in run 256381943. This requires a new GlastRelease. We have also fixed the LD_LIBRARY_PATH problem that meant we did not properly apply the leap second correction. For consistency reasons, we now have the same version of the astro package in both Glast Release and Science Tools. And we have a few bug fixes and updates for the monitoring.
Test Procedure
We have processed data runs in the DEV pipeline with this version of L1Proc.
Rollback procedure
We can switch back to the previous version of L1Proc.
CCB Jira
Details
L1Pipeline v1r71:
- Handle leap seconds properly, JIRA LONE-123.
- Clean up LD_LIBRARY_ and CMT PATHs. LONE-123@JIRA
- Put some info in dontCleanUp locks. LONE-127@JIRA
- Combine setSuccessful and setCrashed into a single script.
- checkRun fails if dontcleanup is present. LONE-133@JIRA
- Store deliveries from Halfpipe in a more official place. LONE-119@JIRA
- ft2Fake files cover only their chunk. LONE-138@JIRA
- Read data from xrootd when making magic7 file. LONE-129@JIRA
- mergeStuff fails before reading input data if it needs pyROOT and can't import it. LONE-134@JIRA
- When making ft1 and ls1, get start,stop times by rounding first,last event times down,up to .1s DATASERV-151@JIRA
GlastRelease v15r47p5:
- There are two changes in this GR wrt the version in use in L1, GR v15r47p1. We have a new version of GCRCalib: "Fix two bugs in the way m_initDir is initialized, and the case of no track in TDS". This fixes the crash we had in run 256381943. Fred Piron also verified that this new version did not change the 2400 events before the crash. We also have updated to the same version of astro that we use in Science Tools. We reprocessed a run and Andrea verified that there were no unexpected changes in the FT2 file.
- No changes in the system tests wrt GR v15r47p1.
dataMonitoring/DigiReconCalMeritCfg: v1r3p4
- Add the quantity Rate_FastMon_AnyThingButTEM to the FastMon trending configuration file.
- Changes to address JIRA GDQMQ-249
svac/Monitor: v1r2p35
- Proper initialization of vectors. This might be the cause of the problem described in JIRA GDQMQ-305.
svac/TestReport: v8r0
- Added datagram ID to the error message, where appropriate
- Fixed a bug in the computation of the size of datagram gaps
Complete set of tags for L1Proc 1.71
Code Versions
GlastRelease (sim/recon): v15r47p5*
ScienceTools (Level 2) : v9r8p2
Science Ops (task defs, scripts):
Level 1 pipeline code and applications running in L1:
svac/L1Pipeline: v1r71*
calibTkrUtil v2r7p3
calibGenTKR v4r5
dataMonitoring/AlarmsCfg: v5r9p4
dataMonitoring/FastMonCfg: v1r6p1
dataMonitoring/DigiReconCalMeritCfg: v1r3p4*
dataMonitoring/Common: v5r7p0
dataMonitoring/FastMon: v4r5p1
datMonitoring/IGRF: v1r0p1
svac/Monitor: v1r2p35*
svac/EngineeringModelRoot: v4r3
svac/TestReport: v8r0*
users/richard/pipelineDatasets: v0r6
ft2Util: v1r2p23
evtClassDefs v0r6
GPLtools: fileOps1
- Powered by Atlassian Confluence 2.10.1, the Enterprise Wiki.
- Printed by Atlassian Confluence 2.10.1, the Enterprise Wiki.
- Bug/feature request \u2013
- Atlassian news \u2013
- Contact administrators
Reason for change
The new version (v5r9p4, as opposed to v5r9p3, previously running in L1Proc 1.70)
is meant take into account a new noisy strip in Tower 3 GTFE 35 Plane 1
The detailed description of the changes is in the last section.
Test Procedure
We have processed monitoring products from real on-orbit data (LPA) locally with this version of AlarmsCfg.
Rollback procedure
The package can be rolled back to the previous version by flipping a soft link. Also note that the package is completely independent from any other package running in the pipeline and will not cause a version change of L1Proc.
CCB Jira
Details
- v5r9p4
- Add an exception for noisy strip in Tower 3 Plane 1 GTFE 35
TkrHitsCounter_PlaneGTFE_TH2_Tower_3 "spikes and holes"
- Add an exception for noisy strip in Tower 3 Plane 1 GTFE 35
Reason for change
The new version (v5r9p3, as opposed to v5r9p2, previously running in L1Proc 1.70)
is meant take into account a new noisy strip in Tower 2 GTFE 19 Plane 31
The detailed description of the changes is in the last section.
Test Procedure
We have processed monitoring products from real on-orbit data (LPA) locally with this version of AlarmsCfg.
Rollback procedure
The package can be rolled back to the previous version by flipping a soft link. Also note that the package is completely independent from any other package running in the pipeline and will not cause a version change of L1Proc.
CCB Jira
Details
-
-
- v5r9p3 ***
-
- Add an exception for noisy strip in Tower 2 Plane 31 GTFE 19
TkrHitsCounter_PlaneGTFE_TH2_Tower_2 "spikes and holes"
Reasons for Change
- Attempts by the GRB_refinement task to analyze data for bursts outside the FOV (off-axis angle > 70) fail when the event selection returns zero photons.
- GRB_blind_search will email duplicate alerts if a run containing a candidate burst is analyzed again (L1Proc will resubmit a run for analysis if more data for that run arrives in a later delivery.)
- Deliveries to FSSC shall now be made daily with no latency.
The release should be ASP v2r11p3.
Test Procedure
Tested in dev on data in /ASP/TestSims2 and on flight data in the prod datacatalog that exhibited this issue.
Rollback Procedure
Revert to ASP v2r11p1.
CCB Jira
Details
- ASP-59@JIRA Abort spectral analysis of burst if the refined position lies outside of the FOV
- ASP-60@JIRA Check if email notifications have already been sent out for a blind search candidate
- ASP v2r11p3
- AspHealPix v0r0p1
- AspLauncher v1r3p6
- AspPolicy v0r6p1
- BayesianBlocks v1
- asp_pgwave v1r9p1
- drpMonitoring v1r7p1*
- Set latency to zero in makeDrpLcTables.py
- grbASP v4r7p6*
- Rewrite GRB_refinement xml task def so that skipped sections are implemented as separate subtasks.
- Query GCNNOTICES db table to determine if a GRB candidate has already been found by the GRB_blind_search task. If so, skip email notification.
- pyASP v3r5p7
Reason for change
The new version (v5r9p2, as opposed to v5r9p1, previously running in L1Proc 1.70)
is meant to match the new configuration upload, in particular we removed many exceptions on Tkr alarms
and added a couple of them
The detailed description of the changes is in the last section.
Test Procedure
We have processed monitoring products from real on-orbit data (LPA) locally with this version of AlarmsCfg.
Rollback procedure
The package can be rolled back to the previous version by flipping a soft link. Also note that the package is completely independent from any other package running in the pipeline and will not cause a version change of L1Proc.
CCB Jira
Details
v5r9p2
- Add minimum number of events requirements to alarms on:
CalX_NHit_TH1_Tower, CalX_Total_NHit_TH1, CondArrCalHi_CalLoOpensWindow_TH1
CondArrCNO_CalLoOpensWindow_TH1, CondArrTKR_CalLoOpensWindow_TH1,
TkrPlanesHit_TH1_Tower - Slightly extend Warning limits for low_high_ratio on CalX_NHit_TH1_Tower_*
in order not to fire during ARR. - Lac_Thresholds_FacePos_TH1_TowerCalLayerCalColumn_4_3_4 exception for CAL noisy channel
- Added exception TkrHitsCounter_PlaneGTFE_TH2_Tower_0 Empty Bin (GTFE 12, Plane 14) fastmon_eor
- New strip masks so removing invalid exceptions in fastmon_eor "spikes and holes" and tkr_trend:
- tower 0 layer 12 and 14 : remove exception in fastmon_eor (12, 14) (14, 12)
- tower 2 layer 31 : remove exception in fastmon_eor (19, 31)
- tower 3 layer 1 and 35 : remove exception in fastmon_eor (1, 35) (12, 1)
- tower 5 layer 32 :: remove exception in fastmon_eor (3, 32)
- New masks are not perfect, adding the following exceptions :
- TkrHitsCounter_PlaneGTFE_TH2_Tower_0 fastmon_eor "spikes and holes" (13, 14)
- TkrHitsCounter_PlaneGTFE_TH2_Tower_0 fastmon_eor "empty bins" (12, 14)
- Number_layerOcc_TowerPlane tkr_trend "Number_layerOcc_TowerPlane" (0, 14) and (3, 35)