Watch me break /sci/

[2+2=5 No.14795474]

1: 2.4+2.4=4.8
2: Round your figures.
3: Go insane.

[Anonymous No.14795494]

>>14795474
2+2=4
I always round down.

[Anonymous No.14795498]

0 = 0.8

[Anonymous No.14795499]

>>14795494
YOU CAN'T ROUND DOWN UNLESS THE DECIMAL IS LESS THAN 5!

[Anonymous No.14795506]

>>14795498
lol mistake
0 = 5

[Anonymous No.14795507]

>>14795506
lol still mistake, im rounding from right to left if anyone wonders
0 = 10

[Anonymous No.14795511]

>>14795474
3*3=3 (in mod 6 arithmetic).

[Anonymous No.14795512]

>>14795474
Retarded thread. OP should kill himself for even spending a minute making this embarrassment.

[Anonymous No.14795513]

>>14795474
Rounding operator isn't linear you absolute mongoloid son of a bitch.
For the idiots here what I mean is that, generally speaking, we have:
[eqn]\lceil x + y \rceil \neq \lceil x \rceil + \lceil y \rceil \\ \text{ for } x, y \in \mathbb{R}[/eqn]

[Anonymous No.14795523]

>>14795512
>>14795513

Rules of rounding.
If you have a number with a decimal, and the decimal figure is less than 5, such as 1.2, you round the figure down to 1. If the decimal figure is 5 or greater, such as 1.6, you round it up to 2.

Rounding is usually done before operatives; however you can also do it post operative.

Following the flexible rule of "When to round" you either end up with
2+2=5
OR
2.4+2.4=4.8

It all depends on the application and way you want to perceive ti.

If your calculation rounds answer (such as in programming) you can easily end up with 2+2=5 because of the rounding post calculation.

This is used in chip damage calculations, RNG generators, and odds manipulators when the display is in whole numbers but the calculations can be decimaled.

[Anonymous No.14795536]

>>14795523
My UI tells me only whole numbers; however my calculations involve decimals; thus rounding is needed.

If Enemy HP is 50/50, and I attack twice with a move that deals 2.3 damage per attack, this is 2.3+2.3; is the Enemy HP technically 45.4? No. Because the UI does not show this. It rounds down to 45 because that is what the display shows.

However; if we apply a different operative turn; First attack deals 2.3 (round down) 48/50 second attack deals 2.3 (round down) 46/50.
Final damage taken: 4.

It all depends on the order if you round post attack or round during each phase of the attack.

[Anonymous No.14795541]

>>14795499
Watch me.

[Anonymous No.14795544]

>>14795536
This is especially true when dealing with calculations that take into account dividers and multipliers such as Defense, Strength, Luck; etc.

If your UI is whole numbers (which most basic UI's are) You're going to have to round, and depending on the order of rounding, post calculation or during calculation can give you the extra +1 damage due to order, or the standard damage as logical /sci/ users like >>14795513
>>14795512
will tell you exists only.

[Anonymous No.14795548]

The scary thing is that this confirmed 80 IQ mongoloid actually thinks he's saying something clever.

[Anonymous No.14795552]

>>14795548
The actual scary thing is that despite being a virgin, you've never played D&D

[Anonymous No.14795560]

>>14795552
Retard, come back when you now what the symbols '2', '+' and '4' mean.

[Anonymous No.14795563]

>>14795560
You come back once you've read
>>14795523
>>14795536
>>14795544
and realize that depending on how you order things, you can get a different answer given your interface.

[Anonymous No.14795570]

>>14795563
I'm not reading any of that. Sorry. It's a given that you're wrong. You need to learn what '2', '4' and '+' mean.

[Anonymous No.14795578]

>>14795570
>He's never programmed in his life.

lol.
lmao even.

[Anonymous No.14795589]

>>14795578
>i'm a retarded pajeet code monkey
That explains it.