<aside> πŸ‘¨πŸΎβ€πŸ³ Written by Um_nik

</aside>

<aside> 😈 Also your proposals will be reviewed by Um_nik, so... tread lightly

</aside>

So, you came up with a problem and decided it will be a great fit for one of the CodeChef monthly contests. Good! You might want to read the doc describing the bigger picture of the whole journey of the problem from an πŸ’‘idea to its rightful place on codechef.com:

How to set a problem in CodeChef monthly contest (step-by-step)

This doc focuses on the second step in this journey.

Technically, nothing can be easier: fill the form. But from my experience I can give you several hints and point out some common mistakes people do. The list is not comprehensive and can (and probably will) be expanded in the future. Let's go!


First we will want to know some information about you, mainly your email address. I hope you can answer that without my help. Let's now turn to the more interesting fields.

Problem Title

Please write one. Something that will identify your problem. You don't have to guess the title it will eventually have in the contest, but name it somehow relevantly for now.

Pre-requisite(s) required to solve the problem

Kind of a list of topics used. I don't really care what you will write here, so let's move on.

Problem's expected difficulty

It's not very important what you will choose here. I like when people can reasonably estimate the difficulty of their problem, it gives additional karma points. But I won't hold against you the fact that you estimated your problem wrong. I will re-estimate the difficulty during the review, and it can be changed later, so don't worry about that.

You can overestimate the difficulty because you didn't notice some simpler solution, that's understandable. Also in the process of the review the problem can change and with it the difficulty can change. And you can simply don't know what the difference between Cakewalk and Easy in CodeChef system! That I can (try to somehow) fix.

Vague correspondence to Codeforces positions and numbers:

In relation to CF

Usual round composition:

5-problem div2: Cakewalk β€” Simple β€” Easy β€” Easy-Medium β€” Easy-Medium/Medium

6-problem div2: Cakewalk β€” Simple β€” Easy β€” Easy/Easy-Medium β€” Easy-Medium β€” Medium

5-problem div1: Easy β€” Easy-Medium β€” Easy-Medium/Medium β€” Medium/Medium-Hard β€” Medium-Hard

6-problem div1: Easy β€” Easy-Medium β€” Easy-Medium β€” Medium β€” Medium-Hard β€” Medium-Hard

I'm not talking about Tie-Breaker (Challenge) here. I think you understand what you are doing if you have chosen that one.

Problem Statement

The most important part. You probably want me to understand what your problem is about. Focus on achieving that goal.