# | User | Rating |
---|---|---|
1 | jiangly | 3898 |
2 | tourist | 3840 |
3 | orzdevinwang | 3706 |
4 | ksun48 | 3691 |
5 | jqdai0815 | 3682 |
6 | ecnerwala | 3525 |
7 | gamegame | 3477 |
8 | Benq | 3468 |
9 | Ormlis | 3381 |
10 | maroonrk | 3379 |
# | User | Contrib. |
---|---|---|
1 | cry | 168 |
2 | -is-this-fft- | 165 |
3 | Dominater069 | 160 |
3 | Um_nik | 160 |
5 | atcoder_official | 159 |
6 | djm03178 | 157 |
7 | adamant | 153 |
8 | luogu_official | 150 |
9 | awoo | 149 |
10 | TheScrasse | 146 |
Name |
---|
Cause when k == 1 it will run n time which is of order 1e9.... But log approach still gives WA on larger tescase as it might have precision errors..
could you give me an example for precision error, i mean int x = ln(n)/ln(k)
we dont have to precisely find out the value of exponent, we can just find the one that's closest, could you give me an example where this approach will fail.
i also did this approach, when n<k then there will be n operations, this also gave TLE
Can you check this out:
Comment-1203949
I tried the log approach, one with multiples of k^x and one with just k^x. (Where k^x will be the largest power of k <= n)