Status: VdM analysis framework Lumi DPG December Monika Grothe (Wisconsin) Jan VdM analysis Framework

Title Jan VdM analysis Framework2 - everything yellow is done and under control of vdm driver -2 luminometers available, HFlumi zero counting and pixel cluster counting - all corrections available for 2013 pPb and pp runs Framework: Current coverage

Available luminometers in the framework HFlumi zero counting Pixel cluster counting – Adopted from Jeroen’s code – Full chain is functional, from generating rates files to filling TGraphs to fitting – Currently tested and compared in detail to output of Jeroen’s original code by Magdalena Vertex counting: – Since Jeroen’s ntuples contain number of vertices, this is rather straight-forward to implement – I checked with Chris that his improved version of the lumi ntuples will contain vertex info as well – Should be available soon Jan VdM analysis Framework3

Available corrections in the framework Length-scale correction factors Ghost and satellite correction factors, the latter available per bcid Beam-beam correction Adding further corrections is technically straight-forward – Corrections implemented as plug-ins (as are the fits) – Corrections applied when making the TGraphs, called by makeGraphsFiles.py – List of corrections given in makeGraphsFiles_Config.json, will be applied in the order given in the list – Corrections factors are actually extracted or generated from their original sources by the python scripts in dataPrep_corr directory Correction factors available for all 2013 VdM scans – Magdalena is testing the correction generation and application functionality Question: – The original sources for the corrections are usually tar files with directories, for example from the LDM people or from LHCb – I think we should make sure to archive them, in their original format – Where/how do we want to archive them ? Jan VdM analysis Framework4

Modifications to DIP info Need t discuss with WBM people how/who takes care of making sure that the modified info sent via DIP during a VdM scan will be properly stored in the CMS cond DB Used in 2012 Jan VdM analysis Framework5 # SQL> DESCRIBE CMS_LHC_BEAM_COND.LHC_LUMINOSITYSCAN # Name Null? Type # # DIPTIME NOT NULL TIMESTAMP(9) # DATAQUALITY NUMBER(10) # PLANE VARCHAR2(4000) # NOMINAL_SEPARATION FLOAT(32) # LUMISCAN_STATUS VARCHAR2(4000) # IP NUMBER(10) # STEP_PROGRESS FLOAT(32) # BEAM NUMBER(10) # ACQUISITION_FLAG NUMBER(1)

16 Oct 2014 Framework input data6 In 2015, there will be “nominal separation” as before In addition, there will be info on displacement of each beam LHC may start sending these additional parameters via DIP in February

Archiving Discuss with Zhen best way of archiving analyses As goal would like to have archived at least – the Nov 2012 VdM analysis – the 2013 pPb and low-energy pp VdM analyses Want to archive – full analysis done in the framework – all “raw” data, i.e. HF rates files from lumiDAQ and Jeroen’s ntuples for PCC and Vtx analyses – but also all external inputs (fore example from LDM group and from LHCb) Jan VdM analysis Framework7

Further to do items Finish framework stage 4, i.e. the part that calculates the visible cross section and the new lumi calibration Provide parser for timber-extracted csv file with currents – actually needed for the HIN VdM scans because DCCT info from DIP appears to be corrupted for them Implement possibility to extract scan info in makeScanFile.py from CMS condDB, as alternative to using the dip file Make 2D fits functional Provide plotting functionality, – for fit output – for lumi calibration output – for rates of the different luminometers – for DIP and timber Documentation Write tutorial – Requests keep coming in, need something to point people to as starting point Jan VdM analysis Framework8