Informação geral
Tipo de concurso: ACM-ICPC
Tipo de concursante: Apenas um
Tipo de acesso: Público
Tipo de registo: Registo livre
Padrão para concurso virtual: No
Penalização por cada envio rejeitado: 20
Tempo congelado (tempo restante com posições congeladas): 30
Tempo muorto (tempo restante sem sentenças): 10
Linguagem de programação: C   C++   C++11   Java  
Mostrar problemas a todos: Sim
Mostrar sentenças aos concursantes: Sim
Mostrar sentenças a todos: Sim
Mostrar posições aos concursantes: Sim
Mostrar posições a todos: Sim
Mostrar estatísticas aos concursantes: Sim
Mostrar estatísticas a todos: Sim
Medalhas de ouro: 1
Medalhas de prata: 1
Medalhas de bronze: 1
Regras específicas Please beware of reading carefully those general clarifications:

You don't need to register in the contest: the registration in the contest is effective with the first submission. To participate you need to have an account in the Caribbean Online Judge (COJ - This competition is part of the MPC-TLJ Mechanism of Selection and Training of Teams (for more information see the c clause of the FIRST STAGE). A Participation List will be made when the contest starts and for those eligible UCI contestants competing on-site (from the Labs 101 and 202 of the Academic Building No. 4). If you have any question regarding to the MPC-TLJ Mechanism, please feel free to ask on (our impersonal account).

The problem-setters and testers for this contest are the following:
  • Guillermo González Jiménez (Team Leader, UCI-Cuba, Student, WIL, gjimenez{at}estudiantes{dot}uci{dot}cu)
  • Oreste Abrahan Nillar Cambara (UCI-Cuba, Student, Oreste, oanillar{at}estudiantes{dot}uci{dot}cu)
  • Reinier Rodríguez González (UCI-Cuba, Student, Spartan, rrgonzalez{at}estudiantes{dot}uci{dot}cu)
  • Gregorio Ferrer Córdova (UCI-Cuba, Professor, gregor, gcordova{at}uci{dot}cu)
For clarifications, we strongly recommend to write in English! And make sure to select the proper Subject (Problem title) before sending the clarification. Don't send the same question several times, all clarifications will be answered by the human judges as soon as possible. A "No comments" response will be delivered if the answer to your question is included in the problem statement.

Do not use the %I64d specifier to read or write 64-bit integers in C++. It is recommended to use cin, cout, streams or the %lld specifier instead.

If the problem statement doesn't specify the number of instances (tests cases) or when to stop reading, this means that you should read until you reach the End Of File (EOF). Also you don't need to process tests cases one by one, although it's possible. You can read all the input first, then process the data, and finally output responses for all instances. Of course, take into account that all this should be done within the limits of time and memory for the problem.

Always respect the problems' output format: this is the main reason for Presentation Error (PE). Beware problems in which the use of real numbers is needed in the written solution. The point '.' is the most commonly used decimal separator in almost all problems involving real numbers in their datasets, therefore perhaps you need to change the locale configuration; formatting the output numbers for using '.' instead of ','.

Also, remember that your program is tested with more datasets than those that appear in the "Sample Input" and "Sample Output" sections: try to think of extreme cases to test your program before submitting a solution. The fact that your program solves the sample input dataset correctly doesn't mean that it solves all datasets correctly.

To submit a code to the judge, select the proper problem and language before sending. Otherwise, you will probably get an unexpected response.

If you are submitting a file (instead of pasting the source code in the text area) to the judge, the filename is irrelevant no matter the language used. You must howeveer respect the common extension of the language you selected (.c for C, .cpp for C++, .cc for C++11, and .java for Java).

Please, read the FAQs for other common questions, like code formats, answers of the judge, etc.

If you have any question regarding to the COJ system, please feel free to ask on (our impersonal account).