Kati Lassila-Perini
Kati Lassila-Perini
The file types of the "normal" collision and simulated data will be nanoaod and nanoaodsim, respectively. We should reflect that in the types of derived datasets so that collision data...
The recids for the production code are - NanoAODRun1: 12505 - PFNano: 12504
@Ari-mu-l, yes, there are. Most of them are like this: ``` { "equivalent_lumi_uncertainty": "-9", "total_value_uncertainty": "0.000e+00", "filter_efficiency_evt_uncertainty": "0.000e+00", "xsec_before_matching": "1.835e+01", "xsec_before_filter": "-9", "HepMC_filter_efficiency": "-9", "xsec_after_matching": "-1.835e+01", "filter_efficiency": "1.000e+00", "xsec_before_matching_uncertainty": "1.579e-02",...
@Ari-mu-l : @d0leh and @danaalsharif can look how to exclude the zero values in the script.
We consider only config files that have `--eventcontent RECO` in the command-line string at the beginning (and in consequence, a `process.RECOoutput` output block). For 1-5 check if there are any...
@danaalsharif would you add the same comment in the comment field for all five datasets in the spreadsheet?
Check that all processes that have values get included, i.e. all subdirs under MC2016/HiggsPhysics and MC2016/StandardModelPhysics. It does not appear for https://opendata-qa.cern.ch/record/75601 while that dataset has computed values under MC2016/StandardModelPhysics/ElectroWeak...
Invalid datasets to be removed: ``` "status": "INVALID", /b_bbar_4l_TuneCP5_13TeV-powheg-pythia8/RunIISummer20UL16MiniAODv2-106X_mcRun2_asymptotic_v17-v1/MINIAODSIM "status": "INVALID", /b_bbar_4l_TuneCP5_13TeV-powheg-pythia8/RunIISummer20UL16NanoAODv9-106X_mcRun2_asymptotic_v17-v1/NANOAODSIM "status": "INVALID", /ChargedHiggs_HplusTB_HplusToHW_M-1000_MH2_M-200_TuneCP5_13TeV_amcatnlo_pythia8/RunIISummer20UL16MiniAODv2-106X_mcRun2_asymptotic_v17-v1/MINIAODSIM "status": "INVALID", /ChargedHiggs_HplusTB_HplusToHW_M-1000_MH2_M-200_TuneCP5_13TeV_amcatnlo_pythia8/RunIISummer20UL16NanoAODv9-106X_mcRun2_asymptotic_v17-v1/NANOAODSIM "status": "INVALID", /ChargedHiggs_HplusTB_HplusToHW_M-800_MH2_M-200_TuneCP5_13TeV_amcatnlo_pythia8/RunIISummer20UL16MiniAODv2-106X_mcRun2_asymptotic_v17-v1/MINIAODSIM "status": "INVALID", /ChargedHiggs_HplusTB_HplusToHW_M-800_MH2_M-200_TuneCP5_13TeV_amcatnlo_pythia8/RunIISummer20UL16NanoAODv9-106X_mcRun2_asymptotic_v17-v1/NANOAODSIM "status": "INVALID", /ChargedHiggs_HplusTB_HplusToHW_M-900_MH2_M-200_TuneCP5_13TeV_amcatnlo_pythia8/RunIISummer20UL16MiniAODv2-106X_mcRun2_asymptotic_v17-v1/MINIAODSIM "status": "INVALID", /ChargedHiggs_HplusTB_HplusToHW_M-900_MH2_M-200_TuneCP5_13TeV_amcatnlo_pythia8/RunIISummer20UL16NanoAODv9-106X_mcRun2_asymptotic_v17-v1/NANOAODSIM...
Replying to my own question: This was due to no resources (type of machines) available in the requested zone. Changing `--zone` and/or `--machine-type` solves the problem. The error message ```...
Perfect, thanks! Can you add that to the search tips? It would be good to have the tips e.g. from here:  I.e. **Help** could be a drop-down menu with...