calling btagging module in analyses code in expert mode

[juhidutta]

Dear Experts,

Could you please kindly let me know how I may run the btagging on a jet from a lhco file in the analyses code for the expert mode ?

Best regards,
Juhi

[BFuks]

Hi Juhi,

This can be achieved through standard b-tagging methods: b-tagging information can be retrieved through the btag() method of the jet class (as described in the manual).

Cheers,

Benjamin

[juhidutta]

Dear Sir, Thank you for your response. Sorry for the confusion. I am referring to a case in which the lhco file only has jets without b tag and I want to tag them separately in the code in expert mode. How could one call the b tagging method in the code or does one have to check for the parent pdg code to be a B meson and if so, tag the jet as a b jet? With best regards, Juhi

…

On Wed, May 31, 2023, 02:56 Benjamin Fuks ***@***.***> wrote: Hi Juhi, This can be achieved through standard b-tagging methods: b-tagging information can be retrieved through the btag() method of the jet class (as described in the manual). Cheers, Benjamin — Reply to this email directly, view it on GitHub <#197 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHNKT6S5B5CZQUS5XC7FPETXIZQXDANCNFSM6AAAAAAYQTID3Y> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[BFuks]

Hi Juhi, This information being not included in the LHCO file, this is impossible to do. Regards, Benjamin

…

On 31 May 2023, at 02:21, juhidutta ***@***.***> wrote: Dear Sir, Thank you for your response. Sorry for the confusion. I am referring to a case in which the lhco file only has jets without b tag and I want to tag them separately in the code in expert mode. How could one call the b tagging method in the code or does one have to check for the parent pdg code to be a B mesons and if so, then tag the jet as a b jet? With best regards, Juhi On Wed, May 31, 2023, 02:56 Benjamin Fuks ***@***.***> wrote: > Hi Juhi, > > This can be achieved through standard b-tagging methods: b-tagging > information can be retrieved through the btag() method of the jet class (as > described in the manual). > > Cheers, > > Benjamin > > — > Reply to this email directly, view it on GitHub > <#197 (comment)>, > or unsubscribe > <https://github.com/notifications/unsubscribe-auth/AHNKT6S5B5CZQUS5XC7FPETXIZQXDANCNFSM6AAAAAAYQTID3Y> > . > You are receiving this because you authored the thread.Message ID: > ***@***.*** > com> > — Reply to this email directly, view it on GitHub <#197 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AIWJNJ3REIGVUAGU3IQAVVTXI2FILANCNFSM6AAAAAAYQTID3Y>. You are receiving this because you commented.

[juhidutta]

Dear Sir, Ok thank you for letting me know. I have one last query pertaining to the latest madanalysis paper https://inspirehep.net/literature/2639007. On page 13, end of first paragraph, it mentions: "Moreover, we define b jets as small jets with pT > 30 GeV and with a ghost-associated b-hadron with pT > 5 GeV [57, 58]." As far as I understood, in this case the hepmc file is used as an input and fast jet is being used to cluster the fat jets and subsequently the small jets. Could you please kindly elaborate on what the ghost associated b hadron mean and how I can access it from the hepmc file? Thank you for your help, With best regards, Juhi

…

On Wed, May 31, 2023, 01:37 Benjamin Fuks ***@***.***> wrote: Hi Juhi, This information being not included in the LHCO file, this is impossible to do. Regards, Benjamin > On 31 May 2023, at 02:21, juhidutta ***@***.***> wrote: > > > Dear Sir, > > Thank you for your response. > > Sorry for the confusion. > > I am referring to a case in which the lhco file only has jets without b > tag and I want to tag them separately in the code in expert mode. How could > one call the b tagging method in the code or does one have to check for the > parent pdg code to be a B mesons and if so, then tag the jet as a b jet? > > With best regards, > Juhi > > > On Wed, May 31, 2023, 02:56 Benjamin Fuks ***@***.***> wrote: > > > Hi Juhi, > > > > This can be achieved through standard b-tagging methods: b-tagging > > information can be retrieved through the btag() method of the jet class (as > > described in the manual). > > > > Cheers, > > > > Benjamin > > > > — > > Reply to this email directly, view it on GitHub > > < #197 (comment) >, > > or unsubscribe > > < https://github.com/notifications/unsubscribe-auth/AHNKT6S5B5CZQUS5XC7FPETXIZQXDANCNFSM6AAAAAAYQTID3Y > > > . > > You are receiving this because you authored the thread.Message ID: > > ***@***.*** > > com> > > > — > Reply to this email directly, view it on GitHub < #197 (comment)>, or unsubscribe < https://github.com/notifications/unsubscribe-auth/AIWJNJ3REIGVUAGU3IQAVVTXI2FILANCNFSM6AAAAAAYQTID3Y >. > You are receiving this because you commented. > — Reply to this email directly, view it on GitHub <#197 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHNKT6R22YB43PHLMYDDG5TXI3RMNANCNFSM6AAAAAAYQTID3Y> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>

[BFuks]

Dear Juhi,

As far as I understood, in this case the hepmc file is used as an input and fast jet is being used to cluster the fat jets and subsequently the small jets.

Precisely. In this case, with the HepMC file we have all the hadron-level information so that we are able to implement any b-tagging method we wanted.

Could you please kindly elaborate on what the ghost associated b hadron mean and how I can access it from the hepmc file?

We just implemented the algorithm as described in the references. As we have all the information, it is easy. Cheers, Benjamin

[juhidutta]

Dear Sir, Thank you for your prompt response. I will look into the references. With best regards, Juhi

…

On Thu, Jun 1, 2023, 00:20 Benjamin Fuks ***@***.***> wrote: Dear Juhi, > As far as I understood, in this case the hepmc file is used as an input and > fast jet is being used to cluster the fat jets and subsequently the small > jets. > Precisely. In this case, with the HepMC file we have all the hadron-level information so that we are able to implement any b-tagging method we wanted. > Could you please kindly elaborate on what the ghost associated b hadron > mean and how I can access it from the hepmc file? We just implemented the algorithm as described in the references. As we have all the information, it is easy. Cheers, Benjamin — Reply to this email directly, view it on GitHub <#197 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AHNKT6USFGD3PUD4NEBZJGLXI6HGZANCNFSM6AAAAAAYQTID3Y> . You are receiving this because you authored the thread.Message ID: ***@***.*** com>