Difference: CosmicSimHowTo (1 vs. 31)

Revision 312009-05-14 - ZacharyMarshall

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 214 to 214
 
  • Trigger fix(s)
    • muon timing
    • trg configuration
Changed:
<
<
  • Use a calo volume (or with something else for ECs?) for muon volume (current muon volume too big and most events useless) - Claude
  • testing - should have a full chain test for cosmic sim running (only a few events) in nightlies (zach has something for this)
  • revisit the idea of storing a large sample of cosmics at the entrance of cavern, and then run from these (with some small smearing) to save speed
    • This was worked on by Ahmet Bingul in 2007 and he started writing a package to do this: CosmicSmear but never finished this
>
>
  • Use a calo volume (or with something else for ECs?) for muon volume (current muon volume too big and most events useless) - Claude (done for 15.2.0 with G4CosmicFilter-00-00-14 and SimuJobTransforms-00-09-03)
  • testing - should have a full chain test for cosmic sim running (only a few events) in nightlies (zach has something for this here)
  • revisit the idea of storing a large sample of cosmics at the entrance of cavern, and then run from these (with some small smearing) to save speed (This functionality is in place for 15.2.0)
    • This was worked on by Ahmet Bingul in 2007 and he started writing a package to do this: CosmicSmear but never finished this (added simple positional and directional smearing to CosmicGenerator - now being validated, but in place for 15.2.0)
 
    • May be easy to finish this work.... (swagato - looking into this)
  • elevator shafts in rock description
Changed:
<
<
  • Momentum sliced samples (change surface area size and generator params) - (missing et reco issue??)
>
>
  • Momentum sliced samples (change surface area size and generator params) - (missing et reco issue??) (Done for 15.2.0; required modifications to cavern infrastructure GeoModel to change the size of the bedrock above ATLAS, so cannot be backported)
 
  • physics lists used etc...

Description of how propagation through rock is done (from Zach - thanks)

Revision 302009-04-28 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 36 to 36
 

Running cosmic sim reco with Reco_trf transform

  • For most efficient help, write questions directly to hn-atlas-offline-commissioning HN
Changed:
<
<
  • (old) setup 14.5.2.3,AtlasProduction and tags mentioned at: /afs/cern.ch/user/g/gencomm/w0/TagsForSimRepro_14.5.2.Y
  • Now use rel. 14.5.2.10,AtlasProduction
>
>
  • Now use rel. 14.5.2.11,AtlasProduction
 
  • Run transform like:
>Reco_trf.py inputRDOFile=dig.root maxEvents=10 preInclude=RecExCommon/RecoUsefulFlags.py,RecExCommission/CosmicSimulationRecoSetup.py,RecExCommission/RecExCommissionRepro.py,RecJobTransforms/UseOracle.py  beamType=cosmics outputESDFile=myESD.pool.root HIST=myMergedMonitoring.root  outputTAGComm=myTAGCOMM.root outputCBNT=myCommission.ntuple.root geometryVersion=ATLAS-GEO-07-00-00 --ignoreunknown

Revision 292009-04-24 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 37 to 37
 

Running cosmic sim reco with Reco_trf transform

  • For most efficient help, write questions directly to hn-atlas-offline-commissioning HN
  • (old) setup 14.5.2.3,AtlasProduction and tags mentioned at: /afs/cern.ch/user/g/gencomm/w0/TagsForSimRepro_14.5.2.Y
Changed:
<
<
  • Now we have our own nightly for this which is called 14.5.2.Y-VAL (note this isnt actually a VAL nightly but ours for this) as of now rel_4 and rel_5 of this contain all the tags we need and we will build 14.5.2.10 from this very soon.
>
>
  • Now use rel. 14.5.2.10,AtlasProduction
 
  • Run transform like:
>Reco_trf.py inputRDOFile=dig.root maxEvents=10 preInclude=RecExCommon/RecoUsefulFlags.py,RecExCommission/CosmicSimulationRecoSetup.py,RecExCommission/RecExCommissionRepro.py,RecJobTransforms/UseOracle.py  beamType=cosmics outputESDFile=myESD.pool.root HIST=myMergedMonitoring.root  outputTAGComm=myTAGCOMM.root outputCBNT=myCommission.ntuple.root geometryVersion=ATLAS-GEO-07-00-00 --ignoreunknown

Revision 282009-04-24 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 211 to 211
 

Future plans

  • Things that have missed 14.5.1.4 but should go in for future(in no particular order!)
  • Muon digitization fix(s)
Added:
>
>
  • Muon dead-channel map from DB
 
  • Trigger fix(s)
Added:
>
>
    • muon timing
    • trg configuration
 
  • Use a calo volume (or with something else for ECs?) for muon volume (current muon volume too big and most events useless) - Claude
Changed:
<
<
  • testing - should have a full chain test for cosmic sim running (only a few events) in nightlies
>
>
  • testing - should have a full chain test for cosmic sim running (only a few events) in nightlies (zach has something for this)
 
  • revisit the idea of storing a large sample of cosmics at the entrance of cavern, and then run from these (with some small smearing) to save speed
    • This was worked on by Ahmet Bingul in 2007 and he started writing a package to do this: CosmicSmear but never finished this
Changed:
<
<
    • May be easy to finish this work....
>
>
    • May be easy to finish this work.... (swagato - looking into this)
 
  • elevator shafts in rock description
Added:
>
>
  • Momentum sliced samples (change surface area size and generator params) - (missing et reco issue??)
 
  • physics lists used etc...

Description of how propagation through rock is done (from Zach - thanks)

Revision 272009-04-17 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 36 to 36
 

Running cosmic sim reco with Reco_trf transform

  • For most efficient help, write questions directly to hn-atlas-offline-commissioning HN
Changed:
<
<
  • setup 14.5.2.3,AtlasProduction and tags mentioned at: /afs/cern.ch/user/g/gencomm/w0/TagsForSimRepro_14.5.2.Y
>
>
  • (old) setup 14.5.2.3,AtlasProduction and tags mentioned at: /afs/cern.ch/user/g/gencomm/w0/TagsForSimRepro_14.5.2.Y
  • Now we have our own nightly for this which is called 14.5.2.Y-VAL (note this isnt actually a VAL nightly but ours for this) as of now rel_4 and rel_5 of this contain all the tags we need and we will build 14.5.2.10 from this very soon.
 
  • Run transform like:
>Reco_trf.py inputRDOFile=dig.root maxEvents=10 preInclude=RecExCommon/RecoUsefulFlags.py,RecExCommission/CosmicSimulationRecoSetup.py,RecExCommission/RecExCommissionRepro.py,RecJobTransforms/UseOracle.py  beamType=cosmics outputESDFile=myESD.pool.root HIST=myMergedMonitoring.root  outputTAGComm=myTAGCOMM.root outputCBNT=myCommission.ntuple.root geometryVersion=ATLAS-GEO-07-00-00 --ignoreunknown
  • Can change outputs by changing transform arguments (ie. if you dont give a outputCBNT argument wont get a CBNT) see this wiki for more details on Reco_trf
Changed:
<
<
>
>
 
  • If you want to run all monitoring (RAW based and ESD based) all in the RAW step you can add to the JO:
Line: 53 to 54
 
