<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0"><channel><atom:link rel="hub" href="http://tumblr.superfeedr.com/" xmlns:atom="http://www.w3.org/2005/Atom"/><description>Brian House is a media artist creating work with large gestures and small collisions.</description><title>rhythmanalysis</title><generator>Tumblr (3.0; @rhythmanalysis)</generator><link>http://blog.brianhouse.net/</link><item><title>I co-taught a Public School class this week — part of the series...</title><description>&lt;img src="http://25.media.tumblr.com/tumblr_m4lochtj4N1qk20gto1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;I co-taught a Public School class this week — part of the series &lt;a href="http://nyc.thepublicschool.org/class/3865" target="_new"&gt;On Time&lt;/a&gt; put together by Jonathan Basile. The imitable &lt;a href="http://jacksonmoore.net/" target="_new"&gt;Jackson Moore&lt;/a&gt; discussed how music may have a biological basis as a faculty for synchronizing actions within groups of people, and he broke down the theories of James Tenney and Fred Lerdahl. I went from there to discuss some of Lefebvre’s structural approaches to examining rhythm in everyday life. We had a great discussion — my favorite points from the group included the idea that musical drones refocus attention on the body as a source of meter, and the suspicion that the CIA assassinated Coltrane because he was spreading subversive rhythms with his tunes.&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/23757671048</link><guid>http://blog.brianhouse.net/post/23757671048</guid><pubDate>Fri, 25 May 2012 18:41:05 -0400</pubDate><category>eyebeam</category><category>the public school</category><category>jackson moore</category><category>rhythmanalysis</category></item><item><title>Multitudes @ Cameo</title><description>&lt;img src="http://24.media.tumblr.com/tumblr_m4lnrzDQeS1qk20gto1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;&lt;a href="http://multitudes.bandcamp.com" target="_new"&gt;Multitudes&lt;/a&gt; @ Cameo&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/23756923842</link><guid>http://blog.brianhouse.net/post/23756923842</guid><pubDate>Fri, 25 May 2012 18:28:47 -0400</pubDate><category>multitudes</category><category>performance</category><category>punk rock</category></item><item><title>I’m working on a new rhythmanalysis project for Eyebeam —...</title><description>&lt;img src="http://25.media.tumblr.com/tumblr_m4j8pd45Ig1qk20gto1_500.png"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;I’m working on a new rhythmanalysis project for Eyebeam — working title is &lt;i&gt;Forty-eight by Sixteen&lt;/i&gt;, it will be a video that is algorithmically edited with data that I generate while biking to work. Cadence, heartrate, respiration, GPS … this graph is looking at cadence (blue) vs heartrate (red) over the course of 30 minutes and 7.5 miles.&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/23673019736</link><guid>http://blog.brianhouse.net/post/23673019736</guid><pubDate>Thu, 24 May 2012 11:08:01 -0400</pubDate><category>eyebeam</category><category>biking</category><category>nyc</category><category>Forty-eight by Sixteen</category><category>rhythmanalysis</category></item><item><title>Familiarity is … enriched by an appreciation of seasonal...</title><description>&lt;img src="http://25.media.tumblr.com/tumblr_m3z4xliUoJ1qk20gto1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;&lt;i&gt;Familiarity is … enriched by an appreciation of seasonal changes, such as the changing light, foliage and wildlife, inducing an apprehension of our enfolding within the larger temporal rhythms of a space of the changing same and the momentarily surprising.&lt;/i&gt;&lt;br/&gt;&lt;br/&gt;
— Tim Edensor&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/22984212133</link><guid>http://blog.brianhouse.net/post/22984212133</guid><pubDate>Sun, 13 May 2012 14:34:32 -0400</pubDate><category>rhythmanalysis</category><category>edensor</category><category>mobility</category><category>quote</category></item><item><title>The end of ‘Tiger’ from our set last Saturday at a...</title><description>&lt;span id="video_player_22823865688"&gt;[&lt;a href="http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash" target="_blank"&gt;Flash 10&lt;/a&gt; is required to watch video.]&lt;/span&gt;&lt;script type="text/javascript"&gt;renderVideo("video_player_22823865688",'http://blog.brianhouse.net/video_file/22823865688/tumblr_m3u9r6oT6b1qk20gt',400,225,'poster=http%3A%2F%2Fmedia.tumblr.com%2Ftumblr_m3u9r6oT6b1qk20gt_frame1.jpg,http%3A%2F%2Fmedia.tumblr.com%2Ftumblr_m3u9r6oT6b1qk20gt_frame2.jpg,http%3A%2F%2Fmedia.tumblr.com%2Ftumblr_m3u9r6oT6b1qk20gt_frame3.jpg,http%3A%2F%2Fmedia.tumblr.com%2Ftumblr_m3u9r6oT6b1qk20gt_frame4.jpg,http%3A%2F%2Fmedia.tumblr.com%2Ftumblr_m3u9r6oT6b1qk20gt_frame5.jpg')&lt;/script&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;The end of ‘Tiger’ from our set last Saturday at a basement show. Killer crowd.&lt;br/&gt;&lt;br/&gt;
More from &lt;a href="http://multitudes.bandcamp.com" target="_new"&gt;Multitudes&lt;/a&gt;.&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/22823865688</link><guid>http://blog.brianhouse.net/post/22823865688</guid><pubDate>Thu, 10 May 2012 23:33:33 -0400</pubDate><category>multitudes</category><category>performance</category><category>punk</category><category>hardcore free punk</category></item><item><title>Cutting records, literally, with favorite new collaborator and...</title><description>&lt;img src="http://25.media.tumblr.com/tumblr_m3jdmogXHX1qk20gto1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;Cutting records, literally, with favorite new collaborator and artist &lt;a href="http://www.secretshape.com/" target="_new"&gt;Ted Riederer&lt;/a&gt;. We’re working on my new sonification piece, coming to Eyebeam in June.&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/22433064140</link><guid>http://blog.brianhouse.net/post/22433064140</guid><pubDate>Sat, 05 May 2012 02:20:48 -0400</pubDate><category>vinyl</category><category>ted riederer</category><category>sonification</category></item><item><title>HISTORICAL DATA FROM PACHUBE
[code] Python (2.6), GPL
Pulling...</title><description>&lt;img src="http://25.media.tumblr.com/tumblr_m3ik3e4QCO1qk20gto1_500.png"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;&lt;b&gt;HISTORICAL DATA FROM PACHUBE&lt;/b&gt;&lt;br/&gt;
[&lt;a href="http://brianhouse.net/files/pachube_historical.txt"&gt;code&lt;/a&gt;] Python (2.6), GPL&lt;br/&gt;&lt;br/&gt;
Pulling historical data from Pachube is not entirely straightforward. I appreciate the design of their &lt;a href="https://pachube.com/docs/v2/" target="_new"&gt;API&lt;/a&gt;, which is designed primarily to ingest live feeds, and otherwise encourages sampling data feeds at larger, regular intervals. However, for signal processing exercises, you really do want all the samples within a time range, and that necessitates a lot of requests (every 6 hours, paginated).&lt;br/&gt;&lt;br/&gt;
This script will pull the last week of data given a datastream identifier.&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/22400908807</link><guid>http://blog.brianhouse.net/post/22400908807</guid><pubDate>Fri, 04 May 2012 17:17:09 -0400</pubDate><category>pachube</category><category>code</category></item><item><title>For the Sound Research Summit at Eyebeam last Saturday, I wanted...</title><description>&lt;span id="video_player_22400891303"&gt;[&lt;a href="http://www.adobe.com/shockwave/download/download.cgi?P1_Prod_Version=ShockwaveFlash" target="_blank"&gt;Flash 10&lt;/a&gt; is required to watch video.]&lt;/span&gt;&lt;script type="text/javascript"&gt;renderVideo("video_player_22400891303",'http://blog.brianhouse.net/video_file/22400891303/tumblr_m3ic1o5CZI1qk20gt',400,225,'poster=http%3A%2F%2Fmedia.tumblr.com%2Ftumblr_m3ic1o5CZI1qk20gt_r1_frame1.jpg,http%3A%2F%2Fmedia.tumblr.com%2Ftumblr_m3ic1o5CZI1qk20gt_r1_frame2.jpg,http%3A%2F%2Fmedia.tumblr.com%2Ftumblr_m3ic1o5CZI1qk20gt_r1_frame3.jpg,http%3A%2F%2Fmedia.tumblr.com%2Ftumblr_m3ic1o5CZI1qk20gt_r1_frame4.jpg,http%3A%2F%2Fmedia.tumblr.com%2Ftumblr_m3ic1o5CZI1qk20gt_r1_frame5.jpg')&lt;/script&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;For the &lt;a href="http://www.eyebeam.org/events/sound-research-summit" target="_new"&gt;Sound Research Summit&lt;/a&gt; at Eyebeam last Saturday, I wanted to develop a concept of sonification. Or musicalization. Or something having to do with some manner of legible sound that has a structural relationship to data.

