Difference: PilotBladeReconstructionLogs (2 vs. 3)

Revision 32016-09-14 - TamasVami

Line: 1 to 1
 
META TOPICPARENT name="PilotBladeReconstruction"
Added:
>
>

Disclaimer: sorry, sometimes not really up to date

 

Pilot Blade Reconstruction

Link to the git repository

Changed:
<
<

Entry log on 2016-09-13

>
>

Log entry on 2016-09-13

 
# creating the local maps one can delete the stats using:
PBClustersMod_344134148__10->SetStats(0)
Changed:
<
<

Entry log on 2016-09-12

>
>

Log entry on 2016-09-12

 miniDAQ: http://cmsonline.cern.ch/cms-elog/947901
MiniDAQ runs: BmI modules had WBC=166.
Runs:
Line: 38 to 39
 Run 280346 w/ All 4 BmI modules
Changed:
<
<

Entry log on 2016-09-11

>
>

Log entry on 2016-09-11

  Runs: 280383, 280384, 280385
Global Runs: BmO modules had WBS=167.
Output dataset: /ZeroBias/tvami-PilotBlade_pp_data_RECO_August_Filtered_RAW_ZeroBias-2016G_Runs280383-280385_v1-ffd4a2cc6f6b3c98894eea447cc8098f/USER
Changed:
<
<

Entry log on 2016-09-02

>
>

Log entry on 2016-09-02

 Output dataset: /ZeroBias/tvami-PilotBlade_pp_data_RECO_August_Filtered_RAW_ZeroBias-2016G_Runs279853-279865_v1-ffd4a2cc6f6b3c98894eea447cc8098f/USER
Changed:
<
<

Entry log on 2016-09-01

>
>

Log entry on 2016-09-01

 New global runs: 279853-279865
WBC moved 3 BX for BmI module and 4 BX for BmO modules. Bora's talk-- page 34
Changed:
<
<

Entry log on 2016-08-27

>
>

Log entry on 2016-08-27

 Working on the plot script.
3 scenarios on crab:

Line: 60 to 61
 /data/vami/projects/pilotBlade/pp2016ReProcessing_v3/CMSSW_8_0_8/src/crab/Ntuple/August-3/crab_PilotBlade_data_Ntuplizer_pp_August_Runs279071-279073-fiducial_v1
Changed:
<
<

Entry log on 2016-08-26

>
>

Log entry on 2016-08-26

 The cluster sizes depend upon: the pixel dimensions [actually, because the local x y conventions were changed thereby messing-up the reconstruction code, they are the same, 100um in local x and 150um in local y], the pixel orientation [low pt tracks are now curving mostly in x instead of y], the distribution of local angles cot(alpha) and cot(beta) [completely different due to the orientation and different z position], thresholds [?], and Lorentz angle [is the pilot blade tilted at 20 deg and operated at 300V?, if not, then it’s probably different too]. When Viktor fixes the geometrical description of the Phase I FPix [wrong in many many details], there will be a simulation to compare with.
Changed:
<
<

Entry log on 2016-08-24

>
>

Log entry on 2016-08-24

 Talk on Pixel Offline
https://tvami.web.cern.ch/tvami/presentations/20160824_PilotBladeAugustRuns_PixelOffline.pdf
Changed:
<
<

Entry log on 2016-08-23

>
>

Log entry on 2016-08-23

 Ntuplizing + plotting
Changed:
<
<

Entry log on 2016-08-22

>
>

Log entry on 2016-08-22

 RECOing the global runs
Changed:
<
<

Entry log on 2016-08-21

>
>

Log entry on 2016-08-21

 

Global run: 279045

Line: 97 to 98
 
Changed:
<
<

Entry log on 2016-08-15 (holidays)

>
>

Log entry on 2016-08-15 (holidays)

 
Key 2042 - fedcard/28 - Master delay:2 - 48 clock cycles.
Key 2043 - fedcard/29 - Master delay:3 - 64 clock cycles.

Line: 167 to 168
 Run 278788 -> 24LS
Changed:
<
<

Entry log on 2016-08-06

>
>

Log entry on 2016-08-06

 miniDAQ run numbers 278242-278245
Changed:
<
<

Entry log on 2016-07-28

>
>

Log entry on 2016-07-28

 miniDAQ reco... no disk replica so I have to do it interactively
Quality study meanwhile

Line: 181 to 182
 
Changed:
<
<

Entry log on 2016-07-21

>
>

Log entry on 2016-07-21

 
Dataset:  /MiniDaq/Run2016E-v2/RAW
Run 277150

Line: 215 to 216
 A lot of NOR errors. The rest is PKAMs.
Changed:
<
<

Entry log on 2016-07-21

>
>

Log entry on 2016-07-21

 
New runs with T0 transfer ON.
Dataset:  /MiniDaq/Run2016E-v2/RAW

Line: 247 to 248
 No luck in running only one channel for these modules.
Changed:
<
<

Entry log on 2016-07-12

>
>

Log entry on 2016-07-12

 

Timing scan 1&2 Ntuplizer

The resulted ntuples are located here:

Line: 255 to 256
 /data/vami/projects/pilotBlade/0RootFiles/Ntuple/TimingScan2onZeroBias/*.root
Changed:
<
<

Entry log on 2016-07-11

>
>

Log entry on 2016-07-11

 If I download then I kill the work of Marton, Janos and Adam... working on the Phase1 Quality problem instead
Changed:
<
<

Entry log on 2016-07-10 (Sunday)

>
>

Log entry on 2016-07-10 (Sunday)

 

Timing scan 1 Ntuplizer

root://cms-xrd-global.cern.ch//store/user/tvami/PBTimingScans/First/*
Changed:
<
<

Entry log on 2016-07-09 (Saturday)

>
>

Log entry on 2016-07-09 (Saturday)

 

Timing scan 1 Ntuplizer

on dataset:

Line: 283 to 284
 /ZeroBias8/tvami-PilotBlade_pp_data_RECO_FirstScan_Filtered_RAW_ZeroBias8-2016B_v1-1aa7bafc2c84e866fe85ed4ed7a53e27/USER

Added:
>
>

Log entry on 2016-07-07

Working in folder pp2016ReProcessing_v3
RECO of every RAW, but only Zminus side is RECOd
/data/vami/projects/pilotBlade/pp2016ReProcessing_v3/CMSSW_8_0_8/src/crab/RECO/
 

Timing scan 2 Ntuplizer

The ntuple files are located here

Line: 291 to 300
 /data/vami/projects/pilotBlade/0RootFiles/Ntuple/TimingScan2onZeroBias/
Changed:
<
<

Entry log on 2016-07-08

>
>

Log entry on 2016-07-08

 config.Data.runRange = '271087-272008' TimingScan1 921 run in Run2016A -v1 and Run2016B -v1
config.Data.runRange = '274000-274954' TimingScan2 954 run in Run2016B -v2

Timing scan 1 RECO

 
This site is powered by the TWiki collaboration platform Powered by Perl This site is powered by the TWiki collaboration platformCopyright &© by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback