MC Job Options merge requestshttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests2024-01-05T16:59:59+01:00https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2812Extension of exotics Prompt HNL request2024-01-05T16:59:59+01:00Yiming AbulaitiExtension of exotics Prompt HNL requestMake sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLMCPROD-11005
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [x] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [x] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [x] The request has been approved by the PA/CP group
- [x] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [x] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [x] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [x] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [x] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [x] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)Yiming AbulaitiYiming Abulaitihttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2807Updating gridpack input tarball and symlink [skip modfiles]2024-02-17T20:55:30+01:00Marisilvia DonadelliUpdating gridpack input tarball and symlink [skip modfiles]## Changes introduced
Update the gridpack input tarball for k_lambda = 1.0 LHE file production and corresponding symlink.
## Tests
LHE production request for 3 k_lambda values (0, 1.0, 5.0) using Athena release 21.6.103 is about to b...## Changes introduced
Update the gridpack input tarball for k_lambda = 1.0 LHE file production and corresponding symlink.
## Tests
LHE production request for 3 k_lambda values (0, 1.0, 5.0) using Athena release 21.6.103 is about to be submitted:
https://docs.google.com/spreadsheets/d/1UOIvokfKGAmxdwfmPIAzEjzGDpZc-YJz9Y2ePmpVCeo/edit#gid=87963823
For reference, see LHE JOs registered for :
LHE JO for k_lambda = 0 (https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/blob/master/602xxx/602763/mc_13p6TeV.Ph_PDF4LHC15_HH_cHHH00d0.GRID.tar.gz?ref_type=heads)
LHE JO for k_lambda = 5 (https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/blob/master/602xxx/602764/mc_13p6TeV.Ph_PDF4LHC15_HH_cHHH05d0.GRID.tar.gz?ref_type=heads)
and the corresponding JIRA: ATLMCPROD-10887
## Issues resolved
Closes #Dominic HirschbuehlAna Rosario Cueto GomezDominic Hirschbuehlhttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2804try to change the existing stau CO2023-12-19T15:43:53+01:00Yang Liutry to change the existing stau CO## Description of bug
Trying to add/change a new filter to the existing stau CO
## Changes introduced
Add a new filter into it
## Tests
## Issues resolved
Closes ### Description of bug
Trying to add/change a new filter to the existing stau CO
## Changes introduced
Add a new filter into it
## Tests
## Issues resolved
Closes #Dominic HirschbuehlAna Rosario Cueto GomezDominic Hirschbuehlhttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2801JOs for boosted resonant VBF HH->bbbb using Composite Higgs Model2023-12-16T20:08:55+01:00Marisilvia DonadelliJOs for boosted resonant VBF HH->bbbb using Composite Higgs ModelMake sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLMCPROD-**10935**
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [ ] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [ ] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [ ] The request has been approved by the PA/CP group
- [ ] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [ ] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [ ] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [ ] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [ ] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [ ] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)Marisilvia DonadelliMarisilvia Donadellihttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2800Switching to 5FS and adjusting safe factor [skip modfiles]2024-02-09T14:15:26+01:00Marisilvia DonadelliSwitching to 5FS and adjusting safe factor [skip modfiles]## Changes introduced
1) Switch from a 4 flavors scheme to 5 flavors scheme ⇒ In agreement with VBF HH
→ bbγγ, matches default settings for other VBF samples (see https://indico.cern.ch/event/1312333/contributions/5525022/attachments/2...## Changes introduced
1) Switch from a 4 flavors scheme to 5 flavors scheme ⇒ In agreement with VBF HH
→ bbγγ, matches default settings for other VBF samples (see https://indico.cern.ch/event/1312333/contributions/5525022/attachments/2694713/4676573/MonteCarloRequest.pdf)
2) Replace the previous safe factor (was set to 30) by 1.1. The safe factor was set to 30 by mistake as there is no filter for this process (so no need to worry about filter efficiency).
## Tests
The MC event generation speed is improved by an order of magnitude compared to Run 2 :) with the safe factor set to 1.1.
More details in this presentation:
https://cernbox.cern.ch/pdf-viewer/public/LYmL5OTibx89j1n/slides_vbf_hh_validation.pdf?contextRouteName=files-public-link&contextRouteParams.driveAliasAndItem=public%2FLYmL5OTibx89j1n&items-per-page=100
JIRA ticket for reference: ATLMCPROD-10960
## Issues resolved
Closes #Dominic HirschbuehlAna Rosario Cueto GomezDominic Hirschbuehlhttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2799test2023-12-15T15:43:53+01:00Spyros ArgyropoulostestATLMCPROD-10960ATLMCPROD-10960https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2798Run 3 JOs for VBF HH->4b2023-12-15T21:15:45+01:00Marisilvia DonadelliRun 3 JOs for VBF HH->4bMake sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLMCPROD-10960
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [ ] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [ ] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [ ] The request has been approved by the PA/CP group
- [ ] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [ ] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [ ] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [ ] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [ ] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [ ] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)Marisilvia DonadelliMarisilvia Donadellihttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2789MC23 Z'->ll signal request at 13.6 TeV2023-12-12T20:00:34+01:00Yiming AbulaitiMC23 Z'->ll signal request at 13.6 TeVMake sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLMCPROD-10974
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [x] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [x] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [x] The request has been approved by the PA/CP group
- [x] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [x] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [x] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [x] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [x] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [x] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)Yiming AbulaitiYiming Abulaitihttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2777Powheg Dijet Slices w/ Nuclear PDFs -- LHE Production2023-12-11T16:00:42+01:00Matthew Caleb HoppeschPowheg Dijet Slices w/ Nuclear PDFs -- LHE ProductionMake sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLHI-455
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [x] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [x] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [ ] The request has been approved by the PA/CP group
- [ ] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [ ] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [ ] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [ ] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [ ] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [ ] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2771pThard1_tW_DR_dyn_with_new_LHE2023-12-05T08:49:48+01:00Qibin LiupThard1_tW_DR_dyn_with_new_LHEMake sure that all the items in the checklists are duly followed:\
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
ATLMCPROD-**10881**
## Checklist for approval
...Make sure that all the items in the checklists are duly followed:\
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
ATLMCPROD-**10881**
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).\
If something is unclear get in touch with the repository maintainers.
* [x] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
* [x] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
* [x] The request has been approved by the PA/CP group
* [ ] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
* [ ] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
* [ ] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
* [ ] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
* [ ] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
* [ ] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2759VBF Hbb + Hcc Run 2 Pythia8+EvGen2024-02-09T07:50:51+01:00Daniela RebuzziVBF Hbb + Hcc Run 2 Pythia8+EvGenMake sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLMCPROD-10934
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [x] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [x] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [x] The request has been approved by the PA/CP group
- [ ] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [ ] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [ ] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [ ] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [x] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [x] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2734MC23 Herwig H->4l and H->mumu2024-02-17T11:27:39+01:00Shu LiMC23 Herwig H->4l and H->mumuMake sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLMCPROD-10851
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [x] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [x] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [x] The request has been approved by the PA/CP group
- [x] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [x] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [x] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [x] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [x] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [x] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2731MC23 Herwig H->4l and H->mumu2024-02-08T16:18:47+01:00Shu LiMC23 Herwig H->4l and H->mumuMake sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLMCPROD-10851
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [x] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [x] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [x] The request has been approved by the PA/CP group
- [x] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [x] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [x] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [x] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [x] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [x] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2729FxFx pp->4l mc23 samples with new gridpack2024-02-09T07:45:44+01:00Daniela RebuzziFxFx pp->4l mc23 samples with new gridpackMake sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLMCPROD-10895
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [x] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [x] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [x] The request has been approved by the PA/CP group
- [ ] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [ ] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [ ] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [ ] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [x] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [x] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2725ggF HH->bbyy JO for Run32024-02-09T14:07:13+01:00Marisilvia DonadelliggF HH->bbyy JO for Run3Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLMCPROD-10841
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [ ] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [ ] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [ ] The request has been approved by the PA/CP group
- [ ] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [ ] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [ ] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [ ] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [ ] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [ ] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)Marisilvia DonadelliMarisilvia Donadellihttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2719tWZ (Z->ll) with MG5+MadSpin+Pythia8/Herwig72023-12-11T19:39:03+01:00Lucia KeszeghovatWZ (Z->ll) with MG5+MadSpin+Pythia8/Herwig7Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
[ATLMCPROD-10911](https://its.cern.ch/jira/browse/ATLMCPROD-10911)
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [x] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [x] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [ ] The request has been approved by the PA/CP group
- [ ] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [ ] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [ ] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [ ] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [x] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [x] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2706Sherpa2.2.14 off-peak sys variations2023-11-10T19:00:46+01:00Miha Muskinjamiha.muskinja@cern.chSherpa2.2.14 off-peak sys variationsMake sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLMCPROD-10910
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [ ] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [ ] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [ ] The request has been approved by the PA/CP group
- [ ] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [ ] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [ ] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [ ] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [ ] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [ ] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2702Regeneration of Slepton to Bino to Higgsino signal grid2023-11-10T13:28:42+01:00Yang LiuRegeneration of Slepton to Bino to Higgsino signal gridMake sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
ATLMCPROD-10878
## Checklist for approval
Thi...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
ATLMCPROD-10878
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [x] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [x] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [x] The request has been approved by the PA/CP group
- [ ] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [ ] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [ ] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [ ] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [ ] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [ ] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2695Powheg+Herwig7.2 dijet2023-11-08T12:18:36+01:00Haifeng LiPowheg+Herwig7.2 dijetMake sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLMCPROD-10803
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [ ] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [ ] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [ ] The request has been approved by the PA/CP group
- [ ] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [ ] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [ ] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [ ] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [ ] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [ ] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)Haifeng LiHaifeng Lihttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2682MC23 H->Z(qq/vv)y samples at 13.6 TeV2024-02-09T07:37:01+01:00Daniela RebuzziMC23 H->Z(qq/vv)y samples at 13.6 TeVMake sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket n...Make sure that all the items in the checklists are duly followed:
follow the instructions of each checklist item and report potential issues to the repository mainteners.
## JIRA ticket
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLMCPROD-10812
## Checklist for approval
This checklist should be normally filled by MC contacts (but it can also be done by the person opening the merge request).
If something is unclear get in touch with the repository maintainers.
- [x] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [x] I have provided the ATLMCPROD JIRA ticket where the request has been discussed
- [x] The request has been approved by the PA/CP group
- [ ] The pipeline has run and the status is green (still check the CI job output - if you see any errors report to the repository maintainers)
- [ ] If the pipeline is orange: check the CI job output to sort out the issues. If the issue is unclear contact the repository maintainers
- [ ] CI jobs have not been skipped (if jobs have been skipped, the requesters should provide a reason for skipping and confirmation from the PMG conveners is necessary before merging)
- [ ] Check that no `log.generate.short` files are included in the commit to be merged to master. If such files are present, it indicates that something went wrong in the pipeline. Check the job logs and contact the package maintainers if needed.
- [x] Check that the title of the MR is descriptive enough (if not ask the requester to modify it)
- [x] Check that the DSID range assigned is correct (500000-999999) and corresponds to [right generator block](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/PmgMcSoftware#DSID_blocks)