CMS: 2016 dataset transfer

[katilp]

(from #124)

JetHT for testing

Transfer started for Run2016G JetHT

$ echo $dataset
/JetHT/Run2016G-UL2016_MiniAODv2-v2/MINIAOD
$  rucio add-rule cms:$dataset 1 T3_CH_CERN_OpenData
5aa90ff16f3541659de09f8406702366

-bash-4.2$ echo $dataset
/JetHT/Run2016G-UL2016_MiniAODv2_NanoAODv9-v1/NANOAOD
-bash-4.2$ rucio add-rule cms:$dataset 1 T3_CH_CERN_OpenData
fc402697fd7f4eedbdc624edd7198bc2

[katilp]

The quota for t3_ch_cern_opendata_local is now updated to 5.1PB (see https://cms-opendata-releaseguide.docs.cern.ch/transfer/site_setup/)

Update 14 Nov 2023:
No: it still shows

----------+---------+
-bash-4.2$ rucio list-account-limits t3_ch_cern_opendata_local
+---------------------+----------+
| RSE                 | LIMIT    |
|---------------------+----------|
| T3_CH_CERN_OpenData | 4.000 PB |
+---------------------+----------+
+------------------+---------+
| RSE EXPRESSION   | LIMIT   |
|------------------+---------|
+------------------+---------+

Now updated. NB the set-limits commands has to be run with the personal account (with admin rights) as RUCIO_ACCOUNT

$ rucio list-account-limits t3_ch_cern_opendata_local
+---------------------+----------+
| RSE                 | LIMIT    |
|---------------------+----------|
| T3_CH_CERN_OpenData | 5.100 PB |
+---------------------+----------+
+------------------+---------+
| RSE EXPRESSION   | LIMIT   |
|------------------+---------|
+------------------+---------+

[katilp]

Datasets to transfer to replace invalidated ones:

For example, invalidated:

/SMS-TChiWZ_ZToLL_mZMin-0p1_LLN2_TuneCP5_13TeV-madgraphMLM-pythia8/RunIISummer20UL16MiniAODv2-106X_mcRun2_asymptotic_v17-v2/MINIAODSIM
/SMS-TChiWZ_ZToLL_mZMin-0p1_LLN2_TuneCP5_13TeV-madgraphMLM-pythia8/RunIISummer20UL16NanoAODv9-106X_mcRun2_asymptotic_v17-v3/NANOAODSIM

to be replaced with:

/SMS-TChiWZ_ZToLL_mZMin-0p1_LLN2_TuneCP5_13TeV-madgraphMLM-pythia8/RunIISummer20UL16MiniAODv2-106X_mcRun2_asymptotic_v17-v4/MINIAODSIM
/SMS-TChiWZ_ZToLL_mZMin-0p1_LLN2_TuneCP5_13TeV-madgraphMLM-pythia8/RunIISummer20UL16NanoAODv9-106X_mcRun2_asymptotic_v17-v4/NANOAODSIM

The full list below

[tiborsimko]

There are 649 datasets in the McM store and/or chain that are flagged INVALID. Perhaps they may appear in the provenance chain of the datasets that are going to be released? It would be good to check and see if this may be a problem:

invalid_datasets_mcm_store_chain.txt