preExec="DQMonFlags.monType.set_Value_and_Lock('BSall')"
Changed:
<
<
  • Currently if i try to run BSall monitoring in this step i get:
  File "/afs/cern.ch/atlas/software/builds/AtlasEvent/14.5.1/InstallArea/jobOptions/AthenaMonitoring/DataQualitySteering_jobOptions.py", line 342, in <module>
    include("MuonCombinedDQA/MuonCombinedMonitoring_jobOptions.py")
  File "/afs/cern.ch/atlas/software/builds/AtlasAnalysis/14.5.1/InstallArea/jobOptions/MuonCombinedDQA/MuonCombinedMonitoring_jobOptions.py", line 28, in <module>
    include("MuonCombinedTrackMon/MuonCombinedTrackMon.py")
  File "/afs/cern.ch/atlas/software/builds/AtlasAnalysis/14.5.1/InstallArea/jobOptions/MuonCombinedTrackMon/MuonCombinedTrackMon.py", line 6, in <module>
    include("MuonSelectionTools/MuonConstructionTool.py")
  File "/afs/cern.ch/atlas/software/builds/AtlasAnalysis/14.5.1/InstallArea/jobOptions/MuonSelectionTools/MuonConstructionTool.py", line 44, in <module>
    include("MuonSelectionTools/MuonSelectionTool.py")
  File "/afs/cern.ch/atlas/software/builds/AtlasAnalysis/14.5.1/InstallArea/jobOptions/MuonSelectionTools/MuonSelectionTool.py", line 711, in <module>
    include("TrackIsolationTools/TrackIsolationTool_jobOptions.py")
  File "/afs/cern.ch/atlas/software/builds/AtlasReconstruction/14.5.1/InstallArea/jobOptions/TrackIsolationTools/TrackIsolationTool_jobOptions.py", line 64, in <module>
    TrackSelector               = TrackIsolationTrackSelectorTool)
  File "/build/atnight/localbuilds/nightlies/14.2.2X-VAL/AtlasReconstruction/rel_0/InstallArea/python/TrackIsolationTools/TrackIsolationToolsConf.py", line 27, in __init__
TypeError: unbound method isInToolSvc() must be called with TrackInCaloTools instance as first argument (got nothing instead)
Py:Athena            INFO leaving with code 8: "an unknown exception occurred"
  • This is submitted as bug 47271
  • A way round this is to not use BSall but to give an AODoutputfilename to the transform which means that art of the monitoring will be done in the ESD->AOD step and then the monitoring histograms merged

(OLD) 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)
>
>
  • Or can run combined monitoring by giving an AODoutputfilename to the transform which means that art of the monitoring will be done in the ESD->AOD step and then the monitoring histograms merged
  • Problem i see right now is that although the job runs through to completion with no problems but the transform returns non-0 exit code due to ERROR messages in the logfile which will be a problem for running in production. needs to be fixed!
 

Test of simulation step in Production

  • Borut has kindly run 3 tasks (to give ~50k events each) of just the simulation step in production

Revision 262009-03-30 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

How to run simulation:

Changed:
<
<
The new simulation transform is included in 14.5.1.24,AtlasProduction,runtime. Run without arguments for instructions - here are some examples anyway:
>
>
The new simulation transform is included in 14.5.1.4,AtlasProduction,runtime. Run without arguments for instructions - here are some examples anyway:
 
    • Pixel volume (= AND of TRT Barrel and pixel volume)
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 runNumber=123 randomSeed=1234 geometryVersion=ATLAS-GEO-07-00-00 CosmicFilterVolume=TRT_Barrel CosmicFilterVolume2=Pixel jobConfig=Cosmics.py
Line: 36 to 36
 

Running cosmic sim reco with Reco_trf transform

  • For most efficient help, write questions directly to hn-atlas-offline-commissioning HN
Changed:
<
<
  • setup 14.5.2.4,AtlasProduction and tags mentioned at: /afs/cern.ch/user/g/gencomm/w0/TagsForSimRepro_14.5.2.Y
>
>
  • setup 14.5.2.3,AtlasProduction and tags mentioned at: /afs/cern.ch/user/g/gencomm/w0/TagsForSimRepro_14.5.2.Y
 
  • Run transform like:
>Reco_trf.py inputRDOFile=dig.root maxEvents=10 preInclude=RecExCommon/RecoUsefulFlags.py,RecExCommission/CosmicSimulationRecoSetup.py,RecExCommission/RecExCommissionRepro.py,RecJobTransforms/UseOracle.py  beamType=cosmics outputESDFile=myESD.pool.root HIST=myMergedMonitoring.root  outputTAGComm=myTAGCOMM.root outputCBNT=myCommission.ntuple.root geometryVersion=ATLAS-GEO-07-00-00 --ignoreunknown

Revision 242009-03-30 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 139 to 139
 
  • You can see the produced monitoring histograms here
  • You can see a couple of event displays here

Known problems

