Skip to content

v2.2.14

Compare
Choose a tag to compare
@jgalan jgalan released this 25 Dec 05:54
· 4333 commits to master since this release
REST Framework
  1. Added new REST_ListMacros.C to list all the REST macros available. It also prints documentation that should be introduced inside the macro code using //*** . Check REST_PrintTrees.C for a documented example.

  2. Added a new sub-dir in the process code directory, util. The util processes are the ones who have nothing to do with data analysis, or that cannot be easily classified with one of the existing categories. Three processes were moved into the folder: TRestDaqChannelSwitchingProcess, TRestRawSignalViewerProcess, TRestSignalViewerProcess.

  3. Full revision of TRestAnalysisPlot. Check forum posts!

  4. Fixed observable leak for TRestTrackAnalysisProcess and TRestTriggerAnalysisProcess. Fixed a bug in TRestTriggerAnalysisProcess

  5. A REST process EndProcess implementation can now access the analysisTree using the method GetFullAnalysisTree.

  6. Added new <panel definition inside TRestAnalysisPlot.

REST processes
  1. Added new util process: TRestBenchMarkProcess. It monitors system load and the performance of REST, then saves the result as observables. The input and output event type is arbitary, so we can insert it anywhere in the process chain.

  2. Added a new validateProcesses.py script to identify problems in the construction of processes. It will be executed in the pipeline when new code is uploaded to the repository.

  3. fixed observable leak for TRestTrackAnalysisProcess and TRestTriggerAnalysisProcess. Fixed a bug in TRestTriggerAnalysisProcess. This bug is detectable now by validateProcesses.py.

REST events
  1. Updated TRestHitsEvent to save fType object. For concatenated MicroMegas readout it is not purely 2D. We should still have X information in YZ hits, and Y information in XZ hits. The new TRestHitsEvent saves all the information. Needs verification.

  2. TRestG4Hits stores also now the information of the remaining kinetic energy of the particle. So that we keep track the information on the kinetic energy at each hit.

  3. TRestG4Hits::GetTime() now returns the global timestamp (in seconds) when the hit was recorded in the stepping action. Previously this method always returned 0.