Decider Combinator converts one signal to another now?

[draslin]

Can someone explain this to me?

05-04-2025, 08-48-57.png (76.36 KiB) Viewed 205 times

It was my understanding that only an arithmetic combinator could convert one signal into another signal. I've always observed it to be true until I started SE. And it seems like combinator behavior over all isn't consistent to me. This combinator, as configured should only output a valid S signal from the green wire. Instead it outputs nothing from the green wire. Meanwhile, if I switch it to output from the red wire it converts the uranium ammo signal to the S signal at the uranium count value. Which isn't what I want it to do.

For context, this is intended to determine what stack size is appropriate to ensure I only transfer exact amounts with an inserter. It needs to use Each so that it can make the comparison for any single item signal.

[Amarula]

You have set the combinator to output the RED input COUNT as the output value for S. The red input count is 46, it is outputting S with a value of 46, exactly as it should. If you want the output count of the green wire, change the checkbox for the output from red to green.

[boskid]

When working on decider combinators, there were 2 possible solutions for this configuration when decider is in "each mode" when you have each signal on conditions side but specific signal on the outputs side: first solution was to get value of that signal S on the input side and multiply it by the amount of signals passing conditions under the each substitute, and second being signal S taking a value of the passing substitutes themselves. Decision was that a second approach is more useful and there are ways to get equivalent of first solution by outputting signal S with value of 1 and using external arithmetic combibator to multiply that value with value of input signal S provided on a separate wire if there is a need for that.

[draslin]

You have set the combinator to output the RED input COUNT as the output value for S. The red input count is 46, it is outputting S with a value of 46, exactly as it should. If you want the output count of the green wire, change the checkbox for the output from red to green.

I appreciate the reply, but I'm aware that it is outputting from the red wire. As I said, it outputs nothing from the green wire when I try selecting the green output. It only outputs something if I select the red wire output.

But separately, it used to be, (or so I believed) that the decider combinator did not convert one signal into another signal. This combined with the fact nothing comes out the green wire clearly meant there was something I didn't understand.

[draslin]

When working on decider combinators, there were 2 possible solutions for this configuration when decider is in "each mode" when you have each signal on conditions side but specific signal on the outputs side: first solution was to get value of that signal S on the input side and multiply it by the amount of signals passing conditions under the each substitute, and second being signal S taking a value of the passing substitutes themselves. Decision was that a second approach is more useful and there are ways to get equivalent of first solution by outputting signal S with value of 1 and using external arithmetic combibator to multiply that value with value of input signal S provided on a separate wire if there is a need for that.

Oof. I'm not sure I follow completely. But it sounds like its only going to output values from the left hand side of the condition. Which is a bummer because I'm trying to minimize how many combinators are used. I'm also probably using Each in an unintended way. I'm using a selector combinator to pre-select a single input from the available inputs before sending it to this combinator. Which makes the Each signal a kind of ersatz THIS signal. I can't use the each, or any, or everything signal on the right hand side of the condition, which pretty much hoses the approach. The inputs to the selector combination would fall off as inventory levels reach the desired quantity. Back to the drawing board I guess.

[Tertius]

But separately, it used to be, (or so I believed) that the decider combinator did not convert one signal into another signal. This combined with the fact nothing comes out the green wire clearly meant there was something I didn't understand.

It was always the case that the decider combinator is able to cast the value of one signal into some given signal. I used this in 1.1 versions from 2021 to convert one arbitrary signal to a known signal. Blueprints from that time still work in current 2.0.

However, the 46 you get isn't exactly the result of a "conversion". It's the result of summing up all matching signals from the EACH and assigning this value to the given output signal. The 46 on red is >= 4 on green, so it will match, so you get the sum of 46, which is 46. If you add another signal on red with a matching value >=4, for example 10, you will get the sum of 46 and 10 , which is 56, as result in S.
Green isn't contributing to the sum, because there is no a match from green, because you removed the green check from the EACH in the condition. So it doesn't matter if you check green on the output or not.