It’s something I’ve been resistant to exploring in the past, because it is so easy to lose any perception of the source (ie, what the data is actually about) in the audible result. One-to-one mappings threaten to be too naive (stock market goes up, pitch goes up), and complex mappings might as well be driven by a random number generator. Nonetheless, sonification is a potentially important rhythmanalysis strategy, so I wanted to try.&lt;br/&gt;&lt;br/&gt;
I am interested in primarily time-domain signals, so I think the key point of departure is to use sources that have inherent periodicity and to tease that out. I cant believe I havent done a project with &lt;a href="http://pachube.com" target="_new"&gt;pachube.com&lt;/a&gt; before — it’s a clearinghouse of open data for Internet-of-things enthusiasts, with DIY feeds of everything from the temperature of some guy’s fish tank to radiation level at Fukushima. Through the Pachube API, I downloaded historical samples of arbitrary feeds (code &lt;a href="http://blog.brianhouse.net/post/22400908807"&gt;here&lt;/a&gt;). I wanted the sound to reveal any periodicity and highlight variations from it — to check for periodicity, I applied &lt;a href="http://en.wikipedia.org/wiki/Autocorrelation" target="_new"&gt;autocorrelation&lt;/a&gt; to the signal (getting comfortable with this technique and assembling a set of python functions was a super useful part of this exercise). What I discovered, unsurprisingly, is that many of these data streams cycle diurnally, and so for the purposes of this event I decided to just apply a 24-hour cycle across the board.&lt;br/&gt;&lt;br/&gt;
I downloaded a weeks worth of data for each feed, and chunked each one into 24-hour segments — each segment essentially becomes a measure. After smoothing and normalizing the signal, I resampled it to a musical pulse of 12hz. So the result is basically a single parameter that changes in musical time with a high and low value in each measure.&lt;br/&gt;&lt;br/&gt;
To give that substance, I opted for hardware. I am enamored of the &lt;a href="http://meeblip.com/" target="_new"&gt;Meeblip&lt;/a&gt; synth for its inherent limitations, hackability, and lo-fi sound (and price). Running it through my pedal board offers some nice possibilities, and hews closer to a more punk/noise sound which is more my thing rather than clean electronic aesthetic that screams futurism. I’m running everything in python and sending MIDI to the synth. I mapped the changing parameter to filter width to give a sense of pitch variation without actual tonal change. Each data source drones on a random fundamental.&lt;br/&gt;&lt;br/&gt;
For the purposes of the event, I fell upon the concept of using an old CRT display to show a visualization of what was being sonified. In building a display for Mary Mattingly’s Flock House (which I haven’t yet posted about), I was a little dismayed at having made a shiny touchable thing on a nice flat monitor, as it points too much toward screen-based interaction — this time, I wanted to invoke an old radar display, and I made a spiral which arrays the data with a turn for each day. Again, animated in python.&lt;br/&gt;&lt;br/&gt;
Artistically, this isn’t satisfying as a complete piece. I’ve created this sculptural display, which makes me somewhat uncomfortable, as I’d like it to have a greater relational component. In the context of the summit, that came for free — the piece became a focus of roving improvisers, and established a nice counterpoint with &lt;a href="http://www.benhouge.com/" target="_new"&gt;Ben Houge&lt;/a&gt;’s sonification work 10-ft over (he tuned his work to fit harmonically with mine).&lt;br/&gt;&lt;br/&gt;
But the next iteration of this idea will have to feature some sort of comparison between multiple sources to make it work. It’s about the inherent &lt;i&gt;relative&lt;/i&gt; musicality of phenomena and the participation of the viewer in that relationship. I’m brainstorming ideas.&lt;br/&gt;&lt;br/&gt;
I regret that my documentation for this sucks, though it’s motivation to produce a followup.&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/22400891303</link><guid>http://blog.brianhouse.net/post/22400891303</guid><pubDate>Fri, 04 May 2012 17:16:00 -0400</pubDate><category>eyebeam</category><category>sonification</category><category>Pachube</category></item><item><title>I had the privilege of participating in an advisory summit for...</title><description>&lt;img src="http://24.media.tumblr.com/tumblr_m3bl06zlph1qk20gto1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;I had the privilege of participating in an advisory summit for &lt;a href="http://www.storycorps.org/" target="_new"&gt;StoryCorps&lt;/a&gt; today — it was a fantastic conversation about the possibilities an innovative oral history archive might fulfill in the shifting media and research landscapes. You may have heard some of StoryCorps inspiring content in edited form on NPR. What people may not realize is that each interview is 40 minutes long, and to date there are 41,000+ recorded stories in the database. That makes StoryCorps an audio repository of singular importance, and not just from a content perspective. It’s both a corpus of speech data spanning geography and demographics of immeasurable interest to linguists and computer scientists, and it’s a source of reference material that I think warrants mention in the same breath as NYT or Wikipedia. The trick, of course, is making that content accessible — there is currently no externally exposed search capabilities, let alone a programmatic interface that would make mash-ups with NYT or NYPL or innovative apps readily possible (my personal priority was to push deep linking of audio segments with canonical urls, to enable StoryCorps references in things like Wikipedia articles). All that is going to change as their amazing team plans the future of the platform. They are looking for ideas and collaborators, so get in touch.&lt;br/&gt;&lt;br/&gt;&lt;i&gt;image credit WXXI.org&lt;/i&gt;&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/22162539200</link><guid>http://blog.brianhouse.net/post/22162539200</guid><pubDate>Mon, 30 Apr 2012 21:19:16 -0400</pubDate><category>storycorps</category><category>archive</category><category>hacking</category><category>future</category><category>oral history</category></item><item><title>Last weekend I participated in the Sound Research Summit @...</title><description>&lt;img src="http://25.media.tumblr.com/tumblr_m2yvu9j7Wu1qk20gto1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;Last weekend I participated in the &lt;a href="http://eyebeam.org/events/sound-research-summit" target="_new"&gt;Sound Research Summit&lt;/a&gt; @ Eyebeam, a bazaar of sound-works in progress and experiments in listening curated by &lt;a href="http://jacksonmoore.net/" target="_new"&gt;Jackson Moore&lt;/a&gt;. I thought the event was successful in juxtaposing a diversity of vocabularies through which we might approach sound, from &lt;a href="http://www.kyleclyde.com/" target="_new"&gt;Kyle Kessler&lt;/a&gt; directly manipulating a plate reverb (shown) to &lt;a href="http://www.benhouge.com/" target="_new"&gt;Ben Houge&lt;/a&gt;’s abstracted sonification of data from sensors at MIT. The result both embodied the spirit of research by challenging any particular framework as well as served as a collective performance in which the audible and conceptual boundaries between the works were continually renegotiated.&lt;br/&gt;&lt;br/&gt;
Particularly rewarding for me was the chance to work with &lt;a href="http://christinesunkim.com/" target="_new"&gt;Christine Sun Kim&lt;/a&gt;. Christine has been deaf from birth, but works with sound as her primary medium. She employs various strategies (such as transducers, piano wire, and feedback at the summit) to emphasize the tactile nature of sound and make it perceptible to her. However, I think that to suggest that she is simply transposing between senses is incorrect — it’s also the semantic and cultural components of sound, how and why we encode it, that comes across in what she does, and which for her I imagine is in many ways more readily approachable. Assisting her with her piece brought this into relief as we debated the qualities of sound it produced and I stumbled over my vocabulary.&lt;br/&gt;&lt;br/&gt;
More on my work for the summit next post.&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/21700514213</link><guid>http://blog.brianhouse.net/post/21700514213</guid><pubDate>Tue, 24 Apr 2012 00:44:32 -0400</pubDate><category>eyebeam</category><category>sound research summit</category><category>workshop</category><category>sound</category><category>exhibition</category></item><item><title>56k RINGTONE
I end up talking about the aesthetics of obsolete...</title><description>&lt;embed type="application/x-shockwave-flash" src="http://assets.tumblr.com/swf/audio_player_black.swf?audio_file=http://www.tumblr.com/audio_file/21686932771/tumblr_m2ymcrFBhg1qk20gt&amp;color=FFFFFF" height="27" width="207" quality="best" wmode="opaque"&gt;&lt;/embed&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;&lt;b&gt;56k RINGTONE&lt;/b&gt;&lt;br/&gt;&lt;br/&gt;
I end up talking about the aesthetics of obsolete technology more than I’m comfortable with as it is, but somehow the other day it suddenly seemed really imperative to have a 56k modem handshake as a ringtone. @akamediasystem made me do it. This is already everywhere online, but I’m posting my version here anyway.&lt;br/&gt;&lt;br/&gt;&lt;a href="http://brianhouse.net/files/modem.m4r.zip"&gt;modem.m4r.zip&lt;/a&gt;&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/21686932771</link><guid>http://blog.brianhouse.net/post/21686932771</guid><pubDate>Mon, 23 Apr 2012 21:19:00 -0400</pubDate><category>modem</category><category>handshake</category><category>56k</category><category>retro</category><category>audio</category></item><item><title>New Multitudes video by David Feinberg for “Horse”,...</title><description>&lt;iframe width="400" height="225" src="http://www.youtube.com/embed/uYMOG2lquSE?wmode=transparent&amp;autohide=1&amp;egm=0&amp;hd=1&amp;iv_load_policy=3&amp;modestbranding=1&amp;rel=0&amp;showinfo=0&amp;showsearch=0" frameborder="0" allowfullscreen&gt;&lt;/iframe&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;New Multitudes video by &lt;a href="http://hi-df.com/" target="_new"&gt;David Feinberg&lt;/a&gt; for “Horse”, off our album &lt;a href="http://multitudes.bandcamp.com/album/twelve-branches" target="_new"&gt;Twelve Branches&lt;/a&gt; (download the album $free).&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/20287537012</link><guid>http://blog.brianhouse.net/post/20287537012</guid><pubDate>Sun, 01 Apr 2012 11:01:29 -0400</pubDate><category>multitudes</category><category>video</category><category>horse</category><category>twelve branches</category><category>punk rock</category></item><item><title>I am incredibly excited to announce that I’ve joined...</title><description>&lt;img src="http://25.media.tumblr.com/tumblr_m0qggjst2o1qk20gto1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;I am incredibly excited to announce that I’ve joined &lt;a&gt;Eyebeam Art and Technology Center&lt;/a&gt; as a resident artist for the spring / summer cycle. it’s been a blast meeting everyone, and I’m intimidated and inspired by &lt;a href="http://eyebeam.org/blogs/roddy/announcing-2012-springsummer-residencies-and-2012-fellowships" target="_new"&gt;my new colleagues&lt;/a&gt;. The residency will complement my work in personal data and sensor networks at the Times — I’ll be exploring similar themes, but in more of a sound-art medium and context.&lt;br/&gt;&lt;br/&gt;
Specifically, Im going to try an execute the first iteration of a concept I first presented at Conflux in October (and named this blog after), &lt;a href="http://rhythmanalysislab.org" target="_new"&gt;The Rhythmanalysis Lab&lt;/a&gt;. Taking the essays of Henri Lefebvre as a starting point, I want to develop a methodology for investigating rhythm as a primary object in personal, architectural, and urban spheres.&lt;br/&gt;&lt;br/&gt;
Ideas, collaborations, talk to me. More to come.&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/19129617346</link><guid>http://blog.brianhouse.net/post/19129617346</guid><pubDate>Sun, 11 Mar 2012 14:24:18 -0400</pubDate><category>eyebeam</category><category>residency</category><category>rhythmanalysis</category></item><item><title>This weekend at AAG (Association of American Geographers) Annual...</title><description>&lt;img src="http://25.media.tumblr.com/tumblr_lzzizcK2Nv1qk20gto1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;This weekend at AAG (Association of American Geographers) &lt;a href="http://www.aag.org/annualmeeting" target="_new"&gt;Annual Meeting&lt;/a&gt;. I presented the following paper in a session led by &lt;a href="http://www.sethspielman.org/" target="_new"&gt;Seth Spielman&lt;/a&gt; (who does some amazing work identifying “personal cities” through geopaths). And I got to hang out with the imitable &lt;a href="http://www.spatialinformationdesignlab.org/" target="_new"&gt;Sarah Williams&lt;/a&gt;.&lt;br/&gt;&lt;br/&gt;&lt;br/&gt;
OpenPaths: A new approach to aggregating personal geographic data&lt;br/&gt;&lt;br/&gt;
The collection of personal geographic data from mobile devices is a ubiquitous practice of service providers and application developers. These data are being stored, analyzed, and monetized primarily by corporate interests; there is limited agency for individuals over their own data. Awareness among the public regarding the value of their personal data is nascent. OpenPaths, created by the Research and Development Lab at the New York Times Company, is a platform and a model and a platform that demonstrates the collective value of personal data sovereignty. It was developed in response to widespread media coverage of the obfuscated but accessible location record generated by all Apple iOS devices. OpenPaths participants store their encrypted geographic data in a cloud infrastructure while maintaining ownership and programatic control. Projects of many kinds, from mobility research to expressive artwork, petition individuals for access to their data in exchange for a stake in the outcome of the project. Ultimately, we would like to activate the practice of “participatory sensing” on a large scale in a way that self-regulates the creation of ad-hoc geographic datasets. Furthermore, within a theoretical context, OpenPaths moves beyond locative media’s primary concerns with connectivity, the coupling of data to place, and spatial representation to address the components of an ethical implementation of crowd-sourced geographic systems in the age of “big data”. How can we seat the individual in a mode of control over personal geographic narratives in a society in which locative media has become banal?&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/18298705837</link><guid>http://blog.brianhouse.net/post/18298705837</guid><pubDate>Sun, 26 Feb 2012 00:23:36 -0500</pubDate><category>speaking</category><category>AAG</category><category>geography</category><category>conference</category><category>openpaths</category></item><item><title>Here’s me at the Internet of Things Meetup on Thursday. I...</title><description>&lt;img src="http://25.media.tumblr.com/tumblr_lzzifzvgd01qk20gto1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;Here’s me at the &lt;a href="http://www.meetup.com/iotnewyork/events/48336912/" target="_new"&gt;Internet of Things Meetup&lt;/a&gt; on Thursday. I presented &lt;a href="https://openpaths.cc" target="_new"&gt;OpenPaths&lt;/a&gt; while Jake evangelized &lt;a href="http://datawithoutborders.cc/" target="_new"&gt;Data Without Borders&lt;/a&gt;, and @edborden tried to get us drunk. Good times.&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/18298070673</link><guid>http://blog.brianhouse.net/post/18298070673</guid><pubDate>Sun, 26 Feb 2012 00:11:59 -0500</pubDate><category>speaking</category><category>meetup</category><category>internet of things</category><category>openpaths</category></item><item><title>MULTITUDES w/ Erostratus, Cathy, Sun Ladders
we’re playing...</title><description>&lt;img src="http://25.media.tumblr.com/tumblr_lz78wz6b1s1qk20gto1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;&lt;a href="http://multitudes.bandcamp.com" target="_new"&gt;MULTITUDES&lt;/a&gt; w/ &lt;a href="http://sunladders.bandcamp.com/" target="_new"&gt;Erostratus&lt;/a&gt;, &lt;a href="http://www.myspace.com/thenewfeelings" target="_new"&gt;Cathy&lt;/a&gt;, &lt;a href="http://sunladders.bandcamp.com/" target="_new"&gt;Sun Ladders&lt;/a&gt;&lt;br/&gt;&lt;br/&gt;
we’re playing tonight at &lt;a href="http://maps.google.com/maps/place?q=lulu%27s+bar+brooklyn&amp;hl=en&amp;cid=9277324803138255625" target="_new"&gt;Lulu’s&lt;/a&gt;, in Greenpoint, $free, starts at 9&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/17391115918</link><guid>http://blog.brianhouse.net/post/17391115918</guid><pubDate>Fri, 10 Feb 2012 17:53:00 -0500</pubDate><category>multitudes</category><category>performance</category><category>hardcore psych</category></item><item><title>PUCK: PUCK of Ubiquitous Contextual Knowledge™Internet-of-things...</title><description>&lt;img src="http://25.media.tumblr.com/tumblr_lz4x5lKzwU1qk20gto1_500.jpg"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;&lt;b&gt;&lt;i&gt;PUCK&lt;/i&gt;&lt;/b&gt;: &lt;b&gt;P&lt;/b&gt;UCK of &lt;b&gt;U&lt;/b&gt;biquitous &lt;b&gt;C&lt;/b&gt;ontextual &lt;b&gt;K&lt;/b&gt;nowledge&lt;b&gt;™&lt;/b&gt;&lt;br/&gt;&lt;br/&gt;&lt;a href="http://en.wikipedia.org/wiki/Internet_of_Things" target="_new"&gt;Internet-of-things&lt;/a&gt; / &lt;a href="http://" target="_new"&gt;ubiquitous computing&lt;/a&gt; … these concepts have been central to &lt;a href="http://nytlabs.com" target="_new"&gt;NYTLabs&lt;/a&gt; thinking over the last year (and related to much of my past work &lt;a href="http://brianhouse.net/works/yellow_arrow" target="_new"&gt;1&lt;/a&gt;, &lt;a href="http://brianhouse.net/works/reveal" target="_new"&gt;2&lt;/a&gt;). They are old ideas, but we are finally seeing their fruition in interesting consumer products on the market.&lt;br/&gt;&lt;br/&gt;
I’m into two concepts in particular: &lt;a href="http://supermechanical.com/twine/" target="_new"&gt;Twine&lt;/a&gt; and &lt;a href="http://www.greengoose.com/" target="_new"&gt;GreenGoose&lt;/a&gt;. Both are looking at dirt simple, generalized hardware (particularly the mighty accelerometer) that wirelessly spit data up to the cloud. Server-side software can then contextualize that data to serve any number of social purposes, like alerting you when the mail comes (Twine) or keeping tabs on whether the dog is getting fed (GreenGoose). It hits that middle range of Greenfield’s notion of scale — the level of the room (as opposed to the individual, building, or street) — which I think is a particularly ripe area.&lt;br/&gt;&lt;br/&gt;
So in tribute I wanted to create our own version at NYTLabs (after acronym brainstorming w/ @mboggie). The idea is a small, generalized piece of hardware that you can attach to a physical thing in your world which can be programmatically assigned to monitor interesting events. It should have long battery life and report data from the accelerometer and other sensors wirelessly. Its logic should be on the server somewhere, not burned into the device, and it should have HTTP and UDP interfaces. And finally, in my twist on the concept, I want it to respond to touch, so that if you pick it up, it turns into a high-resolution controller, like a Nintendo Wii. The idea is to then have hundreds of these all over everything. I’ve been picking at this the last few months, and finally have a proof of concept running.&lt;br/&gt;&lt;br/&gt;
The core component of PUCK is the &lt;a href="http://en.wikipedia.org/wiki/XBee" target="_new"&gt;XBee&lt;/a&gt;. XBees rule. A network of lightweight components is in itself aesthetically appealing, and in essence, all I want to do here is hook a sensor up to one. The XBee is smart enough that this can be done without the help of an Arduino or other microcontroller, which is essential to keeping down the cost.&lt;br/&gt;&lt;br/&gt;
The path I went down and should not have is trying to figure out how to program them directly in python over the serial port. Instead, Andrew Rapp has an &lt;a href="http://code.google.com/p/xbee-api/" target="_new"&gt;awesome java library&lt;/a&gt; and a wealth of documentation that is the way to go. I got hung up in that I didn’t just want to collect data from the XBee, I wanted to reprogram its behavior on the fly, using ‘API’ mode — this library has all that hard work in place.&lt;br/&gt;&lt;br/&gt;
In any case, the rest of the design here comprises an accelerometer, tilt switch, and LED. The tilt switch is able to wake up an XBee — it’s quite sensitive, so moving the device at all can take it from a mode where its just periodically reporting data and put it into high-frequency reporting mode. Finally, the LED just indicates when the puck is awake. When we get a MakerBot I’ll design a housing.&lt;br/&gt;&lt;br/&gt;
On the server side, I’m pushing the data into &lt;a href="http://redis.io" target="_new"&gt;Redis&lt;/a&gt; and rebroadcasting it via OSC. The next step is to figure out how to architect the signal processing and the nature of the interface.&lt;br/&gt;&lt;br/&gt;
But I’m far from a hardware ninja, so I’m pleased to have something together that I can experiment with. Updates to come.&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/17322070284</link><guid>http://blog.brianhouse.net/post/17322070284</guid><pubDate>Thu, 09 Feb 2012 11:44:00 -0500</pubDate><category>PUCK</category><category>nytlabs</category><category>prototype</category><category>xbee</category><category>ubiquitous computing</category></item><item><title>Some OpenPaths news: in the last couple of weeks we’ve...</title><description>&lt;img src="http://24.media.tumblr.com/tumblr_lyty3ufket1qk20gto1_500.png"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;Some OpenPaths news: in the last couple of weeks we’ve revamped the service and launched &lt;a href="http://itunes.apple.com/app/openpaths/id493605283" target="_new"&gt;iPhone&lt;/a&gt; and &lt;a href="https://market.android.com/details?id=com.nytco.rnd.OpenPaths" target="_new"&gt;Android&lt;/a&gt; applications — it’s been exciting to hear about people using the platform again (&lt;a href="https://twitter.com/#!/search/openpaths" target="_new"&gt;OP on Twitter&lt;/a&gt;).&lt;br/&gt;&lt;br/&gt;&lt;a href="http://flowingdata.com/2012/01/26/own-and-securely-store-your-location-with-openpaths/" target="_new"&gt;Flowing data&lt;/a&gt; posts:&lt;br/&gt;
“There are a lot of ways to collect your location, whether it’s for journaling and personal reflection or for sharing with others, but it can be tricky making use of your data once it’s stored behind company servers.”&lt;br/&gt;&lt;br/&gt;&lt;a href="https://openpaths.cc" target="_new"&gt;OpenPaths&lt;/a&gt; is different.&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/16982871511</link><guid>http://blog.brianhouse.net/post/16982871511</guid><pubDate>Fri, 03 Feb 2012 13:31:00 -0500</pubDate><category>data liberation</category><category>OpenPaths</category><category>iphone</category><category>android</category><category>self surveillance</category></item><item><title>Need some color on this blog. Heres some detritus from...</title><description>&lt;img src="http://24.media.tumblr.com/tumblr_lxqv8tGBY51qk20gto1_500.png"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;Need some color on this blog. &lt;a href="http://s3.amazonaws.com/data.tumblr.com/tumblr_lxqv8tGBY51qk20gto1_1280.png"&gt;Heres&lt;/a&gt; some detritus from data-sketching yesterday.&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/15777580254</link><guid>http://blog.brianhouse.net/post/15777580254</guid><pubDate>Fri, 13 Jan 2012 11:02:00 -0500</pubDate><category>python</category><category>drawing</category></item><item><title>CLUSTERING DATA IN PYTHON

