Home » PANDA » PandaRoot » General » Beam profile or interaction point
Beam profile or interaction point [message #8737] |
Tue, 02 June 2009 14:47 |
donghee
Messages: 385 Registered: January 2009 Location: Germnay
|
first-grade participant |
From: *kph.uni-mainz.de
|
|
Dear panda MC users,
I would like to study the effect of different beam profile or certain interaction point.
I think that there is no way to study such kind of feature in the box generator.
Does anyone have some experience of implementation for beam profile or different interaction point in the generator level.
Then could you give me some comment what I have to care and where do I can find good reference in pandaroot framework.
Thank you very much
|
|
|
Re: Beam profile or interaction point [message #8743 is a reply to message #8737] |
Tue, 02 June 2009 15:43 |
Aida Galoyan
Messages: 79 Registered: May 2007 Location: Dubna
|
continuous participant |
From: *jinr.ru
|
|
Hi,
in the root-file produced after work of generator DPMGen
we have for coordinate x,y,z of event vertex: Particles.fVx, Particles.fVy, Particles.fVz.
They are equal 0.
To study of the effect of different beam profile, you have to
smear the Particles.fVx, Particles.fVy, Particles.fVz,
generate them by yourself.
If beam is directed along axis Z, Particles.fVx and Particles.fVy must be sampled according to proposed beam profile. Particles.fVz must be sumpled according to assumed thickness of target.
In generator PndJRGen, smearing of vertex is doing in the macro-files. For example ( in macros PndPi0PhiPhi.C),
>>>
// mean location of the target
//Vertex.SetXYZT(0,0,0,0); // zero by default
/* smearing of the primary vertex (Gauss with the above mean, and this sigma) */
/* TVector3 VtxRes(.1,.1,.2); // what target smearing do you want??? */
TVector3 VtxRes(0.0,0.0,0.0);
TParticle BeamTarget(999,1,0,0,0,0,s,Vertex);
PndReaction reaction(BeamTarget, VtxRes, "Gen_Pi02Phi.root" );
>>>
Aida
|
|
|
|
Re: Beam profile or interaction point [message #8746 is a reply to message #8743] |
Tue, 02 June 2009 16:14 |
donghee
Messages: 385 Registered: January 2009 Location: Germnay
|
first-grade participant |
From: *kph.uni-mainz.de
|
|
Thank you for your helpful answer.
The script looks quite useful in any case.
Actually, my output file is saved with primary vertex position (0,0,0) in the ascii file.
I call this file in the macro level during the simulation run.
There are two choice.
I can make the smearing in the fortran code of generator, this is not convenient,
or I can do it in the panda macro level.
I prefer the latter.
To do that, I have to keep momentum information from ascii file and just put smearing vertex position as you recommended.
Quote: |
// mean location of the target
Vertex.SetXYZT(0,0,0,0); // zero by default
// smearing of the primary vertex (Gauss with the above mean, and this sigma)
TVector3 VtxRes(.1,.1,.2); // what target smearing do you want???
TParticle BeamTarget(999,1,0,0,0,0,s,Vertex);
PndReaction reaction( BeamTarget, VtxRes, "PhiPhi.root" );
|
Quote: |
FairPrimaryGenerator* primGen = new FairPrimaryGenerator();
fRun->SetGenerator(primGen);
PndPythiaGenerator* pygen=new PndPythiaGenerator(inFile.Data());
primGen->AddGenerator(pygen);
fRun->SetStoreTraj(kTRUE);
|
I think that I have to combine some function of PndReaction with PndPythiaGenerator.
I'm not clear what do I have to as a next step?
Could you give me some hint?
Thank you! Aida
Best regards,
Donghee
[Updated on: Tue, 02 June 2009 16:32] Report message to a moderator
|
|
|
Re: Beam profile or interaction point [message #8747 is a reply to message #8746] |
Tue, 02 June 2009 17:06 |
Aida Galoyan
Messages: 79 Registered: May 2007 Location: Dubna
|
continuous participant |
From: *jinr.ru
|
|
Hi again,
For Phytia just now, I look through the file /pgenerators/PndPythiaGenerator.cxx.
There is line
>
primGen->AddTrack(pdgID, fPx, fPy, fPz, fVx, fVy, fVz);
>
It seems to me, before this line, you can insert your smearing of fVx, fVy, fVz.
Aida
|
|
|
|
Goto Forum:
Current Time: Sat Dec 21 17:14:23 CET 2024
Total time taken to generate the page: 0.00684 seconds
|