1 / 10

Calibration: preparation for p a

C. Zampolli. Calibration: preparation for p a. Calibration strategy – CPass0 + CPass1. CPass0. CPass1. Chunk 0. Chunk N. Chunk 1. Chunk 0. Chunk N. Chunk 1. …. …. Alien job. Alien job. Alien job. Alien job. Alien job. Alien job. Alien job. Alien job. snapshot. OCDB.

kaethe
Télécharger la présentation

Calibration: preparation for p a

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. C. Zampolli Calibration: preparation for pa C. Zampolli

  2. Calibration strategy – CPass0 + CPass1 CPass0 CPass1 Chunk 0 Chunk N Chunk 1 Chunk 0 Chunk N Chunk 1 … … Alien job Alien job Alien job Alien job Alien job Alien job Alien job Alien job snapshot OCDB snapshot reconstruction reconstruction ESDs ESDs Calib. train QA train Calib. train Merging + OCDB entires Merging + OCDB entires C. Zampolli OCDB Update OCDB Update

  3. Run selection • Runs are picked automatically from the logbook, with the following criteria: • PHYSICS run, Beam ON, GOOD Data Quality flag, GRPpp in DONE, at least one of SDD, T0, TOF, TPC, TRD, number of kCalibBarrel> 0, data migrated, B field ok • If TPC  TPCppin DONE • If TRD  TRD ppin DONE • If SPD  SPD ppin DONE (SPD should be always there) • GOOD Data Quality flag set online in the ACR • Runs should last at least 5 minutes • NB. • In pp: kCalibBarrel = SPI triggers; kCalibOuter = EMCAL + MUON + PHOS triggers • In pA: kCalibBarrel defined differently (see later); kCalibOuter = EMCAL + MUON + PHOS triggers C. Zampolli

  4. pA • During standard data taking: • Using high-multiplicity trigger (20 Hz) • Still to be set by Trigger experts; using VZERO • During MB-like data taking: • Downscaling at reconstruction level, according to: • min(max(nevents/10,30000),nevents)/nevents • If events <= 30000  reconstruct all • If events >= 300000  reconstruct 10% • In between, 30000 • No kCalibBarrel defined • kCalibOuter kept as now • More QA from fast MUON + calorimeters reconstruction (kPhysME) 30000 due to >3x higher multiplicity in pA than pp 30000 events 10% of the statistics C. Zampolli

  5. Trigger Clusters • Data taking will be in the same run with two different partitions: • Fast cluster  without SDD, AOCRDE, EMCAL, FMD, PHOS, MUON, PMD • ALL cluster  everybody • CENT cluster  without MUON, PMD • MUON cluster MUON + SPD + SSD (?) + T0 + V0 + ZDC Ken's talk at last PB C. Zampolli

  6. But… • Data taking will be in the same run with two different partitions: • Fast cluster  without SDD, ACORDE, EMCAL (?), FMD (?), PHOS, MUON, PMD • ALL cluster  everybody • CENT cluster  without MUON, PMD • MUON cluster MUON + SPD + SSD (?) + T0 + V0 + ZDC • Events in these clusters could be used for calibration, but the absence of SDD could bias the results, and SDD might not have enough events • Only use ALL + CENT • Standard pAkCalibBarrelshould not be associated to events from Fast cluster • MB data taking  dedicated alias as discussed in https://savannah.cern.ch/bugs/?99650 • Since an an event can be read out by two clusters, a sort of “exclusive” selection of aliases is needed (e.g. only ALL, not Fast) Ken's talk at last PB C. Zampolli

  7. CPass calibration code status • V5-03-Rev-03 should have been the “golden” release • Some changes needed, new revision foreseen No reprocessing possible yet C. Zampolli

  8. TPC calibration • dEdx resolution worsens at high rate (~8%), together with space point distortion (3 sigma) • So far, only extrapolation can be done • Procedure definition need data • For space point distortion, a first workaround could be put in place • Require manual calibration after PPass (high-pt trees needed) • After that, full calibration chain to be re-run (TPC calibration would change) C. Zampolli

  9. Current “schedule” • Monday 7 Jan, Sunday 13 Jan  machine and injectors commissioning • Monday 14 Jan  setting up for pA • 4 days of setup (could even be that they declare STABLE BEAMS) • Friday 18 Jan  Physics • 5-7 days of MB (to accumulate 100M events) • Then increase in luminosity, different trigger configuration • Monday 11 feb (at 6 am)  end of pA, start of pp at low energy • Each step depends on the previous one • Any delay could have consequences on the next steps! • E.g.: any delay this week would make pA shift in time • pAvsAp change of period probably better C. Zampolli

  10. 2012 data – what is left • LHC12h • VPass started over Christmas; almost completed • Run 189406 (8740 chunks for ~1.3M of MB events) failed in CPass0 merging (EE) • LHC12i • CPass reprocessing completed over Christmas (checking a few runs) • Manual update window to be opened, QA readiness to be assessed  deadline next week, then busy times for pA, so maybe VPass will need to be postponed C. Zampolli

More Related