I was solving this problem Kingdom Division but i don't know where am i going wrong(just the logic), please forgive me if am doing some very stupid mistake here, I have just started to learn DP, below i am presenting my approach :--
# | User | Rating |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3823 |
3 | Benq | 3738 |
4 | Radewoosh | 3633 |
5 | jqdai0815 | 3620 |
6 | orzdevinwang | 3529 |
7 | ecnerwala | 3446 |
8 | Um_nik | 3396 |
9 | ksun48 | 3390 |
10 | gamegame | 3386 |
# | User | Contrib. |
---|---|---|
1 | cry | 167 |
2 | maomao90 | 163 |
2 | Um_nik | 163 |
4 | atcoder_official | 161 |
5 | adamant | 159 |
6 | -is-this-fft- | 158 |
7 | awoo | 157 |
8 | TheScrasse | 154 |
9 | nor | 153 |
9 | Dominater069 | 153 |
I was solving this problem Kingdom Division but i don't know where am i going wrong(just the logic), please forgive me if am doing some very stupid mistake here, I have just started to learn DP, below i am presenting my approach :--
Name |
---|
Have you tried the following:
Write a very naive and simple solution to the problem (maybe exponential complexity) (if you can, you may also just copy someone else's solution)
Write a program to generate thousands of small (!) test cases
Using those two, find a test case where your program gives the wrong answer
Use print statements or a debugger to see where exactly your program does the wrong thing.
98% of WAs and REs can be resolved this way. People here don't have time to delve into every code posted here, it's much harder to debug somebody else's code and being able to debug your own code is a valuable skill. It is also a very routine process that can be learned much faster than problem solving and algorithms.
yes , it makes a lot of sense but i was just talking about the logic , whether am i approaching in right direction or not ,sry, i didn't clearly mentioned there about this. OK from next time i will not repeat this compelling mistake again!! and thanks for ur humbleness, u r a nice person ...
Wait, I'm not sure I understand what you want here. Do you just want like a hint or something? Or do you want to know what's wrong with your code? If you have a test case that breaks your code it should be quite easy to understand where the mistake in your logic is.
Basically i was trying to do it using 2d states but in editorial they have used 3d states, so just wanted to know why my logic will not work, take this code as pseudo-code , am not asking someone to find bugs here, lol.
Seriously, try the stress testing if you haven't already, it always helps me in such situations.