What would be the most effective way to find 1.55^x, where x could be a number as large as 1 000 000?

Edit: I have a product block that doesn't round, but it stops working effectively (i.e. fast) at > 100 for x.

You can use scientific notation to raise a number to a large power of ten, but there is not a real

 ((b) ^ (e)::operators) 

block. Sorry

sashimiricedev wrote:

You can use scientific notation to raise a number to a large power of ten, but there is not a real

 ((b) ^ (e)::operators) 

block. Sorry

Yeah, I know that, but how do I do it, while avoiding the rounding error?

1. Why would you need such a huge number?
2. Scratch stores numbers as 32 bits (I think) so rounding errors couldn’t be avoided and might result in answer being infinity.
3. Here’s the method I tested on:

griefercube wrote:

1. Why would you need such a huge number?
2. Scratch stores numbers as 32 bits (I think) so rounding errors couldn’t be avoided and might result in answer being infinity.
3. Here’s the method I tested on:

As I said, I already know that. I'm asking for a way to do this efficiently without the rounding error.

griefercube wrote:

1. Why would you need such a huge number?
2. Scratch stores numbers as 32 bits (I think) so rounding errors couldn’t be avoided and might result in answer being infinity.
3. Here’s the method I tested on:

I need a large number for accurate precision.

Unfortunately as I beforehand mentioned, scratch will inevitably round the number as it uses 32 bits (32 digits) to store numbers, meaning that a number cannot exceed 10^309, or else it will display Infinity.

griefercube wrote:

Unfortunately as I beforehand mentioned, scratch will inevitably round the number as it uses 32 bits (32 digits) to store numbers, meaning that a number cannot exceed 10^309, or else it will display Infinity.

Except if you don't use math blocks, which is what I did. My problem is that it is slower than a snail with slowness 99999 if x > 1000

I'll try to make it more effective tomorrow.

I've never had a problem with the 60 second rule before. I feel the pain now.

Did you find a solution?

TheIsJa wrote:

Did you find a solution?

No, but I think it’s fine.

griefercube wrote:

Scratch stores numbers as 32 bits (I think)

Floats are 32-bit but Scratch and JavaScript use double floats which are double the size, so 64 bits.

https://en.wikipedia.org/wiki/Double-precision_floating-point_format