Deleted:
<
<
  • Cant set runnumber in simulation (always 1)
    • Can set the runnumber inside the transform, but needs to be done automatically (normal simulation gets the runnumber from the hits file - but we dont have that step)
    • Suggested to use a combination of the date/time and random seed (using python hash(time)+random seed, but not sure about requirements of runnumber (how many digitis can it be, does it need to be padded, etc... First tests show this is dangerous, simulation runs but not digitization.
  • Should switch to use new condDBtag specially for cosmic simulation: OFLCOND-SIMC-00-00-00
    • Systems need to move any cosmic sim specific (sim, dig and reco) conditions into this tag
 
  • Cant run trigger in reco - i suspect there are many problems for this. the first i get to is:
Shortened traceback (most recent user call last):
Line: 166 to 161
 
    • Testing with UseTOF=False in digitization
    • see This talk for info on RPC timing (its wrong) and trigger issues...
  • Some problems with calibration/alignment???
Changed:
<
<

>
>
    • was a problem with TRT calibration - solved with new condDB tags i hope
 
  • Cosmic charge assymmetry wrong in simulation
  • Generator charge asymmetry is wrong
    • ~1.63 in generator, PDG value ~1.27

Current developments

Changed:
<
<

New Geometry tags

>
>

New Geometry tags (done)

 
  • Pixel need a new set of DetDescrVersions as their HV comes from the geometry DB (and is wrong in the old ones) so we will create
ATLAS-GEO-07-00-00, ATLAS-GEONSF-07-00-00, ATLAS-GEONF-07-00-00, ATLAS-GEONTF-07-00-00
Line: 186 to 181
 
  • Which we need to get rid of as causes transform problems (fixed by SiLorentzAngleSvc-00-00-07-02 which is in 14.5.1.4 nightly).
Changed:
<
<

New conditions DB tags

>
>

New conditions DB tags (done)

 
  • We have created new condDB tags for sim, dig, reco of simulated cosmics (in rel. 14.5.X). Paul has created these tags
OFLCOND-SIMC-00-00-00   [Cosmic simulation - Solenoid off / Toroid off]
Line: 197 to 192
 
  • These tags have been locked (on 9 march 2009) and a DBrelease containing these changes and the updated Geometry tags is being built.
  • experts, Vahko, Paul Laycock
Changed:
<
<

New filter volume

>
>

New filter volume (done)

 
  • The ID asked us to change from using TRTBarrel to ID volume (to increase TRT endcap tracks)
  • Problem is ID volume is much less efficient (only ~30% of events have an offline track)
  • Else is looking at other options but im not sure there will be something useful.
Line: 205 to 200
 
Changed:
<
<

New pixel step size in pixel digitization

>
>

New pixel step size in pixel digitization (done)

 
  • New tags from pixel
SiLorentzAngleSvc-00-00-07-01 
Line: 215 to 210
 
  • These tags are in 14.5.X.Y nightlies
  • Driven by Attillio
Changed:
<
<

Muon digitization

>
>

Muon digitization (not done - working on it for 15.1.0 i think)

 
MDTDigitization.UseTOF=False
Line: 224 to 219
 
  • Driven by Niels
  • Not sure of timescale for this. maybe deferred to second production (or redigitization/reco of first at a later time).
Changed:
<
<

Get elavator shafts into GeoModel

>
>

Get elavator shafts into GeoModel (not done for 15 based sim i hope)

 
  • on page 16 of this talk you can see that the RPC see the effect of the elevator shafts in real data
  • Andreas Korn is working of getting this into GeoModel but probably this wont get into the first production
Changed:
<
<

Runnumber/Eventnumber issues

>
>

Runnumber/Eventnumber issues (done)

 
  • With the tag SimuJobTransforms-00-08-05-03 (requested for 14.5.1.4) one can specifiy optional arguments of runNumber and firstEvent to the simulation transform
  • This means that we will be able to run with a single runnumber for all the jobs in a task (cosmic simulation configuration) and gaurentees unique run/event numbers
  • The production system should be able to deal with this correctly

Extra functionality to get this working in production

Changed:
<
<
  • Need to get the runnumber being set correctly by the simulation transform
    • Issue is if we have 1 runnumber for a whole cosmic sim config then we could have a non unique (run/evt num) combo (which is probably not good)
    • Could try to have a unique runnumber for each job (hash of time and seed?)
    • Or get the eventnumber to be increased for each task?
  • Need to be able to specify the right condDB tag and DetDescrVersion correctly (condDB is correctly set from DetDescrVersions for sim/dig not yet in reco (for new DetDescrVersions...))
  • Need to be able to merge together many simulation outputs into 1 digitization input in production
  • Need to come up with different statistics for types of jobs (for each filter volume)
  • Validation of all of the above (ouch)...
>
>
* Runnumber, firstevent number setting for simulation step works, and should be able to be done by production system (Pavel tells me).
  • Need to come up with different statistics for types of jobs (for each filter volume) - proposed initial sample sizes
1M Pixel Volume - both fields on
1M ID Volume - both fields on <-- maybve upto 5M evts????
0.5M Muon volume - both fields on
1M Pixel Volume - both fields off
1M ID Volume - both fields off
0.5M Muon volume - both fields off
  • Validation of all of above changes - ongoing by Andreas Korn
 

Release issues

Changed:
<
<
  • Looks like we will run the simulation and digitization in 14.5.1.Y AtlasProduction (David Q proposed stopping 14.5.1.Y soon - we need to keep it open (but closed) for cosmic sim)
>
>
  • Looks like we will run the simulation and digitization in 14.5.1.Y AtlasProduction (David Q proposed stopping 14.5.1.Y soon - we need to keep it open (but closed for developer submission) for cosmic sim)
 
  • Then run reco in 14.5.2.Y AtlasProduction (but no tags into that until after the re-reprocessing release is fixed)
Deleted:
<
<
  • Need to finalize how many events as input for each of the steps...
 
  • Need to make sure all changes for this in branches are also in the head (so we can do a rel. 15 production one day).
Added:
>
>
 

Plan now (end of march 2009)

Changed:
<
<
  • Once 14.5.1.4 is out Andreas will test the full chain
>
>
  • 14.5.1.4 is out and Andreas is testing the full chain
 
  • Then try to launch in production the following stats in 14.5.1.4 (reco in 14.5.2.Y)
1M Pixel Volume - both fields on
Line: 269 to 268
 
  • Use a calo volume (or with something else for ECs?) for muon volume (current muon volume too big and most events useless) - Claude
  • testing - should have a full chain test for cosmic sim running (only a few events) in nightlies
  • revisit the idea of storing a large sample of cosmics at the entrance of cavern, and then run from these (with some small smearing) to save speed
Added:
>
>
    • This was worked on by Ahmet Bingul in 2007 and he started writing a package to do this: CosmicSmear but never finished this
    • May be easy to finish this work....
 
  • elevator shafts in rock description
  • physics lists used etc...

Revision 232009-03-25 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

How to run simulation:

Changed:
<
<
* 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
  • In the latest 14.5.X.Y, AtlasProduction nightlies you can run the following for the 3 filter volumes
>
>
The new simulation transform is included in 14.5.1.24,AtlasProduction,runtime. Run without arguments for instructions - here are some examples anyway:
 
    • Pixel volume (= AND of TRT Barrel and pixel volume)
Changed:
<
<
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 randomSeed=1234 geometryVersion=ATLAS-GEO-07-00-00 CosmicFilterVolume=TRT_Barrel CosmicFilterVolume2=Pixel jobConfig=Cosmics.py
>
>
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 runNumber=123 randomSeed=1234 geometryVersion=ATLAS-GEO-07-00-00 CosmicFilterVolume=TRT_Barrel CosmicFilterVolume2=Pixel jobConfig=Cosmics.py
 
    • ID Volume (= OR of TRT Barrel and 2 TRT ECs)
Changed:
<
<
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 randomSeed=1234 geometryVersion=ATLAS-GEO-07-00-00 CosmicFilterVolume=TRT_Barrel CosmicFilterVolume2=TRT_EC jobConfig=Cosmics.py
>
>
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 runNumber=123 randomSeed=1234 geometryVersion=ATLAS-GEO-07-00-00 CosmicFilterVolume=TRT_Barrel CosmicFilterVolume2=TRT_EC jobConfig=Cosmics.py
 
    • Muon Volume (= whole detector)
Changed:
<
<
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 randomSeed=1234 geometryVersion=ATLAS-GEO-07-00-00 CosmicFilterVolume=Muon jobConfig=Cosmics.py
>
>
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 runNumber=123 randomSeed=1234 geometryVersion=ATLAS-GEO-07-00-00 CosmicFilterVolume=Muon jobConfig=Cosmics.py
 
  • The above commands will automatically choose the correct condDB tag from the DetDescrVersion (condDB tag is magnetic field dependent - as is the DetDescrVersion)
  • In production the runnumber and the first event number for each jobs can be set by input arguments to the transform:
Line: 26 to 23
  runNumber=XXX firstEvent=YYYY
  • This is needed to be able to have unique run/event pairs when stuff is produced in production
Added:
>
>
  • setting runnumber is important as having runnumber=0 (current default which i will change) causes monitoring to crash in reco step.
 

Trying to get digitization running from a transform

  • John Chapman has got 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)
Changed:
<
<
>
>
 
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
  • This works. Remember to set STAGE_SVCCLASS=atlasgroupdisk to use this example (if you want to access the HITS file from castor)
Changed:
<
<
  • The CondDB tag used here is automatically chosen from that used in the simulation step (i think)
>
>
  • The CondDB tag used here is automatically chosen from that used in the simulation step
 

Running cosmic sim reco with Reco_trf transform

Changed:
<
<
  • setup 14.5.2.Y,AtlasProduction and tags mentioned at: /afs/cern.ch/user/g/gencomm/w0/TagsForSimRepro_14.5.2.Y
>
>
  • setup 14.5.2.4,AtlasProduction and tags mentioned at: /afs/cern.ch/user/g/gencomm/w0/TagsForSimRepro_14.5.2.Y
 
  • Run transform like:
Changed:
<
<
>Reco_trf.py inputRDOFile=dig.root maxEvents=10 preInclude=RecExCommon/RecoUsefulFlags.py,RecExCommission/CosmicSimulationRecoSetup.py,RecExCommission/RecExCommissionRepro.py,RecJobTransforms/UseOracle.py beamType=cosmics outputESDFile=myESD.pool.root HIST=myMergedMonitoring.root outputTAGComm=myTAGCOMM.root outputCBNT=myCommission.ntuple.root preExec="LArDigitKey='FREE'" geometryVersion=ATLAS-GEO-03-00-00 --ignoreunknown
>
>
>Reco_trf.py inputRDOFile=dig.root maxEvents=10 preInclude=RecExCommon/RecoUsefulFlags.py,RecExCommission/CosmicSimulationRecoSetup.py,RecExCommission/RecExCommissionRepro.py,RecJobTransforms/UseOracle.py beamType=cosmics outputESDFile=myESD.pool.root HIST=myMergedMonitoring.root outputTAGComm=myTAGCOMM.root outputCBNT=myCommission.ntuple.root geometryVersion=ATLAS-GEO-07-00-00 --ignoreunknown
 
Line: 52 to 50
 
  • Or the above can be added as a preExec - in this case the DQMonFlags are already imported so you can just add:
Changed:
<
<
preExec="LArDigitKey='FREE',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...
  • We need the preExec="LArDigitKey='FREE'" part due to a bug in LAr monitoring which gives the error below (LAr experts are working on a fix for this....
  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"
>
>
preExec="DQMonFlags.monType.set_Value_and_Lock('BSall')"
 
Added:
>
>
 
  • Currently if i try to run BSall monitoring in this step i get:
  File "/afs/cern.ch/atlas/software/builds/AtlasEvent/14.5.1/InstallArea/jobOptions/AthenaMonitoring/DataQualitySteering_jobOptions.py", line 342, in <module>

Revision 222009-03-20 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 264 to 264
 
  • Then run reco in 14.5.2.Y AtlasProduction (but no tags into that until after the re-reprocessing release is fixed)
  • Need to finalize how many events as input for each of the steps...
  • Need to make sure all changes for this in branches are also in the head (so we can do a rel. 15 production one day).
Added:
>
>

Plan now (end of march 2009)

  • Once 14.5.1.4 is out Andreas will test the full chain
  • Then try to launch in production the following stats in 14.5.1.4 (reco in 14.5.2.Y)
1M Pixel Volume - both fields on
1M ID Volume - both fields on
0.5M Muon volume - both fields on
1M Pixel Volume - both fields off
1M ID Volume - both fields off
0.5M Muon volume - both fields off
 

Setup for special pixel digitization

Added:
>
>

Future plans

  • Things that have missed 14.5.1.4 but should go in for future(in no particular order!)
  • Muon digitization fix(s)
  • Trigger fix(s)
  • Use a calo volume (or with something else for ECs?) for muon volume (current muon volume too big and most events useless) - Claude
  • testing - should have a full chain test for cosmic sim running (only a few events) in nightlies
  • revisit the idea of storing a large sample of cosmics at the entrance of cavern, and then run from these (with some small smearing) to save speed
  • elevator shafts in rock description
  • physics lists used etc...

Description of how propagation through rock is done (from Zach - thanks)

In the logfile, for every type of material, we get a range cut printed out.

Region <SX1> -- appears in <World::World> world volume
Production cuts :  gamma 2 m      e- 2 m      e+ 2 m

Region <BEDROCK> -- appears in <World::World> world volume
Production cuts :  gamma 1 km     e- 1 km     e+ 1 km

Region <CAV_SHAFTS_CONC> -- appears in <World::World> world volume
Production cuts :  gamma 15 cm     e- 15 cm     e+ 15 cm

These are the cuts that Andrea mentioned.  They should be long enough that secondaries are not being created with any real frequency.  
The next thing to check is the length of the steps.  The muons take about 200-300 steps moving through the bedrock, mostly step-limited 
by interactions (>99%).  That means loosening stepping requirements or "turning off" the muon charge (for example) would not help speed 
things up much.  A typical physics event is several million steps, and a muon traveling straight through the ATLAS detector takes a few 
thousand steps, for comparison.

 -- ElseLytken - 23 Feb 2009
  • stats.ps: CPU performance for grid tests

Revision 212009-03-18 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 37 to 37
 
  • The CondDB tag used here is automatically chosen from that used in the simulation step (i think)

Running cosmic sim reco with Reco_trf transform

Changed:
<
<
  • setup 14.5.2.Y,AtlasProduction and tags mentioned at: /afs/cern.ch/user/g/gencomm/w0/TagsForSimRepro_14.5.2
>
>
  • setup 14.5.2.Y,AtlasProduction and tags mentioned at: /afs/cern.ch/user/g/gencomm/w0/TagsForSimRepro_14.5.2.Y
 
  • Run transform like:
>Reco_trf.py inputRDOFile=dig.root maxEvents=10 preInclude=RecExCommon/RecoUsefulFlags.py,RecExCommission/CosmicSimulationRecoSetup.py,RecExCommission/RecExCommissionRepro.py,RecJobTransforms/UseOracle.py  beamType=cosmics outputESDFile=myESD.pool.root HIST=myMergedMonitoring.root  outputTAGComm=myTAGCOMM.root outputCBNT=myCommission.ntuple.root preExec="LArDigitKey='FREE'" geometryVersion=ATLAS-GEO-03-00-00 --ignoreunknown
  • Can change outputs by changing transform arguments (ie. if you dont give a outputCBNT argument wont get a CBNT) see this wiki for more details on Reco_trf
Changed:
<
<
  • Reco field setup and condDB should be autoconfigured by the DetDescrVersion in CosmicSimulationRecoSetup.py (for new geometries you need to copy this from: ~jboyd/gencomm/newCosmicSimTest/newTags/tests/ATLAS-GEO-07-00-00/RecExCommission/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:

Revision 202009-03-16 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 21 to 21
 csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 randomSeed=1234 geometryVersion=ATLAS-GEO-07-00-00 CosmicFilterVolume=Muon jobConfig=Cosmics.py
  • The above commands will automatically choose the correct condDB tag from the DetDescrVersion (condDB tag is magnetic field dependent - as is the DetDescrVersion)
Added:
>
>
  • In production the runnumber and the first event number for each jobs can be set by input arguments to the transform:
 runNumber=XXX firstEvent=YYYY
  • This is needed to be able to have unique run/event pairs when stuff is produced in production
 

Trying to get digitization running from a transform

  • John Chapman has got 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)

Revision 192009-03-16 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 31 to 31
 
  • This works. Remember to set STAGE_SVCCLASS=atlasgroupdisk to use this example (if you want to access the HITS file from castor)
  • The CondDB tag used here is automatically chosen from that used in the simulation step (i think)
Changed:
<
<

Running cosmic sim reco with Reco_trf transform

  • setup 14.5.1.Y,AtlasProduction
>
>

Running cosmic sim reco with Reco_trf transform

  • setup 14.5.2.Y,AtlasProduction and tags mentioned at: /afs/cern.ch/user/g/gencomm/w0/TagsForSimRepro_14.5.2
 
  • Run transform like:
Changed:
<
<
>Reco_trf.py inputRDOFile=dig.root maxEvents=10 preInclude=RecExCommon/RecoUsefulFlags.py,RecExCommission/CosmicSimulationRecoSetup.py,RecExCommission/RecExCommissionRepro.py,RecJobTransforms/UseOracle.py beamType=cosmics outputESDFile=myESD.pool.root HIST=myMergedMonitoring.root outputTAGComm=myTAGCOMM.root outputCBNT=myCommission.ntuple.root preExec="LArDigitKey='FREE'" --ignoreunknown
>
>
>Reco_trf.py inputRDOFile=dig.root maxEvents=10 preInclude=RecExCommon/RecoUsefulFlags.py,RecExCommission/CosmicSimulationRecoSetup.py,RecExCommission/RecExCommissionRepro.py,RecJobTransforms/UseOracle.py beamType=cosmics outputESDFile=myESD.pool.root HIST=myMergedMonitoring.root outputTAGComm=myTAGCOMM.root outputCBNT=myCommission.ntuple.root preExec="LArDigitKey='FREE'" geometryVersion=ATLAS-GEO-03-00-00 --ignoreunknown
 
  • Can change outputs by changing transform arguments (ie. if you dont give a outputCBNT argument wont get a CBNT) see this wiki for more details on Reco_trf
Changed:
<
<
>
>
  • Reco field setup and condDB should be autoconfigured by the DetDescrVersion in CosmicSimulationRecoSetup.py (for new geometries you need to copy this from: ~jboyd/gencomm/newCosmicSimTest/newTags/tests/ATLAS-GEO-07-00-00/RecExCommission/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

Revision 182009-03-13 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 10 to 10
 
  • In the latest 14.5.X.Y, AtlasProduction nightlies you can run the following for the 3 filter volumes
    • Pixel volume (= AND of TRT Barrel and pixel volume)
Changed:
<
<
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 randomSeed=1234 geometryVersion=ATLAS-GEON-07-00-00 CosmicFilterVolume=TRT_Barrel CosmicFilterVolume2=Pixel jobConfig=Cosmics.py
>
>
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 randomSeed=1234 geometryVersion=ATLAS-GEO-07-00-00 CosmicFilterVolume=TRT_Barrel CosmicFilterVolume2=Pixel jobConfig=Cosmics.py
 
    • ID Volume (= OR of TRT Barrel and 2 TRT ECs)
Changed:
<
<
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 randomSeed=1234 geometryVersion=ATLAS-GEON-07-00-00 CosmicFilterVolume=TRT_Barrel CosmicFilterVolume2=TRT_EC jobConfig=Cosmics.py
>
>
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 randomSeed=1234 geometryVersion=ATLAS-GEO-07-00-00 CosmicFilterVolume=TRT_Barrel CosmicFilterVolume2=TRT_EC jobConfig=Cosmics.py
 
    • Muon Volume (= whole detector)
Changed:
<
<
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 randomSeed=1234 geometryVersion=ATLAS-GEON-07-00-00 CosmicFilterVolume=Muon jobConfig=Cosmics.py
>
>
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 randomSeed=1234 geometryVersion=ATLAS-GEO-07-00-00 CosmicFilterVolume=Muon jobConfig=Cosmics.py
 
  • The above commands will automatically choose the correct condDB tag from the DetDescrVersion (condDB tag is magnetic field dependent - as is the DetDescrVersion)

Revision 172009-03-12 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 195 to 195
 
PixelLorentzAng...  ERROR Conditions Summary Service required but not requested. Will use temperature and voltages from GeoModel or job options.
Changed:
<
<
  • Which we need to get rid of as causes transform problems (fixed by SiLorentzAngleSvc-00-00-07-02).
>
>
  • Which we need to get rid of as causes transform problems (fixed by SiLorentzAngleSvc-00-00-07-02 which is in 14.5.1.4 nightly).
 

New conditions DB tags

  • We have created new condDB tags for sim, dig, reco of simulated cosmics (in rel. 14.5.X). Paul has created these tags
Line: 233 to 233
 
  • Need to know soon, and if there are any associated changes for cosmic sim reco (if so what) - not sure if this will get in for first production
  • Driven by Niels
Added:
>
>
  • Not sure of timescale for this. maybe deferred to second production (or redigitization/reco of first at a later time).
 

Get elavator shafts into GeoModel

  • on page 16 of this talk you can see that the RPC see the effect of the elevator shafts in real data
  • Andreas Korn is working of getting this into GeoModel but probably this wont get into the first production
Added:
>
>

Runnumber/Eventnumber issues

  • With the tag SimuJobTransforms-00-08-05-03 (requested for 14.5.1.4) one can specifiy optional arguments of runNumber and firstEvent to the simulation transform
  • This means that we will be able to run with a single runnumber for all the jobs in a task (cosmic simulation configuration) and gaurentees unique run/event numbers
  • The production system should be able to deal with this correctly
 

Extra functionality to get this working in production

  • Need to get the runnumber being set correctly by the simulation transform
    • Issue is if we have 1 runnumber for a whole cosmic sim config then we could have a non unique (run/evt num) combo (which is probably not good)

Revision 162009-03-10 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 195 to 195
 
PixelLorentzAng...  ERROR Conditions Summary Service required but not requested. Will use temperature and voltages from GeoModel or job options.
Changed:
<
<
  • Which we need to get rid of as causes transform problems.
>
>
  • Which we need to get rid of as causes transform problems (fixed by SiLorentzAngleSvc-00-00-07-02).
 

New conditions DB tags

Changed:
<
<
  • We will be creating new condDB tags for sim, dig, reco of simulated cosmics (in rel. 14.5.X). Paul has created these tags
>
>
  • We have created new condDB tags for sim, dig, reco of simulated cosmics (in rel. 14.5.X). Paul has created these tags
 
OFLCOND-SIMC-00-00-00   [Cosmic simulation - Solenoid off / Toroid off]
OFLCOND-SIMCS-00-00-00  [Cosmic simulation - Solenoid on / Toroid off]
OFLCOND-SIMCT-00-00-00  [Cosmic simulation - Solenoid off / Toroid on]
OFLCOND-SIMCST-00-00-00 [Cosmic simulation - Solenoid on / Toroid on]
Changed:
<
<
  • We need the systems to put the correct conditions in these tags as soon as possible - we want to lock these tags on monday in order to be able to build a DBrelease containing these changes and the updated Geometry tags.
  • experts, Vahko, Paul Laycock, need to be filled by system cond DB experts
>
>
  • These tags have been locked (on 9 march 2009) and a DBrelease containing these changes and the updated Geometry tags is being built.
  • experts, Vahko, Paul Laycock
 

New filter volume

  • The ID asked us to change from using TRTBarrel to ID volume (to increase TRT endcap tracks)
  • Problem is ID volume is much less efficient (only ~30% of events have an offline track)
  • Else is looking at other options but im not sure there will be something useful.
  • Need to decide what to use soon....
Changed:
<
<
>
>
 
  • driven by Christian
Added:
>
>
 

New pixel step size in pixel digitization

  • New tags from pixel
Line: 228 to 231
 
MDTDigitization.UseTOF=False
Changed:
<
<
  • Need to know soon, and if there are any associated changes for cosmic sim reco (if so what)
>
>
  • Need to know soon, and if there are any associated changes for cosmic sim reco (if so what) - not sure if this will get in for first production
 
  • Driven by Niels

Get elavator shafts into GeoModel

Line: 248 to 251
 
  • Looks like we will run the simulation and digitization in 14.5.1.Y AtlasProduction (David Q proposed stopping 14.5.1.Y soon - we need to keep it open (but closed) for cosmic sim)
  • Then run reco in 14.5.2.Y AtlasProduction (but no tags into that until after the re-reprocessing release is fixed)
  • Need to finalize how many events as input for each of the steps...
Added:
>
>
  • Need to make sure all changes for this in branches are also in the head (so we can do a rel. 15 production one day).
 
Added:
>
>

Setup for special pixel digitization

  -- ElseLytken - 23 Feb 2009
  • stats.ps: CPU performance for grid tests

Revision 142009-03-09 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 7 to 7
  * 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
Changed:
<
<

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:
>
>
  • In the latest 14.5.X.Y, AtlasProduction nightlies you can run the following for the 3 filter volumes
    • Pixel volume (= AND of TRT Barrel and pixel volume)
 
Changed:
<
<
get_files -jo Collisions_ATN.py
>
>
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 randomSeed=1234 geometryVersion=ATLAS-GEON-07-00-00 CosmicFilterVolume=TRT_Barrel CosmicFilterVolume2=Pixel jobConfig=Cosmics.py
 
Changed:
<
<
  • edit this file with the following
>
>
    • ID Volume (= OR of TRT Barrel and 2 TRT ECs)
 
Changed:
<
<
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)
>
>
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 randomSeed=1234 geometryVersion=ATLAS-GEON-07-00-00 CosmicFilterVolume=TRT_Barrel CosmicFilterVolume2=TRT_EC jobConfig=Cosmics.py
 
Changed:
<
<
  • then run like:
>
>
    • Muon Volume (= whole detector)
 
Changed:
<
<
athena -c RTTsim=True Collisions_ATN.py
>
>
csc_cosmics_sim_trf.py outputHitsFile=sim.root maxEvents=5000 randomSeed=1234 geometryVersion=ATLAS-GEON-07-00-00 CosmicFilterVolume=Muon jobConfig=Cosmics.py
 
Changed:
<
<
  • 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)
>
>
  • The above commands will automatically choose the correct condDB tag from the DetDescrVersion (condDB tag is magnetic field dependent - as is the DetDescrVersion)

Trying to get digitization running from a transform

  • John Chapman has got 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.Y 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
  • This works. Remember to set STAGE_SVCCLASS=atlasgroupdisk to use this example (if you want to access the HITS file from castor)
  • The CondDB tag used here is automatically chosen from that used in the simulation step (i think)
 

Running cosmic sim reco with Reco_trf transform

Changed:
<
<
  • setup 14.5.1.3,AtlasProduction
>
>
  • setup 14.5.1.Y,AtlasProduction
 
  • Run transform like:
>Reco_trf.py inputRDOFile=dig.root maxEvents=10 preInclude=RecExCommon/RecoUsefulFlags.py,RecExCommission/CosmicSimulationRecoSetup.py,RecExCommission/RecExCommissionRepro.py,RecJobTransforms/UseOracle.py  beamType=cosmics outputESDFile=myESD.pool.root HIST=myMergedMonitoring.root  outputTAGComm=myTAGCOMM.root outputCBNT=myCommission.ntuple.root preExec="LArDigitKey='FREE'" --ignoreunknown
Line: 95 to 84
 
  • This is submitted as bug 47271
  • A way round this is to not use BSall but to give an AODoutputfilename to the transform which means that art of the monitoring will be done in the ESD->AOD step and then the monitoring histograms merged
Changed:
<
<

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
>
>

(OLD) 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:
 
Changed:
<
<
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
>
>
get_files -jo Collisions_ATN.py
 
Changed:
<
<
  • i think this works but it needs to be checked. Remember to set STAGE_SVCCLASS=atlasgroupdisk to use this example
>
>
  • 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)
 

