I ended up testing this match. The suspense regarding my eerily close to red rating will have to be postponed.
The editorial is up: Editorial
The quick write up has been removed because , well it wasn't that good.
skip to main
|
skip to sidebar
vexorian talks about stuff. Mostly programming or programming-adjacent
Search This Blog
Feed
Popular Posts
Popular Posts (All time)
Tags
topcoder
srm
explanation
editorial
recap
rant
codeforces
tco
arenaplugin
googlecodejam
google
badday
algorithm
greed
offtopic
python
implementation
c++
stl
kawigiedit
mylevels
puzzle
tco2012
postmortem
tco2013
programming
snippet
tco12
tco13
listedlinks
acm
behindthescenes
goodday
ipsc
onescreen
vkcup
badbook
cloudyconway
gamedesign
julia
kindagoodday
marathon
pascal
slightlygoodday
strategy
ubuntu
uva
wc3
almostagoodday
answers
bugs
censorship
codechef
contests
crocchamp
embarrassing
emily
gameoflife
gcj2013
gcj2014
gcj2015
gcj2016
gittip
givememoney
glitches
gmp
groklaw
health
html
httpseverywhere
java
kye
lambdas
languages
learnthestatement
lego
levelcuration
ludumdare
meta
nasa
ouch
patreon
postportem
practical
probably_not_a_good_tip
problemsetting
puzzlescript
quora
swerc
tco14
tco2015
ternarysearch
tricks
twitterbots
vjass
youtube
zinc
3 comments :
In D1-250, instead of using the error-prone max-mins, I just iterated all possible locations of each platform and checked if it will collide with the balls. It passed as the constraints are low.
OOT, it seems that you forgot to close the superscript tag.
For some reason, I didn't figure they were so low. The first time I read the problem I was on MPSQAS and apparently it is easier to miss constraints.
I wrote this thing in about 20 minutes between some time during coding phase and the end of the challenge phase. When I revisit it to write the actual editorial, I found many bugs, including that one about superscript. So, I deleted the write up on the blog and replaced it with a link to the editorial.
Post a Comment