It's too late to get involved this year, but look for it to return at the
same time next year and use this year's schedule as an estimate.
https://code.google.com/codejam/schedule
Follow the other navigation links at the top for more information. The
brief summary follows:

Registration starts some time in March with a qualification round about a
month after registration starts.

When each contest round starts, there will be a link on the main code jam
page to participate. There will be three or four problems for you to solve.
You can write programs in any language, subject to a few restrictions you
can find in the rules - the compiler, libraries, etc. must be available for
free, with an exception allowing Visual Studio, Excel, and MATLAB. You can
use any editor or development environment.

The code must be your own - this is a solo solving competition. Freely
available software libraries are permitted.

For most problems, there will be a small input and a large input. Please
read the problem statements carefully regarding the restrictions on these
inputs - many times some solutions which work for small inputs will either
be too slow or now able to handle cases in the large input. There is also a
specified output file format your program should follow.

When you think you have a problem solved, you can click a button in the
problem to download a small input. Run your program on this input and
submit both the output file and the program through the form that appears
within the problem page; you have a 4 minute limit for this step. This will
be scored immediately as correct or incorrect. If it is wrong, you can try
again with a new small input after figuring out what you did wrong; you
suffer a 4 minute penalty in the tiebreak time for each small input you get
wrong (which is otherwise the time of your last correct submission). When
you get the small input correct, the large input becomes available. You
only have one chance for this and it will not be scored until after the
contest is over, and you have 8 minutes to submit the output.

Each input for each problem is worth a certain number of points. In the
qualification round, you have a whole day to work on it and just need to
score a certain number of points to qualify, which in my experience is
always achievable with only small inputs, so you can be certain you have
qualified before stopping. In subsequent rounds, you have only two and a
half hours, and the top so many solvers will advance, based first on the
total number of points earned and second on the tiebreak time as mentioned
above. Round 1 has 3 heats on different weekends and different times of
day, and you can compete in all of them until you qualify in the top 1000
of one of the rounds. Out of the 3000 who advance to the single heat for
round 2, the top 500 will advance to round 3.

There is also a Distributed Code Jam, for problems that must run very
quickly but distributed across 100 computers. This one has a lot more
restrictions on languages and such based on the limitations of their test
environment, but Google will run your code in their test environment to
solve the problems. If you advance to round 2 of regular Code Jam, you also
get to compete in Distributed Code Jam, so focus on the regular version of
Code Jam first.

There is a Past Contests link on the site, which allows you to try all the
problems from past contests in practice mode. In practice mode, you do not
submit your code, only the output files. Also, all outputs will be judged
immediately, and you can try as many times as you like. There is only one
small input for each practice mode problem - no different inputs after you
get one wrong. This is a great way to get started now so that you are ready
when the contests start up next year.


On Thu, Aug 3, 2017 at 1:09 PM, shyam selvaraj <[email protected]>
wrote:

> Pls explain how to take part in this contest and when to?
>
> --
> 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/dd5b780e-2d80-4f45-9f26-f77a2f2b9054%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/CAMAzhzgXa9VQveQw2KtxwhrT4%2B0RLB%3DOi8WA2Qxum51JeLG8UQ%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to