| 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.

C-ORM: docs, API.

Last 100 entries

Calling C From Fortran 95; Bjork DJ Set; Z3 Example With Python; Week 1; Useful Guide To Starting With IJulia; UK Election + Media; Review: Reinventing Organizations; Inline Assembly With Julia / LLVM; Against the definition of types; Dumb Crypto Paper; The Search For Quasi-Periodicity...; Is There An Alternative To Processing?; CARDIAC (CARDboard Illustrative Aid to Computation); The Bolivian Case Against Chile At The Hague; Clear, Cogent Economic Arguments For Immigration; A Program To Say If I Am Working; Decent Cards For Ill People; New Photo; Luksic And Barrick Gold; President Bachelet's Speech; Baltimore Primer; libxml2 Parsing Stream; configure.ac Recipe For Library Path; The Davalos Affair For Idiots; Not The Onion: Google Fireside Chat w Kissinger; Bicycle Wheels, Inertia, and Energy; Another Tax Fraud; Google's Borg; A Verion That Redirects To Local HTTP Server; Spanish Accents For Idiots; Aluminium Cans; Advice on Spray Painting; Female View of Online Chat From a Male; UX Reading List; S4 Subgroups - Geometric Interpretation; Fucking Email; The SQM Affair For Idiots; Using Kolmogorov Complexity; Oblique Strategies in bash; Curses Tools; Markov Chain Monte Carlo Without all the Bullshit; Email Para Matias Godoy Mercado; The Penta Affair For Idiots; Example Code To Create numpy Array in C; Good Article on Bias in Graphic Design (NYTimes); Do You Backup github?; Data Mining Books; SimpleDateFormat should be synchronized; British Words; Chinese Govt Intercepts External Web To DDOS github; Numbering Permutations; Teenage Engineering - Low Price Synths; GCHQ Can Do Whatever It Wants; Dublinesque; A Cryptographic SAT Solver; Security Challenges; Word Lists for Crosswords; 3D Printing and Speaker Design; Searchable Snowden Archive; XCode Backdoored; Derived Apps Have Malware (CIA); Rowhammer - Hacking Software Via Hardware (DRAM) Bugs; Immutable SQL Database (Kinda); Tor GPS Tracker; That PyCon Dongle Mess...; ASCII Fluid Dynamics; Brandalism; Table of Shifter, Cassette and Derailleur Compatability; Lenovo Demonstrates How Bad HTTPS Is; Telegraph Owned by HSBC; Smaptop - Sunrise (Music); Equation Group (NSA); UK Torture in NI; And - A Natural Extension To Regexps; This Is The Future Of Religion; The Shazam (Music Matching) Algorithm; Tributes To Lesbian Community From AIDS Survivors; Nice Rust Summary; List of Good Fiction Books; Constructing JSON From Postgres (Part 2); Constructing JSON From Postgres (Part 1); Postgres in Docker; Why Poor Places Are More Diverse; Smart Writing on Graceland; Satire in France; Free Speech in France; MTB Cornering - Where Should We Point Our Thrusters?; Secure Secure Shell; Java Generics over Primitives; 2014 (Charlie Brooker); How I am 7; Neural Nets Applied to Go; Programming, Business, Social Contracts; Distributed Systems for Fun and Profit; XML and Scheme; Internet Radio Stations (Curated List); Solid Data About Placebos; Half of Americans Think Climate Change Is a Sign of the Apocalypse; Saturday Surf Sessions With Juvenile Delinquents; Ssh, tty, stdout and stderr; Feathers falling in a vacuum; Santiago 30m Bike Route

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

Andrew

Comment on this post