Tuesday, August 19, 2008

Dinner reflections

"Per" as a prefix is great, btw. I think the people who study these things label one of the profusion of noun cases in Finnish the "perlative" for things set on some path through a place, a time, or some other thing.

I was in San Diego last week and this weekend working with friends. I'm back now, and I'm thinking about your voicemail. So how'd it go? How was dinner?

Some stuff and some hopes come to mind. We're smashing molecular biology & music together and so we can expect what we might call fruitful model friction, right? You guys have different practices devoted entirely to aspects of visualizing stuff at levels much much smaller than the cell. And right there a question arises — do you guys feel yourselves visualizing the abstract or the concrete? The abstract / concrete thing is probably a false dichotomy under any circumstances ... and it seems especially problematized by the whole premise of molecular visualization ... especially at the level that Scott is pushing it ... and at the level you're pushing at Cambridge, right? Whatever these ribosomal (sub)structures turn out to actually "be" the visualization is always going to be some type of superabstraction. More so, sounds like in plenty of cases we're only going to be able to visualize the (indirect) effects these structures generate on their immediate environment and on other local structures with which they interact ... rather than, say, (direct) observation of the structures themselves. So, fine. One of the implications of proceeding that way is that the visualization is model-governed from beginning to end. Which means that whatever model(s) we can invoke from the way that we think about music — the development and dissolution of musical structures, the perception or reception of those structures by people, or how structure vanishes when we think musically in different ways — carry at least the possibility of friction with whatever models it is that drive the work of visualization in the lab. Which is what we can point to by 'model friction'.

Related thought: language matters in this work. We've got the blog, some trips and possibilities to meet for a reason, and we're opening up times and places to exchange language in the process. So posit for a minute that language use for each of us depends on some graph of whole, fractured or composite concepts that interconnect all over the place in our thinking, and also when we write to each other, and talk. Stuff connects in different ways and the words and syntactic patterns we pick out and avoid when we look at each other's work — sketches, result sets, pics, soundfiles, whatever — probably trigger things for us even before they mean things for us. Which probably comes out to mean that we can sure as hell expect something to tremor or to shake in our thinking when you let a molecular biologist in to critique to the construction and development of the sounds in music as the piece progresses and when you let a composer feed back and react to data of actual results as research progresses.

We carry whatever models it is we have with us as our most powerful tools in the form of learned connections — neural, numeric, sonic, maybe literary. And we communicate whatever it that we carry through our language ... and also the sound and image we embed in and around that language.

So that's where the friction — the constructive friction — will lie. In the language of research (and questions about research) rubbing up against the language of composition (and questions about composition) as the work progresses.

So tell me about dinner ... and whether 'visualization' became a keyword at the table. And then I'll tell you what's frictive in the sketches I'm working on now.