I think this idea is very cool. The token can be in the format: [Problem code]-[small/large]-[# of tries, starting with 0]
> One simple, if perhaps unaesthetic solution: > > > The first line of the input file contains a unique token (perhaps random, > perhaps text identifying the file, or whatever amuses the Code Jam > developers). The number of test cases is then on the second line of the input > file. The first line of the output file must contain the unique token from > the corresponding input file. > > > A possible refinement: if the input file's token is FOO, then the output's > first line must be "FOO output" or some such. Thus the input and output files > have different first lines, so one can't submit the input file. Although > these two files can usually be distinguished by their format, anyway. > > > On Mon, Apr 17, 2017 at 12:48 PM, 'Pablo Heiber' via Google Code Jam > <[email protected]> wrote: > > Hi everyone, > > > Thanks for all the suggestions. We'll experiment with doing different number > of cases within inputs of the same problem. However, please be advised that > there is no guarantee to that, so please try to be careful and upload the > right file. Within a problem, it's probably wise to delete or move any output > files after uploading them, so you don't grab them by mistake. > > > That being said, there is still the worry of people re-uploading their first > Small attempt when attempting for the second time, and none of these > suggestions address that use case. Moreover, since the number of attempts can > be really big, using the number of test cases as a check for that one > requires too much variance on the number of test cases. It's one thing to go > from 100 to 99, and a different thing to use 90-110, or even longer, because > the number of test cases you get will have too much of an impact in the > running time. And we would especially not want that within attempts to the > same dataset. > > > Anyhow, we won't be making any large-scale changes mid-season, because > there's already an expectation of rounds being a certain way, but we'll > investigate better options for our following seasons. Feel free to keep > brainstorming ideas, though, there's never too much of those! > > > Best, > Pablo > > > > > On Mon, Apr 17, 2017 at 10:26 AM, Wing-chung Leung <[email protected]> wrote: > On Monday, April 17, 2017 at 12:37:42 AM UTC, Xiongqi ZHANG wrote: > > > First of all, the input file always begin with the number of test cases. > > > > > > Secondly, the submission page will always stop you from submitting answer > > if the number of test cases in input/output file mismatches. > > > > > > So it will not create any burden to the user at all. It just work. > > > > > > > On Thursday, April 13, 2017 at 11:21:23 PM UTC, Xiongqi ZHANG wrote: > > > > > One easy option is to use different test case number for small/large > > > > input. > > > > > > > > > > So at least you will be warned that the test case number does not match. > > > > > > > > > > > > > Possible... but that would add some burden to the user unless the test > > > case number is specified in the input file. > > > > er... You're right. I've misread your message. Sorry. I thought that the case > numbers from #101 to #200. What a blunder. :-( > > > > Anyway: I think that the number of cases can vary all from 90 to 110, so you > have a unique number per input in the same round. e.g. A-small = 90, A-large > = 91, B-small = 92, etc. > > > > And indeed this is even easier than to check again previously validated > inputs. > > > > -- > > 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/0a53823e-4c84-48e1-8a1a-756dddfae47e%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/CANa5jcD2c-_neL5rTfZH7H6xihT-dkn_GAnRiYScm7XuOaYyoQ%40mail.gmail.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/426f8b6f-0db7-4902-867e-4fd793c70fb8%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
