| Andrew Cooke | Contents | Latest | RSS | Twitter | Previous | Next

C[omp]ute

Welcome to my blog, which was once a mailing list of the same name and is still generated by mail. Please reply via the "comment" links.

Always interested in offers/projects/new ideas. Eclectic experience in fields like: numerical computing; Python web; Java enterprise; functional languages; GPGPU; SQL databases; etc. Based in Santiago, Chile; telecommute worldwide. CV; email.

Personal Projects

Lepl parser for Python.

Colorless Green.

Photography around Santiago.

SVG experiment.

Professional Portfolio

Calibration of seismometers.

Data access via web services.

Cache rewrite.

Extending OpenSSH.

Last 100 entries

Chat Wars; Real-life Financial Co Without ACID Database...; Flexible Muscle-Based Locomotion for Bipedal Creatures; SQL Performance Explained; The Little Manual of API Design; Multiple Word Sizes; CRC - Next Steps; FizzBuzz; Update on CRCs; Decent Links / Discussion Community; Automated Reasoning About LLVM Optimizations and Undefined Behavior; A Painless Guide To CRC Error Detection Algorithms; Tests in Julia; Dave Eggers: what's so funny about peace, love and Starship?; Cello - High Level C Programming; autoreconf needs tar; Will Self Goes To Heathrow; Top 5 BioInformatics Papers; Vasovagal Response; Good Food in Vina; Chilean Drug Criminals Use Subsitution Cipher; Adrenaline; Stiglitz on the Impact of Technology; Why Not; How I Am 5; Lenovo X240 OpenSuse 13.1; NSA and GCHQ - Psychological Trolls; Finite Fields in Julia (Defining Your Own Number Type); Julian Assange; Starting Qemu on OpenSuse; Noisy GAs/TMs; Venezuela; Reinstalling GRUB with EFI; Instructions For Disabling KDE Indexing; Evolving Speakers; Changing Salt Size in Simple Crypt 3.0.0; Logarithmic Map (Moved); More Info; Words Found in Voynich Manuscript; An Inventory Of 3D Space-Filling Curves; Foxes Using Magnetic Fields To Hunt; 5 Rounds RC5 No Rotation; JP Morgan and Madoff; Ori - Secure, Distributed File System; Physical Unclonable Functions (PUFs); Prejudice on Reddit; Recursion OK; Optimizing Julia Code; Cash Handouts in Brazil; Couple Nice Music Videos; It Also Works!; Adaptive Plaintext; It Works!; RC5 Without Rotation (2); 8 Years...; Attack Against Encrypted Linux Disks; Pushing Back On NSA At IETF; Summary of Experimental Ethics; Very Good Talk On Security, Snowden; Locusts are Grasshoppers!; Vagrant (OpenSuse and IDEs); Interesting Take On Mandela's Context; Haskell Cabal O(n^2) / O(n) Fix; How I Am 4; Chilean Charity Supporting Women; Doing SSH right; Festival of Urban Intervention; Neat Idea - Wormholes Provide Entanglement; And a Link....; Simple Encryption for Python 2.7; OpenSuse 13.1 Is Better!; Little Gain...; More Details on Technofull Damage; Palmrest Cracked Too....; Tecnofull (Lenovo Support) Is Fucking Useless; The Neuroscientist Who Discovered He Was a Psychopath; Interpolating Polynomials; Bottlehead Crack as Pre-amp; Ooops K702!; Bottlehead Crack, AKG K701; Breaking RC5 Without Rotation; Great post thank you; Big Balls of Mud; Phabricator - Tools for working together; Amazing Julia RC5 Code Parameterized By Word Size; Chi-Square Can Be Two-Sided; Why Do Brits Accept Surveillance?; Statistics Done Wrong; Mesas Trape from Bravo; European Report on Crypto Primitives and Protocols; Interesting Omissions; Oryx And Crake (Margaret Atwood); Music and Theory; My Arduino Programs; Elliptic Curve Crypto; Re: Licensing Interpreted Code; Licensing Interpreted Code; ASUS 1015E-DS03 OpenSuse 12.3 SSD; translating lettuce feature files into stub steps files; Re: translating lettuce feature files into stub steps files; A Tale of Two Psychiatrists

