Project Scope
Oracle's disks has been filling up pretty fast since data taking. As of Sept 26th there are 137 Gb of free space (< 10%).
The main users are:
- Science Data Trending (750Gb; 8Gb/day)
- HSK Data Trending (240Gb; 2Gb/day)
For Science Trending it was decided to keep all the data for 60 days, and to purge the great majority of the older data.
Purging has started around 2pm on Sept 25th.
CCB Jira
Reason for change
We have a new GR based on FSW B1-1-3. This FSW build will be activated on September 30. In addition, this new GR also has the ACD trapezoids.
There is also a new version of Science Tools and general updates to the monitoring.
Test Procedure
We have processed data runs in the DEV pipeline with this version of L1Proc.
Rollback procedure
FSW B1-1-3 has a new version of the Gamma-filter. While DFI is backwards compatible, the evt file format is not. So we have prepared four Glast Releases in case we need to back out of FSW B1-1-3 or B1-1-2:
GR v15r44p1: Base releases based on FSW B1-1-0. Contains the ACD trapezoids.
GR v15r45p1: Base release + new evt file format.
GR v15r46p1: Base release + new evt file format + based on FSW B1-1-2.
GR v15r47p1: Base release + new evt file format + based on FSW B1-1-3.
This way we are prepared for whatever happens next week. Note that because of time pressure only GR v15r47p1 has been tested in the L1 pipeline.
CCB Jira
Details
L1Pipeline v1r66:
- Alarms for FastMon errors, acdPeds, calGains, calPeds. LONE-111@JIRA, LONE-107@JIRA
- Keep 1-second ft2 FITS file (ft2Seconds).
- Run gtmktime to make ft1/ls1 GTIs match gaps from 1-second ft2. LONE-78@JIRA
- Stage files from AFS buffers to scratch disk.
- Use new version of GPLtools which checksums files as they are copied.
GlastRelease v15r47p1:
- Systemtestsfor GR v15r47p1with respect to the previous production release, GR v15r40. For a detailed discussion of differences seen in the system tests, see GR v15r47p1.
- RM diffwith respect to GR v15r40.
dataMonitoring/DigiReconCalMeritCfg: v1r2p30
- Changes to address JIRA GDQMQ-263
- Changes to address JIRAs GDQMQ-234, GDQMQ-252 and GDQMQ-261
- Change default value when GPS out of lock fraction cannot be computed. This avoid having negative values. This addresses JIRA GDQMQ-259.
dataMonitoring/Common: v4r10p0
- Implemented the reference subtraction in the AcdPedsAnalyzer.
- Implemented the difference wrt the truncated average in pCalGainAnalyzer. Relevant JIRA: GDQMQ-265.
svac/Monitor: v1r2p31
- Added functionalities required to address JIRA GDQMQ-263.
- Bug fix reported in JIRA GDQMQ-264.
- Added new quantities to address JIRA GDQMQ-254.
Complete set of tags for L1Proc 1.66
Code Versions
GlastRelease (sim/recon) v15r47p1*
ScienceTools (Level 2) : v9r7p1*
Science Ops (task defs, scripts):
Level 1 pipeline code and applications running in L1:
svac/L1Pipeline: v1r66*
calibTkrUtil v2r7p3*
calibGenTKR v4r5
dataMonitoring/AlarmsCfg: v4r7p5
dataMonitoring/FastMonCfg: v1r6p0
dataMonitoring/DigiReconCalMeritCfg: v1r2p30*
dataMonitoring/Common: v4r10p0*
dataMonitoring/FastMon: v4r5p0
datMonitoring/IGRF: v1r0p1
svac/Monitor: v1r2p31*
svac/EngineeringModelRoot: v4r3
svac/TestReport: v6r16
users/richard/pipelineDatasets: v0r6
ft2Util: v1r2p23
evtClassDefs v0r6
GPLtools: v1r13p1*
Reason for change
There was a bug in ASP/asp_pgwave v1r8 (in ASP v2r9) that was not tested by the data in dev that caused the PGWave task to crash when running the position refinement process for sources. This bug is related to the interface changes in pointlike/pointfit in ST v9r7p1.
Test Procedure
Tested on the flight data for which the bug was found. Tested in dev on /ASP/TestSims2. The code was modified so that it now operates identically on the test and flight data.
Rollback Procedure
Revert to ASP v2r8p5 and ST v9r6p1 (cannot rollback to ASP v2r9 since it is broken).
CCB JIRA
Details
- ASP v2r9p1
- AspHealPix v0r0p1
- AspLauncher v1r3p3
- AspPolicy v0r6p1
- BayesianBlocks v0r2
- asp_pgwave v1r8p1*
- In v1r8 and earlier, a separate position refinement step was performed for sources within 5 deg of the plane if their TS value was below threshold. This isn't necessary with pointfit in ST v9r7p1, and it was in this separate step where the bug resides in v1r8. This separate step has been removed from refinePositions.py.
- drpMonitoring v1r6p2*
- Employ Jean Ballet's recommendation for ROI-based zenith angle cuts in gtmktime for ROIs near the orbital poles. The cut in v1r6p1 and earlier removes too many events for these ROIs.
- grbASP v4r6
- pyASP v3r5p6
Reason for change
Added RSP data.
Test Procedure
This version has been tested on the DEV server.
Rollback procedure
There isn't a way to roll back. Changes to the database structure will prevent previous versions from working. This is a one way street.
CCB Jira
Reasons for Change
There were two interface changes in ST v9r7p1: pointfit and gtmktime. In order to move beyond ST v9r6p1 (current), these changes need to be accomodated. Moving to ST v9r7p1 is necessary since the old interface and implementation of pointfit in ST v9r6p1 is no longer supported.
Test Procedure
Test in dev on data in /ASP/TestSims2
Rollback Procedure
Revert to ASP v2r8p5 and ST v9r7p1
CCB JIRA
Details
- ASP v2r9
- AspHealPix v0r0p1
- AspLauncher v1r3p3
- AspPolicy v0r6p1*
- use asp symlink to GPLTools location in wrapperGenerator.py
- BayesianBlocks v0r2
- asp_pgwave v1r8*
- modifications to refinePositions.py to use new pointfit interface in ST v9r7p1
- drpMonitoring v1r6p1*
- update for ST v9r7p1 interface to gtmktime
- grbASP v4r6*
- skip test notices for "Fermi" in GCN_Notice_processor.py
- correct fraction of day calculation in GRB labeling
- pyASP v3r5p6