Implementing BiPo event data processing in REST

[jgalan]

Class documentation preview has been rendered here.

In order to launch the event data processing the file needs to be uncompressed. Inside the pipeline/external/BiPo/ there is an example of launching a basic processing chain.

We still need to uncompress the original file before start the data processing, so we need to do something like this:

gzip -d -c /path/to/binary/data/BiPo3Mod2_run_2600.data.gz > /tmp/BiPo3Mod2_run_2600.data
restManager --c /path/to/rml/BiPoToRawSignal.rml --f /tmp/BiPo3Mod2_run_2600.data
rm /tmp/BiPo3Mod2_run_2600.data

Then, we can access the information of the new generated ROOT file and quickly inspect the file using:

restRoot RawData_BiPo3Mod2_02600.root

Inside the ROOT command shell, we can access:

• Run information

run0->PrintMetadata();

• Matacq and BiPo configuration settings:

md0_BiPo->PrintMetadata()

• Finding some event entries that satisfy certain conditions

root [1] run0->GetEventEntriesWithConditions("rawAna_MaxPeakAmplitude>50 && rawAna_MaxPeakAmplitude<1000")
(std::vector<int>) { 0, 1, 2, 4, 9, 14, 17, 20, 22, 25, 26 }

• Updating the entry and printing analysis tree observables

root [3] run0->GetEntry(17)
root [4] run0->GetAnalysisTree()->PrintObservables()

• Drawing the active event and saving to png

TCanvas c;
ev0->DrawEvent();
c.Print("Entry17.png");

An example was added to include the analysis (using TRestRawSignalAnalysisProcess) of two different range of the waveforms, the example at examples/01.BiPo/ contains a plots.rml definition that will generate few prebuilt plots.

restManager --c plots.rml --f RawData_BiPo3Mod2_02600.root

[jgalan]

@juanangp I get the following compilation error.

error: constexpr variable cannot have non-literal type 'const std::string' (aka 'const basic_string<char>')
constexpr std::string TAG_ACQ_2 = "AC2";

what is the problem using just const?

[jgalan]

Then I get plenty of errors, because fread requires a void * and changing it to std::array the compilation complains. So I just pushed force the original version.

Perhaps this is a change to be made once the validation pipeline is running for this example.

[juanangp]

@juanangp I get the following compilation error.

error: constexpr variable cannot have non-literal type 'const std::string' (aka 'const basic_string<char>')
constexpr std::string TAG_ACQ_2 = "AC2";

what is the problem using just const?

Indeed, constexpr cannot be used with std::string, but should be possible to do constexpr std::string_view TAG_ACQ_2 = "AC2"; or constexpr char[] TAG_ACQ_2 = "AC2";

Is better to use constexpr in this case because it would be already available at compile time, which means that will be faster https://stackoverflow.com/questions/41125651/constexpr-vs-static-const-which-one-to-prefer. Anyhow, it is not a big deal but I think is a good practise to use constexpr.

[juanangp]

Then I get plenty of errors, because fread requires a void * and changing it to std::array the compilation complains. So I just pushed force the original version.

Perhaps this is a change to be made once the validation pipeline is running for this example.

I guess you have to do something like &stdArray[0], I can have a look later on.