Draft:New final states in existing module selecting B -> Eta(') MuMu decays

We add eta->pipigamma and eta'->rhogamma to the existing eta->pipipi0 decays. A second line will be added to add eta->gammagamma decays. Current test yield:

StrippingReport                                                INFO Event 10000, Good event 10000
 |                                              *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*|
 |_StrippingGlobal_                                            |  0.0400|         4|       |  15.597|
 |_StrippingSequenceStreamBhadron_                             |  0.0400|         4|       |  15.571|
 |!StrippingB2EtaMuMuAllX0SelectionLine                        |  0.0400|         4|  1.750|  14.313|
 |!StrippingB2EtaMuMuAllX0SelectionLine_TIMING                 |  0.0400|         4|  1.750|   0.051|

changed milestone to %2023 Re-Strip Campaign -- Development and Testing

added RD label

requested review from @mbirch, @yusong, and @yitang

assigned to @chefdevi

changed target branch from run2-patches to RD_2018-patches

After adding eta(gammagamma)mumu decays and tightening the B vertex cuts:

StrippingReport                                                INFO Event 10000, Good event 10000
 |                                              *Decision name*|*Rate,%*|*Accepted*| *Mult*|*ms/evt*|
 |_StrippingGlobal_                                            |  0.0400|         4|       |  16.686|
 |_StrippingSequenceStreamBhadron_                             |  0.0400|         4|       |  16.656|
 |!StrippingB2EtaMuMuAllX0SelectionLine                        |  0.0100|         1|  1.000|  15.049|
 |!StrippingB2EtaMuMuEta2ggSelectionLine                       |  0.0300|         3|  1.333|   0.147|
 |!StrippingB2EtaMuMuAllX0SelectionLine_TIMING                 |  0.0100|         1|  1.000|   0.047|
 |!StrippingB2EtaMuMuEta2ggSelectionLine_TIMING                |  0.0300|         3|  1.333|   0.051|

marked this merge request as ready

Dear @yitang @mbirch @yusong, is this good to be merge? Note that I didn't "git fetch all..." as this commit is about an existing module that would get over-written by the command. Yet my branch was pretty up-to-date. Best regards

@chefdevi Is this not a B2OC development? You are making only (and many) edits to the B2OC modules. It is likely these will cause conflicts with the B2OC branch in the end. Can you explain why this doesn't live in RD?

Additionally, your title states 2 lines will be added, but you only cite one here. Can you please give the test output of the second line?

In the stripping report above, there are two lines: StrippingB2EtaMuMuAllX0 and StrippingB2EtaMuMuEta2gg.

marked this merge request as draft

Why is this sort of thing being added? None of the information in these changes are related to the title. Are you sure you know that what you are adding is intended?

@yitang I need to block this request until it is understood what is going on. Please do not merge until we (SC) approve.

@chefdevi

Please remake this request with your changes. See the commits here, none of which is your information. Please follow closely the instructions in the writing a stripping line webdoc to make sure you start in the right place.

closed

I followed the instructions. There must have been interferences between my line developments in B2OC and RD (which each checkouts a different branch). I'll make a new commit/request starting from a fresh checkout.

mentioned in merge request !1826 (merged)

OK, I created the request !1826 (merged). Please, let's follow-up there. Hopefully the inconsistencies are gone. Apologies.