Message: Re: Tracking in a UnionSolid Not Logged In (login)
 Next-in-Thread Next-in-Thread
 Next-in-Forum Next-in-Forum

Question Re: Tracking in a UnionSolid 

Forum: Event and Track Management
Re: Question Tracking in a UnionSolid (Rafayel Paremuzyan)
Re: Feedback Re: Tracking in a UnionSolid (Gumplinger Peter)
Date: 08 Jan, 2014
From: Rafayel Paremuzyan <Rafayel Paremuzyan>

Dear Peter,

Thank you for you suggestions and the link.

Yes with different angles of view, and other tests, geometry looks ok to me.

I used your suggestions, and in PrimaryGeneratorAction, where I generate event vertexes over all the target length (includes cylinder and end-cap)
the method "touchable->GetVolume()->GetLogicalVolume()->GetName()" always gives the same "LH2_target_log", so seems it is one logical volume.

Then I implemented this method in the stepping action. At each step of main tarck (atrack->GetTrackID() == 1) 
I took position of PrestepPoint, and in the same way determine the Name of LogicalVolume.

Here I already observe different results.

When I generate events only in the end-cap part, then
It shows always single "LH2_target_log" immediately followed by different logical volumes, which is indication that this track indeed originated
in the target volume, but however doesn't interact with the target itself. I pasted small fraction from output at the and of the message.

Then with another run, when events were generated in the cylindrical part of the target, It always shows at least 
two consequent "LH2_target_log", which is indication that track has at least two points in the target volume.
I added a small part from this output also at the and of the message.

These facts repeat the same conclusion from previous post, that when particle is produced in cylinder, it interacts within target, 
but when it produced in end-cap part, it doesn't.

Now with these results of test, do you think that it is geometry related problem or tracking?

Rafo


===================Events were generated in the end-cap part of the target================
The volumen name is LH2_target_log
The volumen name is kapton_window_log
The volumen name is kapton_window_log
The volumen name is air_window_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is LH2_target_log
The volumen name is kapton_window_log
The volumen name is kapton_window_log
The volumen name is air_window_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is LH2_target_log
The volumen name is Vac_scat_chamber
The volumen name is Al_scat_chamber
The volumen name is Al_scat_chamber
The volumen name is Al_scat_chamber
The volumen name is Al_scat_chamber
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log




===================Events were generated in the cylindrical part of the target================
The volumen name is LH2_target_log
The volumen name is LH2_target_log
The volumen name is LH2_target_log
The volumen name is kapton_window_log
The volumen name is kapton_window_log
The volumen name is air_window_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is LH2_target_log
The volumen name is LH2_target_log
The volumen name is kapton_window_log
The volumen name is kapton_window_log
The volumen name is air_window_log
The volumen name is HRS_window_log
The volumen name is HRS_window_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is LH2_target_log
The volumen name is LH2_target_log
The volumen name is kapton_window_log
The volumen name is kapton_window_log
The volumen name is air_window_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log
The volumen name is LH2_target_log
The volumen name is LH2_target_log
The volumen name is kapton_window_log
The volumen name is kapton_window_log
The volumen name is air_window_log
The volumen name is HRS_window_log
The volumen name is HRS_window_log
The volumen name is world_log
The volumen name is world_log
The volumen name is world_log

Inline Depth:
 1 1
 All All
Outline Depth:
 1 1
 2 2
 All All
Add message: (add)

1 Feedback: Re: Tracking in a UnionSolid   (Gumplinger Peter - 08 Jan, 2014)
(_ Feedback: Re: Tracking in a UnionSolid   (Rafayel Paremuzyan - 09 Jan, 2014)
(_ Feedback: Re: Tracking in a UnionSolid   (Gumplinger Peter - 09 Jan, 2014)
(_ Feedback: Re: Tracking in a UnionSolid   (Rafayel Paremuzyan - 09 Jan, 2014)
(_ Disagree: Re: Tracking in a UnionSolid   (Gumplinger Peter - 10 Jan, 2014)
(_ Feedback: Re: Tracking in a UnionSolid   (Rafayel Paremuzyan - 11 Jan, 2014)
(_ Ok: Re: Tracking in a UnionSolid   (Rafayel Paremuzyan - 16 Jan, 2014)
(_ Disagree: Re: Tracking in a UnionSolid   (Gumplinger Peter - 16 Jan, 2014)
(_ Agree: Re: Tracking in a UnionSolid   (Gumplinger Peter - 16 Jan, 2014)
 Add Message Add Message
to: "Re: Tracking in a UnionSolid"

 Subscribe Subscribe

This site runs SLAC HyperNews version 1.11-slac-98, derived from the original HyperNews


[ Geant 4 Home | Geant 4 HyperNews | Search | Request New Forum | Feedback ]