G4MICE/G4Beamline interface

Kenny Walaron

Before March ’04 Collaboration Meeting

• G4MICE Initially modelled cooling channel

• G4Beamline Initially modelled Beamline (and also cooling channel)

• Was proposed that interface point would be Diffuser 2.

• Would enable clean, definitive break

March ’04 Changes

• TOF0 relocated to between Q4 and Q5• Makes interface point more hazy as

TOF0 must be incorporated into G4MICE• G4Beamline Quad code incorporated

into G4MICE by Tom and Yagmur• Pushed back interface to be somewhere

between B2 and Q4.

JAN04f Layout

Output from G4beamline

• Default output is a .hst histo file

• Can be read with Histoscope executable to produce nice pictures

• G4Beamline can also be made to produce a text output

G4Beamline Output cont.

• The G4beamline exe. takes a text file input where the positions and properties of the volumes are configured

• In this file “ascii detectors” can be set up along z. e.gblah blah…..asciifile det radius=400 length=1 color=1,1,1 file=ThatsWhatWeWant.txtPlace Det z=99999 Blah blah…..

G4Beamline Output cont.

• Format of output file isx y z Px Py Pz t PDGid Ev# TrkId Parent wt

mm MeV/c n/s

• Note that this is not yet in documentation, will be remedied in next release

Interface

• Most of previous datacards use default Muon beam type.

• The ascii output from G4Beamline can be used as a substitute for this.

• Entries in a datacard like below enable us to interface G4Beamline with G4MICEBeamType G4BeamLine InputBeamFileName ThatsWhatWeWant.txt

Right now

• Have shown that G4MICE does read G4Beamline output (# of events consistent)

• Trying to work out way to place a virtual recording plane just after interface. Needed to check that tracks are consistently being traversed across interface boundary. i.e. track has 3 mom and energy ??? before and after and that track number one is still track number one after boundary

Right Now

• Currently trying to look into placing a virtual plane using the VIRTUALParamsFile parameter

• This would in theory produce a file called VirtualRec.dat.

• The file is produced but has a problem with event number and there is also no associated data with the events

Next in line

• Would have been nice to show some plots of distributions before and after interface.

• Not quite yet, need to get a virtual plane close to G4MICE side of interface.

• Need to get virtual planes working. Just ran out of time to show such plots at this meeting