Closed mmcdermott closed 1 year ago
Patch coverage: 86.36
% and project coverage change: -0.28
:warning:
Comparison is base (
943086f
) 69.35% compared to head (84e9e03
) 69.07%.
:umbrella: View full report in Codecov by Sentry.
:loudspeaker: Do you have feedback about the report comment? Let us know in this issue.
Does two things: (1) Removes the ability for measurements to explicitly be configured to occur only on select event types. (2) Removes support for dynamic single-label classification tasks (aside from
event_type
, which is a special case and always mandated to be single label).These are necessary for the following reasons: (1) For event type specificity to be meaningful during generation, we need to have post processing that removes measurements not allowed after event types have been generated, which we currently don't have. As a result, this current functionality is broken. It should be re-added (correctly) at some point, with tests to validate it, but until then it should be removed so as to avoid broken portions of the code. (2) Without the ability to state that a measurement is specific to an event type, dynamic, single-label classification tasks don't actually make that much sense, as there is an inherent assumption in them that they will always be measured exactly one time (on their allowed event types). As we support event aggregation, many "single label" tasks in reality end up being multi-label (as multiple valid events get aggregated together) and without event type support others end up being only partially observed single label tasks, which we don't currently support (as we'd need to predict (a) whether the task is measured at all and if so then (b) what label is observed, whereas now we just predict (b) by virtue of the assumption it is universally observed on valid event types.)