1 / 7

Kevin Burkett, Sushil S. Chauhan , Geng -Yuan Jeng , Ting Miao,

First week of beamspot operations at 70 TeV. Kevin Burkett, Sushil S. Chauhan , Geng -Yuan Jeng , Ting Miao, Lenny Spiegel , Slawomir Tkaczyk , Lorenzo Uplegger, Francisco Yumiceva. Overview. The goal is to have an automated workflow which

fitzgerald-johnson
Download Presentation

Kevin Burkett, Sushil S. Chauhan , Geng -Yuan Jeng , Ting Miao,

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. First week of beamspot operations at 70 TeV Kevin Burkett, Sushil S. Chauhan, Geng-Yuan Jeng, Ting Miao, Lenny Spiegel, SlawomirTkaczyk, Lorenzo Uplegger, Francisco Yumiceva

  2. Overview • The goal is to have an automated workflow which • runs the beam spot producer over the express files arriving at T0 • calculate the beam spot position for each run • update the relevant tags ( hlt, express, prompt, offline) when needed I’ll give a summary of last week’s operations and say where are we now.

  3. Last week operations • When last Tuesday the first collisions arrived we realized that the automatic crab job • submission at T0 was not working but, we were able to run crab jobs using another • workflow that wait until the files are notified in DBS. • This workflow is also totally automated but it runs on all the files of a run if they are already • present in DBS and then as soon as a file appear in DBS it start another job without • waiting for all the files of that run to be available. • To make sure we collect enough statistics we want to run on all the files of each run. Since • this is not guaranteed by the above workflow, we are starting, once a day, new jobs that run • on the data collected till that moment. • During the first few days of last week, we have been constantly in touch with Rainer and • Gianluca who helped us understand which tags needed to be updated and when so, on • Wednesday, we updated the prompt express and also the offline tag. • On Friday we were told to update again the offline tag but I couldn’t meet the deadline and • so I updated it after the re-reco was already under way. • During all week we have been in touch with Hassen who has been working hard to fix • the automated workflow

  4. Runs processed so far

  5. Runs processed so far

  6. Runs processed so far

  7. Where are we now ? • Yesterday Hassen told me that the automated workflow has been fixed so I started a job • before I went home. I have just checked now and looks like it is still not performing as we • expect. • Since I am quite confident that Hassen will fix it quickly, soon we will have all the • software pieces to make the totally automated workflow a reality. • So far the tags are updated up to: • BeamSpotObjects_2009_v1_hlt: Run 123926 (very old because hlt still has old alignment) • BeamSpotObjects_2009_v1_prompt: Run 132472 (updated with Run 132442) • BeamSpotObjects_2009_v1_express: Run 132472 (updated with Run 132442) • BeamSpotObjects_2009_v7_offline: Run 132478 • In the mean time we keep running the jobs daily. We have so far processed till run • 132662 and in the next few hours we will create the BeamSpotObjects_2009_v8_offline • updated till this run. • Today we will also update the prompt and express tag with the most recent values

More Related