Hello, Codeforces Community!
I invite you to January Easy '16 today at 2130 IST. The difficulty of the contest will be similar to div2 CF round. The problems have been set by harshil, kunal93 and I.
A lot of you can manage to solve all the 6 problems in 3 hours, for sure. The order of the problems will be random. Each problem is worth 100 points but scoring is partial so try to pass as many tests as possible!
Importantly, I want to thank Kamil (Errichto) — he is the tester and editorialist for the contest. It was amazing to work with him. He is, hands down, the most active setter/tester as of now — and an extremely productive one, too. I hope he was able to tolerate me. :)
Link: https://www.hackerearth.com/january-easy-16/
Enjoy the contest, see you all on the hall of fame!
Starts in an hour. Have fun!
How to solve GJ's invasion (P4)?
I tried to use such dp:
f[i][mask] — answer, when we built some prefix of length i and used numbers, whose bits in mask are 1. ways[i][mask] — number of ways to reach this state
Then, I try to add some guy (j = 0..n-1) and if:
I update state:
Where getCount(j, mask) returns the numbers of such k, that (mask & (1 << k)) != 0 and k > j.
Why does it get WA?
Thanks in advance!
your approach looks ok. There are some technical issues and we must wait for editorials.
My code is here — http://ideone.com/FQZYvd
Thanks.
I found, that I forgot to clear the "ways" array.
When will upsolving be available?
There is some caching issue in a contest. But you can find a problem here — https://www.hackerearth.com/problems/ and there upsolve it.
You can try submitting your solutions to the problems now, Yury. It should work fine.
upsolving should be available now
overflow maybe?
Best contest on hackerearth till date!
fun contest :)
Had a stupid mistake on the third one because recursion stack was too big and BOOM. That happens when you spend too much time on codeforces with its hulk-strong recursion stack :P
fun contest :)
Congratulations to winners! And to all fighting with problems. Now you can read editorials and upsolve problems. Remember that upsolving is maybe the most important thing in competitive programming. Will you be able to get all problems accepted? And you can always read e.g. my codes — for each problem you will see my code below the editorial.
Kudos to belowthebelt for preparing very nice problems!