No error prompted when the output/input event type of two processes do not match

RESTFramework
1

REST version : v2.2.15
REST commit : bd341058

Hi,

in previous versions of REST the input/output type of processes was being validated, and in case the output event type of the previous process did not match the input event type of the next process an error was prompted on screen, and the user was aware of the problem.

Now, I can connect without problems a TRestHitsEvent process with a TRestRawSignalEvent process. This might seem quite easy to detect, but new people trying to understand how the framework works are not aware of it and do not understand what it is going on.

For example the following process definition is wrong and should end up in an error.

15
151714×1020 508 KB

No error message is given, and simply there will be 0 successfully processed events.

There is a way to come back to event input/output validation in the process chain definition?

2

Indeed, the chain validation was removed in commit 0421d528, because:

  • We have some general-input processes. They cannot initialize its input/output event

  • We also have some analysis processes that directly passes the input TRestEvent pointer, therefore initializating input/output event is not needed.

In these cases, the old validation method cannot work.

Maybe we can skip the processes with null input/ouput event when doing validation?

3

Yes, I guess that might be a way.

Then we match the last valid output event with the next valid input event.

1 Like