...
At C&A's request: We have a new GR, GR v15r40, which contains the space craft alignment code. We also have two new sets of job options. One set is to enable the space craft alignment. The other is to turn on the TKR alignment again which was accidentally turned off on July 16 (in L1Proc 1.61). ***ADDED May 13, 2010 by anders: The TKR alignment was turned off in L1Proc 1.62, see this***
Note that while C&A has accepted the S/C alignment, there is no explicit SSC JIRA for them. I copied over the set with flavor "align" to "vanilla" which is the default flavor in L1. We need to start tracking them like we track all other calibrations. In particular to make sure any updates (if there are any) get propagated into L1 ("vanilla").
...
We have processed data runs in the DEV pipeline with this version of L1Proc. C&A has looked at the difference between a reprocessed run (with S/C and TKR alignment) and the original processing (no S/C or TKR alignment). Their results are here. A direct comparison between the Multiple scattering angle for reprocessed and original processing can be found in the attachments to this JIRA: GDQMQ-252.
Rollback procedure
We can switch back to the previous version of L1Proc in case of problems.
...
dataMonitoring/FastMonCfg: v1r6p0
- All histograms at the tower level needs a _Tower added as a suffix. Relevant jira(s):GDQMQ-258
- Add spacecraft_orbit_mode and spacecraft_orbit_inSAA. Relevant jira(s): GDQMQ-195
- Remove cut at 0 for Cal plots CalX_Total_NHit_TH1 and CalX_NHit_TH1 in config.xml. Relevant jira(s): GDQMQ-230
- Remove Tick20MHzDeviation_SuperZoom_TH1 and tune Tick20MHzDeviation_Zoom_TH1 x-axis to (-300, -100) in config.xml configLCI.xml MergeHistos_FastMon.txt. Relevant jira(s): GDQMQ-246
- Change histogram name AcdHitsCounter_CableChannel_TH2 to AcdHitMap_GafeGarc_TH2, and swap axis to match the Digi definition in config.xml configLCI.xml MergeHistos_FastMon.txt. Relevant jira(s): GDQMQ-244
Wiki Markup
- Trend the rate of TEM bugs using the FastMon_error_summary bit 23, type is rate in (monconfig_fastmon_trending.xml). Changes to address GDQMQ-254
- Corrected bug in filter for some of the compressed size rates (monconfig_digi_trending.xml).
\- Add FastMon trending quantities
- Add FastMon trending quantities FastMon_spacecraft_orbit_mode and FastMon_spacecraft_orbit_inSAA as ValueChange. in monconfig_fastmon_trending.xml
\
- Changes to address [GDQMQ-195|https://jira.slac.stanford.edu/browse/GDQMQ-195]
\- Check that signal > 0 in ACD PMT that vetoed before computing Log10() to fill histogram. This only affects recon histos job
- Check that signal > 0 in ACD PMT that vetoed before computing Log10() to fill histogram. This only affects recon histos job (monconfig_recon_histos.xml).
\
- Remove cut at 0 for Cal plots CalX_Total_NHit_TH1 and CalX_NHit_TH1_Tower\[16\]. Changes to address [GDQMQ-230|https://jira.slac.stanford.edu/browse/GDQMQ-230]
\- Remove
- Remove Tick20MHzDeviation_SuperZoom_TH1 from merge histo digi list. Changes to address [GDQMQ-246|https://jira.slac.stanford.edu/browse/GDQMQ-246]
\- Remove
- Remove Tick20MHzDeviation_SuperZoom_TH1 and tune Tick20MHzDeviation_Zoom_TH1 x-axis to (-300, \ -100). Changes to address [GDQMQ-246|https://jira.slac.stanford.edu/browse/GDQMQ-246]
\- Add histogram to hold pedestals from the
- Add histogram to hold pedestals from the database.
dataMonitoring/Common: v4r9p0
- Add function LookupErrorCode to Lookup the symbolic name of an error code in FastMon. Relevant jira(s): GDQMQ-257
- New variable in pGloblals to tell FastMon to dump event with an error to file : FASTMON_DUMP_ERRORS_TO_FILE is set to false, and is used only for debugging. Relevant jira(s): GDQMQ-253
- New attribute "seconds_elapsed" in the FastMon parsed by the pErrorLogger module.
- New algorithm to normalize the number of errors to the run duration added to pErrorLogger.
- Minor bug fix: the algorithm alg__values was crashing if for some reason it was not run (for instance if the plot was missing). Which should never happen, but... good to be prepared.
- Another bug fix: exception handling correctly implemented in alg__empty_bins.
- Added a new class (pErrorLogger) to apply alarms on the xml output files from the fastMon error handler and the verify module. The interface is identical to the one of the alarm handler, with the only difference that the new class operates on xml files, rather than root files (and the algorithms are obviously different). Not running into the pipeline, yet.
- Implemented the pedestal deviation in the CAL fitting tool, based on the new file from David (with the histogram of the pedestal references).
- Number of degrees of freedom and reduced chisuare added to the details dict for all the algorithms involving fitting.
- Left fitting range changed from 1.5 to 2.5 sigma for LEX8 and HEX8 CAL pedestals in pCalPedsAnalyzer.py.
- Some minor refactoring in the p*Analyzer classes to allow the derived classes to add their own histograms to the ones specified in the base class.
- Added histograms of the mean and rms values wrt the truncated average method in pCalPedsAnalyzer and pAcdPedsAnalyzer.
- Added placeholders for the pedestal deviations in pCalPedsAnalyzer and pAcdPedsAnalyzer.
- New alarm algorithm added: alg__low_high_ratio, measuring the ratio--in terms of number of entries--below and above a given pivot point. Relevant jira(s): GDQMQ-26
- All the alarms parameters with a default value (i.e. those which may not be specified in the xml file) added to the parameters dict of the algorithm so that they make it to the output xml file.
- Methods to adjust the x range in pAlarmBaseAlgorithm modified to use the getParameter() method for consistency (this way the min and max parameters make it to the output xml file).
- All algorithms modified to accept both TH1F and TH1D (and/or TH2F and TH2D where necessary).
- Test functions for all the algorithms modified as to print out the actual parameters dict, as it is shipped out to the xml file. * Relevant jira(s): GDM-133
- Output status promoted to warning (used to be undefined) in the edge finders if the edege(s) is (are) not found. The idea is that a minimu suitable number of entries is required before running an alarm on a plot; if the condition is not met the status is UNDEFINED---no need to bother. This change is intended to distinguish the cases in which the algorithm is supposed to have enough stastistics (and hence to find the edge) but it doesn't.
- Bug fix in pBaseAnalyzer: undefined variable when printing the fit parameters on the screen, was affecting the debug mode only.
- Bug fix in pBaseAnalyzer: the errors bars were not set correctly, there was an offset of -1.
- Default values for the ACDanalyzer quantites (for the unphysical empty histograms) set to 0.0 rather than -1.0
...
dataMonitoring/DigiReconCalMeritCfg: v1r2p26v1r2p27*
dataMonitoring/Common: v4r9p0*
dataMonitoring/FastMon: v4r5p0*
datMonitoring/IGRF: v1r0p1
...