Part 1 *********************************************************************** Hi Angela and Marco, I have started going through the E1 menu of the v14.93 list to see what tools/filters we need to enter for v15. Here is part 1 of that inventory. We already have a first L3 RunIIb list which we used to test the download of the new tools online back in Feruary. It is called Test_4Per_RunIIb / 1.00 and contains examples of many of the v15 L3 tools/filters. Test_4Per_RunIIb contains 3 electron filters which can be used as templates for v15: L3FEle(ELE_NLV_SHT,1,15.,0.,3.6,-99.,99.,-1.) / 1 L3FEle(IsoEle_SHT,1,15.,0.,3.6,-99.,99.,-1.) / 1 L3FEle(ELE_NLV_SHT,1,10.,0.,3.6,-99.,99.,-1.) / 1 For all electron filters in v15 we have one new parameter, MinELike (the electron likelihood which is set to -1,not used, by default). The L3 tracker has also changed for v15 which means that ALL the electron tools are also different from v14. Below is a list of the additional electron terms I find for the E1 suite in triggerlist v14.93 (and which I think Marco also wants to use in v15 for a start). So these need to be translated to v15 L3 with the help of the examples from the Test_4Per_RunIIb list: L3FEle(ELE_NLV_SHT,1,22.,0.,3.6,-99.,99.) / 2 L3FEle(IsoEle_SHT,1,22.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_SHT,1,25.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_SH,1,30.,0.,3.6,-99.,99.) / 2 L3FEle(IsoEle_SH,1,30.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_SH,1,35.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV,1,70.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_SH,1,30.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_SHT,1,20.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_SHT_T13,1,15.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_SH_T15,1,20.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_T13,1,15.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV,2,15.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_SH,1,15.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV,1,20.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV,2,20.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV,1,25.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_SH,2,10.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV,2,10.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_T10,1,10.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV,1,15.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV,2,6.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV,1,8.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_SHT_T5,1,6.,0.,3.6,-99.,99.) / 2 Let me know if you have any questions or need more info. I will continue my inventory of the v15 L3 tools/filters. Cheers, Per Part 2 ***************************************************************************** Hi Angela, here's part 2 of my v15 L3 inventory. Test_4Per_RunIIb / 1.00 contains the following MET term which again can be used as a template for the v15 MET terms: L3FMEt(CalMEt_PV3_NLC_N,25.,2000.,0.) / 4 In v14.93 I also find the following MET terms, which need to be translated to v15: L3FMEt(CalMEt_PV3_NLC_N,15.,2000.,0.) / 3 L3FMEt(CalMEt_PV3_NLC_N,20.,2000.,0.) / 3 L3FMEt(CalMEt_PV3_NLC_N,12.,2000.,0.) / 3 Test_4Per_RunIIb / 1.00 contains the following track term which again can be used as a template for the v15 track terms: L3FTrack(PhTrk10,1,10.,1.,10,0) / 3 In v14.93 I also find the following track terms, which need to be translated to v15: L3FTrack(PhTrk8,1,13.,1.,10,0) / 2 L3FTrack(PhTrk3,2,5.,1.,10,0) / 2 L3FTrack(PhTrk05,4,.5,1.,10,0) / 2 L3FTrack(PhTrk05,3,.5,1.,10,0) / 2 L3FTrack(PhTrk1,2,1.,1.,10,0) / 2 L3FTrack(PhTrk05,3,.75,1.,10,0) / 2 L3FTrack(PhTrk1,2,3.,1.,10,0) / 2 L3FTrack(PhTrk5,1,5.,1.,10,0) / 2 L3FTrack(PhTrk10,2,10.,1.,10,0) / 2 L3FTrack(PhTrk3,1,3.,1.,10,0) / 2 L3FTrack(PhTrk12,1,12.,1.,10,0) / 2 L3FTrack(PhTrk8,1,8.,1.,10,0) / 2 L3FTrack(PhTrk3,2,3.,1.,10,0) / 2 L3FTrack(PhTrk5,2,5.,1.,10,0) / 2 L3FTrack(PhTrk1,2,1.5,1.,10,0) / 2 Let me know if you need any more information. Cheers, Per Part3 *************************************************************************** Hi, here's part 3 of the v15 L3 filters. I have also copied the complete list to: www-d0.fnal.gov/~jonsson/v15L3.txt All jet tools have two new parameters (for the L1confirmation, which is switched off by default) in v15: "UseL1Conf" and "L1CALUNPACK" The SC5JET_9_PV3 tool is also affected by the change to the new tracker. Test_4Per_RunIIb / 1.00 contains the following jet terms which again can be used as templates for the other v15 jet terms: L3FJet(SC5JET_9_PV3,1,15.,0.,3.6) / 4 L3FJet(SC5JET_9_PV3,1,9.,0.,3.6) / 4 In v14.93 i find the following additional jet terms which need to be translated: L3FJet(SC5JET_9_PV3,2,12.,0.,3.6) / 2 L3FJet(SC5JET_9_PV3,2,15.,0.,3.6) / 2 L3FJet(SC5JET_9_PV3,2,20.,0.,3.6) / 2 L3FJet(SC5JET_9_PV3,1,25.,0.,3.6) / 2 L3FJet(SCJET_8,1,45.,0.,4.) / 2 L3FJet(SCJET_8,1,15.,0.,4.) / 2 L3FJet(SCJET_8,1,95.,0.,4.) / 2 L3FJet(SCJET_8,1,125.,0.,4.) / 2 L3FJet(SCJET_8,1,8.,0.,4.) / 1 L3FJet(SCJET_8,1,25.,0.,4.) / 2 L3FJet(SCJET_8,1,65.,0.,4.) / 2 L3FJet(SC5JET_9_PV3,3,15.,0.,3.6) / 2 L3FJet(SC5JET_9_PV3,2,25.,0.,3.6) / 2 L3FJet(SC5JET_9_PV3,4,20.,0.,3.6) / 2 L3FJet(SC5JET_9_PV3,3,20.,0.,3.6) / 2 L3FJet(SC5JET_9_PV3,3,12.,0.,3.6) / 2 L3FJet(SC5JET_9_PV3,3,10.,0.,3.6) / 2 L3FJet(SC5JET_9_PV3,1,35.,0.,3.6) / 1 L3FJet(SC5JET_9_PV3,1,12.,0.,3.6) / 2 part 4 ************************************************************************** The following Hta term exists with the new jet filter: L3FHta(L3FJet(SC5JET_9_PV3,1,9.,0.,3.6),50.) / 4 We also need to translate: L3FHta(L3FJet(SC5JET_9_PV3,1,9.,0.,3.6),80.) / 2 The following PVZ terms already exist for the new tracker: L3FCFTVertex(prvtx3_phys,1,2.,500.,-35.,35.) / 3 L3FCFTVertex(prvtx1_phys,1,2.,500.,-35.,35.) / 3 I see no other PVZ term in v14.93 The following HT term exists already: L3FHt(L3FJet(SC5JET_9_PV3,1,9.,0.,3.6),L3FJet(SC5JET_9_PV3,1,9.,0.,3.6),100.,2000.) / 4 We also need to translate the following term; L3FHt(L3FJet(SC5JET_9_PV3,1,9.,0.,3.6),L3FJet(SC5JET_9_PV3,1,9.,0.,3.6),250.,2000.) / 2 Part 5 ****************************************************************************** The following track matched muon terms already exist (the non track matched muon terms are the same as in v14): L3FMuon(MUON_CM,1,0.,0.,2.5,0.,5.,MEDIUM) / 3 L3FMuon(MUON_CM,1,0.,0.,2.5,0.,3.,LOOSE) / 3 L3FMuon(MUON_CM,1,0.,0.,2.5,0.,4.,MEDIUM) / 2 These ones from v14.93 need to be translated: L3FMuon(MUON_CM,2,1.5,ASTUB) / 2 L3FMuon(MUON_CM,3,1.5,ASTUB) / 2 L3FMuon(MUON_CM,1,0.,0.,2.5,0.,8.,LOOSE) / 2 L3FMuon(MUON_CM,1,0.,0.,2.5,0.,3.,MEDIUM) / 2 L3FMuon(MUON_CM,1,0.,0.,2.5,0.,10.,LOOSE) / 2 L3FMuon(MUON_CM,1,0.,0.,2.5,0.,5.,LOOSE) / 2 L3FMuon(MUON_CM,2,0.,0.,2.5,0.,3.,LOOSE) / 2 L3FMuon(MUON_CM,1,0.,0.,2.5,0.,6.29,0.,12.,LOOSE,FALSE,TRUE) / 2 The following inv. mass term exists with the new tracker: L3FInvMass(PhTrk05,.98,1.08,.494,.494,TRUE) / 3 We also need to translate the following (see below for IPTrk05): L3FInvMass(IPTrk05,.98,1.08,.494,.494,TRUE) / 1 L3FInvMass(L3FJet(SCJET_8,1,8.,0.,4.),L3FJet(SCJET_8,1,8.,0.,4.),250.,1960.,0.,0.,FALSE) / 1 L3FInvMass(L3FJet(SCJET_8,1,8.,0.,4.),L3FJet(SCJET_8,1,8.,0.,4.),430.,1960.,0.,0.,FALSE) / 1 The following IPtrack term exists with the new tracker: L3FIP(IPTracker,2,3.,20.,1.5,10,0,2,0) / 4 We also need to translate the following: L3FIP(IPTracker,3,3.,20.,.75,10,0,2,0) / 3 L3FIP(IPTracker,4,3.,20.,.5,10,0,2,0) / 3 L3FIP(IPTracker,1,3.,20.,.5,10,0,2,0) / 4 Part 6 ************************************************************* Test_4Per_RunIIb / 1.00 contains the following BID term with the new tracking and jet tool: L3FBID(IPTag_JT10,1,.3) / 7 We also need to translate these two from v14.93: L3FBID(IPTag_JT10,1,.05) / 4 L3FBID(IPTag6_JT10,1,.05) / 5 The RunIIb test list does not contain any PhysIP filter. The following needs to be created with the new track matched muon and IPtrk filters: L3FPhysIP(L3FIP(IPTracker,1,3.),L3FMuon(MUON_CM,1,4.,M)) / 3 Part 7 ************************************************************* I found some more electron terms in v14.93 which need to be translated. L3FEle(ELE_NLV_SHT,1,12.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_T12,1,12.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_SH_T5,2,5.,0.,3.6,-99.,99.) / 3 L3FEle(ELE_NLV_SHT_T7,1,8.,0.,3.6,-99.,99.) / 2 L3FEle(ELE_NLV_SH_IT7T,1,8.,0.,3.6,-99.,99.) / 3 L3FEle(ELE_NLV_SHT_IT10T,1,10.,0.,3.6,-99.,99.) / 3 The ELE_NLV_SH_IT7T and IT10T terms need to be redone for v15 using the RunIIbtracker instead of the GlobalTracker everywhere at all layers. ....and so do these terms (there are no examples of isolated track terms in the RunIIb test list, sorry....): L3FTrack(IsoTrk5_T1,1,10.,1.,10,0) / 3 L3FTrack(IsoTrk15_L1,1,15.,1.,10,0) / 2 L3FTrack(IsoTrk20_L1,1,20.,1.,10,0) / 2 L3FTrack(IsoTrk10_L1,1,10.,1.,10,0) / 1 L3FTrack(IsoTrk10_T1,1,10.,1.,10,0) / 2 L3FTrack(IsoTrk12_T1,1,12.,1.,10,0) / 2 L3FTrack(TightIsoTrk5_swtrrfst05,1,10.,1.,10,0) / 1