2018-team4/AugTrain-06

从 Trac 迁移的文章

这是从旧校内 Wiki 迁移的文章，可能存在一些样式问题，您可以向 memset0 反馈。

原文章内容如下：

[[Image(img.png,600px)]]

== Contest Information ==
[https://codeforc.es/group/J1GbXiu37w/contest/227019 2017 - ICPC - Europe - NEERC - Northern Subregional]
== 流水账 ==

At the beginning, we did the classic 3-direction problem reading as usual. HYY found that A is a sign-in problem, but he swore not to submit the 1st problem of the team yesterday, so he thought for a while and got '''A13(0)'''. Then LYC started to solve L after discussion with HYY, while DHR is thinking about E. LYC got WA, and we analyzed that it might be precision's matter, LYC decided to replace pow function with 2-division method; DHR told LYC to think twice before coding. DHR solved B on his own '''B60(1)'''. Meanwhile, HYY found out the way to solve K, yet another sign-in problem, but made a mistake on I/O file name in the 1st trial '''C77(1)'''. DHR explained I and K for HYY, then in about 20 minutes we got '''I98(0)''', '''L105(1)''' and '''K121(1)'''. At this point sign-in was already done. Time remained: 3h.

We decided to solve E, H and G orderly. DHR got WA on E and HYY found the solution of H is incomplete. LYC started to code G. HYY found the way to code H, and started to help DHR debug. After discussion, we found H's solution is partly wrong, meanwhile LYC finished coding G and got WA. HYY decided not to wait for debugging when there was 50 min left, and got '''H264(0)'''. Debugging for nearly an hour and a half ,DHR finally got '''E279(36)'''. Suffered from the large code burden of G, LYC debugged till the end of the contest.

== 总结 ==


=== Yeungyat ===

Got much better performance myself in sign-in problems.(But failed on file I/O, fk)

It seems that all members in team YaSHa needs to improve code stability.(And readability)
=== Sky_miner ===

今天游戏体验为0

开局写L因为精度问题被卡，贡献罚时

后来写G时写出了一堆bug，到结束都没有de完

自己在比赛的时候写代码写的太急，写出了很多bug，而且自己debug时也不够冷静

以后一定要提高debug能力，提高码力

=== HbFS ===
今天游戏体验很差

签到题贡献了一次WA，写程序的时候太急了，都不知道自己在写些啥。

还有就是用好每一分钟，哪怕是在机下也要好好想题，代码写得好看一点，不要抢时间。细节想清楚。

锻炼一下自己肉眼查错的能力。
== 补题 ==
D[]

F[]

G[lyc]

J[]

Contest Information

2017 - ICPC - Europe - NEERC - Northern Subregional

流水账

At the beginning, we did the classic 3-direction problem reading as usual. HYY found that A is a sign-in problem, but he swore not to submit the 1st problem of the team yesterday, so he thought for a while and got A13(0). Then LYC started to solve L after discussion with HYY, while DHR is thinking about E. LYC got WA, and we analyzed that it might be precision's matter, LYC decided to replace pow function with 2-division method; DHR told LYC to think twice before coding. DHR solved B on his own B60(1). Meanwhile, HYY found out the way to solve K, yet another sign-in problem, but made a mistake on I/O file name in the 1st trial C77(1). DHR explained I and K for HYY, then in about 20 minutes we got I98(0), L105(1) and K121(1). At this point sign-in was already done. Time remained: 3h.

We decided to solve E, H and G orderly. DHR got WA on E and HYY found the solution of H is incomplete. LYC started to code G. HYY found the way to code H, and started to help DHR debug. After discussion, we found H's solution is partly wrong, meanwhile LYC finished coding G and got WA. HYY decided not to wait for debugging when there was 50 min left, and got H264(0). Debugging for nearly an hour and a half ,DHR finally got E279(36). Suffered from the large code burden of G, LYC debugged till the end of the contest.

总结

Yeungyat

Got much better performance myself in sign-in problems.(But failed on file I/O, fk)

It seems that all members in team YaSHa needs to improve code stability.(And readability)

Sky_miner

今天游戏体验为0

开局写L因为精度问题被卡，贡献罚时

后来写G时写出了一堆bug，到结束都没有de完

自己在比赛的时候写代码写的太急，写出了很多bug，而且自己debug时也不够冷静

以后一定要提高debug能力，提高码力

HbFS

今天游戏体验很差

签到题贡献了一次WA，写程序的时候太急了，都不知道自己在写些啥。

还有就是用好每一分钟，哪怕是在机下也要好好想题，代码写得好看一点，不要抢时间。细节想清楚。

锻炼一下自己肉眼查错的能力。

补题

D[]

F[]

G[lyc]

J[]