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  December 2014

HPS-SOFTWARE December 2014

Subject:

Re: shared hits

From:

Sho Uemura <[log in to unmask]>

Reply-To:

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

Date:

Wed, 17 Dec 2014 14:47:21 -0800

Content-Type:

TEXT/PLAIN

Parts/Attachments:

Parts/Attachments

TEXT/PLAIN (81 lines)

Weighted LCRelations (cluster->hit, weight equal to the sharing fraction) 
seem natural. You can decide whether shared hits show up in the hit list 
for the cluster; I think yes.

The cluster energy and position saved to LCIO is whatever your cluster 
class reports it to be, and are not recalculated after the cluster is read 
back out of LCIO, so those will not be affected by the details of how you 
represent things in LCIO.

On Wed, 17 Dec 2014, McCormick, Jeremy I. wrote:

> The rejected hit list should already be accessible in a separate hits collection.  You added this to your IC clustering Driver and I've ported this to the new ecal.cluster package as well.  So I think that problem is solved.
>
> For the shared hits, internally, you will need to keep track of which hits are shared for your energy calculation, but you can't directly store two separate lists of hits within a cluster.  It has only one list of hits.  Later on in analysis you could tell that a hit is shared, because it will be present in more than one cluster.  So if all you want to be able to do is tell if a hit is shared, simply add it to more than one cluster.  Then take the sharing into account within your energy calculation somehow.  With this approach though, you will lose the low level information about how you split up that hit's energy between multiple clusters.
>
> If you actually need to keep track of and persist to LCIO the individual shared energy contributions per hit, in other words breaking up the hits themselves into their contributions you've calculated per cluster, then I think the best approach is probably creating new CalorimeterHit objects with these individual energies, in a new LCIO hit collection which you would write to the event.  Then the hit which has the partial energy in it would only be added to that cluster's hit list, and you could tell later which hits are shared by using the ID.  With this approach, you would have multiple hits per crystal for those hits which are shared.
>
> Hope that makes sense...
>
> -----Original Message-----
> From: Holly Vance [mailto:[log in to unmask]]
> Sent: Wednesday, December 17, 2014 2:01 PM
> To: McCormick, Jeremy I.
> Cc: Graf, Norman A.
> Subject: Re: shared hits
>
> Hi Jeremy,
>
> We absolutely need to keep this information. It should be accessible just as the rejected hit list should also be accessible. I am not sure the simplest way to do this.
>
> -Holly
>
> On Wed, Dec 17, 2014 at 4:50 PM, McCormick, Jeremy I. <[log in to unmask]> wrote:
>
> 	Hi,
>
> 	Holly is trying to write clustering code that "shares" hits between different clusters.  Can you provide some guidance on this?  I was not sure of the best way to do it.
>
> 	Right now there is code in the Cluster extension class HPSEcalClusterIC which has a list of shared hits, but of course it isn't persisted to LCIO.  Because shared hits are not part of the LCIO API.
>
> 	I thought that if this information needs to be recoverable later, there should be a relation collection that associates the cluster with its shared hits, but I'm not sure.
>
> 	Do we really need this list of hits when reading back from an LCIO file?  Or is it okay to take this into account in the energy calculation and hide it from an analyst?
>
> 	--Jeremy
>
>
> 	--
> 	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 03NsJPaa0) is spam:
>
> 	Spam:        https://www.spamtrap.odu.edu/canit/b.php?i=03NsJPaa0&m=79da0dd8b8d7&t=20141217&c=s
>
> 	Not spam:    https://www.spamtrap.odu.edu/canit/b.php?i=03NsJPaa0&m=79da0dd8b8d7&t=20141217&c=n
>
> 	Forget vote: https://www.spamtrap.odu.edu/canit/b.php?i=03NsJPaa0&m=79da0dd8b8d7&t=20141217&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

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

June 2024
May 2024
April 2024
March 2024
February 2024
January 2024
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