Linear Collider Forum



Home » Simulation » Full Simulations » Re-running a given simulations set (Re-running some simulations with modified geometry)
icon5.gif  Re-running a given simulations set [message #2296] Mon, 03 February 2014 06:09 Go to next message
protopop
Messages: 5
Registered: January 2014
Location: UK
Thank you for the reply to my first question!

I have a few other questions now. Say I have on disk locally

/ilc/prod/clic/350gev/hzee/ILD/DST/00001338/000/hzee_dst_133 8_*.slcio

and say I want to re-simulate these events with a slightly modified ILD geometry and be able to compare with the set on DIRAC.

Looks like the corresponding "gen" set is not in the catalogue ...

/ilc/prod/clic/350gev/hzee/gen/00001338/000

I was using /ilc/prod/clic/350gev/hzee/gen/00001335/000 for the moment, and running

Mokka -U -e ./particle.tbl 1335_93_mdf1.steer

where 1335_93_mdf1.steer contains this

/Mokka/init/lcioFilename hzee_sim1335_93_mdf1.slcio
/Mokka/init/lcioWriteMode WRITE_NEW
/Mokka/init/MokkaGearFileName Gear1335_93_mdf1.xml

/Mokka/init/user consult
/Mokka/init/dbPasswd consult

/Mokka/init/detectorModel CLIC_ILD_CDR500
/Mokka/init/lorentzTransformationAngle 10 mrad
/Mokka/init/physicsListName QGSP_BERT

/Mokka/init/rangeCut 0.1 mm # Geant4 production range cut [default is 0.005 mm]
/Mokka/init/TPCCut 10 MeV # Default is 10MeV

/Mokka/init/lcioDetailedTRKHitMode VXDCollection
/Mokka/init/lcioDetailedTRKHitMode FTDCollection
/Mokka/init/lcioDetailedTRKHitMode ETDCollection
/Mokka/init/lcioDetailedTRKHitMode SETCollection
/Mokka/init/lcioDetailedTRKHitMode SITCollection
/Mokka/init/lcioDetailedTRKHitMode TPCCollection

# To run with modified detector parameters use command line option '-U'
/Mokka/init/globalModelParameter Ecal_nlayers1 17
/Mokka/init/globalModelParameter Ecal_nlayers2 8
/Mokka/init/globalModelParameter Ecal_radiator_layers_set1_thickness 2.4
/Mokka/init/globalModelParameter Ecal_radiator_layers_set2_thickness 4.8
# (above numbers from http://agenda.linearcollider.org/getFile.py/access?contribId =50&sessionId=9&resId=0&materialId=slides&co nfId=5686)

# this simply sets hzee_gen_1335_93.stdhep as input
/Mokka/init/initialMacroFile 1335_93_mdf1.g4macro

/Mokka/init/printLevel 1
/Mokka/init/BatchMode true


So, does anyone know exactly ...

1) How can I find the corresponding generated (.stdhep) events ?
2) Where could I get the correct Mokka settings for this set ?
3) Is the particle.tbl file needed
Re: Re-running a given simulations set [message #2297 is a reply to message #2296] Mon, 03 February 2014 06:25 Go to previous messageGo to next message
sailer
Messages: 34
Registered: February 2009
protopop wrote on Mon, 03 February 2014 06:09

1) How can I find the corresponding generated (.stdhep) events ?
2) Where could I get the correct Mokka settings for this set ?
3) Is the particle.tbl file needed


1) use "ancestor" in the dirac filecatolog on the file, it will tell you were it comes from
FC:/ilc/prod/clic/350gev/hzee/ILD/DST/00001338/000>ancestor hzee_dst_1338_1.slcio -1
/ilc/prod/clic/350gev/hzee/ILD/DST/00001338/000/hzee_dst_1338_1.slcio
1       /ilc/prod/clic/350gev/hzee/ILD/SIM/00001337/000/hzee_sim_1337_126-1-500.slcio
2            /ilc/prod/clic/350gev/hzee/ILD/SIM/00001336/000/hzee_sim_1336_77.slcio
3                 /ilc/prod/clic/350gev/hzee/gen/00001335/000/hzee_gen_1335_73.stdhep

the 00001338 or similar is the production ID, the production ID is different for any production. A production (also known as transformation in the dirac speak) is a transformation of an input file into an output file.
So the first production is the generation of the input files (prodID 1335), then the simulation of the generator file (production 1336). and so on

Or use dirac-ilc-get-info -p 1338
which tells you the input files are from Prod 1337 and go down the chain.

2) If you run anajob on the slcio file, it will contain the mokka steering file at the top of the output.

3) If there are no B-mesons/baryons decays in the generator file it is probably not needed.
But it is probably better to provide it.
Re: Re-running a given simulations set [message #2298 is a reply to message #2297] Mon, 03 February 2014 07:38 Go to previous messageGo to next message
protopop
Messages: 5
Registered: January 2014
Location: UK
Thanks a lot for the reply. That clarifies a lot of issues.

In view of the included Mokka steering file (quoted in red in my previous post), any idea how to find its source and correct the (runtime) error below ?

-------- WWWW ------- G4Exception-START -------- WWWW -------
*** G4Exception : GeomNav1002
      issued by : G4Navigator::ComputeStep()
Track stuck or not moving.
          Track stuck, not moving for 10 steps
          in volume -Slab- at point (48.8322,-1897.95,772.416)
          direction: (0.352256,0.813033,-0.463566).
          Potential geometry or navigation problem !
          Trying pushing it of 1e-07 mm ...Potential overlap in geometry!

*** This is just a warning message. ***
-------- WWWW -------- G4Exception-END --------- WWWW -------


Even if it says it's jus a warning, and we're only talking about 10^{-7}mm, the "Potential overlap in geometry!" bit worries me.
Re: Re-running a given simulations set [message #2299 is a reply to message #2298] Mon, 03 February 2014 07:54 Go to previous message
sailer
Messages: 34
Registered: February 2009
To check for overlaps:
In the geant4 shell (or in a macro)
run
/geometry/test/recursive_test
Have a look at the built in documentation (run "help" in geant4 shell) for more information and other tests.
Note that false positives are possible.

You can also do a visual inspection of the geometry.
Or check the parameters printed for the different drivers (e.g., ECal position and size vs. hcal position)
Previous Topic:How to count events in .stdhep file
Next Topic:Recalibration needed after change in geometry ?
Goto Forum:
  

[ PDF ]

Current Time: Mon Oct 21 06:06:21 Pacific Daylight Time 2019
.:: Contact :: Home ::.

Powered by: FUDforum 3.0.1.
Copyright ©2001-2010 FUDforum Bulletin Board Software