Commit e934aca5 authored by Simon Spannagel's avatar Simon Spannagel
Browse files

EventLoaderEUDAQ2: allow to ignore BORE events

parent 16e5522b
Pipeline #1055266 passed with stages
in 17 minutes and 24 seconds
......@@ -161,6 +161,12 @@ std::shared_ptr<eudaq::StandardEvent> EventLoaderEUDAQ2::get_next_event() {
auto event = events_.front();
events_.erase(events_.begin());
// If this is a Begin-of-Run event and we should ignore it, please do so:
if(event->IsBORE() && ignore_bore) {
LOG(DEBUG) << "Found EUDAQ2 BORE event, ignoring it";
continue;
}
// Read and store tag information:
if(get_tag_vectors) {
retrieve_event_tags(event);
......
......@@ -92,6 +92,7 @@ namespace corryvreckan {
std::string m_filename{};
bool get_time_residuals{};
bool get_tag_vectors{};
bool ignore_bore{};
double m_skip_time{};
Matrix<std::string> adjust_event_times;
......
......@@ -72,6 +72,7 @@ Also, more complex constructs such as arrays or matrices read by the Corryvrecka
* `skip_time`: Time that can be skipped at the start of a run. Default is `0ms`.
* `get_time_residuals`: Boolean to change if time residual plots should be created. Default value is `false`.
* `get_tag_vectors`: Boolean to enable creation of EUDAQ2 event tag histograms. Default value is `false`.
* `ignore_bore`: Boolean to completely ignore the Begin-of-Run event from EUDAQ2. Default value is `true`.
* `adjust_event_times`: Matrix that allows the user to shift the event start/end of all different types of EUDAQ events. The first entry of each row specifies the data type, the second is the offset which is added to the event start and the third entry is the offset added to the event end. A usage example is shown below. Default is `0ms, 0ms`, `"other"` is just a placeholder.
### Plots produced
......
Markdown is supported
0% or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment