Skip to main content

Shell Sort Notes

I don't understand this passage.  What are the two alternatives? (Algorithms, 258)
One way to implement shellsort would be, for each h, to use insertion sort indepen-
dently on each of the h subsequences. Because the subsequences are independent, we
can use an even simpler approach: when h-sorting the array, we insert each item among
the previous items in its h-subsequence by exchanging it with those that have larger
keys (moving them each one position to the right in the subsequence).
Have to research different implementations of Shell Sort.  Would also help to clarify the mistake I made in my discussion yesterday.

Having said that, I can think of two possibilities.  Given, for instance, h of 3 and a sequence:

1 2 3 4 5 6 7 8 9

-- two methods would be first:

Compare and exchange 1 and 4...
...2 and 5
...3 and 6
...4 and 7
...5 and 8
...6 and 9

-- or second:

Do an insertion sort on 1, 4, and 7
Do an insertion sort on 2, 5, and 8
Do an insertion sort on 3, 6, and 9

Is that what the authors are getting at?  What is the difference between "using insertion sort independently on each of the h subsequences" and "inserting each item among the previous items in its h subsequence"?

Maybe the first method looks like this:

For each element in the array, perform an insertion sort that increments by h (instead of 1 -- why Shell Sort is a generalization of insertion sort).  Then go to the next h in the increment sequence.

And the second method looks like this:

Iterate through the array.  (Because we'll be looking h elements to the left of each item, we can start at h.)  For each item, exchange it with the element h to its left if the left element is less until you reach the beginning of the h-sequence to which it belongs (i.e. and index less than or equal to h).

The second method I know is just a refined description of the implementation I discussed yesterday (cribbed from memory).  So I just have to make sure that the first method really is different from the second.  Well, in some sense, the two must be equivalent -- but they should be different operationally.  So how are they different?

Because the first method goes through every element in one h-sequence and puts it into place before moving to the next h-sequence.  The second, on the other hand, goes element by element and organizes each of the h-sequences as it goes.  It must be like finishing five braids either by performing all the first's weaves, then all the second's weaves, in order, or by performing the first weave for the first, the first weave for the second, and so on -- in order, but a different order.

Comments

Post a Comment

Popular posts from this blog

Getting Geodata From Google's API

The apps I'm going to be analyzing are part of Dr. Charles Severance's MOOC on Python and Databases and work together according to the following structure (which applies both in this specific case and more generally to any application that creates and interprets a database using online data). The data source, in this case, is Google's Google Maps Geocoding API.  The "package" has two components: geoload.py  and geodump.py .  geoload.py  reads a list of locations from a file -- addresses for which we would like geographical information -- requests information about them from Google, and stores the information on a database ( geodata.db ).  geodump.py  reads and parses data from the database in JSON, then loads that into a javascript file.  The javascript is then used to create a web page on which the data is visualized as a series of points on the world-map.  Dr. Severance's course focuses on Python, so I'm only going to work my way through ...

Compiling and Executing Java Files With -cp

I decided I was going to "man up" and figure out how to compile a java program with an external dependency from the command line instead of relying on an IDE-- the DOS command line, to be more specific. I ran into a few problems: 1.  The external dependency was given to me as a java file.  I experimented compiling it as a .jar, but I wasn't sure how to import a class from a .jar, so I ended up compiling it into a class. 2.  When I tried to run the file, I got an error saying that the class had been compiled with a different version of Java than my JRE.  The Internet told me to check my path variable for Java.  It sure looked like it was pointing to the latest JRE (and the same version of Java as my compiler).  I asked the Internet again and found the following command: for %I in (java.exe) do @echo %~$PATH:I I'm not exactly sure what the syntax of that magic command is (intuitively it's returning the path that executes when I run the "java" com...

Quick Find / Quick Union (Connected Nodes)

Setup This week I learned about the "Quick Find" or "Quick Union" algorithm. Imagine an NxN grid of nodes, some of which are connected by lines. A connection can be interpreted as accessibility: if two nodes are connected, you can get from one to the other. Every node is accessible to itself: to get where you already are, stay there. Also, If you can get from A to B, you can go back from B to A. And if you can get from A to B and from B to C, then you can get from A to C. As a consequence, the connection between nodes divides the grid into regions of mutually accessible nodes. You can travel from any node in a given region to any other node in that region -- but not to any nodes outside that region (exercise to reader -- proof by contradiction). The problem has two parts. First, find a way to represent this grid structure and the accessibility relation; second, use your schema to efficiently calculate whether two given nodes are accessible to each other. ...