Cosmic Simulation in rel 14: Samples

Overview

  • These samples are produced in 14.4.0 AtlasProduction on the batch system, although simulation step is also available with Simulation/SimuJobTransforms/scripts/csc_cosmics_sim_trf.py
  • What we used for these samples is now included in SimuJobTransforms-00-07-99, which needs tags G4CosmicFilter-00-00-12 and CosmicGenerator-00-00-34.
  • The new simulation transform is included in 14.5.1.2,AtlasProduction,runtime. Run without arguments for instructions - here is an example anyway:
  csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=10000 randomSeed=1234 geometryVersion=ATLAS-GEONF-04-00-00 CosmicFilterVolume=TRT_Barrel CosmicFilterVolume2=Pixel conditionsTag=OFLCOND-CSC-01-00-00 jobConfig=Cosmics.py
  • Tags for digitization: CommissionUtils-00-00-21, PixelDigitization-00-07-13-02, SiDigitization-03-05-04, SCT_Digitization-00-11-13 . jobOptions testdig.py attached.
  • The size of the ATLAS-GEO samples will be ~50k events when first stage finished.
  • To access the data use STAGE_SVCCLASS=atlasgroupdisk
  • Two filters: CosmicGenerator constrains the production vertex and direction of generator-level tracks, G4CosmicFilter requires simulated hits inside a certain volume - more details on the settings for the generator can be found in the attached jobOptions_ConfigCosmicProd.py. Note that the CosmicGenerator settings for pixelbarrel-filtered samples are optimized for pixel studies and may not be appropriate for other detector studies.
  • Some limitations:
    • Several questions lately: note that the mu+/mu- ratio in simulation (1.5) is not the same as in data. The simulation flux calculation uses this reference: A. Dar , Phys. Rev. Letters 51, 227 (1983)
    • Timing is wrong for the muons, trigger will not work correctly.

List of geometries used:

  • ATLAS-GEO-03-00-00 (aligned, Solenoid On, Toroids On)
  • ATLAS-GEONF-04-00-00 (aligned, no magn field)
  • ATLAS-GEO-04-00-00 (aligned, Solenoid off, Toroids On)

List of simulation filter volumes used:

  • Muon (all of Atlas, geant volume is MUONQ2::MUONQ2)
  • TRT barrel (geant volume is TRT::BarrelOuterSupport)
  • Pixel barrel (has to have hits inside geant volumes TRT::BarrelOuterSupport and Pixel::Pixel)
Please note that all subsystems are switched on in all samples; the naming refers just to the filtering on the track direction

Samples

Production with Muon Volume

ATLAS-GEO-03-00-00:
  • 5000 events at /castor/cern.ch/grid/atlas/atlasgroupdisk/proj-simcos/rel14/ATLAS-GEO-03-00-00/dig/dig.muon_B.70000x.root
where x=1-5

ATLAS-GEONF-04-00-00:
  • so far only a few thousand test events. Pixel hit timing not correct for these. Can be found at ~gencomm/w0/cosmicSim_rel14/NoField/dig.muon*.root .

Production with TRT barrel Volume

ATLAS-GEO-03-00-00:
  • 58666 events at /castor/cern.ch/grid/atlas/atlasgroupdisk/proj-simcos/rel14/ATLAS-GEO-03-00-00/dig/dig.GEO-03-TRTBarrel.*.root
  • The corresponding hits files can be found in the ATLAS-GEO-03-00-00/sim directory

ATLAS-GEONF-04-00-00:
  • 50327 events at /castor/cern.ch/grid/atlas/atlasgroupdisk/proj-simcos/rel14/ATLAS-GEONF-04-00-00/dig.trtbarrel.200*.root
  • The corresponding hits files can be found in the ATLAS-GEONF-04-00-00/hits directory

ATLAS-GEO-04-00-00:
  • 57756 events at /castor/cern.ch/grid/atlas/atlasgroupdisk/proj-simcos/rel14/ATLAS-GEO-04-00-00/dig
  • corresponding hits files can be seen in ATLAS-GEO-04-00-00/sim directory

Production with pixel barrel Volume

ATLAS-GEO-03-00-00:
  • Approx 46k events can be found at: /castor/cern.ch/grid/atlas/atlasgroupdisk/proj-simcos/rel14/ATLAS-GEO-03-00-00/dig/dig.pixelbarrel_B.400*.root
  • The corresponding hits files can be found in the ATLAS-GEO-03-00-00/sim directory

ATLAS-GEONF-04-00-00:
  • Approx 48k events at /castor/cern.ch/grid/atlas/atlasgroupdisk/proj-simcos/rel14/ATLAS-GEONF-04-00-00/dig.pixelbarrel.500*.root
  • The corresponding hits files can be found in the ATLAS-GEONF-04-00-00/hits directory

ATLAS-GEO-04-00-00:
  • 55368 events. Files are in /castor/cern.ch/grid/atlas/atlasgroupdisk/proj-simcos/rel14/ATLAS-GEO-04-00-00/dig/dig.pixelbarrel_B.600*.root
  • The corresponding hits files can be found in the ATLAS-GEO-04-00-00/sim directory

How to run reconstruction:

  • Use release 14.5.0.2,AtlasProduction
  • Check out and compile
    cmt co -r RecExCommission-00-03-94 Reconstruction/RecExample/RecExCommission
  • get JO:
get_files -jo Collisions_ATN.py
  • edit this file with the following
