One Point Solution

  • Subscribe to our RSS feed.
  • Twitter
  • StumbleUpon
  • Reddit
  • Facebook
  • Digg

Thursday, 7 March 2013

SRM 572 Editorial WIP : Div1 500 and div2 1000 (and div1 250)

Posted on 16:42 by Unknown

Development for this editorial is a bit in difficult waters. Solving the div1 hard problem might take a while. But here are some explanations for the easier (less hard) problems.

DistinctRemainders: Div2 Hard | Link to problem statement

EllysBulls: Div1 Medium | Link to problem statement

Update: NewArenaPassword: Div1 Easy | Link to problem statement

Finding out the division 1 medium solution was a bit embarrassing. Meet in the middle was actually one of the first ideas I had for the problem. But something made me believe that meet in the middle wouldn't work because of memory. It makes no sense, the limit on the number of things to store in memory is O(105), it does not matter if the number of valid keys that could be generated is O(550), because we will use a std::map anyway.

The remaining problems (except for div2 250) are looking to be tougher to explain. Div2 500 and div1 250 are not too easy to prove. Div1 1000 is looking undoable right now and I am yet to receive the usual help message from admins about it. Codeforces is as always the only place to have explanations for these div1 hard problems and as usual the explanations are in Russian and very short ^^.

Div2 500 is much harder than it should have been. I think using the problem that was div1 250 would have been ok for this slot.

As you can see, the editorial is so preliminary right now it doesn't even have the usual problem statistics and links. It will be fixed soon, I hope.

Email ThisBlogThis!Share to XShare to Facebook
Posted in editorial, srm, topcoder | No comments
Newer Post Older Post Home

0 comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Popular Posts

  • TopCoder SRM 557 - finally
    SRM 557 Explanation for division 1 Easy and match recap. Explanations for div2 easy and div2 medium. It feels like it has been ages since t...
  • SRM 589 Editorial
    I have finished writing the editorial for TopCoder SRM 589: http://apps.topcoder.com/wiki/display/tc/SRM+589 . As you most likely noticed. L...
  • SRM 590 recap and editorial
    Another week another Topcoder match. Not a great day. I had a bad flu and still do. Div1 500: The one with Xor Given a list of cards with nu...
  • SRM 546: relief
    I figured I should post something about this SRM. I've been very busy these weeks because the semester is ending and I tried to win a t-...
  • SRM 526: The killing wait for results
    While I wait for results, here is my perspective on this algorithm contest. It began with issues, it had to be postponed 15 minutes. TC has ...
  • SRM 554 div1 hard: TheBrickTowerHardDivOne
    Link to problem statement We got infinitely many bricks of dimensions 1x1x1 and C different colors. Count the number of towers of size 2x2...
  • SRM 533: Div1 500 MagicBoard explanation
    Finally solved it. It is a nice problem that is worth explaining in a post. You have a grid/board of at most 50x50 cells. Some cells contain...
  • Member SRM 505: Part 1
    So, let me explain a couple of problems from a Topcoder Member SRM that I wrote and never got an editorial. BTW, it was the last member SRM....
  • ListedLinks 2012-02-10
    Saturday Morning Breakfast Cereal comics: Grace Hopper's ghost That Oracle engineer blog post Oracle would really not like anyone to se...
  • Codeforces "Good bye 2013" round
    So it was a special round for coders of both divisions, problems ranged from the super easy problem A to the super difficult problems E,F,G....

Categories

  • acm
  • algorithm
  • answers
  • arenaplugin
  • badday
  • behindthescenes
  • bugs
  • c++
  • censorship
  • codechef
  • codeforces
  • contests
  • crocchamp
  • editorial
  • editorial.srm
  • embarrassing
  • explanation
  • gcj2013
  • gmp
  • goodday
  • google
  • googlecodejam
  • greed
  • groklaw
  • health
  • html
  • httpseverywhere
  • implementation
  • ipsc
  • ispc
  • java
  • kawigiedit
  • kindagoodday
  • lamebook
  • languages
  • lego
  • listedlinks
  • marathon
  • nasa
  • offtopic
  • ouch
  • postmortem
  • postportem
  • practical
  • probably_not_a_good_tip
  • problemsetting
  • programming
  • python
  • quora
  • rant
  • recap
  • slightlygoodday
  • snippet
  • srm
  • stl
  • strategy
  • swerc
  • tco
  • tco12
  • tco13
  • tco2012
  • tco2013
  • ternarysearch
  • topcoder
  • tricks
  • ubuntu
  • uva
  • vjass
  • vkcup
  • wc3
  • zinc

Blog Archive

  • ►  2014 (1)
    • ►  January (1)
  • ▼  2013 (141)
    • ►  December (14)
    • ►  November (8)
    • ►  October (13)
    • ►  September (11)
    • ►  August (14)
    • ►  July (15)
    • ►  June (13)
    • ►  May (13)
    • ►  April (12)
    • ▼  March (11)
      • SRM 574 editorial supposedly ready
      • SRM 574: Stupid "dp sense"
      • SRM 573 Editorial supposedly complete
      • SRM 573 editorial WIP: Div1 850: WolfPack
      • SRM 573: Lack of speed
      • TopCoder SRM 572, editorial for div1 hard: NextAnd...
      • TCO 2013 Round 1C editorial
      • SRM 572, d2 250 - NextOrPrev editorial (WIP)
      • SRM 572 Editorial WIP : Div1 500 and div2 1000 (an...
      • SRM 572: hmnn
      • Another week another TCO 2013 editorial: 1B
    • ►  February (11)
    • ►  January (6)
  • ►  2012 (94)
    • ►  December (5)
    • ►  October (6)
    • ►  September (8)
    • ►  August (6)
    • ►  July (3)
    • ►  June (5)
    • ►  May (8)
    • ►  April (10)
    • ►  March (20)
    • ►  February (16)
    • ►  January (7)
  • ►  2011 (51)
    • ►  December (7)
    • ►  November (12)
    • ►  October (5)
    • ►  September (1)
    • ►  August (3)
    • ►  July (4)
    • ►  June (3)
    • ►  May (7)
    • ►  April (3)
    • ►  March (2)
    • ►  February (1)
    • ►  January (3)
  • ►  2010 (9)
    • ►  December (4)
    • ►  October (1)
    • ►  June (1)
    • ►  May (1)
    • ►  January (2)
  • ►  2009 (1)
    • ►  December (1)
Powered by Blogger.

About Me

Unknown
View my complete profile