Invitation to OPC March 2026

Revision en11, by mnnit.prakharg, 2026-03-15 14:49:39
Hello, Codeforces!

Computer Coding Club of MNNIT is pleased to invite you to participate in OPC March 2026 on Sunday, March 15, 2026 at 21:00 (UTC+5:30)


oooopc

Contest Registration: Registration for the contest will open 6 hours before it begins. To participate, ensure you are a member of this group and have completed your registration.

Join CC club to be able to participate in the contest.

It is mandatory for each participant from MNNIT to fill out the Google Form provided for registration.

The problem set will consist of 7–8 problems, and participants will have a total of 2 hours and 30 minutes to complete them. The problems were authored and prepared by NPsolved.cpp, late_night_dreams, himan_8, mnnit.prakharg

Contest Rules

Individual Participation – The contest is strictly for individual participants. Any form of collaboration or discussion during the contest is prohibited.

Strict Prohibition of AI Tools – The use of any AI-based tools, including code generation or problem-solving assistants, is strictly forbidden. Any participant found violating this rule will be disqualified and removed from the rankings.

Plagiarism and Malpractice – Any form of code plagiarism, sharing of solutions, or unauthorized assistance will lead to immediate disqualification. The organizing team reserves the right to take necessary actions in such cases.

Scoring and Ranking: The contest will adopt a binary scoring system. The rank of contestants will be determined by the total number of problems successfully solved by the participant, and the total time taken to solve the problems. A penalty of 20 minutes will be added for each incorrect submission on a problem before it is solved. Problems are organized in increasing order of difficulty to provide a progressively challenging experience for participants.

NOTE: Please make sure to use fast input/output (FASTIO) in every problem. Some problems may contain large input and output, and using slow I/O methods may lead to TLE (Time Limit Exceeded) even if your solution is otherwise correct. Reference for C++, Java, Python.

Good luck & have fun! We hope to see you all participating in OPC March 2026

UPD1: Registration has started.

History

 
 
 
 
Revisions
 
 
  Rev. Lang. By When Δ Comment
en14 English NPsolved.cpp 2026-03-19 22:56:07 40
en13 English NPsolved.cpp 2026-03-19 19:47:55 930
en12 English mnnit.prakharg 2026-03-15 14:51:38 2 Tiny change: 'h 2026\n\nUPD1: ' -> 'h 2026\n\n\nUPD1: '
en11 English mnnit.prakharg 2026-03-15 14:49:39 39 Tiny change: 'March 2026' -> 'March 2026\n\nUPD1: **Registration has started.**'
en10 English NPsolved.cpp 2026-03-13 22:15:54 0 (published)
en9 English NPsolved.cpp 2026-03-13 22:06:02 4
en8 English NPsolved.cpp 2026-03-13 22:05:43 59
en7 English NPsolved.cpp 2026-03-13 22:03:01 309 Tiny change: '# Hello, C' -> '## Hello, C'
en6 English NPsolved.cpp 2026-03-13 21:08:08 74
en5 English NPsolved.cpp 2026-03-13 20:56:08 99
en4 English late_night_dreams 2026-03-13 20:54:28 60
en3 English NPsolved.cpp 2026-03-13 20:53:35 93 Tiny change: '1=176)\n\n[Here It is](/predownl' -> '1=176)\n\n(/predownl'
en2 English NPsolved.cpp 2026-03-13 20:49:42 81 Tiny change: '176)\n\n\n**Co' -> '176)\n\n\n\n**Co'
en1 English NPsolved.cpp 2026-03-13 20:44:56 2901 Initial revision (saved to drafts)