Hello Norman,
You can get the row (iy) and column (ix) with the method
CalorimeterHit.getIdentifierFieldValue("ix") or
CalorimeterHit.getIdentifierFieldValue("iy"). This returns an integer
between (if I remember correctly) -23 and 23 for ix and -5 and 5 for it.
Note that iy = 0 is the beam gap and shouldn't ever occur, and that ix = 0
does not actually exist (so ix = 1 is adjacent to ix = -1).
For edge crystal identification, TriggerModule.inFiducialRegion(Cluster)
should do what you want. (It returns true if a cluster is in the fiducial
region, and false if it is an edge cluster.) If you are specifically
working with hits, you can just copy the logic from the code. It should be
pretty simple, since it ultimately checks the seed hit of the cluster to
make the decision.
Let me know if this helps,
Kyle
On Wed, Nov 29, 2017 at 4:17 PM, Graf, Norman A. <[log in to unmask]>
wrote:
> Hello All,
>
>
> I normally use the calorimeter CellID to identify calorimeter crystals,
> but I would like to know if there is a standard calorimeter cell indexing
> scheme that identifies individual crystals by their geometrical location,
> say, row and column? Is there a method that allows one to quickly tell that
> a crystal is on the edge (including the cutout region)? I.e. is there a
> row-column convention that locates a crystal? If so, is there a convenience
> method anywhere in hps-java that can return that convention given the
> CellID? Or the inverse? viz. given the long CellID, it returns row and
> column for a crystal?
>
>
> Thanks,
>
> Norman
>
>
>
> ------------------------------
>
> 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
