Project

General

Profile

Actions

Development #1511

closed

Development #1510: Online software for mCBM 2020

Unpackers mCBM 2020

Added by Volker Friese over 2 years ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Assignee:
Target version:
Start date:
02/05/2020
Due date:
03/25/2020
% Done:

100%

Estimated time:
(Total: 13.00 h)
Spent time:
(Total: 1.00 h)

Description

We need unpackers for all involved detector systems. Running versions are available, but are probably not yet optimised ore intertwingled with monitoring and QA.

The unpackers themselves shall be framework-independent. The data flow will be implemented in wrappers for FairTask (CbmRoot) and FairDevice (CbmMQ). The data interfaces for the unpackers are:

  • input: Reference to time slice
  • output: vector<Digi>, where Digi is a concrete digi class
  • parameters: to de defined (needed for time calibration)

As discussed previously, a class template shall be provided where the concrete unpackers have to derive from. The template parameter is the digi class.

The class template shall be implemented in CbmUnpack.h.


Subtasks 3 (0 open3 closed)

Development #1518: Class template for unpackersClosedVolker Friese02/05/202002/07/2020

Actions
Feature #1555: Store error messages and flags during raw data unpackingClosed02/19/202003/25/2020

Actions
Feature #1575: Central (tsa)-source classClosedVolker Friese02/25/2020

Actions

Related issues

Related to CbmRoot - Development #1253: mCBM unpakers - wrong ProcessTs method called?ClosedPierre-Alain Loizeau03/25/2019

Actions
Actions #1

Updated by Pierre-Alain Loizeau over 2 years ago

Actions #2

Updated by Volker Friese about 2 years ago

  • Target version changed from APR20 to APR21
Actions #3

Updated by Florian Uhlig 11 months ago

  • Target version changed from APR21 to DEC21
Actions #4

Updated by Pierre-Alain Loizeau 4 months ago

  • Status changed from Assigned to Feedback

I think the current versions in reco/base, reco/detectors/<XXX>/unpack, reco/steer/ and MQ/mcbm answer the initial scope of this issue.

Or do you think this should be kept open until we have the skeleton unpackers in the algo folder? (in which case this should probably be re-assigned)

Not sure also to which degree the sub-tasks were answered...

Actions #5

Updated by Volker Friese 3 months ago

  • Status changed from Feedback to Resolved
  • Assignee changed from Pierre-Alain Loizeau to Volker Friese

Well, is anyhow not much relevant any longer, I think.

Actions #6

Updated by Volker Friese 3 months ago

  • Status changed from Resolved to Closed
Actions

Also available in: Atom PDF