Java I/O is really slow. I can’t help it. I can’t memorize a huge template for INOI.
Yeah that’s probably why they gave you the 110.
Just to be clear, had they already given you 110, or did they only re-evaluate once you told them that your solution works within the time limit?
“They said they checked my algorithm and its OK”
I’m guessing they looked at his program and probably realized it timed out only due to Java I/O and gave him the score later.
@superty, probably, or maybe they had already looked at the algorithm earlier and given him 110. That would conform with our assumption that they actually read most of the programs.
When I checked on the grader it was 75 so I immediately emailed them . They replied that they had checked and it was OK. They also said , “As things stand , I should qualify.” . So I guess my score is 110.
Did anyone else get a couple of random TLEs in Special Sums because of slow I/O?
I rather stupidly forgot to set stdio sync to false :/. By any chance, are they considering that for reevaluation?
They are. Slow I/O shouldn’t lead to any less marks, as long as your algorithm is correct.
They checked my algorithm for P2 .They found it “OK” so they increased my score to 110. I had the same problem. 
@idraumr , @animesh_f Thanks! I currently have a 10 
because I messed up problem 2 completely by mixing up two variable names. Wrote them an email, hoping for a 100 at the very least.
Please tell us if they give you any marks for your second problem.
Sure. But I doubt they would, since my code for the second problem is pretty much unreadable with the pre-computations and stuff.
Well, just in case they do.
In periodic string, in JAVA, it is showing TLE(execution timed out(wall clock time limit exceeded)) and the execution time is 5.6s and 5.8s for the first two input data of subtask 4.But when I ran it on my computer each of those two data sets are taking approximately 1s. Will I be given marks for subtask 4?
PS: I used System.currentTimeMillis() for timing.I think there is something wrong with Special Sum also so I am waiting for test data to be downloaded(currently showing 5 hours left) before I finally write for reevaluation.
By the looks of the previous answer, this is a common issue.
Do tell us if you get more marks on reevaluation.
I didn’t use any fast I/O but still got 100 in special sums.
Yeah, once I fixed my mistake I got 100. cout/cin. No fast IO.
@idraumr For periodic string, my solution was “deemed to be” 100/100. I am currently waiting for my response of special sum.
I had the exact same issue with the same problem (I also code in JAVA) and I wrote to them. They checked my algorithm and they made it 100 after seeing it. Slow I/O error is unfair for JAVA 
Ok guys, as all of you would have seen your scores, and most of you finalised it,
lets try to approximate the cutoff:
Please choose your score:
INOI score
(vote only after you have finalised your score)
1 Like