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:

Monospaced Font

LISTSERV Archives

LISTSERV Archives

HPS-SOFTWARE Home

HPS-SOFTWARE Home

HPS-SOFTWARE  February 2017

HPS-SOFTWARE February 2017

Subject:

Re: Cluster particle id

From:

"McCormick, Jeremy I." <[log in to unmask]>

Reply-To:

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

Date:

Tue, 7 Feb 2017 00:05:10 +0000

Content-Type:

text/plain

Parts/Attachments:

Parts/Attachments

text/plain (1 lines)

This was my initial thought, but the problem with actually persisting this is that the C++ will read this single value as the length of a list of items, because that's how the LCIO format is defined. And it will then crash. So we can't do it that way...

The proper thing to do would be implement the PID + likelihood list properly using an SIO class. Is this something we need? I don't think it would be that difficult.

It could also be done using an LCRelation and LCObject collection but a proper implementation of the format is obviously preferable.

-----Original Message-----
From: [log in to unmask] [mailto:[log in to unmask]] On Behalf Of Holly Vance
Sent: Monday, February 06, 2017 2:44 PM
To: McCormick, Jeremy I.
Cc: hps-software
Subject: Re: Cluster particle id

We could just set the first item in the list to be the PID we use for the corrections. What does that require for us to change in the code?

On Fri, Feb 3, 2017 at 5:32 PM, McCormick, Jeremy I. <[log in to unmask]> wrote:


Okay, so looking further at the LCIO API, it seems that each Cluster is supposed to have a list of PID values sorted by their likelihood and that this was never implemented in lcsim. Should you instead be working from information in ReconstructedParticle? This is not something that can be fixed just by just adding a single particle ID to the output because I guess zero here is actually the length of the PID list. Probably it needs to stay that way to be compatible with the C++ API.


On Feb 3, 2017, at 1:02 PM, McCormick, Jeremy I. <[log in to unmask]> wrote:

The particle ID is available at runtime via BaseCluster but the persistency is broken because the PID is hard-coded to zero (no idea why).

We should be able to fix this in lcsim, and then the information should be available. You shouldn’t need to cast to BaseCluster — the information will be available via the Cluster.getParticleId() method (once it is actually written out).


On Feb 3, 2017, at 12:54 PM, Holly Vance <[log in to unmask]> wrote:

In our reconstruction code, ReconParticleDriver.java, we set the pid of the cluster in track cluster matching. This definitely happens because this then goes to set energy and position corrections to the cluster in ClusterEnergyCorrection.java and ClusterPositionCorrection.java. Both of these correction drivers call "cluster.getParticleId()" to determine what particle type is associate with this cluster.

I'm guessing that this is not getting written out to the cluster collections somehow, although it should be written out to the corrected collection. The reason this is good information to have is to know which corrections were used for a cluster.

I've been trying to read the particle id of clusters when running the tuple driver, but it is not working since they are all set to 0. Maybe casting it wasn't the correct thing to do, but then I want to know why this is not being written out to the corrected cluster collection.

On Fri, Feb 3, 2017 at 3:08 PM, McCormick, Jeremy I. <[log in to unmask]> wrote:


Hi,

From what I can tell the particle ID on Cluster was never implemented. It is always hard-coded to ‘0’ in the output code, but this could be easily changed to write out the value from getParticleId() and still be backward compatible (there is a space for an int there in the Cluster output that we are already using/reserving). It looks like maybe the LCIO standard indicates there could be multiple particle IDs, as there is some commented out code in the SIO class for writing a list of PID values.

The SIOCluster class seems to implement Cluster directly, so it isn’t a BaseCluster (for some reason it was done differently than the other SIO classes that extend a base class). That’s why the cast fails. I’m not sure what you are trying to do, but you can use the copy constructor of BaseCluster to create an object with the same information. If you’re trying to modify the collection in place though, this probably won’t do what you want. You would probably need to create a new collection to contain the copied Cluster objects.


—Jeremy


On Feb 2, 2017, at 6:19 PM, Holly Vance <[log in to unmask]> wrote:

Hi Jeremy,

I'm trying to write out from recon files what the pid is of the cluster. During recon, we assign this as a BaseCluster and setParticleId(). Additionally, when applying cluster corrections to energy and position, we use cluster.getParticleId(), and this returns something like +/-11, 22.

However, when I look at a fully reconstructed file and try to do cluster.getParticleId(), it is always set to 0.

I tried casting this to BaseCluster, but it doesn't work. I've tried this on both collections "EcalClusters" and "EcalClustersCorr".


if (event.hasCollection(Cluster.class,"EcalClustersCorr")){

List<Cluster> ecalClusters = event.get(Cluster.class,"EcalClustersCorr");

Cluster c1 = ecalClusters.get(0));




System.out.println("Cluster pid:\t"+c1.getParticleId());




If I try to do:

((BaseCluster)c1).getParticleId()


then I get

org.lcsim.job.EventMarkerDriver process :: Event 10085820 with sequence 0

java.lang.ClassCastException: org.lcsim.lcio.SIOCluster cannot be cast to org.lcsim.event.base.BaseCluster

<https://ssl.gstatic.com/ui/v1/icons/mail/images/cleardot.gif>

Is there a reason this is not persisted?

-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

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