2 unresolved threads
2 unresolved threads
Update !1243 (merged) and !1306 (merged) with excited B* reconstruction.
Edited by Ching-Hua Li
Merge request reports
Activity
Filter activity
requested review from @chinghua
assigned to @chinghua
Welcome to Analysis Productions!This is a summary of the productions requested in this merge request:
Step Production ID Num Test LFNs Run time Estimated Output Size (MB) HLT1_b0_dstp_e_MagDown,HLT2,SPRUCE,DV 57582 1 0:23:44.578938 0.3 HLT1_b0_dstp_muon_MagDown,HLT2,SPRUCE,DV 57583 1 0:24:25.459581 0.7 HLT1_b0_dstp_taue_MagDown,HLT2,SPRUCE,DV 57584 1 0:28:23.741806 0.4 HLT1_bp_dstst_e_MagDown,HLT2,SPRUCE,DV 57586 1 0:30:13.899686 0.4 HLT1_bp_dstst_taue_MagDown,HLT2,SPRUCE,DV 57587 1 0:24:51.247176 0.5 HLT1_b0_dststp_e_MagDown,HLT2,SPRUCE,DV 57588 1 0:27:59.271967 0.4 HLT1_b0_dststp_taue_MagDown,HLT2,SPRUCE,DV 57589 1 0:18:13.440858 0.3 HLT1_b0_dstp_e_MagUp,HLT2,SPRUCE,DV 57590 1 0:23:20.415068 0.3 HLT1_b0_dstp_muon_MagUp,HLT2,SPRUCE,DV 57591 1 0:19:44.261224 0.7 HLT1_b0_dstp_taue_MagUp,HLT2,SPRUCE,DV 57592 1 1:45:21.997023 0.4 HLT1_b0_dstp_taumuon_MagUp,HLT2,SPRUCE,DV 57593 1 0:18:30.928423 0.6 HLT1_bp_dstst_e_MagUp,HLT2,SPRUCE,DV 57594 1 0:28:47.102378 0.5 HLT1_bp_dstst_taue_MagUp,HLT2,SPRUCE,DV 57595 1 0:11:47.331911 0.5 HLT1_b0_dststp_e_MagUp,HLT2,SPRUCE,DV 57596 1 0:23:21.232779 0.4 HLT1_b0_dststp_taue_MagUp,HLT2,SPRUCE,DV 57597 1 0:22:25.121636 0.3 data_b0_dstp_muon 57599 1 0:17:54.660511 0.1 data_b0_dstp_taue 57600 1 0:13:51.450352 0.8 data_b0_dstp_taumuon 57601 1 0:14:25.732583 1.6 data_b0_dstp_e_fake 57602 1 0:46:44.154009 0.6 data_b0_dstp_muon_fake 57603 1 0:11:57.832640 0.3 data_b0_dstp_taue_fake 57604 1 0:45:29.640223 0.4 data_b0_dstp_taumuon_fake 57605 1 0:08:22.849479 1.0 data_b0_dstp_e 57606 1 0:19:22.246967 1.5 HLT1_b0_dstp_taumuon_MagDown,HLT2,SPRUCE,DV 57607 1 0:30:05.422960 0.5 Edited by LHCb Data Processing and Analysis
added SL label
added 1 commit
- f2edf471 - remove brems variables for non-lepton particles
requested review from @lmartel
Hi @chinghua, everything looks good. Some jobs have >5GB memory usage peaks, but I suppose this is similar to what we saw in !1306 (merged). Can you just check to make sure this is indeed the same behavior ? I'll merge after that.
mentioned in commit 81ba2045
mentioned in issue #583 (closed)
mentioned in commit 5b17087a
mentioned in merge request !1513 (merged)
Please register or sign in to reply