RBE/Filter node: definition of "last input value"

[binderth]

as described here

Remove / smoothen unrealistic item values which randomly appear

so update: It seems to work flawlessly. Usually, there's at least one or two drops within a few hours, and right until now it's not happened anymore! Great!

I used the RBE/filter node to ignore values that have changed by >25% since last input value.

So question: "last input value" corresponding to the last accepted input value? or the very last input value at all - even if unaccepted?

Let's assume the following input values:

1. 20
2. 22
3. 40
4. 45
5. 45

So, the second input value gets accepted (it's only 10% more), but the third input value gets ignored, because it's >25% change.

So question is to clarify:

• 45 is accepted again, because it's <25% change to 40?

RBE/Filter node

[
    {
        "id": "e8d801ca77ee111a",
        "type": "rbe",
        "z": "58c52084.f5de9",
        "name": "unrealistisch raus",
        "func": "narrowbandEq",
        "gap": "25%",
        "start": "",
        "inout": "in",
        "septopics": true,
        "property": "payload",
        "topi": "topic",
        "x": 950,
        "y": 340,
        "wires": [
            [
                "acfcaafe.4d56a"
            ]
        ]
    }
]

[Colin]

@binderth

So question: "last input value" corresponding to the last accepted input value? or the very last input value at all - even if unaccepted?

Isn't the last accepted input value the same as the last output value?

[binderth]

@Colin

Isn't the last accepted input value the same as the last output value?

nope. The RBE-node filters values, which don't meet the conditions in it. So, in my example the "last output value" in step 3 will be that of step 2: 22. BUT the "last output value" of step 4 is still 22.

So, to sharpen my question: is the "last input value" really just that: the last input - regardless of the filter condition? or is it the last "accepted" input value. In the latter case, it's kinda useless for my use case - but I'll get the impression as the output values tend to not change... I'll have to log everything to be sure (that's why I ask here first)

[jbudd]

I figured a minute's experimentation was better than hours in the forum so I tried it.
Is this the filter node settings?

I conclude that the "last input value" really is just that: the last input.

[Colin]

@binderth

@Colin

Isn't the last accepted input value the same as the last output value?

nope. The RBE-node filters values, which don't meet the conditions in it. So, in my example the "last output value" in step 3 will be that of step 2: 22. BUT the "last output value" of step 4 is still 22.

So what is the 'last accepted input value` at steps 3 and 4?

[binderth]

@jbudd

I conclude that the "last input value" really is just that: the last input.

Thanks for that test! Appreciated!

@Colin

So what is the 'last accepted input value` at steps 3 and 4?

That was the question. But as jbudd kindly demonstrated, it should work as intended. I'll have to look elsewhere for the cause of my "flatline".

[Colin]

@binderth

That was the question.

In your first post you asked

@binderth

So question: "last input value" corresponding to the last accepted input value? or the very last input value at all - even if unaccepted?

It is clear what is meant by 'very last input value at all', but I don't understand what you meant by 'last accepted input value'. I suggested that you mean the last value passed on (which is the last output value) but you said no. So what did you mean by 'last accepted input value' if it is not the previous value passed in and is not the last value passed on.