MC Job Options merge requestshttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests2024-03-27T04:05:45+01:00https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2979R23 Run2 & Run3 signal request for ISRC1C1 and ISRC1N22024-03-27T04:05:45+01:00Yang LiuR23 Run2 & Run3 signal request for ISRC1C1 and ISRC1N2Make 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-11090
## Checklist for approval
This...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-11090
## 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)
- [ ] Check that the ATLMCPROD link provided in "JIRA ticket" field above works and that a working link pointing to this MR is posted on the corresponding JIRA page. If not contact the package maintainers.https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2974Heavy vector triplet, DarkJets, 3-prong signals2024-03-25T04:40:01+01:00Yi YuHeavy vector triplet, DarkJets, 3-prong signalsMake 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-11119
## 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)
- [ ] Check that the ATLMCPROD link provided in "JIRA ticket" field above works and that a working link pointing to this MR is posted on the corresponding JIRA page. If not contact the package maintainers.https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/297613.6 TeV gridpack for tWZ, Z->ll with DR22024-03-22T21:48:14+01:00Lucia Keszeghova13.6 TeV gridpack for tWZ, Z->ll with DR2Make 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-11145
## 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)
- [x] Check that the ATLMCPROD link provided in "JIRA ticket" field above works and that a working link pointing to this MR is posted on the corresponding JIRA page. If not contact the package maintainers.https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2972Heavy vector triplet, DarkJets, 3-prong signals2024-03-20T13:31:49+01:00Yi YuHeavy vector triplet, DarkJets, 3-prong signalsMake 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-**{\*PLEASE FILL THIS\*}**
## 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)
- [ ] Check that the ATLMCPROD link provided in "JIRA ticket" field above works and that a working link pointing to this MR is posted on the corresponding JIRA page. If not contact the package maintainers.https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2971Heavy vector triplet, DarkJets, 3-prong signals2024-03-19T17:41:21+01:00Yi YuHeavy vector triplet, DarkJets, 3-prong signalsMake 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-**{\*PLEASE FILL THIS\*}**
## 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)
- [ ] 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)
- [ ] Check that the ATLMCPROD link provided in "JIRA ticket" field above works and that a working link pointing to this MR is posted on the corresponding JIRA page. If not contact the package maintainers.https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2968pMSSM models for 3G Bino scan2024-03-19T13:30:14+01:00Yang LiupMSSM models for 3G Bino scanMake 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-11120
## Checklist for approval
This...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-11120
## 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)
- [ ] Check that the ATLMCPROD link provided in "JIRA ticket" field above works and that a working link pointing to this MR is posted on the corresponding JIRA page. If not contact the package maintainers.https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2951mc20 & mc23 signal requests for highmass dilepton search2024-03-15T15:15:49+01:00Yiming Abulaitimc20 & mc23 signal requests for highmass dilepton searchMake 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-11102
## 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)
- [x] Check that the ATLMCPROD link provided in "JIRA ticket" field above works and that a working link pointing to this MR is posted on the corresponding JIRA page. If not contact the package maintainers.Yiming AbulaitiYiming Abulaitihttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2955Request for signal samples Z' -> bb with ISR2024-03-13T19:26:03+01:00Yiming AbulaitiRequest for signal samples Z' -> bb with ISRMake 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-11112
## 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)
- [x] Check that the ATLMCPROD link provided in "JIRA ticket" field above works and that a working link pointing to this MR is posted on the corresponding JIRA page. If not contact the package maintainers.Yiming AbulaitiYiming Abulaitihttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2945VH(bb/cc) leptonic decay of vector boson MC23 shower JOs2024-03-11T17:15:17+01:00Stephen JigginsVH(bb/cc) leptonic decay of vector boson MC23 shower JOsMake 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-10752
## 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-10752
## 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)
- [ ] Check that the ATLMCPROD link provided in "JIRA ticket" field above works and that a working link pointing to this MR is posted on the corresponding JIRA page. If not contact the package maintainers.https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2874VH(bb/cc) leptonic decay of vector boson MC23 shower JOs2024-03-08T15:19:28+01:00Stephen JigginsVH(bb/cc) leptonic decay of vector boson MC23 shower JOs## JIRA ticket
ATLMCPROD-10752
## 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 repos...## JIRA ticket
ATLMCPROD-10752
## 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/2905JOs for tta(bb) H7 signal2024-02-23T14:20:15+01:00Marisilvia DonadelliJOs for tta(bb) H7 signalMake 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-11072
## 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)
- [ ] Check that the ATLMCPROD link provided in "JIRA ticket" field above works and that a working link pointing to this MR is posted on the corresponding JIRA page. If not contact the package maintainers.Marisilvia DonadelliMarisilvia Donadellihttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2919Herwig Lund2024-02-22T17:14:39+01:00Haifeng LiHerwig LundMake 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-10870
## 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)
- [ ] Check that the ATLMCPROD link provided in "JIRA ticket" field above works and that a working link pointing to this MR is posted on the corresponding JIRA page. If not contact the package maintainers.https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2914Wprime2024-02-21T16:42:29+01:00Haifeng LiWprimeMake 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-10983
## 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)
- [ ] Check that the ATLMCPROD link provided in "JIRA ticket" field above works and that a working link pointing to this MR is posted on the corresponding JIRA page. If not contact the package maintainers.https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2881Wprime2024-02-21T16:03:58+01:00Haifeng LiWprimeMake 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-10983
## 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)Haifeng LiHaifeng Lihttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2562test samples for new HF Pythia settings2024-02-17T12:42:29+01:00Marjorie Shapirotest samples for new HF Pythia settingsMake 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.
<!-- Fill the line below with the JIRA ticket number, e.g. ATL...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.
<!-- Fill the line below with the JIRA ticket number, e.g. ATLMCPROD-1234 -->
ATLMCPROD-10749
## 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:
Rquest discussed in GIT meeting 23 June 2023
- [ ] 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)
Note: DSID 950739 uses 100 input files (the max allowed by the commit script) but the CPU time is very short. This results in an error being reported in the commit script. Spiros suggested I use the -u flag to ignore the error. As a result, CI is not run.
- [ ] 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.
See above
- [ ] 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/1612ggZH(ll,vv)+1j production using MadGraph5+Pythia8.2024-02-16T12:41:27+01:00Stephen JigginsggZH(ll,vv)+1j production using MadGraph5+Pythia8.## JIRA ticket
ATLMCPROD-9747
## Checklist for requesters
- [ ] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [ ] I have provided the ATLMC...## JIRA ticket
ATLMCPROD-9747
## Checklist for requesters
- [ ] 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
## Checklist for approvers
- [ ] All the items in the "Checklist for requesters" have been completed successfully
- [ ] The pipeline has run and the status is green (if it is orange look at the CI job output and iterate with the requesters to sort out the issues if possible)
- [ ] 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)
- [ ] Look at the output of the child pipeline created by `run_child_pipeline` and make sure that **at least one `run_athena_DSID` job has run**. If it's not the case, 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 no file has been modified or deleted
- [ ] 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/2890jO for ttbb evgen sample2024-02-09T22:04:12+01:00Lucia KeszeghovajO for ttbb evgen sampleMake 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-11071
## 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/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/2350JOs for ZX reanalysis2024-02-09T08:05:36+01:00Yanlin LiuJOs for ZX reanalysisMake 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-10461
## 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)