Support #669
Tracker Unpacking in MAUS
0%
Description
Dear Yordan,
This is Edward, from the tracker group. I want to do the unpacking for tracker cosmic events in MAUS. I'm not sure what tools already exist and what's left to do. David Addey told me some stuff but advised me to ask you more. Where is this MDdataEventVLSB? Will InputCppData need work, or is it ready to take tracker events? - and i believe that it's currently broken, right? I always fail to import it when I run a MAUS "application".
cheers,
ES
This is an email from Edward.
I think is better to have it as en issue.
This is also related to the already existing issue http://micewww.pp.rl.ac.uk/issues/592
Related issues
Updated by Karadzhov, Yordan over 11 years ago
I did some investigations on the DAQ computer in Lab 7 and I am confused.
I remember that JS was doing modifications of the VLSB equipment unpacking till the very last moment. I was thinking that these modifications were committed to the local repository, but it seems to me that they are not. After this I started to use the launchpad repository instead of the local repository at RAL and all later modifications I did are committed only to the launchpad repository. So we have to merge the real tracker unpacking code with the code in the launchpad repository. I guess the only difference is in the class MDfragmentVLSB and maybe in the example application.
Edward, can you tell me where exactly is the code you are using right now?
Updated by Santos, Edward over 11 years ago
David Adey is doing the unpacking, I'm adding him as watcher so that he can reply.
Karadzhov, Yordan wrote:
I did some investigations on the DAQ computer in Lab 7 and I am confused.
I remember that JS was doing modifications of the VLSB equipment unpacking till the very last moment. I was thinking that these modifications were committed to the local repository, but it seems to me that they are not. After this I started to use the launchpad repository instead of the local repository at RAL and all later modifications I did are committed only to the launchpad repository. So we have to merge the real tracker unpacking code with the code in the launchpad repository. I guess the only difference is in the class MDfragmentVLSB and maybe in the example application.Edward, can you tell me where exactly is the code you are using right now?
Updated by Adey, David over 11 years ago
Ok. What I meant was that I can provide unpacked data in some format until the "MD*" unpacking in integrated into MAUS, at which point we can shift data formats. I do not have time to do this myself. I don't know what JSG did with the committing - I thought he had done so. The code for the VLSB and Banks are still in ~/Software/MDunpack on miceacq11.
Updated by Tunnell, Christopher over 11 years ago
The new unpacker seems to work in MAUS but we're finalizing it. It should be done within two weeks so that it doesn't block this.
Updated by Karadzhov, Yordan over 11 years ago
David,
The code for unpacking of the new VLSB equipment in not in /home/daq/Software/MDunpack/unpacking
according to the DATE database NewVLSB and NewVLSBBank equipments have IDs 131 and 132.
However in the code in /home/daq/Software/MDunpack/ I see only the VLSB_C equipment with ID 80 (the old one).
Updated by Adey, David over 11 years ago
I don't know then. There is also /home/daq/Software/DATE/unpacking which seems to have one extra file - MDpartEventVLSB.
Updated by Rogers, Chris over 11 years ago
- Category changed from Input to RealData
- Assignee set to Santos, Edward
- Target version set to Future MAUS release
Updated by Santos, Edward over 11 years ago
Yordan,
Where exactly is the repository for the unpacking code? The VLSB_C files are on miceacq11 but they should be in the repository also and we'd like to run the unpackig on other machines.
Thanks, David
Updated by Karadzhov, Yordan over 11 years ago
You can get the last version of the unpacking that includes only VLSB_C (the old version of the VLSB equipement) by doing
bzr co lp:unpacking