sphenix-hcal-l AT lists.bnl.gov
Subject: sPHENIX HCal discussion
List archive
Re: [Sphenix-hcal-l] HCal channel numbering/mapping
- From: Stefan Bathe <stefan.bathe AT baruch.cuny.edu>
- To: Chris Pinkenburg <pinkenburg AT bnl.gov>
- Cc: sphenix-hcal-l AT lists.bnl.gov
- Subject: Re: [Sphenix-hcal-l] HCal channel numbering/mapping
- Date: Fri, 7 Jan 2022 15:39:13 -0500
Hi Eric, Chris, All,
Thanks for the feedback.
OK, looks like we should go with a tower ID based on the digitizer channels
(blocks of 0-63 channels overarching four blocks of 16 channels (sector
thirds of four different sectors), which we map into an integer ID that
increments in both eta and phi. The (eta, phi) ID can then easily be
translated into actual eta and phi. How the tower ID blocks are ordered will
eventually be determined by how the Meritec cables will be plugged in, which
isn’t decided yet, it sounds like.
Regards,
Stefan
-
---------------------------------------------------------------------------------
Stefan Bathe
Professor of Physics
Baruch College, CUNY
and RIKEN Visiting Scientist
Baruch: BNL:
17 Lexington Ave Bldg. 510
office 940 office 2-229
phone 646-660-6272 phone 631-344-8490
----------------------------------------------------------------------------------
> On Jan 5, 2022, at 08:39, pinkenburg via sPHENIX-HCal-l
> <sphenix-hcal-l AT lists.bnl.gov> wrote:
>
> Hi Stefan,
>
> I looked at the presentations and they are a bit opaque to me but I think I
> get the general idea. I would make the software a secondary thought - there
> will always be some mapping to translate a channel to row/column, even if
> it is some one to one. In terms of how to set up the channel numbers I
> would concentrate more on monitoring/debugging needs when using raw data.
> If e.g. you run some packet ddump and the channel number tells you directly
> where some given tower is located rather than going through some geometry
> translation, there is value in that - or if it is easier to make a
> connection between slow control and a given tower.
>
> Not sure if this helps - whatever makes running the hcal easier and more
> bullet proof should be done. Software can always be recompiled if you got
> something wrong even after you are done taking data.
>
> Chris
>
>
> On 1/4/2022 9:10 PM, Stefan Bathe via sPHENIX-HCal-l wrote:
>> Dear All, (specifically Xiaochun, Eric, Chris)
>>
>> Xiaochun asked in today’s HCal Meeting about the HCal channel mapping for
>> his Geant simulation. As far as I can tell, this was last discussed in
>> the 8/27/19 HCal Meeting:
>>
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__indico.bnl.gov_event_6688_&d=DwIGaQ&c=dTXc8cCP8suVpClwB1HRHQACHN4UFMgL7MtSjCbKyts&r=VpzLtnjcGB03vfJuG_p478bcDf7zDOFn2OeUM-jusdY&m=HOtxraNOUgIc4-76m05ZxyZtpgYw4n-p8fGrdxsrtWg&s=9RxZH7QPTVmIlD3px64gHbUwypaf0HdiI0LEJhwZ8aQ&e=
>>
>> where both Eric and I gave presentations on our ideas of how to map
>> hardware channels to digitizer channels. I think we basically agreed. In
>> the end, though, I think, it might be up to the software group (Chris?) to
>> decide which numbers to assign to the channels. I guess the two options
>> would be to either adopt the digitizer channel numbering (no additional
>> map needed, but geometrically more complex) or to have numbers simply
>> increment in z and phi (geometrically simple, but additional map needed).
>> The other open question is where to start counting. Naturally one would
>> like to start counting at phi = 0 (and at the South end, so along the z
>> axis). But the sector at phi = 0 (and at phi = 180 degrees) have their
>> outer radius combs vertical. Therefore phi = 0 is in the center of a
>> sector, not at the edge. This would introduce an offset with respect to
>> the digitizer channel number, which is ugly. The answer to this question
>> might also depend on which sectors get plugged into which digitizer
>> boards/crates, which Eric and Steve would know. (I’m saying this because
>> it might make sense to start counting at channel 0 of a digitizer board.)
>>
>> Regards,
>> Stefan
>> -
>> ---------------------------------------------------------------------------------
>> Stefan Bathe
>> Professor of Physics
>> Baruch College, CUNY
>> and RIKEN Visiting Scientist
>>
>> Baruch: BNL:
>> 17 Lexington Ave Bldg. 510
>> office 940 office 2-229
>> phone 646-660-6272 phone 631-344-8490
>> ----------------------------------------------------------------------------------
>>
>>
>>
>> _______________________________________________
>> sPHENIX-HCal-l mailing list
>> sPHENIX-HCal-l AT lists.bnl.gov
>> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.bnl.gov_mailman_listinfo_sphenix-2Dhcal-2Dl&d=DwIGaQ&c=dTXc8cCP8suVpClwB1HRHQACHN4UFMgL7MtSjCbKyts&r=VpzLtnjcGB03vfJuG_p478bcDf7zDOFn2OeUM-jusdY&m=HOtxraNOUgIc4-76m05ZxyZtpgYw4n-p8fGrdxsrtWg&s=BKDeCcnB7JXDQcAC2Q7d74DAsFXwQssxireUDZiijuc&e=
>>
>
> --
> *************************************************************
>
> Christopher H. Pinkenburg ; pinkenburg AT bnl.gov
> ;
> https://urldefense.proofpoint.com/v2/url?u=http-3A__www.phenix.bnl.gov_-7Epinkenbu&d=DwIGaQ&c=dTXc8cCP8suVpClwB1HRHQACHN4UFMgL7MtSjCbKyts&r=VpzLtnjcGB03vfJuG_p478bcDf7zDOFn2OeUM-jusdY&m=HOtxraNOUgIc4-76m05ZxyZtpgYw4n-p8fGrdxsrtWg&s=nu-FeBKygAFlKapywWhtOzbpikwq6f-KC2G7V7CRjIw&e=
>
> Brookhaven National Laboratory ; phone: (631) 344-5692
> Physics Department Bldg 510 C ; fax: (631) 344-3253
> Upton, NY 11973-5000
>
> *************************************************************
>
> _______________________________________________
> sPHENIX-HCal-l mailing list
> sPHENIX-HCal-l AT lists.bnl.gov
> https://urldefense.proofpoint.com/v2/url?u=https-3A__lists.bnl.gov_mailman_listinfo_sphenix-2Dhcal-2Dl&d=DwIGaQ&c=dTXc8cCP8suVpClwB1HRHQACHN4UFMgL7MtSjCbKyts&r=VpzLtnjcGB03vfJuG_p478bcDf7zDOFn2OeUM-jusdY&m=HOtxraNOUgIc4-76m05ZxyZtpgYw4n-p8fGrdxsrtWg&s=BKDeCcnB7JXDQcAC2Q7d74DAsFXwQssxireUDZiijuc&e=
-
[Sphenix-hcal-l] HCal channel numbering/mapping,
Stefan Bathe, 01/04/2022
- Re: [Sphenix-hcal-l] HCal channel numbering/mapping, Eric Mannel, 01/04/2022
-
Re: [Sphenix-hcal-l] HCal channel numbering/mapping,
pinkenburg, 01/05/2022
-
Re: [Sphenix-hcal-l] HCal channel numbering/mapping,
Stefan Bathe, 01/07/2022
-
Re: [Sphenix-hcal-l] HCal channel numbering/mapping,
Martin Purschke, 01/07/2022
- Re: [Sphenix-hcal-l] HCal channel numbering/mapping, Eric Mannel, 01/07/2022
-
Re: [Sphenix-hcal-l] HCal channel numbering/mapping,
Martin Purschke, 01/07/2022
-
Re: [Sphenix-hcal-l] HCal channel numbering/mapping,
Stefan Bathe, 01/07/2022
Archive powered by MHonArc 2.6.24.