Test of simulation step in Production

  • Borut has kindly run 3 tasks (to give ~50k events each) of just the simulation step in production

Revision 132009-03-09 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 190 to 190
 
  • Problem is ID volume is much less efficient (only ~30% of events have an offline track)
  • Else is looking at other options but im not sure there will be something useful.
  • Need to decide what to use soon....
Changed:
<
<
>
>
 
  • driven by Christian

New pixel step size in pixel digitization

  • New tags from pixel
Line: 208 to 208
 
  • Need to know soon, and if there are any associated changes for cosmic sim reco (if so what)
  • Driven by Niels
Added:
>
>

Get elavator shafts into GeoModel

  • on page 16 of this talk you can see that the RPC see the effect of the elevator shafts in real data
  • Andreas Korn is working of getting this into GeoModel but probably this wont get into the first production
 

Extra functionality to get this working in production

  • Need to get the runnumber being set correctly by the simulation transform
Changed:
<
<
  • Need to be able to specify the right condDB tag and DetDescrVersion correctly (either as input to transforms - or autoconfigured??)
>
>
    • Issue is if we have 1 runnumber for a whole cosmic sim config then we could have a non unique (run/evt num) combo (which is probably not good)
    • Could try to have a unique runnumber for each job (hash of time and seed?)
    • Or get the eventnumber to be increased for each task?
  • Need to be able to specify the right condDB tag and DetDescrVersion correctly (condDB is correctly set from DetDescrVersions for sim/dig not yet in reco (for new DetDescrVersions...))
 
  • Need to be able to merge together many simulation outputs into 1 digitization input in production
  • Need to come up with different statistics for types of jobs (for each filter volume)
  • Validation of all of the above (ouch)...

