Data Quality Tools Update: Enhancing Data Integrity and Performance Analysis

1. Data quality tools: some updates =============================================================================================================== RUNNR - insn - VERSION - K00PM - K00PM_REF - K00PM_S - DLUM - DLUM_REF - DLUM_S - SQRTS - SQRTS_REF - SQRTS_S =============================================================================================================== 34439 1 21 2.612 2.59 1.29412 -0.03525 0.025 -10.0417 1019.62 1019.68 -1.28 34440 1 21 2.575 2.59 -0.882353 -0.2101 0.025 -39.1833 1019.6 1019.68 -1.66 34441 1 21 2.593 2.59 0.176471 -0.02347 0.025 -8.07833 1019.64 1019.68 -0.9 34443 1 21 2.591 2.59 0.0588235 0.02262 0.025 -0.396667 1019.68 1019.68 0 • CNDRUN.quality table being tested • New commands for data quality: • list_quality [run1][run2] • list_quality –long • list_quality –ok • list_runs -q Default mode: displays run#, charged/neutral, vlab-trgmon, s, intlum Displays all the quality infos +intlum, dead wires, hot wires Same display as default mode, with charged/neutral and s within 3σ from reference, and intlum>20nb-1 Standard list_runs output, with the same requests of list_quality –ok Salvatore Fiore – Data quality tools: some updates– LNF, 06-06-06

2. Integrated luminosity and dead/hot selection • = hot wires • = dead wires • In order to reject runs with poor statistics, we would cut on Ldt>20nb-1 • For 2004-2005 data runs below this integrated luminosity amount for about 1.6pb-1: negligible! 200 Which threshold for hot and dead wires? Now in dcdelete the threshold is 300. Too high? Salvatore Fiore – Data quality tools: some updates– LNF, 06-06-06