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


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.

C-ORM: docs, API.

Last 100 entries

M John Harrison; Playing Games on a Cloud GPU; China Gamifies Real Life; Can't Help Thinking It's Thoughtcrime; Mefi Quotes; Spray Painting Bike Frame; Weeks 10 + 11; Change: No Longer Possible To Merge Metadata; Books on Old Age; Health Tree Maps; MRA - Men's Rights Activists; Writing Good C++14; Risk Assessment - Fukushima; The Future of Advertising and Surveillance; Travelling With Betaferon; I think I know what I dislike so much about Metafilter; Weeks 8 + 9; More; Pastamore - Bad Italian in Vitacura; History Books; Iraq + The (UK) Governing Elite; Answering Some Hard Questions; Pinochet: The Dictator's Shadow; An Outsider's Guide To Julia Packages; Nobody gives a shit; Lepton Decay Irregularity; An Easier Way; Julia's BinDeps (aka How To Install Cairo); Good Example Of Good Police Work (And Anonymity Being Hard); Best Santiago Burgers; Also; Michael Emmerich (Vibrator Translator) Interview (Japanese Books); Clarice Lispector (Brazillian Writer); Books On Evolution; Looks like Ara (Modular Phone) is dead; Index - Translations From Chile; More Emotion in Chilean Wines; Week 7; Aeon Magazine (Science-ish); QM, Deutsch, Constructor Theory; Interesting Talk Transcripts; Interesting Suggestion Of Election Fraud; "Hard" Books; Articles or Papers on depolarizing the US; Textbook for "QM as complex probabilities"; SFO Get Libor Trader (14 years); Why Are There Still So Many Jobs?; Navier Stokes Incomplete; More on Benford; FBI Claimed Vandalism; Architectural Tessellation; Also: Go, Blake's 7; Delusions of Gender (book); Crypto AG DID work with NSA / GCHQ; UNUMS (Universal Number Format); MOOCs (Massive Open Online Courses); Interesting Looking Game; Euler's Theorem for Polynomials; Weeks 3-6; Reddit Comment; Differential Cryptanalysis For Dummies; Japanese Graphic Design; Books To Be Re-Read; And Today I Learned Bugs Need Clear Examples; Factoring a 67 bit prime in your head; Islamic Geometric Art; Useful Julia Backtraces from Tasks; Nothing, however, is lost with less discomfort than that which, when lost, cannot be missed; Article on Didion; Cost of Living by City; British Slavery; Derrida on Metaphor; African SciFi; Traits in Julia; Alternative Japanese Lit; Pulic Key as Address (Snow); Why Information Grows; The Blindness Of The Chilean Elite; Some Victoriagate Links; This Is Why I Left StackOverflow; New TLS Implementation; Maths for Physicists; How I Am 8; 1000 Word Philosophy; Cyberpunk Reading List; Detailed Discussion of Message Dispatch in ParserCombinator Library for Julia; FizzBuzz in Julia w Dependent Types; kokko - Design Shop in Osaka; Summary of Greece, Currently; LLVM and GPUs; See Also; Schoolgirl Groyps (Maths); Japanese Lit; Another Example - Modular Arithmetic; Music from United; Python 2 and 3 compatible alternative.; Read Agatha Christie for the Plot; A Constructive Look at TempleOS; Music Thread w Many Recommendations; Fixed Version; A Useful Julia Macro To Define Equality And Hash

© 2006-2015 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.


Comment on this post