I can easily see this for the "numerical" calc and the longin records. But what does the new behavior for the "enum" mbbi record mean? Suppressing spikes? How does that interact with the ACKT field?
« Back to merge proposal
I can easily see this for the "numerical" calc and the longin records.
But what does the new behavior for the "enum" mbbi record mean? Suppressing spikes? How does that interact with the ACKT field?