唔 神题一道 大家感受一下

1873. GOV Chronicles

Time limit: 0.5 second
Memory limit: 64 MB
A chilly autumn night. Well wrapped up in a coat, a man is rapidly walking
along a gray street. This is the Tradition Keeper of the ACM club in Ural
State University. Drizzle and dull sky have always turned him
nostalgic. And here we go again, the Tradition Keeper is bringing back the
memories of distant past when Ural Federal University wasn't yet existing,
and the story of Team.GOV was only starting. Indeed, this story deserves
to be preserved for descendants. However, the details are slipping from
the Keeper's mind and he seems to need an archive.
4 Turgeneva st. The sixth floor, home Department of Mathematics and
Mechanics where the Keeper himself has been studying a long time ago. Long
corridors, narrow light bars on the floor, dark corners and eventually an
office with ACM archive. The Keeper opened the door and found himself in a
cramp room with numerous racks. Dozens of boxes and piles of paper are
dumped near the walls. On one box three letters glittered with gold — GOV.
The Keeper stepped to the box, drew a heavy file and opened it. On the
first page in the right upper corner there was a photo of a smiling young
man with curly hair and a subscript: “Vadik Kantorov, the permanent
captain of Team.GOV”.
Right after Vadik had entered University he played a few tricks and got into
the half-ready team of Alex and Misha. Alex had been a bright
programmer even he was a schoolar and so troubled the ACM old-timers. Thus, Alex
was ready to name the team: “Alarm”.
So the Vadik's ACM-career began. The team existed during a year.
The first battle was the Ural SU Championship where Alarm
took only the fifth place and allayed the veterans' fear. Next
contest was the ACM ICPC subregional contest. The team played slightly better
and took the seventh place out of all teams from Ural region, and the
third out of teams from Ural SU. Alarm became the third freshmen
team in the Ural SU history to qualify for the regional contest in St. Petersburg.
Unfortunately, on the regional contest the team scored 86th and broke the
record of lowest position of Ural SU teams. It
was a hard hit for the team. The choice had to be made: practice a lot,
leave programming contests or keep performing poorly.
Putting back the decision, the team participated in the Ural Championship,
and scored 19th of all teams and 5th of Ural SU teams. That very moment it
became clear that the line-up had to change. However, before the Ural
Championship Alarm had applied to the Tatarstan Championship where the
team's final battle took place. The team could not even solve a half of the
offered problems and did not make in the best ten teams (11th place). On
the way back in a train it was decided that Misha had to quit the team.
In the new season the team needed a new name. Here the preamble is
completed and the story of Team.GOV commences. The team consisted of two
members having little experience and even less success. A new name was
defined — Team.GOV. After long considerations Vadik figured out that the
team missed a strong mathematician. Sasha who had been Vadik's high school
friend was picked to fill this role. With Sasha's appearance everyone felt
that everything was going to run smoothly.
The time of Ural SU Championship came, the autumn of 2008, second
university year. In unclear circumstances Sasha has not come to the
contest, but even in that case Team.GOV was second best of Ural SU teams.
One-year experience paid off! Sasha did come to the subregional contest
but the team reached only 14th place and did not qualify for the regional
contest.
Luckily, Ural SU as the host of the subregional contests has a right to
send one extra team to the regional contest. After long negotiations
Team.GOV could make it to the regional contest but with a sudden change
in the line-up — Ivan B. came instead of Sasha. The replacement turned
out to be fruitful — 76th place (+10 to Alarm's achievement).
After returning home Ivan B. found another team, thus Team.GOV had to fix
the line-up again. Nikita was invited as the third player for the Ural
Championship. On the qualification contest Vadik, Nikita and Alex played
very well: the team scored second of Ural SU teams.
Truly an astounding success!
Being very enthusiastic Vadik and Nikita came to the Ural Championship.
For some strange reason Alex did not come. The team performed very poorly
yet another time — 25th place of all teams and 5th of Ural SU teams.
Nikita was not satisfied with such attitude and Team.GOV became only two players
again — Alex and Vadik. What a curse! The team started to search for the
third player.
And the next season came — it's been two years since Vadik entered Ural
SU. The search for the third teammate was completed successfully. Senior
student Fedor was very experienced and had been practicing since 9th
grade of high school. Bright future was ahead of the team.
The curse was over and Team.GOV played three official contests
with the same line-up. The team scored 12th on the subregional contest,
safely advanced to the regional, and then took the third place on the Ural
SU Championship.
The regional contest in St. Petersburg yielded a diploma and the 61st
place, which was +15 to the previous year's position.
Having returned from St. Petersburg, Team.GOV participated in a unique
competition of ACM ICPC veterans and current teams — Battle of
Generations. Sadly, Alex couldn't come but team figured it out — Ivan K.
came to the rescue and replaced Alex.
Alex wasn't keeping fit: no practice, light attitude to contests — Vadik
began to look for a replacement. Nikita accepted the invitation cheerfully
once he heard of Alex quitting the team. The first contest after his
return to Team.GOV was qualification for the Ural Championship.
Suddenly Vadik had some urgent business in Europe, so Fedor and Nikita
participated without him. They performed quite well and solved as many problems
as the leaders did. As a result, the team got the third place and
qualified for the Ural Championship.
The Ural Championship brought a new grief: 25th place out of all teams,
and 4th out of Ural SU teams. Fedor and Nikita couldn't hold the nerves,
and Vadik had to look for new teammates all over again.
The fourth and the last year of university. Vadik wanted to put an end to
his ACM-career and he needed a new team. The veterans recommended to take
young and promising Den. Vadik conducted a little test, and Den was taken.
Only a few days were left before the Ural SU Championship, almost all
the teams were formed, while Vadik was still answering his eternal
question — where to get the third team member? Accidentally he found
that Egor was looking for a new team after his previous team broke
apart. A new line-up
of Team.GOV was born.
On the Ural SU Championship Team.GOV failed again and got only 5th place.
Subregional contest wasn't successful as well — 9th place out of all
teams and 4th out of Ural SU teams. Ural SU got an extended quota and
Team.GOV was going to St. Petersburg again.
Before St. Petersburg Team.GOV needed a serious practice session.
All-Siberian Olympiad was a perfect shot. Team.GOV went to Novosibirsk and
discovered again how weak they were: 39th place out of all teams and the
worst performance out of Ural SU teams. So the guys set out to St.
Petersburg with great leisure plans. Well, taking part counts no less than
victory!
On the regional contest, surprisingly for the coaches, Team.GOV scored
five problems in the first four hours and was quite high ranked. After the contest the coaches
discovered that the team scored not only the sixth problem but also a
seventh one. The result — 26th place (+35 to the last year's position)
and a second grade diploma. Team.GOV finally reached success and glory.
The road back home was ahead.
The spring, Team.GOV traditionally broke up. Vadik wanted to do something
fancy, it was his last contest after all. Vadik invites his Chinese girlfriend
Xiaohong. The
third invited teammate unfortunately didn't come, so on the last minute
Vadik took Vitaliy (medal winner of ACM ICPC World Finals) for the Game
Tournament before the Ural Championship. Unfortunately, Vitaliy could not participate in the main
contest, so Vadik took Sasha as an old friend. This was the last contest
of Team.GOV.
The Tradition Keeper scratched his head: in how many Alarm / Team.GOV
contests has every team member participated? Vadik had always told that
Misha is the member number zero, because he had played in Team.GOV before
the team got its name. Vadik is indeed player number one.
There's a tricky case with Vitaliy: of course he hasn't taken part in any
Team.GOV contest, Game Tournament shouldn't be counted. But he definitely
deserves to be included in the history of Team.GOV, because he is an award winner
of World Finals and a valuable player in general.
The Tradition Keeper meticulously listed all the members of Team.GOV.
(Misha — 0, Vadik — 1, Alex — 2, Sasha — 3, Ivan B. — 4,
Nikita — 5, Fedor — 6, Ivan K. — 7, Den — 8, Egor — 9,
Xiaohong — 10, Vitaliy — 11). He counted that a number zero has played
for 5 times (because exactly 5 contests were played by Alarm). And a number
one participated in 20 contests.

Input

The only line contains an integer from 0 to 11 — the number of Team.GOV player.

Output

Output the number of contests that a given member played in the legendary
team. All contests must be counted but the Game Tournament before the Ural
Championship.

Samples

input output
1
20
11
0

Problem Author: Mikhail Rubinchik
Problem Source: Ural Regional School Programming Contest 2011

 #include<iostream>
#include<string.h>
#include<stdio.h>
#include<ctype.h>
#include<algorithm>
#include<stack>
#include<queue>
#include<set>
#include<math.h>
#include<vector>
#include<map>
#include<deque>
#include<list>
using namespace std;
int main()
{
int n;
scanf("%d",&n);
int a[]={,,,,,,,,,,,};
printf("%d",a[n]);
}

URAL 1873. GOV Chronicles的更多相关文章

  1. URAL 1881 Long problem statement

    1881. Long problem statement Time limit: 0.5 secondMemory limit: 64 MB While Fedya was writing the s ...

  2. URAL 1728. Curse on Team.GOV(STL set)

    题目链接:space=1&num=1728" target="_blank">http://acm.timus.ru/problem.aspx?space= ...

  3. hdu 1873 看病要排队(优先级队列)

    题目链接:http://acm.hdu.edu.cn/showproblem.php?pid=1873 题目大意: 三个医生看病,病人排队看病,病人有优先级,优先级高的提前看病,同样的优先级按先后.I ...

  4. 后缀数组 POJ 3974 Palindrome && URAL 1297 Palindrome

    题目链接 题意:求给定的字符串的最长回文子串 分析:做法是构造一个新的字符串是原字符串+反转后的原字符串(这样方便求两边回文的后缀的最长前缀),即newS = S + '$' + revS,枚举回文串 ...

  5. ural 2071. Juice Cocktails

    2071. Juice Cocktails Time limit: 1.0 secondMemory limit: 64 MB Once n Denchiks come to the bar and ...

  6. ural 2073. Log Files

    2073. Log Files Time limit: 1.0 secondMemory limit: 64 MB Nikolay has decided to become the best pro ...

  7. ural 2070. Interesting Numbers

    2070. Interesting Numbers Time limit: 2.0 secondMemory limit: 64 MB Nikolay and Asya investigate int ...

  8. ural 2069. Hard Rock

    2069. Hard Rock Time limit: 1.0 secondMemory limit: 64 MB Ilya is a frontman of the most famous rock ...

  9. ural 2068. Game of Nuts

    2068. Game of Nuts Time limit: 1.0 secondMemory limit: 64 MB The war for Westeros is still in proces ...

随机推荐

  1. Android Framebuffer介绍及使用【转】

    转自:https://www.jianshu.com/p/df1213e5a0ed 来自: Android技术特工队 作者: Aaron 主页: http://www.wxtlife.com/ 原文连 ...

  2. Mysql 监控性能状态 QPS/TPS【转】

    QPS(Query per second) 每秒查询量 TPS(Transaction per second)每秒事务量 这是Mysql的两个重要性能指标,需要经常查看,和Mysql基准测试的结果对比 ...

  3. 七、springcloud之配置中心Config(二)之高可用集群

    方案一:传统作法(不推荐) 服务端负载均衡 将所有的Config Server都指向同一个Git仓库,这样所有的配置内容就通过统一的共享文件系统来维护,而客户端在指定Config Server位置时, ...

  4. SpringMVC 返回JSON数据的配置

    spring-mvc-config.xml(文件名称请视具体情况而定)配置文件: <!-- 启动Springmvc注解驱动 --> <mvc:annotation-driven> ...

  5. Codefroces 628B New Skateboard(数位+思维)

    题目链接:http://codeforces.com/contest/628/problem/B 题目大意:给你一段数字串s(1?≤?|s|?≤?3·10^5),求该字符串有多少子串是4的倍数.解题思 ...

  6. yum安装Mysql-5.6

    MySQL yum库提供了一个简单的和方便的方法来安装和更新MySQL相关的软件包到最新版本. MySQL yum库文档说明:http://dev.mysql.com/doc/mysql-yum-re ...

  7. appium----新版appium 1.11.1 支持ByName定位

    org.openqa.selenium.InvalidSelectorException: Locator Strategy 'name' is not supported for this sess ...

  8. servlet 学习笔记(二)

    ---------------------第二讲--------------------------------- 开发servlet有三种方法: 1.实现servlet接口(最原始的) 实现接口的5 ...

  9. Asp.net Vnext 自定义日志

    概述 本文已经同步到<Asp.net Vnext 系列教程 >中] 可以通过自定义日志,把错误消息记录到数据库 实现 在启动文件Startup Configure方法中加入自定义的日志提供 ...

  10. ava包(package)的命名规范,java中package命名规则

    Java的包名都有小写单词组成,类名首字母大写:包的路径符合所开发的 系统模块的 定义,比如生产对生产,物资对物资,基础类对基础类.以便看了包名就明白是哪个模块,从而直接到对应包里找相应的实现. 由于 ...