FF 151211

Tracker workshop web page:

Rogers notes:

  • Data structure
    • In proposed data structure need to distinguish between data tied to execution of the code and data tied to the MICE run
  • Definition of constants/configuration calls
    • Ken requests that we have ability to process a subset of the data that may span multiple Runs but not include all run data
    • This means that we have to know for each spill which configuration we are looking at and update e.g. geometry, calibrations etc per spill
  • We additionally need dead time model in the MC - and this is a tracker responsibility
  • There was some comment about bugs in the simulation - Rogers needs to look at this

Updated by Rogers, Chris about 9 years ago ยท 1 revisions