Tutorial is loading...
Tutorial is loading...
Tutorial is loading...
Tutorial is loading...
Tutorial is loading...
№ | Пользователь | Рейтинг |
---|---|---|
1 | tourist | 4009 |
2 | jiangly | 3821 |
3 | Benq | 3736 |
4 | Radewoosh | 3631 |
5 | jqdai0815 | 3620 |
6 | orzdevinwang | 3529 |
7 | ecnerwala | 3446 |
8 | Um_nik | 3396 |
9 | ksun48 | 3388 |
10 | gamegame | 3386 |
Страны | Города | Организации | Всё → |
№ | Пользователь | Вклад |
---|---|---|
1 | cry | 164 |
1 | maomao90 | 164 |
3 | Um_nik | 163 |
4 | atcoder_official | 161 |
5 | -is-this-fft- | 158 |
6 | awoo | 157 |
7 | adamant | 156 |
8 | TheScrasse | 154 |
8 | nor | 154 |
10 | Dominater069 | 153 |
Название |
---|
Is there a specific reason for having N = 106 in the 3rd problem ? This makes it almost impossible to solve it in Java.
I had 2 submissions with 100% idential complexity, number of iterations, the one in Java gave me TLE, the one in C++ gave me AC.
Good day to you,
well the reason might be (in my humble opinion) to get rid of O(Nlog(M)^2) solution (I've tried it and got TLE).
I know it is naive, yet if you (in each binary-search body) copy all possible elements and sort them (with some basic sort algorithm) you will get such complexity (and also TLE :P)
So that is what I imagine as reason
Good Luck & Have Nice Day ^_^
Problem C, and not D
Oh apologies, I simply can't read :'(
In this case, nothing reasonable came to my mind :/
For problem D, when n = m =10^6 and t =10^7, O(n(logn)^2) is really same as O(tlogm). But to my surprise, the former get TLE!
I wrote dfs using my own stack and got accept in 1 second in Java. But constraints are really bad :(
I totally agree with you!
My exactly the same algo (O(N)) got TLE in Java. Is it possible to get tests e.g. Test-12?
In problem A, it seems OK to have a trailing space at the end of a list of numbers. Is this standard in Codeforces (i.e., trailing spaces are ignored)?
By the way, I LOVED, LOVED problem A. It looked sooo clear and simple but I just couldn't wrap my brain around it until the very end. It was really infuriating!! And even then I didn't end up with the intended solution which was really beautiful.
"Implementation problems" are often just a bunch of boring details. This one was a real gem!
I think this solution is wrong but it passed.
I've already mentioned it here.
For D question,
I have an N *Ackermaninverse of N solution i feel. which is based on pure simulation with greedy.It is working because of poor systests or is it fine(Can anyone say what is the exact complexity of my solution)
code here
so weak tests(
Another solution for problem D: - First, store all the cartons you can buy at the store in a vector and sort them non-increasing.
Then, iterate all the possible dates from the biggest one down, store a value to keep track of the amount of cartons that needs to be drank in the current date. Let's call this value cur
If at a certain moment, cur > 0, that means we have drank enough from this day forward. Update our answer using the vector of milk cartons. This can be done by using a pointer.
Therefore, our total complexity is O(N log N + t)
For more details, here is the code
I got surprised to know that the intended solution uses the binary search. Many people actually did solve D using binary search.
My solution is O(n log n + m log m), due to the costs of sorting two input arrays. The solving part is in fact greedy and linear O(n + m).
The short description of the solution is as follows:
Link to the Java code
Hello, Can somebody please explain why my solution here receives a TLE, even if the solution complexity is the same as in the presented solution? Thank you :D
because you used cin without sync_with_stdio(false) and there are too many inputs. I added it to your solution and got accepted.
http://codeforces.me/contest/767/submission/24792608
Thank you, I didn't know it could make such a difference :D
maybe scanf for larger data is prefered?
yay! :) Then I can consider my O(107 + m) solution for D pretty good. :)
Solution for B: ~~~~~ ~~~~~
So easy...
Can anyone help me understand why my solution to problem D is getting TLE???. I am pretty sure complexity is O(10^7+n+m). Shouldn't it get accepted???
My solution
Please help me.....
When dealing with large input size with C++, consider desyncing the IO stream by "ios_base::sync_with_stdio(false);", or use printf/scanf to improve IO time.
Wonderful!!!!!! Very much thank you.
Could you please explain it to me why and what happens by adding above statement in code??? I haven't came across such thing till now. Hope I don't sound stupid....
Hello, could someone write more detailed explanation of C problem, I still don't understand how the second case works, even though I took a look at a couple of solutions and read the editorial.
Any help would be greatly appreciated, thanks!
The first sample in the problem is illustrating the second case, which v1 = 1 and v2 = 4. As you can see, neither v1 nor v2 is the ancestor of other. Also, s1 = s4 = 5 = x / 3. You can take a look at the explanation below the statement.
Can somebody please help me in question C.I have created a tree and used recursive calls to find sum.Implementation is O(n) but still it gets time limit exceeded in Testcase 12. Please check my solution and tell me the problem please. Code is with proper comments. Thanks http://codeforces.me/contest/767/submission/24804939
Try changing all cin/cout with scanf/printf ...
See my these two submissions -
24812029 TLE in test 12
24812043 AC after using scanf/printf
:)
The solution is much more simple that the author's. Do DFS from root node, and for every subtree, can calculate the total heat using regular tree DP. Then, when returning the value, if the total heat of subtree is equal to total heat of whole three / 3 then set to 0 in order to avoid double counting. Code explains the concept much better than words, in my opinion.
Code: 24764409
Magical Solution! :D
In problem C, Both cases can be handled by this —
While calculating sub tree sums, If you find a node with sub_tree_sum == sum/3 then do not add this sum to it's ancestors :) This will solve the first case as well as second case.
Now you just need to find just 2 such nodes :) Which can be done while calculating the sums. :) Needs ~10 lines of code :)
See this code — 24812043
In problem C, Both cases can be handled by this trick —
"While calculating sub tree sums, If you find a node with sub_tree_sum == sum/3 then do not add this sum to it's ancestors :D"
This will solve the first case as well as second case.
Now you just need to find just 2 such nodes :) Which can be memorized while calculating the sums. If if we can't find at least 2 such nodes then there is no solution.
My Code — 24812043