sPHENIX MAPS tracker discussion

[Yasser Corrales Morales <ycorrale AT cern.ch>]

Hi Martin,

of Course we can sit and discuss about this.

the previous decoder was written for single stave and to retrieve basic information only, with the implementation of the full MVTX detector everything expand use a single file look to my impossible. In addition, I thought the trying to use in someway the ITS code would be more simple and it rely in a set of class that we adapt it as a framework to be used by the decoder. All of this is in development stage and could change drastically in the future, so I did not want just to force everybody to install all dependencies and mvtx decoder files for now, that is why we put everything in sPHENIX gitea and add some option to enable/disable.

But, if anyone want to take the responsibility to develop the MVTX decoder in a more simple way are more than welcome.

Cheers,

Yasser.

On 2/9/23 15:50, Martin Purschke via sPHENIX-MAPS-l wrote:

    Hi All,
      especially Jo, Jakub, Yasser,
      
      
      after that meeting today where I merged the pull request against
      the github repo (only to then learn that everything really lives
      in gitea - WHY???).
      
      
      To begin with, I will not allow the configure and Makefiles to be
      mangled just to accommodate a particular packet. We will not be
      going through hundreds of install/jenkins/test/nightly_rebuild
      scripts and put custom flags in. It either works, or it doesn't.
      We can also not make custom installs for the eventual
      reconstruction jobs.
      
      
      Then of course, this thing cannot depend on external files.
      
      
> ../../../newbasic/oncsSub_idmvtxv3.cc:4:10:
>         fatal error: MVTXDecoder/ChipMappingMVTX.h: No such file or
>         directory
>         
>          #include "MVTXDecoder/ChipMappingMVTX.h"
>         
>                   ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>         
>       
      
      We had all this so nicely self-contained with the v1 and v2
      packets. Why are we making this so complicated? I feel that there
      is all this complexity for no good reason.
      
      
      Before we go on on a tangent here, please let's sit together and
      get it sorted out. (I think we will pull Chris in - we just did
      this next to each other here and the above is not just my
      opinion).
      
      
      Best,
      
      
          Martin
      
      
      
      
      
      
    
-- 
Yasser Corrales Morales

Staff Scientist at the Relavistic Heavy Ion Group

Laboratory for Nuclear Science

Massachusetts Institute of Technology