Release issues

  • Looks like we will run the simulation and digitization in 14.5.1.Y AtlasProduction (David Q proposed stopping 14.5.1.Y soon - we need to keep it open (but closed) for cosmic sim)
  • Then run reco in 14.5.2.Y AtlasProduction (but no tags into that until after the re-reprocessing release is fixed)
Added:
>
>
  • Need to finalize how many events as input for each of the steps...
 

-- ElseLytken - 23 Feb 2009

Revision 122009-03-09 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 169 to 169
 
  • which are exactly the same as the GEO-03/04 ones but with the pixel HV fixed (this is bug report 47235 )
  • These have been created and have the correct InnerDetector-GEO-00-01 tag which has the corrected ID setup in it (from Grant)
  • needed for Attillio, made by Vahko
Added:
>
>
  • with this we get the error:
PixelLorentzAng...  ERROR Conditions Summary Service required but not requested. Will use temperature and voltages from GeoModel or job options.
  • Which we need to get rid of as causes transform problems.
 

New conditions DB tags

  • We will be creating new condDB tags for sim, dig, reco of simulated cosmics (in rel. 14.5.X). Paul has created these tags
Line: 185 to 190
 
  • Problem is ID volume is much less efficient (only ~30% of events have an offline track)
  • Else is looking at other options but im not sure there will be something useful.
  • Need to decide what to use soon....
