Decision mask in arbter kernel output schema

The downstream analysis need to know the decision of kernels.

@hammerd

Just to make sure I understand the goal: it's now enough to know the final decision mask, downstream also wants to know the masks resulting from each intermediary step of the selection plan? That seems fine, is presumably still small. Then I'd also update AdvancedFrameSelectionArbiter.on_matched_data to actually write this out.

Correct. The the typical example, when the final decision is a mix of all hits and small random fraction of misses. Then the downstream processing is different for hits and misses. Arbiter kernels label data each for specific reason, which is a result itself.

Sure, that makes sense.

This line actually writes... Or do I misunderstand you?

Oh you're right of course. Not sure how I missed this line.

LGTM

merged

mentioned in commit ec337400