AlvaroEzq
commented
4 months ago Getting rid of the keys variable, metadata and observable would simplify a lot the code as it would get rid of the following duplicated code lines: https://github.com/rest-for-physics/framework/blob/d31c89d501817ec6e93663fd1c6f24e62a7fc9ab/source/framework/core/src/TRestDataSetPlot.cxx#L353-L391 https://github.com/rest-for-physics/framework/blob/d31c89d501817ec6e93663fd1c6f24e62a7fc9ab/source/framework/core/src/TRestDataSetPlot.cxx#L589-L634
But they are needed in TRestDataSetPlot::GenerateDataSetFromFilePattern(). A possible workaround could be to use the double [[]] encapsualting variable keywords ( e.g. [[entries]] ), the single [] encapsulating metadata (e.g. [TRestDetector::fPressure]) and naked observable names (e.g. rawAna_ThresholdIntegral) to identify them inside that method.
Extended the scale option to use any mathematical expression in combination with the special keywords. New keywords:
Add cuts, cutNames, panelCut and panelCutNames to paramMap to be able to show them in the panel (in the same way as meanRate for example). Also add RESTinfo message to output the global and additional panel cuts applied.
EnableMultiThreading when handling the TRestDataSet (avoids annoying _"Warning in: Implicit multi-threading is already disabled"_ message)
Added new key expression in panel definition to parse a mathematical expression that can contain any of the previous key values (variable, metadata and observable). It is a generalization of these previous keys, so this new expression key could replace them for good but I keep them for retrocompatibility.