Are you sure that maus-input-transform triggered the death? KeyboardInterrupt - usually comes from receiving a SIGINT from the bin/analyze_data_online.py application launcher.

In bin/analyze_data_online.py main(), we poll_processes (line 377) unless there is an exception. If an exception occurs, we go into the finally: where we call cleanup(PROCESSES). cleanup(PROCESSES) calls SIGINT (ctrl-c/KeyboardInterrupt) on remaining processes. I note in tofcalib reducer the following error

     34 Traceback (most recent call last):
     35   File "/home/mice/MAUS/.maus_release/src/common_py/ErrorHandler.py", line 162, in HandleCppException
     36     raise CppError(error_message)
     37 ErrorHandler.CppError: In branch daq_data
     38 Failed to recognise all json properties emr  at ObjectProcessor<ObjectType>::JsonToCpp
     39 Traceback (most recent call last):
     40   File "/home/mice/MAUS/.maus_release/src/common_py/framework/merge_output.py", line 281, in execute
     41     run_again = will_run_until_ctrl_c and self._execute_inner_loop()
     42   File "/home/mice/MAUS/.maus_release/src/common_py/framework/merge_output.py", line 327, in _execute_inner_loop
     43     self.process_event(spill)
     44   File "/home/mice/MAUS/.maus_release/src/common_py/framework/merge_output.py", line 238, in process_event
     45     raise RuntimeError("Failed to execute Output")
     46 RuntimeError: Failed to execute Output

There is indeed no emr branch in the DAQDataProcessor:

     21 DAQDataProcessor::DAQDataProcessor()
     22     : _V830_proc(), _trigger_request_proc(new TriggerRequestProcessor),
     23       _tof1_proc(new TOFDaqProcessor), _ckov_proc(new CkovDaqProcessor),
     24       _tof2_proc(new TOFDaqProcessor), _unknown_proc(new UnknownProcessor),
     25       _kl_proc(new KLDaqProcessor), _tag_proc(new TagProcessor),
     26       _tof0_proc(new TOFDaqProcessor), _trigger_proc(new TriggerProcessor) {
     27     RegisterValueBranch
     28           ("V830", &_V830_proc, &DAQData::GetV830,
     29           &DAQData::SetV830, false);
     30     RegisterValueBranch
     31           ("trigger_request", &_trigger_request_proc, &DAQData::GetTriggerRequestArray,
     32           &DAQData::SetTriggerRequestArray, false);
     33     RegisterValueBranch
     34           ("tof1", &_tof1_proc, &DAQData::GetTOF1DaqArray,
     35           &DAQData::SetTOF1DaqArray, false);
     36     RegisterValueBranch
     37           ("ckov", &_ckov_proc, &DAQData::GetCkovArray,
     38           &DAQData::SetCkovArray, false);
     39     RegisterValueBranch
     40           ("tof2", &_tof2_proc, &DAQData::GetTOF2DaqArray,
     41           &DAQData::SetTOF2DaqArray, false);
     42     RegisterValueBranch
     43           ("unknown", &_unknown_proc, &DAQData::GetUnknownArray,
     44           &DAQData::SetUnknownArray, false);
     45     RegisterValueBranch
     46           ("kl", &_kl_proc, &DAQData::GetKLArray,
     47           &DAQData::SetKLArray, false);
     48     RegisterValueBranch
     49           ("tag", &_tag_proc, &DAQData::GetTagArray,
     50           &DAQData::SetTagArray, false);
     51     RegisterValueBranch
     52           ("tof0", &_tof0_proc, &DAQData::GetTOF0DaqArray,
     53           &DAQData::SetTOF0DaqArray, false);
     54     RegisterValueBranch
     55           ("trigger", &_trigger_proc, &DAQData::GetTriggerArray,
     56           &DAQData::SetTriggerArray, false);
     57     RegisterIgnoredBranch("single_station", false);
     58 }

So Yordan needs to tell us what data structure he wants so we can fix this.

The issue is that the data structure is strict - so just adding random bits and pieces will break the code. If we don't do a strict data structure, then nobody has a clue what data looks like and we end up in a mess, so we do have to be strict.

Pushed to merge branch as r994