Betlista, thank you for your comment! And YES, I thought about that too since RDF(N,N) = 0… Still I got lost pretty fast and was, as I said, a very humbling contest… I hope I can really take some valuable insights and actually learn new things with the upcoming editorials
As for the FIRESC problem, that was based on disjoint set data structure. And I was unaware of that during the contest, but without much knowledge of graph implementation was able to get AC using hashing and stacking. There’s always a best way to approach a problem, but then there are other ways too.
So, your tester is part of your submitted code…
I solved it similarly, but I defined interface in java and set implementation in my testing only.
I had problems with flushing I guess, so I left C++ and moved to Java. I’m wondering how to write two programs that one writes to others stdin…
Not needed actually, at least for this problem. You can virtually get input from a function as if you were getting from another program!
I solved FIRESC thanks to one of the past contests problems. My point is if you keep practicing you will eventually know a lot of helpful algorithms and will gain experience.
I learned a lot here in codechef and I’m glad to say that I grew up a lot here, looking back I can see how much I have improved, in this contest I could solve 5 problems and believe it or not in the first contest I participated I couldn’t solve even 1. I know there is a long way to go but what would be the fun of achieving something without any effort, right ?
My only advice is keep practicing, never give up.
I really don’t know what you have against me, but FYI I thought it was one of the best Codechef problems I’ve seen.
Thank you very much @Bugkiller, I will definitely look into these videos when I have more time to spare
Altough atm univ is a bit more important and different things are required there…
I have nothing against you. But all my previous tries to add some tricky corner case to the problem met a strong critic from you.
@gojira: Could it be that, on the systems where your code was run, an int was larger than 32 bits ? (e.g. they had 64 bit ints) This could explain why your code reached i above 50 (as the result did not become 0 at i=34). I know this seems unlikely, but maybe it’s possible. I tried to test this behavior by submitting a simple code at several practice problems, but sizeof(int) was always 4 – but maybe there’s a different set of machines used during contests ?
I really don’t want to derail another thread, so this will be only my only further reply on the topic, but I have never and will never critique anyone for deliberately adding tricky corner cases. That’s what programming contests are all about. The previous issues were unrelated: a) solutions/editorials which tell you to solve the problem, you must use unsigned variables, which rules out languages like Java entirely, and b) when the problem author did not expect or handle all corner cases properly, which you admitted yourself for ANDOOR. Had they been intended, I would have had no problems
I should mention that I am not the author of ANDOOR.
I would think 1000 times before posting such problem.
Because of many issues with other problems I had no time to consider it properly, hence such crap
So I am not the only one with such feelings. :D. Except that I took almost 6 approaches and 6-7 days to solve the FIRESC after approx and TOTR which were tip of the iceberg…
I never thought of any algorithm to solve FIRESC but feeling ashamed now that It was something I learnt in second year of Engineering…
Dude, a topper at Codechef is expecting easier problems. Not expected! Just kidding bro, all the best.
I feel ashamed at every contest basically!! Especially because the kind of Maths used on these contests (Discrete Maths, series, graphs theory, recurrences) is all about practicing and well, also learning from editorials! There are problems where if you don’t know the concept behind them, you simply won’t solve them!! And I really appreciate having a place where I can share my feelings towards my learning curve on these contests