LISTSERV mailing list manager LISTSERV 16.5

Help for HPS-SOFTWARE Archives


HPS-SOFTWARE Archives

HPS-SOFTWARE Archives


HPS-SOFTWARE@LISTSERV.SLAC.STANFORD.EDU


View:

Message:

[

First

|

Previous

|

Next

|

Last

]

By Topic:

[

First

|

Previous

|

Next

|

Last

]

By Author:

[

First

|

Previous

|

Next

|

Last

]

Font:

Proportional Font

LISTSERV Archives

LISTSERV Archives

HPS-SOFTWARE Home

HPS-SOFTWARE Home

HPS-SOFTWARE  October 2015

HPS-SOFTWARE October 2015

Subject:

Re: Track position at Ecal

From:

Sho Uemura <[log in to unmask]>

Reply-To:

Software for the Heavy Photon Search Experiment <[log in to unmask]>

Date:

Wed, 21 Oct 2015 08:47:58 -0700

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (171 lines)

Also, I meant to say this:

Since the TrackState array index is pretty arbitrary, but each TrackState 
has a location ID, people should not be hard-coding the array index in 
their code, and should use the location ID instead (loop over all track 
states, and pick the one with the correct location). It's less convenient 
but safer.

And I'm not picking on Holly's code here - this is something that a lot of 
recon code does. This is our fault.

If it helps, there is a utility method that does this for you: 
TrackUtils.getTrackStateAtECal(track).

On Wed, 21 Oct 2015, Sho Uemura wrote:

> Tim is talking about the track state location ID (state.getLocation()). Holly 
> is using the track state array index.
>
> What happened was that Pelle added an additional track state for GBL tracks, 
> which represents the track parameters at the last layer of the SVT (this 
> doesn't seem to be working quite right, which is an outstanding bug). This 
> shows up at index 1, which used to be where the ECal extrapolation went.
>
> For seed tracks:
> getTrackStates(0) = at IP (TrackState.AtIP), ref to origin
> getTrackStates(1) = at ECal (TrackState.AtCalorimeter), ref to ECal 
> intersection
>
> For GBL tracks:
> getTrackStates(0) = at IP (TrackState.AtIP), ref to origin
> getTrackStates(1) = at last layer (TrackState.AtLastHit), ref to origin
> getTrackStates(2) = at ECal (TrackState.AtCalorimeter), ref to ECal 
> intersection
>
> I don't know why Holly is seeing a nonzero ref point that's centimeters off 
> from the cluster position. Maybe we screwed that up, or maybe for GBL tracks 
> the ECal extrapolation is being done from the AtLastHit track state (which is 
> bogus), which should not have been turned on until it had been checked. I can 
> check if that's what's going on.
>
> Hope this clears things up. And hopefully I'm not adding any misinformation 
> to the mix here, there's enough of it going around.
>
> On Wed, 21 Oct 2015, Holly Vance wrote:
>
>> Just in case this was missed-
>> 
>> Ok-after checking this in the DST and when using the FSParticle collection,
>> the track position at the Ecal is still obtained as it was before and
>> works. If I directly iterate over the UnconstrainedMollerCandidate
>> collection, and get the tracks associated with a vertex, the track
>> positions at the ecal don't really make a lot of sense (as mentioned in my
>> previous e-mail). I'm not sure why this doesn't work in Pass3, but it did
>> work in Pass 2.
>> 
>> The getReferencePoint method is working, but I am having different results
>> in the UnconstrainedMollerCandidateCollection than I did with Pass2.
>> Additionally, this method still works for FSParticle collection.
>> 
>> On Wed, Oct 21, 2015 at 10:56 AM, Nelson, Timothy Knight <
>> [log in to unmask]> wrote:
>> 
>>> Hi Matt,
>>> 
>>> In LCIO, TrackState 1 is ?at IP?, so this definitely doesn?t seem like a
>>> good convention. Track state 4 is ?at calorimeter? but, in any case, the
>>> reference point is meant to be independent of the trajectory itself, and I
>>> think using to store a track position (simply by our own convention) is 
>>> not
>>> a good idea, since there is no way to guarantee this behavior (as is now
>>> found.)
>>> 
>>> Tim
>>> 
>>>> On Oct 21, 2015, at 7:36 AM, Graham, Mathew Thomas <
>>> [log in to unmask]> wrote:
>>>> 
>>>> 
>>>> I had put the track position at the ECal as the reference point for
>>> track state 1 (and adjusted the track parameters accordingly IIRC)?this 
>>> may
>>> have changed though, but not by me.
>>>> 
>>>>> Hi Holly,
>>>>> 
>>>>> I?m not an expert on finding position at the ECal, but the reference
>>> point for the track doesn?t have anything to do with the position of the
>>> track at any position along it?s path (it could be kilometers away from 
>>> the
>>> track, in principle), and was probably never really the right way even if
>>> it did seem to give sensible results.  The reference point is simply the
>>> zero of the coordinate system for the track parameters.  This is usually
>>> the origin of our global coordinates.
>>>>> 
>>>>> Can someone else chime in and provide the ?right? answer here?
>>>>> 
>>>>> Tim
>>>>> 
>>>>>> On Oct 21, 2015, at 6:20 AM, Holly Vance <[log in to unmask]> wrote:
>>>>>> 
>>>>>> Hello,
>>>>>> 
>>>>>> Can anyone confirm that this is still the correct method to get the
>>> track position at the Ecal from Pass 3?
>>>>>> track->getTrackStates()[1]->getReferencePoint()
>>>>>> 
>>>>>> This same code worked for Pass 2, but now I mostly get 0 for all
>>> values. Has anyone else confirmed this works? The few times I get 
>>> something
>>> other than 0, the distribution sits 6-10cm away from the matched cluster
>>> x-y positions. Z position still looks fine.
>>>>>> 
>>>>>> -Holly
>>>>>> 
>>>>>> 
>>>>>> Use REPLY-ALL to reply to list
>>>>>> 
>>>>>> To unsubscribe from the HPS-SOFTWARE list, click the following link:
>>>>>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1
>>>>>> 
>>>>> 
>>>>> 
>>>>> ########################################################################
>>>>> Use REPLY-ALL to reply to list
>>>>> 
>>>>> To unsubscribe from the HPS-SOFTWARE list, click the following link:
>>>>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1
>>>> 
>>> 
>>> 
>>> 
>>> --
>>> BEGIN-ANTISPAM-VOTING-LINKS
>>> ------------------------------------------------------
>>> 
>>> NOTE: This message was trained as non-spam.  If this is wrong,
>>> please correct the training as soon as possible.
>>> 
>>> Teach CanIt if this mail (ID 01PvOV0rk) is spam:
>>> Spam:
>>> https://www.spamtrap.odu.edu/canit/b.php?i=01PvOV0rk&m=13ee7639fef7&t=20151021&c=s
>>> Not spam:
>>> https://www.spamtrap.odu.edu/canit/b.php?i=01PvOV0rk&m=13ee7639fef7&t=20151021&c=n
>>> Forget vote:
>>> https://www.spamtrap.odu.edu/canit/b.php?i=01PvOV0rk&m=13ee7639fef7&t=20151021&c=f
>>> ------------------------------------------------------
>>> END-ANTISPAM-VOTING-LINKS
>>> 
>>> 
>> 
>> ########################################################################
>> Use REPLY-ALL to reply to list
>> 
>> To unsubscribe from the HPS-SOFTWARE list, click the following link:
>> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1
>> 
>
> ########################################################################
> Use REPLY-ALL to reply to list
>
> To unsubscribe from the HPS-SOFTWARE list, click the following link:
> https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1
>

