anup.kalbalia's blog

By anup.kalbalia, 12 years ago, In English

CodeChef invites you to participate in the Silver Jubilee August 2012 CookOff at http://www.codechef.com/COOK25

Time: 2130 hrs 19th August 2012 to 0000 hrs, 20th August 2012 (Indian Standard Time — +5:30 GMT) — Check your timezone.
Details: http://www.codechef.com/COOK25/
Registration: Just need to have a CodeChef user id to participate. New users please register here
Problem Setter: Shilp Gupta.
Problem Tester: Hiroto Sekido.
Problem Editorialist: Shilp Gupta.

It promises to deliver on an interesting set of algorithmic problems with something for all.
The contest is open for all and those, who are interested, are requested to have a CodeChef userid, in order to participate.

  • Vote: I like it
  • +4
  • Vote: I do not like it

»
12 years ago, # |
Rev. 3   Vote: I like it +49 Vote: I do not like it

I think that it must be unrated.

  • »
    »
    12 years ago, # ^ |
      Vote: I like it +8 Vote: I do not like it

    unrated +1. I could not submit a correct solution about 45 mins, because I could not choose a language.

  • »
    »
    12 years ago, # ^ |
      Vote: I like it +16 Vote: I do not like it

    +1. I waited for 35 minutes for a verdict only to get a CE that I could fix in no time.

    • »
      »
      »
      12 years ago, # ^ |
        Vote: I like it 0 Vote: I do not like it

      I don't really think that the contest should be unrated, but I had the same problem (my code got pasted twice into the submission window and it took me almost half an hour to find out). So, I wrote to the admins with a request to adjust my time penalty; I would still understand if the request had been denied, but I didn't even get a response.

»
12 years ago, # |
Rev. 2   Vote: I like it +12 Vote: I do not like it

There was an issue with our online judge that we fixed during the contest and stopped the contest for 15 minutes. We sincerely apologize for the same. We had also extended the contest by 20 minutes for the loss of time. Making the contest unrated will be a bit harsh on the problem setters and the tester as it was no fault of theirs. While we understand the problems faced by your guys, we tried our best to resolve it asap. We shall ensure that this is not repeated.

»
12 years ago, # |
  Vote: I like it +3 Vote: I do not like it

Why command in.close() in Java leads to Run-time Error(NZEC)?

boolean oj = System.getProperty("LOCAL") == null;
Reader reader = oj ? new InputStreamReader(System.in) : new FileReader("input.txt");
Writer writer = oj ? new OutputStreamWriter(System.out) : new FileWriter("output.txt");
in = new BufferedReader(reader);
tokenizer = null;
out = new PrintWriter(writer);
solve();
in.close();
out.close();

Without in.close() it gets OK.