Added:
>
>
 
  • driven by Christian

New pixel step size in pixel digitization

  • New tags from pixel
Line: 193 to 199
 PixelDigitization-00-07-17-05
Added:
>
>
  • These tags are in 14.5.X.Y nightlies
 
  • Driven by Attillio

Muon digitization

Revision 112009-03-05 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 167 to 167
 ATLAS-GEO-07-00-00, ATLAS-GEONSF-07-00-00, ATLAS-GEONF-07-00-00, ATLAS-GEONTF-07-00-00
  • which are exactly the same as the GEO-03/04 ones but with the pixel HV fixed (this is bug report 47235 )
Added:
>
>
  • These have been created and have the correct InnerDetector-GEO-00-01 tag which has the corrected ID setup in it (from Grant)
 
  • needed for Attillio, made by Vahko

New conditions DB tags

Changed:
<
<
  • We will be creating new condDB tags for sim, dig, reco of simulated cosmics (in rel. 14.5.X). Paul will create these today and we will have 4 tags foor solenoid on/off and toroid on/off.
  • We need the systems to put the correct conditions in these tags as soon as possible (one they are created)
  • made by Paul Laycock, need to be filled by system cond DB experts
>
>
  • We will be creating new condDB tags for sim, dig, reco of simulated cosmics (in rel. 14.5.X). Paul has created these tags
