JIRA : JIRA-JetEtmiss
MC15 : https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/JetEtmissMC15
DC14 : https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/JetEtmissDC14
Pre-recommendation: https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/JetEtmissPrerecSamples2014
Upgrd: https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/JetEtmissMC12Upgrade
MC12: https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/JetEtmissMC12
MC11: https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/JetEtmissMC11
2015 pre-recommendation : https://twiki.cern.ch/twiki/bin/view/AtlasProtected/JetEtmissPrerecSamples2014

New JobOption and DSID: https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/JetEtmissMCDCID


Monitoring samples:
BigPanda : http://bigpanda.cern.ch/prodsys/prodtask/request_table/#/?type=MC&phys_group=JETM
AtlProd: http://www-f9.ijs.si/atlpy/atlprod/prodtask/?ot=desc&tagr__exact=J&o=2

Production group wiki pages (useful for the full production spreadsheet, which is updated frequently, and for sim/rec tags):
MC15a : https://twiki.cern.ch/twiki/bin/view/AtlasProtected/AtlasProductionGroupMC15a

MC12a : https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/AtlasProductionGroupMC12a
MC12b : https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/AtlasProductionGroupMC12b
MC12c : https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/AtlasProductionGroupMC12c
Upgrad : https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/AtlasProductionGroupMC12Upgrade
MC14a : https://twiki.cern.ch/twiki/bin/view/AtlasProtected/AtlasProductionGroupMC14a

Information on conditions tags:

New samples jobos and validation:
MC12JobOptions: https://svnweb.cern.ch/trac/atlasoff/browser/Generators/MC12JobOptions/trunk/share/ &nbsp&nbsp wsvn

MC11JobOptions: https://svnweb.cern.ch/trac/atlasoff/browser/Generators/MC11JobOptions/trunk/share/ &nbsp&nbsp wsvn
Evgen production MC12: https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/AtlasMcProductionMC12
Core samples MC12: https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/AtlasMCProductionM12CoreConf
Running: https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/RunningGenerators

Disk space : gustavo.otero@cern.ch

A useful tutorial from Wolfgang and Claire:

When someone makes a request:

1. First check with conveners that this is suitable.

  • They should specify which generator, process, which cofm energy, the detector geometry for example standard, ATLAS+IBL

2. Ask them:

  • How many events (for dijets how many per slices) -usually 400K
  • ESD or AOD? (default AOD) If ESD check with M&A that they can be stored at SLAC.
  • What is the priority? Zero is top priority. Usually can determine the priority by asking
  • What is the timescale and motivation?
  • If ESD, do they need calibration hits, particle ID (default is NO)? Is it okay to have frozen showers in FCAL (default is YES)?
  • Pileup overlay : fixed mu or mu+-10 range?

  • What about pileup? Default is standard pileup. If they want NO pileup, this is done via reco tags (see below)
  • Special pileup samples: will send separate email...
  • The default is 50ns bunch crossing. Some requests may state 25ns inthe future.
  • The default physics list is QGSP_BERT but we also have some dijetswith FTFP_BERT
  • If you know already that you start from merged HITS, can you add the tags for evgen, sim and sim merging into the spread sheet? This also clarifies then if you want cal hits or not as these are defined by the sim tag. Also, the spread sheet has columns as ECM, generator, contact and a few more. At least the three mentioned should be filled. The comment field can then contain cal hits, the mu value and only intime pileup.

Group production rights : https://twiki.cern.ch/twiki/bin/viewauth/AtlasComputing/GroupsOnGrid#Group_Production_Role

If someone asks you what tune their sample was produced with : https://twiki.cern.ch/twiki/bin/viewauth/AtlasProtected/McGeneratorsForAtlas

Notes on tags:

e_* tag: this is assigned by Wolfgang and Claire
s_* : physics list, frozen showers in FCAL, etc.

If you can't figure out the tags, just leave them empty and Wolfgang will fix it.


 DSIDS e.g from joboptions

New JobOption
Datasets numbers range (184100,184149) reserved for perf-jets.
Need to request that Giovanni Siragusa <giovanni.siragusa@cern.ch>, Eva Bouhova-Thacker <Evelina.Bouhova@cern.ch> would commit the properly named JOs to svn.

  1. -184107 : used for single pi generation.

What are calibration HITS?

Calibration types
ATLAS: EMJES, Global Cell Weighting (GCW), Local Cluster Weighting (LCW) and Global Sequential (GS) calibrations.


"Optimal filter coefficients". This is what is used to estimate the peak of the pulse from the digitized 5 time samples. We base this on a linear estimator E_peak = Sum a_i sample_i where a_i are the OFC coefficients optimized to provide a correct estimator of the amplitude and to minimize noise (so the a_i values depend on what noise is used in the optimization)

See for instance https://cds.cern.ch/record/1057879 for some words on the atlas/athena implementation

and W.E.Cleland and E.G.Stern, NIM A338 (1994) 467. for the historical reference on the OFC technique.

LAr Noise Threshold
The noise sigma of a cell is made of two different parts - the electronics noise and the the RMS of the energy distribution of PileUp. Both values are stored in the conditions database and correspond to a certain configuration (the optimal filter constants (OFC) are adjusted for a certain mu and the actual mu for the PileUp itself needs to be chosen) which is kept stable for longer periods (of the order of half a year). Thus sigma_noise indeed depends on the mu chosen for the OFC and the mu chosen for the PileUp contribution but are not changed event-by-event. This would create too large instabilities of the noise thresholds and it is better to keep a typical mu-OFC/mu-PileUp configuration for an entire running period. http://cern.ch/go/tz8L, LArOFCOptimization

EM FCal Frozen Shower Simulation
FCal frozen shower method is a fast simulation method used at EM forward calorimeter to speed up detector simulation. The frozen shower approach is well described by its name. Prior to the simulation of physics events, showers of electromagnetic particles below a certain energy cut-off (typically 1 GeV) are frozen and stored in a library for use at simulation time. Then, during simulation, when electromagnetic particles fall below that energy cut-off, the particle is stopped and a frozen shower from the library is substituted. SLAC-PUB-14790

MC requests : web interface
as commented some time ago as part of of the migration to ProdSys2, there is a new procedure to place requests. Placing request will have to be done using the web interface at :
it is a two step submission, the last step will send the mail to the csc-prodman list. The information that you will have to provide is the same as for the direct mail to csc-prodman but now you will be entering the request in the ProdSys2 DB and the mail for approval will be sent automatically. We have updated the procedure :

and the instructions on how to place the request using the new interface are at :

Edit | Attach | Watch | Print version | History: r3 < r2 < r1 | Backlinks | Raw View | WYSIWYG | More topic actions
Topic revision: r3 - 2015-05-26 - HaifengLi
    • Cern Search Icon Cern Search
    • TWiki Search Icon TWiki Search
    • Google Search Icon Google Search

    Main All webs login

This site is powered by the TWiki collaboration platform Powered by PerlCopyright & 2008-2019 by the contributing authors. All material on this collaboration platform is the property of the contributing authors.
Ideas, requests, problems regarding TWiki? Send feedback