© 2006-2013 Andrew Cooke (site) / post authors (content).

O(n) and O(n^2) in a Dynamic Programming Problem

From: andrew cooke <andrew@...>

Date: Sat, 6 Aug 2011 14:39:51 -0400

I posted an answer at
http://stackoverflow.com/questions/6967853/dynamic-programing-can-interval-of-even-1s-and-0s-be-found-in-linear-time
that I want to copy here, beause I am worried that it will be deleted by the
moderators.

The question asks for a linear solution to a problem which generates O(N^2)
results.  That seems impossible, but if you look in more detail there's a cute
argument that hinges on the difference between "finding" and "printing" the
results:


A linear solution is possible (sorry, earlier I argued that this had to be
n^2) if you're careful to not actually print the results!

First, let's define a "score" for any set of zeros and ones as the number of
ones minus the number of zeroes.  So (0,1) has a score of 0, while (0) is -1
and (1,1) is 2.

Now, start from the right.  If the right-most digit is a 0 then it can be
combined with any group to the left that has a score of 1.  So we need to know
what groups are available to the left, indexed by score.  This suggests a
recursive procedure that accumulates groups with scores.  The sweep process is
O(n) and at each step the process has to check whether it has created a new
group and extend the table of known groups.  Checking for a new group is
constant time (lookup in a hash table).  Extending the table of known groups
is also constant time (at first I thought it wasn't, but you can maintain a
separate offset that avoids updating each entry in the table).

So we have a peculiar situation: each step of the process identifies a set of
results of size O(n), but the calculation necessary to do this is constant
time (within that step).  So the process itself is still O(n) (proportional to
the number of steps).  Of course, actually printing the results is O(n^2).

I'll write some Python code to test/demonstrate.

Here we go:

    SCORE = [-1,1]
    
    class Accumulator:
    
        def __init__(self):
            self.offset = 0
            self.groups_to_right = {} # map from score to start index
            self.even_groups = []
            self.index = 0
    
        def append(self, digit):
            score = SCORE[digit]
            # want existing groups at -score, to sum to zero
            # but there's an offset to correct for, so we really want
            # groups at -(score+offset)
            corrected = -(score + self.offset)
            if corrected in self.groups_to_right:
                self.even_groups.append(
                    (self.index, self.groups_to_right[corrected]))
            # this updates all the known groups
            self.offset += score
            # this adds the new one, which should be at the index so that
            # index + offset = score (so index = score - offset)
            groups = self.groups_to_right.get(score-self.offset, [])
            groups.append(self.index) 
            self.groups_to_right[score-self.offset] = groups
            # and move on
            self.index += 1
            #print self.offset
            #print self.groups_to_right
            #print self.even_groups
            #print self.index
    
        def dump(self):
            # printing the results does take longer, of course...
            for (end, starts) in self.even_groups:
                for start in starts:
                    if start < end:
                        print (start, end)
    
        @staticmethod
        def run(input):
            accumulator = Accumulator()
            print input
            for digit in input:
                accumulator.append(digit)
            accumulator.dump()
            print
    
    Accumulator.run([0,1,0,0,1,1,1,1,0])

And the output:

    dynamic: python dynamic.py 
    [0, 1, 0, 0, 1, 1, 1, 1, 0]
    (0, 1)
    (1, 2)
    (1, 4)
    (3, 4)
    (0, 5)
    (2, 5)
    (7, 8)

You might be worried that some additional processing (the filtering for `start
< end`) is done in the dump routine that displays the results.  But that's
because I am working around Python's lack of linked lists (I want to both
extend a list and save the previous value in constant time).

It may seem surprising that the result is of *size* O(n^2) while the process
of *finding* the results is O(n), but it's easy to see how that is possible:
at one "step" the process identifies a number of groups (of size O(n)) by
associating the current point (`end` in `dump()`) with a list of end points
(`ends`).


Andrew

Comment on this post