add the lines:
jobproperties.Beam.beamType.set_Value_and_Lock('cosmics')
rec.doTrigger.set_Value_and_Lock(False)
after the importing of the flags.
edit the lines:
<             globalflags.DetDescrVersion.set_Value_and_Lock('ATLAS-Comm-02-00-00')
<             athenaCommonFlags.PoolRDOInput.set_Value_and_Lock( ["/afs/cern.ch/atlas/maxidisk/d17/dig.trtbarrel_ma_B100.root"])
to point to the dataset you want and to set teh DetDescrVersion correctly for that datset.
(you may also have to edit the lines:
            jobproperties.BField.solenoidOn=True
            jobproperties.BField.barrelToroidOn=True
            jobproperties.BField.endcapToroidOn=True
to se the magnetic field configuration correctly).
for simulation made in rel 14 remove the line: 
           SpecialTileConfigHack=True
edit the number of events you want to run over:
athenaCommonFlags.EvtMax.set_Value_and_Lock(500)
  • then run like:
athena -c RTTsim=True Collisions_ATN.py
  • This will run and produce ESD, CBNT. you can configure the job to also produce monitoring histograms, TAG_COMM, Jive xml by adding the appropriate rec flags.
(monitoring histograms fail if the run number changes during the job - which happens with old (<14) simulated cosmics)

Running cosmic sim reco with Reco_trf transform

  • setup 14.5.1.3,AtlasProduction
  • Run transform like:
>Reco_trf.py inputRDOFile=dig.root maxEvents=10 trigStream=IDCosmic preInclude=RecExCommon/RecoUsefulFlags.py,RecExCommission/CosmicSimulationRecoSetup.py,RecExCommission/RecExCommissionRepro.py,RecJobTransforms/UseOracle.py   outputESDFile=myESD.pool.root HIST=myMergedMonitoring.root  outputTAGComm=myTAGCOMM.root outputCBNT=myCommission.ntuple.root --ignoreunknown
  • Not sure if need trigStream
  • Can change outputs by changing transform arguments (ie. if you dont give a outputCBNT argument wont get a CBNT)
  • Can change the DetdescrVersion by using preExec="globalflags.DetDescrVersion.set_Value_and_Lock('ATLAS-GEO-03-00-00')" or by editing CosmicSimulationRecoSetup.py - field setup should be autoconfigured by the DetDescrVersion in CosmicSimulationRecoSetup.py
  • If you want to run all monitoring (RAW based and ESD based) all in the RAW step you can add to the JO:
from AthenaMonitoring.DQMonFlags import DQMonFlags
DQMonFlags.monType.set_Value_and_Lock('BSall')
  • This is new so may have bugs - please let me (Jamie Boyd) know if you find some problem...
  • I note that in 14.5.1.3 AtlasProduction nightlies this doesnt work if you run monitoring (ie. if you have HIST= as an argument) due to:
  File "/afs/cern.ch/atlas/software/builds/nightlies/14.5.X.Y-VAL/AtlasProduction/rel_3/InstallArea/jobOptions/RecExCommon/RecExCommon_topOptions.py", line 540, in <module>
    protectedInclude ("AthenaMonitoring/DataQualitySteering_jobOptions.py")
  File "/afs/cern.ch/atlas/software/builds/AtlasEvent/14.5.1/InstallArea/jobOptions/AthenaMonitoring/DataQualitySteering_jobOptions.py", line 109, in <module>
    treatException("DataQualitySteering_jobOptions.py: exception when setting up LAr monitoring")
  File "/afs/cern.ch/atlas/software/builds/AtlasEvent/14.5.1/InstallArea/jobOptions/AthenaMonitoring/DataQualitySteering_jobOptions.py", line 107, in <module>
    include("LArMonTools/LArAllMonitoring_jobOptions.py")
  File "/afs/cern.ch/atlas/software/builds/nightlies/14.5.X.Y-VAL/AtlasProduction/rel_3/InstallArea/jobOptions/LArMonTools/LArAllMonitoring_jobOptions.py", line 69, in <module>
    include ("LArMonTools/LArOddCellsMonTool_jobOptions.py")
  File "/afs/cern.ch/atlas/software/builds/nightlies/14.5.X.Y-VAL/AtlasProduction/rel_3/InstallArea/jobOptions/LArMonTools/LArOddCellsMonTool_jobOptions.py", line 24, in <module>
    gainMonitored             = [LArDigitKey,LArDigitKey], # [EM,HEC] ; Monitor only one gain.
NameError: name 'LArDigitKey' is not defined
Py:Athena            INFO leaving with code 8: "an unknown exception occurred"
  • This needs to be fixed!

Trying to get digitization running from a transform

  • John Chapman is trying to get cosmic simulation digitization working out of the box in a fixed production release from a transform (so it can be run in production). (thanks John)
  • Currently in 14.5.1.3 AtlasProduction nightlies can run like
csc_digi_trf.py inputHitsFile=rfio:/castor/cern.ch/grid/atlas/atlasgroupdisk/proj-simcos/rel14/ATLAS-GEO-03-00-00/sim/pixelbarrel_B-400299/sim.root outputRDOFile=test.RDO maxEvents=10 skipEvents=0 geometryVersion=ATLAS-GEO-03-00-00 jobConfig=SimuJobTransforms/CosmicsDigitConfig.py  digiSeedOffset1=0 digiSeedOffset2=0
  • i think this works but it needs to be checked.

useful info

  • we can see how full our castor diskpool is by looking: here our limit is 5TB

-- ElseLytken - 9 Dec 2008

Topic attachments
I Attachment History Action Size Date Who Comment
Texttxt jobOptions_ConfigCosmicProd.py.txt r1 manage 2.9 K 2008-12-10 - 20:49 ElseLytken Cosmic generator settings
Edit | Attach | Watch | Print version | History: r45 | r41 < r40 < r39 < r38 | Backlinks | Raw View | Raw edit | More topic actions...
Topic revision: r39 - 2009-02-22 - JamieBoyd
 
    • 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