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

Re: Python's sad, unimaginative Enum; Re: Some explanation; Some explanation; Printing binary trees sideways; Atoms in python; About "Python's sad, unimaginative Enum"; Frustration Understood; Some good feedback here; this is fucking useless; I agree with you #nt; What would be imaginative?; Re: Enum; Enum; Python's sad, unimaginative Enum; Possible Fix; Work, Exhaustion, Vacation; VirtualBox with Centos 6.3 to 6.4, client; Matasano - Programming Lessons Learned; PDF to HTML; Alternate Substitution; Why RSA Works; Trigger; Dreaming of Death; Example: Tracing; Using Coroutines In Protocol Simulations; Python 3.3 Only; Pure Python SHA1 and MD4 Implementations; Ubuntu on VirtualBox; Starting TOR as a service on OpenSuse 12.3; 1001 Albums; Using fail2ban on OpenSuse 12.3; PPPoE on OpenSuse 12.3; Good Article on Unified Physics; It's Police (Carabineros); Linux Software for Listening to and Exploring Music; Android is Pretty Bad; Lucky Number; 3D Printing for Casting; Cover Art for MPDroid; Who'd a thought the French were so bigoted?; PS Input Signal; Small Problem with Roksan K2 Amp; Roksan K2 Amp + ATC SCM7 Speakers; Do What Makes Sense; Re: Arguing About Tests, Still; Arguing About Tests, Still; Images; Good Article on NY Drummers; Related Bug Report; Getting Python 3.3 and Virtualenv Working in OpenSuse 12.3; How I Am; Awesome video about digital audio; The Difference Between Dimensional and Normalized Databases; The rise of the new Chinese bogeyman; Updated Syntax; Very First Steps to C-ORM; The Ideal User Interface For Music Exploration; Can The Republicans Be Saved?; Rate Limiting Calls to EchoNest; Mods to Cache; Comparing UYKFG and UYKFD/E/F; Someone Else is Concerned; EchoNest-based Playlist Generator for MPD; Example Voting Results; A Heavyweight Python Cache; Identifying Artists with EchoNest; Notes on Pregalex / Pregabalina / Lyrica; The Neil Cowley Trio; Drake - Make for Data; A Reliable Python Web Service; Useful Python Date/Time Library?; Need to Sleep, But this is Good; Command Line Set Difference; Little Details...; Linux Command Line Tricks; AutoTools Tutorial; Hangman Tactics; A Tor Proxy Embedded In A Web Page; Tree (Nested Dicts) in Python; Sleeping at Parties; I Know Someone Who Hurts Other People; Light and Tea; Description of the LCS35 Time Capsule Crypto-Puzzle; Re: I can relate to that ...; I can relate to that ...; Re: It's 2012 Why Does My IDE Suck?; My Own Alternative Medicine; Nice explanation of SVM; Why and How Writing Crypto is Hard; Re: It's 2012 Why Does My IDE Suck?; Incremental Regular Expressions; BBC Map Confused at Pole; Social Media: Ground Zero in the Culture War; My Visit to the Psycho Doc; Learning Modern 3D Graphics Programming; Hope you got some crackers to go with the cheese; Re: But how easy would it be ...; But how easy would it be ...; Powerline Freq Fingerprinting of Audio; The Folly of Scientism; Cheese - Because You're Going to Die Anyway

Image Processing with CUDA / Python (Dynamic Pipelines)

From: "andrew cooke" <andrew@...>

Date: Sun, 3 Aug 2008 13:20:21 -0400 (CLT)

I've been thinking about how best to apply CUDA to image processing
(particularly in astronomy, which is what I know).

Many image processing tasks are *very* suitable for parallelisation, since
the processing is "per-pixel" across several arrays (for example,
subtracting oen image from another).

So my idea is to write a parser (in Python) that accepts an expression in
a "language" that describes image processing and compiles that (literally)
to a CUDA process.

The motivation for this approach is to reduce the memory transfer overhead
compared to the alternative: a library of primitive operations.  If add,
multiple, etc are each separate primitives then data must be loaded for
each.  But in many cases it should be possible to combine these so that
all data are loaded just once, and the "per pixel" operation does several
steps.  Thie lowers the data transfer cost while at the same time grouping
the arithmetic processing into a single "chunk" (useful because it can run
while other data are loading).

It may not be clear that there is sufficient complexity, but my idea is to
support "error" and "uality" data too.

Andrew

Re: CUDA and astronomical image processing

From: andrew cooke <andrew@...>

Date: Sun, 8 Jul 2012 08:35:38 -0400

Hi,

I need to update my blog - it doesn't handle multipart mime messages like 
yours (which is why it wasn't displayed).

Anyway, no - I never got any further.  One reason was that I thought Theano
http://deeplearning.net/software/theano/ did a lot of what I was planning.  So
if you're looking for something like I described, you might want to consider
that.

Cheers,
Andrew

On Sun, Jul 08, 2012 at 11:47:42AM +0930, Andrew Cool wrote:
> Hi Andrew,
> 
> It's now 2012. Did you get anywhere with your CUDA processing?
> 
> Regards,
> 
> Andrew Cool
> 
> www.skippysky.com.au

CUDA and astronomical image processing

From: "Andrew Cool" <andrew@...>

Date: Sun, 8 Jul 2012 11:47:42 +0930

Hi Andrew,

It's now 2012. Did you get anywhere with your CUDA processing?

Regards,

Andrew Cool

www.skippysky.com.au

 

From: "andrew cooke" <andrew@...> 

Date: Sun, 3 Aug 2008 13:20:21 -0400 (CLT) 

I've been thinking about how best to apply CUDA to image processing

(particularly in astronomy, which is what I know).

 

Many image processing tasks are *very* suitable for parallelisation, since

the processing is "per-pixel" across several arrays (for example,

subtracting oen image from another).

 

So my idea is to write a parser (in Python) that accepts an expression in

a "language" that describes image processing and compiles that (literally)

to a CUDA process.

 

The motivation for this approach is to reduce the memory transfer overhead

compared to the alternative: a library of primitive operations.  If add,

multiple, etc are each separate primitives then data must be loaded for

each.  But in many cases it should be possible to combine these so that

all data are loaded just once, and the "per pixel" operation does several

steps.  Thie lowers the data transfer cost while at the same time grouping

the arithmetic processing into a single "chunk" (useful because it can run

while other data are loading).

 

It may not be clear that there is sufficient complexity, but my idea is to

support "error" and "uality" data too.

 

Andrew

 

 

All of us could take a lesson from the weather........ It pays no attention
to Criticism.

Comment on this post