Project

General

Profile

Actions

Sim-Development #1016

closed

TRD time-based detector response

Added by Volker Friese almost 5 years ago. Updated over 3 years ago.

Status:
Closed
Priority:
Normal
Target version:
Start date:
10/30/2017
Due date:
03/05/2019
% Done:

100%

Estimated time:
30.00 h
Spent time:

Description

Implementation of time-based detector response incl. noise for the CBM-TRD.

For general information, see the mother issue #1014.


Related issues

Related to CbmRoot - Development #1213: TRD and Global TrackingClosedIouri Vassiliev02/18/2019

Actions
Actions #1

Updated by Volker Friese almost 5 years ago

  • Parent task set to #1014
Actions #2

Updated by Volker Friese over 3 years ago

  • Target version changed from DEC17 to APR19

A time-based response implementation is available in DEC17. A more realistic response simulation is in work.

Actions #3

Updated by Volker Friese over 3 years ago

  • Parent task deleted (#1014)
Actions #4

Updated by Volker Friese over 3 years ago

The current TRD digitizer (OCT17) seems not to deliver absolute time (digi->GetTime()), but possibly time frames. See CP-SIM meeting of 14 February 2019. This leads to incorrect sorting of TrdDigis in time-slices and has to be fixed for the APR19 release.

Actions #5

Updated by Volker Friese over 3 years ago

Actions #6

Updated by Etienne Bechtel over 3 years ago

The timing was indeed used with the clock count and is now set to absolute values again.

Actions #7

Updated by Etienne Bechtel over 3 years ago

  • % Done changed from 0 to 90

The remaining problems with the links were solved and the newest version of front end simulation is in the trunk (@revision14038).
Final parameter optimization and more precise time reconstruction are in progress and will be added as soon as they are available.

Actions #8

Updated by Volker Friese over 3 years ago

  • Status changed from Assigned to Closed
  • % Done changed from 90 to 100

Ok, so that is what will enter the release; further developments and improvements will be document in a follow-up issue.

Actions #9

Updated by Volker Friese over 3 years ago

  • Due date set to 03/05/2019
Actions

Also available in: Atom PDF