| 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

The Quest for Randomness; 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

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

Notes on Array Layout

From: andrew cooke <andrew@...>

Date: Wed, 9 Dec 2009 11:22:56 -0300

2D array data are typically stored in computer memory in one of two
layouts: row major or column major.

This doesn't help explain anything without knowing which index is
"row" and which "column".  It turns out that the conventional indexing
is [y,x] (sigh).  So the first index is row (where you are in a
column) and the second is column (where you are in a row).

For example, this is how the indices of a 2x3 (2 rows x 3 columns)
matrix, called A, are conventionally visualised:

 A[0,0]  A[0,1]  A[0,2]
 A[1,0]  A[1,1]  A[1,2]

Where I am using 0-based indexing (normal for C).  In Fortran and
Matlab, things are similar but you need to add 1 to all the indices
(so A[0,0] becomes A[1,1] etc).

If we put numbers in the array it might look like:

 1 2 3
 4 5 6


Row Major

With row major layout, rows are stored together.  So the data above
would be stored as sequence in memory as:

 A[0,0]  A[0,1]  A[0,2]  A[1,0]  A[1,1]  A[1,2]

In terms of numbers in the array:

 1 2 3 4 5 6

This is how arrays are stored in C.  As you move through the data, the
last index increases most quickly, like a car's mileometer (mnemoic: C
is Car)


Column Major

With column major layout, columns are stored together.  So the data
above would be stored as a sequence in memory as:

 A[0,0]  A[1,0]  A[0,1]  A[1,1]  A[0,2]  A[1,2]

In terms of numbers in the array:

 1 4 2 5 3 6

This is how arrays are stored in Fortran and Matlab (except that
indexing is 1-based).  As you move through the data, the first index
varies faster (mnemonic: Fortran First Fastest).


Note that there are two separate issues here.  First, there's the
convention of which array index is interpreted as row and which as
column.  Second, there's the convention of how you map the indices to
memory.  These two are mixed up by the names used.

We can separate these two issues by focussing on the indexing.  Then we have:

In C, last index varies most quickly as we move through memory.
In Fortran and Matlab, the first index varies most quickly as we move
through memory

And, separately:

It is conventional for the first index to indicate "row" and the
second "column".

Putting these together we get "row major" for C and "column major" for
Fortran and Matlab.

Andrew

Comment on this post