sPHENIX discussion of software

[Martin Purschke <purschke AT bnl.gov>]

Hi Tony,

by and large, this is still the same structure. It may be a bit hard to 
get to the "meat" of what is happening here. On my slides today I showed 
some of the API calls that I used for the digitizers as an example. 
Here, if you look at the actual code -

https://sphenix-collaboration.github.io/doxygen/d4/d92/TpcPrototypeUnpacker_8cc_source.html

in line 442 we ask if a FEE provided data here in the first place.

In L 486 we retrieve the sample value (the SAMPA ADC), and in L487
the BCO for it.

If this stays exactly the same remains to be seen as JohnK and I develop 
this further, but it's a good start.

Hope it helps,

        Martin



On 4/5/22 16:55, Huang, Jin via sPHENIX-software-l wrote:
> Hi Tony
>
>  > hat code has to interface the data to the reconstruction software, 
> and so we should be discussing what we need it to produce.
>
> For TPC, I don’t think we have the module for the final event format 
> yet. But I wrote the module unpacking the test beam data using Martin’s 
> Event interface:
>
> https://sphenix-collaboration.github.io/doxygen/dd/d60/classTpcPrototypeUnpacker.html 
> <https://sphenix-collaboration.github.io/doxygen/dd/d60/classTpcPrototypeUnpacker.html> 
>
>
> It output TPC hit to our standard TrkHit containers: 
> TpcPrototypeUnpacker::exportDSTHits 
> <https://sphenix-collaboration.github.io/doxygen/dd/d60/classTpcPrototypeUnpacker.html#ae1ef5126324a38fcce0e1e39e346ee6a>() 
>
>
> For simplicity, I also did the clustering in the same module: 
> intTpcPrototypeUnpacker::exportDSTCluster 
> <https://sphenix-collaboration.github.io/doxygen/dd/d60/classTpcPrototypeUnpacker.html#a018feffce2f4cf203fb9efc95d3c701a>(ClusterData 
> <https://sphenix-collaboration.github.io/doxygen/d1/d3e/classTpcPrototypeUnpacker_1_1ClusterData.html>& 
> cluster, constinticlus)
>
> In the same repo, there are also MVTX unpacker from Yasser for the last 
> test beam data at
>
> https://sphenix-collaboration.github.io/doxygen/d2/d5b/classMvtxPrototype2UnpackPRDF.html 
> <https://sphenix-collaboration.github.io/doxygen/d2/d5b/classMvtxPrototype2UnpackPRDF.html> 
>
>
> I am not sure the status of INTT unpacker and the readout is still in 
> development. But the unpacker with the PHENIX readout chain is 
> offline/packages/fvtx_subsysreco/FvtxUnpackPRDF at 
> https://phenix-intra.sdcc.bnl.gov/WWW/offline/doxygen/html/dd/d44/classFvtxUnpackPRDF.html 
> <https://phenix-intra.sdcc.bnl.gov/WWW/offline/doxygen/html/dd/d44/classFvtxUnpackPRDF.html> 
>
>
> Cheers
>
> Jin
>
> ______________________________
>
> Jin HUANG
>
> Physicist, Ph.D.
>
> Brookhaven National Laboratory
>
> Physics Department, Bldg 510 C
>
> Upton, NY 11973-5000
>
> Office: 631-344-5898
>
> Cell:   757-604-9946
>
> ______________________________
>
> *From:* sPHENIX-software-l <sphenix-software-l-bounces AT lists.bnl.gov> 
> *On Behalf Of *Anthony Frawley via sPHENIX-software-l
> *Sent:* Tuesday, April 5, 2022 3:56 PM
> *To:* sphenix-software-l AT lists.bnl.gov
> *Subject:* [Sphenix-software-l] Event builder?
>
> Hi All,
>
> During our discussion today in the software meeting about the raw data 
> format, it seemed to me that we are missing a step. The raw data 
> consists of packets, the reconstruction software expects to see 
> assembled events.
>
> Who is writing the code that converts packets to assembled events? That 
> code has to interface the data to the reconstruction software, and so we 
> should be discussing what we need it to produce. That discussion should 
> happen soon ....
>
> Thanks
>
> Tony
>
>
> _______________________________________________
> sPHENIX-software-l mailing list
> sPHENIX-software-l AT lists.bnl.gov
> https://lists.bnl.gov/mailman/listinfo/sphenix-software-l


--
Martin L. Purschke, Ph.D.        ;   purschke AT bnl.gov
                                 ;   http://www.phenix.bnl.gov/~purschke
                                 ;
Brookhaven National Laboratory   ;   phone: +1-631-344-5244
Physics Department Bldg 510 C    ;   fax:   +1-631-344-3253
Upton, NY 11973-5000             ;   skype: mpurschke
-----------------------------------------------------------------------