where is this wrong ?
i had the exact same solution and got wrong answer!
I also had the same logic but it gave me WA everytime!!!
it gives WA for all solutions in python inspite of correct here,can anybody explain why?
Yeah, it’s very strange! I also gave the same solution in C++. And every time it gave WA. At last my partner tried it in JAVA and it worked! Probably, the contest was a bit language biased.
same problem faced…
Exactly faced the same problem.Its very sad and frustrating,when you submit with full confidence and get WA,and after viewing same kind of AC solutions, frustration increases more.Really, time-wasting. Codechef must take some action to prevent such kind of fuss.@admin @dpraveen
yup… faced the same problem…
Indeed its a contest for high school students…
it’s not meant for computer science students at all…
That too… somany mistakes in framing the problem statements exactly…
fedup with this…
And waste of time for 2 hrs unnecessarily…
(-1,-5) did not even satisfy the radius 5. Terrible competition.
Somebody please explain why this happened.
It is so strange.
What is wrong in this solution?
your solution prints available or non available after it encounters each pair of co=ordinates. The problem statement asked to check for availability from a set of co-ordinates.
I faced the same problem in java, same logic but only got WA
The reason is overflow happens in int while it does not in long long int. As the value of x and y are in the range of 10^4 x^2=10^8 which does not fit in int but does in long long . I believe the test cases have been given keeping the values of x and y and probably k as int or long hence the solution with int passed while the one with long long did not .
However this is just my assumption and there could be some other reason also.
Upvote and accept my answer if you find it to be correct.
yeah… u r ryt… but long int is enough for that which could hold upto 10^9 @sdssudhu
General mistakes in this types of questions are:
- **Using wrong data type** , for instance here Xi and Yi lies in [ -104 , 104 ]. It is quite obvious that Xi2 and Yi2 will lie in [ 0 , (104)2 ] i.e. [ 0 , (10)8 ] now this value can't be hold in an int datatype hence is to be stored in **long int** or **long long int** .
- **Wrong output format** , since codechef only gives WA or AC for a compiled solution ( neglect runtime error ) , users often mistake wrong output format with WA. for instance, here in this question out was supposed to be print in one line for each test case regardless of the number of cars but of the availability of the cars. but some of users were printing availability for every cars.
Just make Xi and Yi of type int and you will get AC.
After observing the pattern of wrong answer I realised that somehow the author of the question had made some mistake while setting testcases. The values of Xi and Yi are given in the range of long long or long but user he has set data accoring to int eg. (100000)2 when taken in int gives a negative value but when taken in long long gives positive value and this whole thing is generating wrong output.
Problem link : https://www.codechef.com/problems/UEMP01
Solutions with different combinations of data types and their verdicts : https://www.codechef.com/status/UEMP01,radeonguy
if we are taking square root of (x^2 + y^2) and comparing it with radius(k)… then it is giving WA verdict
but if we do compare (x^2+y^2) with square of radius (k^2)… it is giving AC verdict…
the difference is… in the 1st submission, i’ve done comparison sqrt(xx+yy) <= k …
in the 2nd submission, i’ve done comparison (xx+yy) <= (k*k)…
@kishore1 This is due to the inacurracy of results returned by the sqrt function for large inputs.For eg if the input is large and the sqrt function returns the value 10000.0001(inaccurate value) instead of 10000.0000(actual result) and the radius is 10000 then your program will output “Not Available” instead of “Available”.
I think something is wrong with the testcases. The constraints mention that coordinate values are between -10^4 to 10^4 but it is probably not followed. The author might have added the testcases where Xi is around 10^5 or greater and generated the output for those testcases using int data type. This explains why long long int in C++ fails. Similar case with the languages supporting big integer.