OFLCOND-SIMC-00-00-00   [Cosmic simulation - Solenoid off / Toroid off]
OFLCOND-SIMCS-00-00-00  [Cosmic simulation - Solenoid on / Toroid off]
OFLCOND-SIMCT-00-00-00  [Cosmic simulation - Solenoid off / Toroid on]
OFLCOND-SIMCST-00-00-00 [Cosmic simulation - Solenoid on / Toroid on]
  • We need the systems to put the correct conditions in these tags as soon as possible - we want to lock these tags on monday in order to be able to build a DBrelease containing these changes and the updated Geometry tags.
  • experts, Vahko, Paul Laycock, need to be filled by system cond DB experts
 

New filter volume

  • The ID asked us to change from using TRTBarrel to ID volume (to increase TRT endcap tracks)
  • Problem is ID volume is much less efficient (only ~30% of events have an offline track)

Revision 102009-03-05 - ElseLytken

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 101 to 101
 
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
Changed:
<
<
  • i think this works but it needs to be checked.
>
>
  • i think this works but it needs to be checked. Remember to set STAGE_SVCCLASS=atlasgroupdisk to use this example
 

Test of simulation step in Production

  • Borut has kindly run 3 tasks (to give ~50k events each) of just the simulation step in production
Line: 134 to 134
 

Known problems

  • Cant set runnumber in simulation (always 1)
    • Can set the runnumber inside the transform, but needs to be done automatically (normal simulation gets the runnumber from the hits file - but we dont have that step)
