MC Job Options merge requestshttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests2022-11-09T16:39:59+01:00https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2142change the nEventsPerJob and filterMultiplier for 601589 [skip modfiles]2022-11-09T16:39:59+01:00Yi Yuchange the nEventsPerJob and filterMultiplier for 601589 [skip modfiles]It should run fine with 10k,
for nonallhad the filter efficiency is 0.54, thus 2 would be enough.It should run fine with 10k,
for nonallhad the filter efficiency is 0.54, thus 2 would be enough.https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2112added new gridpack ttW (2L filter) at 13p6 com2022-10-26T12:57:24+02:00Marcos Miralles Lopezadded new gridpack ttW (2L filter) at 13p6 comThe gridpack for 700706 (ttW with 2L filter) has to be updated to the new COM.The gridpack for 700706 (ttW with 2L filter) has to be updated to the new COM.https://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2103ttV (ttW/ttZ) samples for run 32022-10-21T11:29:17+02:00Marcos Miralles LopezttV (ttW/ttZ) samples for run 3Make 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 maintainers.
## JIRA ticket
ATLMCPROD-10185
## Checklist for approval
Th...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 maintainers.
## JIRA ticket
ATLMCPROD-10185
## 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/1785New JobOptions for Sherpa dijet samples in v2.2.112022-10-12T17:06:54+02:00Haifeng LiNew JobOptions for Sherpa dijet samples in v2.2.11## JIRA ticket
ATLMCPROD-9881
## Checklist for requesters
- [x] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [x] I have provided the ATLMC...## JIRA ticket
ATLMCPROD-9881
## Checklist for requesters
- [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
## Checklist for approvers
- [x] All the items in the "Checklist for requesters" have been completed successfully
- [x] 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)
- [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] 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
- [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 no file has been modified or deleted
- [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/1859Draft: ggH aMCPy8 with LFV H to ltau2022-10-12T17:06:04+02:00Spyros ArgyropoulosDraft: ggH aMCPy8 with LFV H to ltauMake 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-9853
## 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)Shu LiShu Lihttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/1541VHbb aMC@NLO+Pythia8 production for VHbb processes2022-10-12T17:03:22+02:00Stephen JigginsVHbb aMC@NLO+Pythia8 production for VHbb processes## JIRA ticket
[ATLMCPROD-9678](https://its.cern.ch/jira/browse/ATLMCPROD-9678)
## Checklist for requesters
- [ ] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampl...## JIRA ticket
[ATLMCPROD-9678](https://its.cern.ch/jira/browse/ATLMCPROD-9678)
## 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/1942LHE files production of Powheg ttH at 13.6 TeV - DSID 601406 (all had)2022-10-11T15:52:52+02:00Daniela RebuzziLHE files production of Powheg ttH at 13.6 TeV - DSID 601406 (all had)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-10030
## 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-10030
## 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)Daniela RebuzziDaniela Rebuzzihttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/1844Sherpa dijets CKKW2022-10-07T13:54:48+02:00Javier Llorente MerinoSherpa dijets CKKWMake 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-9947
## 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/2077Fixed description of two new jO2022-10-05T14:20:46+02:00Dominic HirschbuehlFixed description of two new jOfixed descriptions of two jO, which had the wrong filter explainedfixed descriptions of two jO, which had the wrong filter explainedhttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/2069JOs for A->ZH->lltt/vvbb2022-10-04T11:27:29+02:00Yanlin LiuJOs for A->ZH->lltt/vvbbMake 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-10180
## 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/2046cLFV in top decay and production2022-09-16T20:45:53+02:00Rohin Thampilali NarayancLFV in top decay and 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 -->
ATLMCPROD-10154
## 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/1980Sherpa 2.2.12 10<mll<40 GeV Run-3 E2E samples2022-08-03T23:52:41+02:00Matthew GignacSherpa 2.2.12 10<mll<40 GeV Run-3 E2E samplesMake 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-9898
## 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)Matthew GignacMatthew Gignachttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/1977Sherpa dijets 2->2 @ LO2022-08-02T20:13:32+02:00Javier Llorente MerinoSherpa dijets 2->2 @ LOMake 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-10094
## 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)Javier Llorente MerinoJavier Llorente Merinohttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/1944LHE files production of Powheg ttH at 13.6 TeV - dilep2022-07-28T16:13:22+02:00Daniela RebuzziLHE files production of Powheg ttH at 13.6 TeV - dilepMake 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-10030
## Checklist for approval
Th...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-10030
## 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)
- [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)
- [ ] 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)Daniela RebuzziDaniela Rebuzzihttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/1582long-lived GMSB higgsino with 50% BR to either Z+gravitino or higgs+gravitino2022-07-27T16:48:21+02:00Elodie Deborah Resseguielong-lived GMSB higgsino with 50% BR to either Z+gravitino or higgs+gravitino## JIRA ticket
ATLMCPROD-9571
## Checklist for requesters
- [x] I have followed the [guidelines in McSampleRequestProcedure](https://twiki.cern.ch/twiki/bin/view/AtlasProtected/McSampleRequestProcedure)
- [x] I have provided the ATLMC...## JIRA ticket
ATLMCPROD-9571
## Checklist for requesters
- [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 (https://its.cern.ch/jira/browse/ATLMCPROD-9571)
- [x] 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/1955Removing inputFilesPerJob criteria for DSID 6000262022-07-26T18:04:27+02:00Louis D'EramoRemoving inputFilesPerJob criteria for DSID 600026## Description of bug
When running with the JO 600026, two flags for production were set: nEventsPerJob and inputFilesPerJob.
Given that the LHE files have been run with 10k events per file, the latter argument is in contradiction with ...## Description of bug
When running with the JO 600026, two flags for production were set: nEventsPerJob and inputFilesPerJob.
Given that the LHE files have been run with 10k events per file, the latter argument is in contradiction with the first one.
## Changes introduced
Removing inputFilesPerJob and keeping nEventsPerJob to 10k.
## Tests
See log.generate attached running with 14TeV LHE file (similar test was done with 13TeV one).[log.generate](/uploads/6669d09177ec80234594c791c46c414c/log.generate)
## Issues resolved
Closes #Matthew GignacJan KretzschmarChristian GutschowMatthew Gignachttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/1941LHE files production of Powheg ttH at 13.6 TeV2022-07-18T14:24:39+02:00Daniela RebuzziLHE files production of Powheg ttH at 13.6 TeV## Description of bug
The inked GRID file was wrong, I have just fixed the link.
This request refers to ATLMCPROD-10030.
## Changes introduced
Link to GRID file fixed in 601405.
## Tests
## Issues resolved
Closes ### Description of bug
The inked GRID file was wrong, I have just fixed the link.
This request refers to ATLMCPROD-10030.
## Changes introduced
Link to GRID file fixed in 601405.
## Tests
## Issues resolved
Closes #Matthew GignacJan KretzschmarChristian GutschowMatthew Gignachttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/1921JOs for Leptophilic low mass Z'->4mu signal samples2022-07-07T13:55:47+02:00Yanlin LiuJOs for Leptophilic low mass Z'->4mu signal samplesMake 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-10035
## 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)Yanlin LiuYanlin Liuhttps://gitlab.cern.ch/atlas-physics/pmg/mcjoboptions/-/merge_requests/1864joboptions for active learning effort 512985-5130142022-05-27T11:34:22+02:00Zubair Bhattijoboptions for active learning effort 512985-513014Make 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-9514
## 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
- [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/1761Draft: Allow logParser job to throw dynamic warning2022-05-16T11:10:22+02:00Spyros ArgyropoulosDraft: Allow logParser job to throw dynamic warning## Changes introduced
logParser job will return "warning" status when there are warnings in the logParser
## Tests
To do
## Issues resolved
Closes #48## Changes introduced
logParser job will return "warning" status when there are warnings in the logParser
## Tests
To do
## Issues resolved
Closes #48Christian GutschowChristian Gutschow