[code] Python (2.6), GPLPreviously, I...</title><description>&lt;img src="http://24.media.tumblr.com/tumblr_lxlmjrBV7q1qk20gto1_500.png"/&gt;&lt;br/&gt;&lt;br/&gt;&lt;p&gt;&lt;b&gt;CLUSTERING DATA IN PYTHON&lt;/b&gt;&lt;br/&gt;

[&lt;a href="http://brianhouse.net/files/clustertree.txt"&gt;code&lt;/a&gt;] Python (2.6), GPL&lt;br/&gt;&lt;br/&gt;&lt;a href="http://blog.brianhouse.net/post/13237909720"&gt;Previously&lt;/a&gt;, I demonstrated clustering approximate geographic points from &lt;a href="https://openpaths.cc" target="_new"&gt;OpenPaths&lt;/a&gt; to identify places of interest. Heres the code I used to accomplish that, which can be applied to any dataset, it doesnt have to be limited to two dimensions. The algorithm is known as &lt;a href="http://en.wikipedia.org/wiki/Hierarchical_clustering" target="_new"&gt;agglomerative hierarchical clustering&lt;/a&gt; because it works by repeatedly grouping the closest two nodes together, starting with each data point as a node, and ending with the entire set in a single monster node. (“Closest” is defined by any distance metric; for many applications, it will be &lt;a href="http://en.wikipedia.org/wiki/Euclidean_distance" target="_new"&gt;euclidean distance&lt;/a&gt;, but for geographic data, Im using the &lt;a href="http://en.wikipedia.org/wiki/Haversine_formula" target="_new"&gt;haversine distance formula&lt;/a&gt;.) Along the way, youve constructed a &lt;a href="http://en.wikipedia.org/wiki/Binary_tree" target="_new"&gt;binary tree&lt;/a&gt; which represents the hierarchical relationships between the vectors in the set. The result is a kind of ad-hoc taxonomy, and is frequently used to hypothesize relatedness between images, documents, proteins, users, etc. (heres a &lt;a href="http://brianhouse.net/files/clustering.png"&gt;nice diagram&lt;/a&gt; courtesy &lt;a href="http://cs.jhu.edu/~razvanm/" target="_new"&gt;Razvan Musaloiu-E.&lt;/a&gt;)&lt;br/&gt;&lt;br/&gt;
To use agglomerative clustering as a classifier, however, what we really want is just a flat set of clusters. It’s akin to choosing the branches of the tree that best represent the natural divisions in the data. Cut too close to the trunk and the clusters will be too general; cut by the leaves and youve got too much noise. With geographic information from OpenPaths, at least, we have a heuristic to decide what is appropriate — the platform is only going to be accurate to a quarter-mile or so, so we can look for the largest branches that do not exceed that limit. The code provides a method, &lt;span style="font-family: monospace"&gt;get_pruned&lt;/span&gt;, that takes such a parameter and returns a resulting set of clusters.&lt;br/&gt;&lt;br/&gt;
Clustering packages for python are &lt;a href="http://code.google.com/p/scipy-cluster/" target="_new"&gt;out there&lt;/a&gt;, but I prefer touching the code and this is a dirt simple implementation that nonetheless should prove effective for most creative coding purposes.&lt;/p&gt;</description><link>http://blog.brianhouse.net/post/15629863565</link><guid>http://blog.brianhouse.net/post/15629863565</guid><pubDate>Tue, 10 Jan 2012 15:07:00 -0500</pubDate><category>code</category><category>clustering</category><category>machine learning</category><category>python</category><category>mapping</category><category>analytics</category></item></channel></rss>