Changed:
<
<
    • Suggested to use a combination of the date/time and random seed (using python hash(time)+random seed, but not sure about requirements of runnumber (how many digitis can it be, does it need to be padded, etc...
>
>
    • Suggested to use a combination of the date/time and random seed (using python hash(time)+random seed, but not sure about requirements of runnumber (how many digitis can it be, does it need to be padded, etc... First tests show this is dangerous, simulation runs but not digitization.
 
  • Should switch to use new condDBtag specially for cosmic simulation: OFLCOND-SIMC-00-00-00
    • Systems need to move any cosmic sim specific (sim, dig and reco) conditions into this tag
  • Cant run trigger in reco - i suspect there are many problems for this. the first i get to is:

Revision 82009-03-04 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 159 to 159
 
    • Testing with UseTOF=False in digitization
  • Some problems with calibration/alignment???
Added:
>
>

Current developments

New Geometry tags

  • Pixel need a new set of DetDescrVersions as their HV comes from the geometry DB (and is wrong in the old ones) so we will create
ATLAS-GEO-07-00-00, ATLAS-GEONSF-07-00-00, ATLAS-GEONF-07-00-00, ATLAS-GEONTF-07-00-00
  • which are exactly the same as the GEO-03/04 ones but with the pixel HV fixed (this is bug report 47235" target="_blank">http://savannah.cern.ch/bugs/?47235][47235]])
  • needed for Attillio, made by Vahko

New conditions DB tags

  • We will be creating new condDB tags for sim, dig, reco of simulated cosmics (in rel. 14.5.X). Paul will create these today and we will have 4 tags foor solenoid on/off and toroid on/off.
  • We need the systems to put the correct conditions in these tags as soon as possible (one they are created)
  • made by Paul Laycock, need to be filled by system cond DB experts

New filter volume

  • The ID asked us to change from using TRTBarrel to ID volume (to increase TRT endcap tracks)
  • Problem is ID volume is much less efficient (only ~30% of events have an offline track)
  • Else is looking at other options but im not sure there will be something useful.
  • Need to decide what to use soon....
  • driven by Christian

New pixel step size in pixel digitization

  • New tags from pixel
SiLorentzAngleSvc-00-00-07-01 
PixelDigitization-00-07-17-05
  • Needed for bug: 47684
  • Driven by Attillio

Muon digitization

MDTDigitization.UseTOF=False
  • Need to know soon, and if there are any associated changes for cosmic sim reco (if so what)
  • Driven by Niels

Extra functionality to get this working in production

  • Need to get the runnumber being set correctly by the simulation transform
  • Need to be able to specify the right condDB tag and DetDescrVersion correctly (either as input to transforms - or autoconfigured??)
  • Need to be able to merge together many simulation outputs into 1 digitization input in production
  • Need to come up with different statistics for types of jobs (for each filter volume)
  • Validation of all of the above (ouch)...

Release issues

  • Looks like we will run the simulation and digitization in 14.5.1.Y AtlasProduction (David Q proposed stopping 14.5.1.Y soon - we need to keep it open (but closed) for cosmic sim)
  • Then run reco in 14.5.2.Y AtlasProduction (but no tags into that until after the re-reprocessing release is fixed)
 -- ElseLytken - 23 Feb 2009
  • stats.ps: CPU performance for grid tests

Revision 72009-03-02 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 115 to 115
 dq2-get valid2.000700.Cosmic_test.simul.HITS.s507_tid040594
  • A few performance plots on CPU, number of events etc are attached to this twiki here
Added:
>
>

Test of digitization step in production

dq2-get valid2.000700.Cosmic_test.digit.RDO.s507_d155_tid042840
 

Current validation

  • I have run digitization and reconstruction as described above over 689 events from the production tests (i chose the TRTBarrel, ATLAS-GEO-03-00-00 sample)

Revision 62009-03-02 - ElseLytken

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 110 to 110
 
Changed:
<
<
  • They havent all fully completed yet but you can download the HITS files to play with by doing using dq2-get eg.
>
>
  • You can download the HITS files to play with by doing using dq2-get eg.
 
dq2-get valid2.000700.Cosmic_test.simul.HITS.s507_tid040594
Added:
>
>
  • A few performance plots on CPU, number of events etc are attached to this twiki here
 

Current validation

  • I have run digitization and reconstruction as described above over 689 events from the production tests (i chose the TRTBarrel, ATLAS-GEO-03-00-00 sample)
  • You can see the produced monitoring histograms here
Line: 147 to 149
 
  • Some problems with calibration/alignment???

-- ElseLytken - 23 Feb 2009 \ No newline at end of file

Added:
>
>
  • stats.ps: CPU performance for grid tests

META FILEATTACHMENT attachment="stats.ps" attr="" comment="CPU performance for grid tests" date="1235994836" name="stats.ps" path="stats.ps" size="241554" stream="stats.ps" user="Main.ElseLytken" version="1"

Revision 52009-02-26 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 120 to 120
 
  • You can see a couple of event displays here

Known problems

  • Cant set runnumber in simulation (always 1)
Added:
>
>
    • Can set the runnumber inside the transform, but needs to be done automatically (normal simulation gets the runnumber from the hits file - but we dont have that step)
    • Suggested to use a combination of the date/time and random seed (using python hash(time)+random seed, but not sure about requirements of runnumber (how many digitis can it be, does it need to be padded, etc...
  • Should switch to use new condDBtag specially for cosmic simulation: OFLCOND-SIMC-00-00-00
    • Systems need to move any cosmic sim specific (sim, dig and reco) conditions into this tag
 
  • Cant run trigger in reco - i suspect there are many problems for this. the first i get to is:
Shortened traceback (most recent user call last):
Line: 139 to 143
 Py:Athena INFO leaving with code 8: "an unknown exception occurred"
  • Muon timing wrong
Added:
>
>
    • Testing with UseTOF=False in digitization
 
  • Some problems with calibration/alignment???

-- ElseLytken - 23 Feb 2009 \ No newline at end of file

Revision 42009-02-24 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 102 to 102
 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.
Added:
>
>

Test of simulation step in Production

dq2-get valid2.000700.Cosmic_test.simul.HITS.s507_tid040594
 

Current validation

  • I have run digitization and reconstruction as described above over 689 events from the production tests (i chose the TRTBarrel, ATLAS-GEO-03-00-00 sample)
  • You can see the produced monitoring histograms here

Revision 32009-02-23 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 46 to 46
 
  • setup 14.5.1.3,AtlasProduction
  • Run transform like:
Changed:
<
<
>Reco_trf.py inputRDOFile=dig.root maxEvents=10 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 preExec="LArDigitKey='FREE'" --ignoreunknown
>
>
>Reco_trf.py inputRDOFile=dig.root maxEvents=10 preInclude=RecExCommon/RecoUsefulFlags.py,RecExCommission/CosmicSimulationRecoSetup.py,RecExCommission/RecExCommissionRepro.py,RecJobTransforms/UseOracle.py beamType=cosmics outputESDFile=myESD.pool.root HIST=myMergedMonitoring.root outputTAGComm=myTAGCOMM.root outputCBNT=myCommission.ntuple.root preExec="LArDigitKey='FREE'" --ignoreunknown
 
Line: 104 to 104
 
  • i think this works but it needs to be checked.

Current validation

  • I have run digitization and reconstruction as described above over 689 events from the production tests (i chose the TRTBarrel, ATLAS-GEO-03-00-00 sample)
Changed:
<
<
  • You can see the produced monitoring histograms here
>
>
  • You can see the produced monitoring histograms here
 
  • You can see a couple of event displays here
Deleted:
<
<
  • SCT tracks seem to be missing from the monitoring histograms although clearly they should be there from the EVDs and the CBNT
 

Known problems

  • Cant set runnumber in simulation (always 1)
  • Cant run trigger in reco - i suspect there are many problems for this. the first i get to is:

Revision 22009-02-23 - JamieBoyd

Line: 1 to 1
 
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

Line: 93 to 93
 TypeError: unbound method isInToolSvc() must be called with TrackInCaloTools instance as first argument (got nothing instead) Py:Athena INFO leaving with code 8: "an unknown exception occurred"
Changed:
<
<
  • Which seems like a bug to me. Have contacted experts to try to get this fixed...
>
>
  • This is submitted as bug 47271
  • A way round this is to not use BSall but to give an AODoutputfilename to the transform which means that art of the monitoring will be done in the ESD->AOD step and then the monitoring histograms merged
 

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
Line: 101 to 102
 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.
Changed:
<
<
>
>

Current validation

  • I have run digitization and reconstruction as described above over 689 events from the production tests (i chose the TRTBarrel, ATLAS-GEO-03-00-00 sample)
  • You can see the produced monitoring histograms here
  • You can see a couple of event displays here
  • SCT tracks seem to be missing from the monitoring histograms although clearly they should be there from the EVDs and the CBNT

Known problems

  • Cant set runnumber in simulation (always 1)
  • Cant run trigger in reco - i suspect there are many problems for this. the first i get to is:
Shortened traceback (most recent user call last):
  File "/afs/cern.ch/atlas/software/builds/AtlasCore/14.5.1/InstallArea/share/bin/athena.py", line 459, in <module>
    include( script )
  File "/afs/cern.ch/atlas/software/builds/AtlasProduction/14.5.1.3/InstallArea/jobOptions/RecJobTransforms/skeleton.RAWtoESD.py", line 137, in <module>
    else: include( "RecExCommon/RecExCommon_topOptions.py" )
  File "/afs/cern.ch/atlas/software/builds/AtlasProduction/14.5.1.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 46, in <module>
    treatException("DataQualitySteering_jobOptions.py: exception when setting up L1 Calo monitoring")
  File "/afs/cern.ch/atlas/software/builds/AtlasEvent/14.5.1/InstallArea/jobOptions/AthenaMonitoring/DataQualitySteering_jobOptions.py", line 44, in <module>
    include("TrigT1Monitoring/TrigT1Monitoring_forRecExCommission.py")
  File "/afs/cern.ch/atlas/software/builds/AtlasTrigger/14.5.1/InstallArea/jobOptions/TrigT1Monitoring/TrigT1Monitoring_forRecExCommission.py", line 7, in <module>
    TTjob += LVL1__TriggerTowerMaker( 'TriggerTowerMaker' )
TypeError: attempt to redefine type of "TriggerTowerMaker" (was: LVL1__TriggerTowerMaker, new: TriggerTowerMaker_TTL1_Rel13)
Py:Athena            INFO leaving with code 8: "an unknown exception occurred"
  • Muon timing wrong
  • Some problems with calibration/alignment???
  -- ElseLytken - 23 Feb 2009 \ No newline at end of file

Revision 12009-02-23 - ElseLytken

Line: 1 to 1
Added:
>
>
META TOPICPARENT name="CosmicSimulationSamplesRel14"

Cosmic Simulation in rel 14: How to

How to run simulation:

* 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

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 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 preExec="LArDigitKey='FREE'" --ignoreunknown
  • Can change outputs by changing transform arguments (ie. if you dont give a outputCBNT argument wont get a CBNT) see this wiki for more details on Reco_trf
  • 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')
  • Or the above can be added as a preExec - in this case the DQMonFlags are already imported so you can just add:
preExec="LArDigitKey='FREE',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...
  • We need the preExec="LArDigitKey='FREE'" part due to a bug in LAr monitoring which gives the error below (LAr experts are working on a fix for this....
  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"
  • Currently if i try to run BSall monitoring in this step i get:
  File "/afs/cern.ch/atlas/software/builds/AtlasEvent/14.5.1/InstallArea/jobOptions/AthenaMonitoring/DataQualitySteering_jobOptions.py", line 342, in <module>
    include("MuonCombinedDQA/MuonCombinedMonitoring_jobOptions.py")
  File "/afs/cern.ch/atlas/software/builds/AtlasAnalysis/14.5.1/InstallArea/jobOptions/MuonCombinedDQA/MuonCombinedMonitoring_jobOptions.py", line 28, in <module>
    include("MuonCombinedTrackMon/MuonCombinedTrackMon.py")
  File "/afs/cern.ch/atlas/software/builds/AtlasAnalysis/14.5.1/InstallArea/jobOptions/MuonCombinedTrackMon/MuonCombinedTrackMon.py", line 6, in <module>
    include("MuonSelectionTools/MuonConstructionTool.py")
  File "/afs/cern.ch/atlas/software/builds/AtlasAnalysis/14.5.1/InstallArea/jobOptions/MuonSelectionTools/MuonConstructionTool.py", line 44, in <module>
    include("MuonSelectionTools/MuonSelectionTool.py")
  File "/afs/cern.ch/atlas/software/builds/AtlasAnalysis/14.5.1/InstallArea/jobOptions/MuonSelectionTools/MuonSelectionTool.py", line 711, in <module>
    include("TrackIsolationTools/TrackIsolationTool_jobOptions.py")
  File "/afs/cern.ch/atlas/software/builds/AtlasReconstruction/14.5.1/InstallArea/jobOptions/TrackIsolationTools/TrackIsolationTool_jobOptions.py", line 64, in <module>
    TrackSelector               = TrackIsolationTrackSelectorTool)
  File "/build/atnight/localbuilds/nightlies/14.2.2X-VAL/AtlasReconstruction/rel_0/InstallArea/python/TrackIsolationTools/TrackIsolationToolsConf.py", line 27, in __init__
TypeError: unbound method isInToolSvc() must be called with TrackInCaloTools instance as first argument (got nothing instead)
Py:Athena            INFO leaving with code 8: "an unknown exception occurred"
  • Which seems like a bug to me. Have contacted experts to try to get this 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.

-- ElseLytken - 23 Feb 2009

 
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