########################################################################
Use REPLY-ALL to reply to list

To unsubscribe from the HPS-SOFTWARE list, click the following link:
https://listserv.slac.stanford.edu/cgi-bin/wa?SUBED1=HPS-SOFTWARE&A=1

Top of Message | Previous Page | Permalink

Advanced Options


Options

Log In

Log In

Get Password

Get Password


Search Archives

Search Archives


Subscribe or Unsubscribe

Subscribe or Unsubscribe


Archives

December 2023
November 2023
October 2023
September 2023
August 2023
July 2023
June 2023
May 2023
April 2023
March 2023
February 2023
January 2023
December 2022
November 2022
October 2022
September 2022
August 2022
June 2022
April 2022
March 2022
February 2022
January 2022
December 2021
November 2021
October 2021
September 2021
August 2021
July 2021
June 2021
May 2021
April 2021
March 2021
February 2021
January 2021
December 2020
November 2020
October 2020
September 2020
August 2020
July 2020
June 2020
May 2020
April 2020
March 2020
February 2020
January 2020
December 2019
November 2019
October 2019
September 2019
August 2019
July 2019
June 2019
May 2019
April 2019
March 2019
February 2019
January 2019
December 2018
November 2018
October 2018
September 2018
August 2018
July 2018
June 2018
May 2018
April 2018
March 2018
February 2018
January 2018
December 2017
November 2017
October 2017
September 2017
August 2017
July 2017
June 2017
May 2017
April 2017
March 2017
February 2017
January 2017
December 2016
November 2016
October 2016
September 2016
August 2016
July 2016
June 2016
May 2016
April 2016
March 2016
February 2016
January 2016
December 2015
November 2015
October 2015
September 2015
August 2015
July 2015
June 2015
May 2015
April 2015
March 2015
February 2015
January 2015
December 2014
November 2014
October 2014
September 2014
August 2014
July 2014
June 2014
May 2014
April 2014
March 2014
February 2014
January 2014
December 2013
November 2013
October 2013
September 2013
August 2013
July 2013
June 2013
May 2013
April 2013
March 2013
February 2013
January 2013
December 2012
November 2012
October 2012
September 2012
August 2012
July 2012
June 2012
May 2012
April 2012
March 2012
February 2012
January 2012
December 2011
November 2011
October 2011
September 2011
August 2011
July 2011
June 2011
May 2011
April 2011
March 2011

ATOM RSS1 RSS2



LISTSERV.SLAC.STANFORD.EDU

Secured by F-Secure Anti-Virus CataList Email List Search Powered by the LISTSERV Email List Manager

Privacy Notice, Security Notice and Terms of Use