Ok, we are working to get a simpler way than copy/pasting to put samples onto the run-test input box, but for now, copy/pasting should work well. Regarding checking correctness, we are working on doing that only when running the sample input in the statement. Checking in general would be too much help in some problems in which checking an answer may be a significant part of the problem.
Regarding checking just formatting, given that the format depends on the problem, there's not a great way to do that. There are partial ways that may work for all or almost all problems (say, grep "Case #[1-9][0-9]*: " and make sure it appears several times) but it's hard to do a partial check and not be misleading about the things you are not checking, or the ways in which the check is imperfect. The system is already lenient in a number of ways regarding formatting, so after you solved a few problems, we'd expect you to have little to no problems with it. On Sat, Feb 16, 2019 at 10:09 AM Xiongqi ZHANG <[email protected]> wrote: > I think what Guessing want is a button that you can use to run your code > against the sample input and optionally check the correctness of the output > against sample (or at least formatting). > > This may not work well thought if multiple answers are acceptable, i.e. > need special judge. > > > > > Hi, > > > > > > > > What do you mean "you are not able to test your code". You should be, > you are just not expected to be able to do it on real data, you have to > provide your own data, and results may depend on data, of course. Regarding > visibility, you can see our FAQ, but the definition of visibility only > regards to access to the judgement and scoring: judgement of visible test > will be shown to you before the end of the round, while judgement of hidden > tests will be withheld until the round is over. For neither of them we show > the test data or the actual output your code gave, only for test runs with > user-provided data. > > > > > > I hope this clarifies things. I suggest checking the FAQ for more > precise definitions of Visible/Hidden test sets and test runs. > > > > > > Best, > > Pablo > > > > > > On Sat, Feb 16, 2019 at 3:43 AM Guessing <[email protected]> wrote: > > seems odd that I am not able to test my code on the contest website > before submitting. I mean of course I can test it on my computer but I > rather test it using the platform to avoid issues where I have an extra > space printed put for example and I don't see it because it's easy to not > see an extra space when using your eyes. > > > > > > > > Also, with the new platform I am not able to see any of the tests - I am > talking about the non hidden (visible) ones. Is there something I missed? > > > > > > > > Thanks for your reply! > > > > > > > > On Friday, February 15, 2019 at 11:09:00 PM UTC+1, Pablo Heiber wrote: > > > > > Hi, > > > > > > > > > > > > > > > Notice that the inputs for test runs and real submissions are > different, so it's not unlikely to obtain different results. Additionally, > the time limit might be different (test runs have a 10 second time limit at > present, while real runs depend on the problem), which can also lead to > different outcomes, especially for problems imported from our previous > system which tend to have higher time limits. > > > > > > > > > > > > > > > Hope this helps. > > > > > > > > > > > > > > > Best, > > > > > Pablo > > > > > > > > > > > > > > > On Fri, Feb 15, 2019 at 12:18 PM Guessing <[email protected]> wrote: > > > > > I had every test fail but when I submit the code, I get 2 green V > saying I solved both the small and large data set. Tried writing google > about it and they kind of ignored it and just sent me to the FAQ. > > > > > > > > > > Is this what you have been experiencing? > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > On Tuesday, February 12, 2019 at 10:44:26 PM UTC+1, Ionelia Buzatu > wrote: > > > > > > > > > > > Why it says "WA test case skipped" when I runt it? It's fine on my > machine. Am I not parsing the input correctly? What's wrong here? > > > > > > > > > > > > > > > > > > > > > > this is from 2018 Burger Optimization exercises. It gives me the > same error for all exercises. > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > > from itertools import permutations > > > > > > > > > > > > > > > > > > > > > > def burger(): > > > > > > > > > > > output = {} > > > > > > > > > > > for repeat in range(1, int(input())+ 1): > > > > > > > > > > > ingredients = int(input()) > > > > > > > > > > > distance_ingredients = [int(x) for x in input().split()] > > > > > > > > > > > totpermutations = permutations(distance_ingredients) > > > > > > > > > > > value = 999999 > > > > > > > > > > > if len(distance_ingredients) > 4: > > > > > > > > > > > for distance in totpermutations: > > > > > > > > > > > value = min(value, (distance[0] - 0) ** 2 + > (distance[1] - 1) ** 2 + sum( > > > > > > > > > > > [(i - 2) ** 2 for i in distance[2:-2]]) + > (distance[-2] - 1) ** 2 + (distance[-1] - 0) ** 2) > > > > > > > > > > > if len(distance_ingredients) == 4: > > > > > > > > > > > for distance in totpermutations: > > > > > > > > > > > value = min(value, (distance[0] - 0) ** 2 + > (distance[1] - 1) ** 2 + (distance[-2] - 1) ** 2 + ( > > > > > > > > > > > distance[-1] - 0) ** 2) > > > > > > > > > > > if len(distance_ingredients) == 3: > > > > > > > > > > > for distance in totpermutations: > > > > > > > > > > > value = min(value, (distance[0] - 0) ** 2 + > (distance[1] - 1) ** 2 + (distance[-1] - 0) ** 2) > > > > > > > > > > > if len(distance_ingredients) == 2: > > > > > > > > > > > for distance in totpermutations: > > > > > > > > > > > value = min(value, (distance[0] - 0) ** 2 + > (distance[1] - 1) ** 2) > > > > > > > > > > > if len(distance_ingredients) == 1: > > > > > > > > > > > for distance in totpermutations: > > > > > > > > > > > value = min(value, (distance[0] - 0) ** 2) > > > > > > > > > > > output[repeat] = "Case #{}: {}".format(repeat, value) > > > > > > > > > > > # print("Case #{}: {}".format(repeat, value)) > > > > > > > > > > > return "\n".join(output.values()) > > > > > > > > > > > > > > > > > > > > > > # print(burger()) > > > > > > > > > > > > > > > > > > > > -- > > > > > > > > > > You received this message because you are subscribed to the Google > Groups "Google Code Jam" group. > > > > > > > > > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > > > > > > > > > To post to this group, send email to [email protected]. > > > > > > > > > > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-code/2931a629-fafb-453e-9a02-171b68af6dff%40googlegroups.com > . > > > > > > > > > > For more options, visit https://groups.google.com/d/optout. > > > > > > > > -- > > > > You received this message because you are subscribed to the Google > Groups "Google Code Jam" group. > > > > To unsubscribe from this group and stop receiving emails from it, send > an email to [email protected]. > > > > To post to this group, send email to [email protected]. > > > > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-code/17db3b28-08ef-46fa-a4aa-477ec8910475%40googlegroups.com > . > > > > For more options, visit https://groups.google.com/d/optout. > > -- > You received this message because you are subscribed to the Google Groups > "Google Code Jam" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > To view this discussion on the web visit > https://groups.google.com/d/msgid/google-code/4cd4b045-66eb-4e61-8d09-fbeb51870385%40googlegroups.com > . > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "Google Code Jam" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/google-code/CANa5jcC32%2B2f6_pTHhuacBOjQ%3Ddadr3nQfV30PFOZCgERGmqNQ%40mail.gmail.com. For more options, visit https://groups.google.com/d/optout.
