| mvd classes [message #4584] |
Thu, 28 June 2007 12:49  |
asanchez
Messages: 350
Registered: March 2006
|
first-grade participant |
From: *gsi.de
|
|
Dear all, I will like to use
the MVD classes as example to implement
the silicon detector in hyp directory.
Is it OK for you?
Are there any remark I should follow?
thanks a lot
Alicia S.
|
|
|
|
|
|
| Re: mvd classes [message #4586 is a reply to message #4584] |
Thu, 28 June 2007 19:03  |
Ralf Kliemt
Messages: 507
Registered: May 2007
Location: GSI, Darmstadt
|
first-grade participant |
From: 141.30.85*
|
|
Hi Alicia,
We are at a point, where the Pixel digitization is more or less done. The structure will not change very much.
As I remember you have strip sensors. I decided to write a separated Strip part for the Mvd, because there will be possibly non-orthogonal strip sensors (some other skewing angle). This is ongoing now.
If you like, I could send something in the svn (which compiles at least). If you want to learn something I'd suggest to have a look into the MvdHybridHitProducer, thats the pixel digitization.
Then a technical question rises to me: Do you want to implement our Classes from the mvd directory, or do you waqnt to copy a working snapshot and tune it to your needes?
Ciao, Ralf.
PS: I think Tobias is from now on about 4 weeks vacant.
[Updated on: Thu, 28 June 2007 19:05] Report message to a moderator |
|
|
|
|
|
|
|
| Re: mvd classes [message #4590 is a reply to message #4587] |
Fri, 29 June 2007 11:06 |
Ralf Kliemt
Messages: 507
Registered: May 2007
Location: GSI, Darmstadt
|
first-grade participant |
From: 141.30.85*
|
|
| Quote: |
In the Hybrid hitProducer when you ask for GetlocalHitPoint transformation , how will be the coordinates system of
the silicon sensor defined? Is the same as the global frame?
|
GetLocalHitPoints(point, posInL, posOutL);
Takes the MvdPoint point (global frame) and converts the in and out points to the local sensor frame (written to posInL and posOutL).
| Quote: |
in The CalcGlobalPoint(..) method,
what is thedifference between the col and colB?
are they both the variable for the clumn number?
|
The CalcGlobalPoint Methyod is a MC-Clustering. It will go outside the Digitization. As far as I know this should not be called in the Exec Of the HybridHitProducer. The col is the column number, which becomes a charge-weighted mean for this cluster. The colB is the non-weighted mean.
| Quote: |
why do you do col += 0.5, what is the meaning of this 0.5?
|
I think Tobias made this, because the column numbers are integers of the pixel borders. The output value is just shifted into the middle of the pixel.
I hope this helps.
Regards, Ralf.
[Updated on: Fri, 29 June 2007 11:07] Report message to a moderator |
|
|
|
|
|
|
|
| Re: mvd classes [message #4593 is a reply to message #4590] |
Fri, 29 June 2007 11:25 |
asanchez
Messages: 350
Registered: March 2006
|
first-grade participant |
From: *gsi.de
|
|
[quote title=Ralf Kliemt wrote on Fri, 29 June 2007 11:06]| Quote: |
In the Hybrid hitProducer when you ask for GetlocalHitPoint transformation , how will be the coordinates system of
the silicon sensor defined? Is the same as the global frame?
|
GetLocalHitPoints(point, posInL, posOutL);
Takes the MvdPoint point (global frame) and converts the in and out points to the local sensor frame (written to posInL and posOutL).
Yes that i have already understood, maybe my question was not so clear, I mean
In the global frame my layers (bos xyz)
are defined in the x-z plane(horizontal), with the strips along the x-axis or along the z-axis,
So In the local frame, is this definition kept, I mean is the x-z plane in the global frame
the same as in the local frame?
best regards
alicia s.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
GSI Forum
Search
Help
Members
Login
Home
