MC request using splitSim to study different decay modes with converted photons

Requires the use of

$APPCONFIG/options/Gauss/SplitSim-GammaConversionFilter.py https://gitlab.cern.ch/lhcb-datapkg/AppConfig/-/blob/v3-patches/options/Gauss/SplitSim-GammaConversionFilter.py and $APPCONFIG/options/Gauss/GammaConversionFilter_ExtendZ.py https://gitlab.cern.ch/lhcb-datapkg/AppConfig/-/blob/v3-patches/options/Gauss/GammaConversionFilter_ExtendZ.py?ref_type=heads

FYI : the production will pass through the RD group , CC'ed @elsmith , @abiolchi , @rihender

THe production is across different channels :

• Bs-> Phi gamma
• B0 -> K* gamma
• Lb-> L gamma
• B+ -> K+ pi0 ( to verify we could gain something in pi0 -> gg )

The SplitSim with the conversion at Z < 2400 has a retention rate of 20% in Gauss, so i scaled 2M generated events by a factor 4. All samples to be generated DST since it would be useful to study also some 'restripping' dedicated to those decays.

As i am new to the request, which field has to be added to the yaml to specify this is SplitSim and the additional AppConfig has to configured @adavis ?

Requires lbmcsubmit!66 (merged)

added RD label

@rquaglia see lbmcsubmit!66 (merged) . Once reviewed and merged, you should be able to use in the yaml file

fast-mc:
  splitsim: yes

added 1 commit

• a48a94d0 - add ```fast-mc : splitsim : yes``` flag

Compare with previous version

changed the description

changed the description

added 1 commit

• a6e16749 - Update converted_gamma_request.yaml , with extend-z mode flag

Compare with previous version

resolved all threads

added 1 commit

• 13600d30 - commit to re-trigger pipeline

Compare with previous version

added 1 commit

• dd68d4a3 - Fix yaml to work with lb-mc script

Compare with previous version

The MR should be ok, i tried to test the yaml with

lb-mc converted_gamma_request_stage0.yaml converted_gamma_request_stage6.yaml
Loading converted_gamma_request_stage0.yaml
Running checks
Generated 6 production requests
    containing 24 subrequests
    and 192,000,000 events

Is this the correct way to do this? Should i rename the file to be _stage0?

added 1 commit

• 253fd9e7 - Add retention-rate : 0.2

Compare with previous version

added 1 commit

• 0b04cce1 - Change to 2M the request accounting for the retention-rate

Compare with previous version

mentioned in merge request !65 (merged)

Hello, is there anything i should be doing in this? I would need those samples to verify some new stripping lines i am planning to develop for the restripping campaign.

Thanks in advance for any feedback

added 1 commit

• 205df3e1 - Commit to re-trigger pipeline

Compare with previous version

marked this merge request as ready

marked this merge request as draft

marked this merge request as ready

added 1 commit

• f8169847 - Update converted_gamma_request.yaml

Compare with previous version

added 1 commit

• 5e8705e0 - Update converted_gamma_request.yaml, add file format in samples slot

Compare with previous version

added 1 commit

• 6687deeb - Update converted_gamma_request.yaml

Compare with previous version

approved this merge request

added 1 commit

• db92e809 - Try increasing num-test-events to pass pipeline

Compare with previous version

@admorris I can only merge this request if the pipeline has passed, so I have tried increasing num-test-events but I expect this will take a while to finish. Is there any alternative for this type of request which tends to fail the tests because of the gamma conversion filter, or is waiting for enough events to generate the only option?

approved this merge request

merged

mentioned in commit 8cf5f756

mentioned in issue #104 (closed)

Just for completeness, @admorris and @adavis , the SplitSim worked as charm. Here the z-plot of the converted photon conversion location. The x-y map across all z

In the Velo .

resolved all threads

mentioned in merge request !238