Skip to content

Production configuration for Run3 May collisions #4678

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 5 commits into from
Jun 1, 2022

Conversation

germanfgv
Copy link
Contributor

Production configuration following results in #4677

@germanfgv
Copy link
Contributor Author

fyi @francescobrivio

@germanfgv
Copy link
Contributor Author

test syntax please

@francescobrivio
Copy link
Contributor

@germanfgv I spotted these differences:

  • for the dataset DoubleEG you forgot to update one of the producers from HcalCalIsoTrkFilter to HcalCalIsoTrkProducerFilter
  • for the datasets AlCaLumiPixelsCountsPrompt* there are few flags that should be switched to true:
    • do_reco = True
    • write_reco = True
    • write_aod = True
    • and add disk_node="T2_CH_CERN"

@germanfgv germanfgv force-pushed the CollisionsMay2022_Config branch from 4a7b14a to 394f2da Compare May 25, 2022 09:42
@germanfgv germanfgv force-pushed the CollisionsMay2022_Config branch from 394f2da to 37bd26c Compare May 25, 2022 09:46
@germanfgv
Copy link
Contributor Author

test syntax please

@francescobrivio
Copy link
Contributor

+1 on commit 37bd26c

@tvami
Copy link
Contributor

tvami commented May 25, 2022

Although it's not for collisions, I think we should add the cosmics producer SiStripCalCosmicsNano, it was tested and works #4661 -- just so that we dont forget about this

@jhonatanamado
Copy link
Contributor

Hi @germanfgv . German please take into account the following changes that were included in #4668 , https://github.com/jhonatanamado/T0/blob/0a24d7c7243def7f24edeb8f3a6afe15cf1b3d12/etc/ProdOfflineConfiguration.py#L961-L975

DATASETS = ["AlCaLumiPixelsCountsExpress0", "AlCaLumiPixelsCountsExpress1", "AlCaLumiPixelsCountsExpress2", "AlCaLumiPixelsCountsExpress3",
            "AlCaLumiPixelsCountsExpress4", "AlCaLumiPixelsCountsExpress5", "AlCaLumiPixelsCountsExpress6", "AlCaLumiPixelsCountsExpress7",
            "AlCaLumiPixelsCountsExpress8", "AlCaLumiPixelsCountsExpress9", "AlCaLumiPixelsCountsExpress10", "AlCaLumiPixelsCountsExpress11",
            "AlCaLumiPixelsCountsExpress12", "AlCaLumiPixelsCountsExpress"]

for dataset in DATASETS:
    addDataset(tier0Config, dataset,
               do_reco=True,
               write_reco=False, write_aod=False, write_miniaod=False, write_dqm=False,
               reco_split=alcarawSplitting,
               proc_version=alcarawProcVersion,
               alca_producers=["AlCaPCCZeroBias", "RawPCCProducer"],
               timePerEvent=0.02,
               sizePerEvent=38,
               scenario=alcaLumiPixelsScenario)

If Im not wrong, this will allow promptreco for the PD AlCaLumiPixelsCountsExpressX due that the rate for that stream will be splitted. FYI @tvami

@tvami
Copy link
Contributor

tvami commented Jun 1, 2022

This is used in the current collisions, right? Can we merge this please?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants