Sort 12 Discussions, By:
Please Login in order to post a comment
can someone explain the variable "m"?
Click the "Load more comments" link below, someone asked about it 14 days ago. Basically you don't have to store all the digits of the final answer; e.g. if m=1000 you only report the last 3 digits of the answer.
My code works properly for the first 13 test cases, but times out for the next few. The last few are listed as "abort in 0s" so I guess it doesn't bother running the last ones if a bunch of earlier ones fail due to timeout, right?
In thouse cases the result is very huge so you sould review the data type in witch you save you result
I think you mean "the intermediate calculations tend to be very huge" since the final result is calculated mod m
I found this problem. In original you must find the answer with given input (32, 10), and it is just back to back with time complexity, O(num_of_vars^2). But here we have stricter requirements. So, can you share an idea of how to solve it?
This link lists the environments used for running solutions. Do these apply to contests as well?
(I assume so, but would like to confirm either way)
can anyone pls explain me the qustion
what is criteria for difference in ranking when score is equal? Why not differentiate in score itself?
Can we use a block(configuaration) in layer(i), in another layer that is not immediate to layer(i).
i am unable to get the logic to solve this problem so anybody is there for help to get the logic of this problem to solve
We can help clearify the problem, but as this is competing, it's your own job to find the logic and work towards a solution.
i am not getting the logic. how to solve it
break the problem into subproblems, solve the individual subproblems, and combine the partial solutions to get the whole solution. what programming techniques would apply?
What maybe be the reason for my code to fail for some inputs and work fine with other?
Obviously you have bugs in your code. Use the custom inputs feature to test your code with multiple inputs and see if you can find cases where the answer is wrong. Then debug your code.
For instance you may be using the wrong data structure -- the data structure you're using may work properly for small inputs, but when you're given large inputs it may use more memory than is available.