Archive

Archive for the ‘General Thoughts’ Category

Greener Than Expected

August 8th, 2011

I just picked up one of the new Mac Minis that Apple released this summer, which added the Thunderbolt port, dropped the optical drive, and ship with the new Intel i5 and i7 CPUs. Given that this is largely nerd talk, most of that isn’t particularly germane to the story, except the new processors, which were originally designed for laptop use (they’re also shipping in the new Thunderbolt-equipped MacBook Airs).

This computer replaced a five year-old Mac Pro; the very first tower Mac that Apple shipped with Intel CPUs.

In a nut, the Mac Pro had been a trusty computer, and actually still works splendidly. The only trouble is that it takes up a bunch of floor space, guzzles electricity, and – most painfully, during a NYC summer – kicks off a ton of heat. I was looking to lower all three profiles.

As part of my intention to use less electricity, I also picked up a Digital POWERCENTER 650G “GreenPower” surge protector, by Monster. It looks like this:

For anyone unfamiliar with Monster’s “GreenPower” products, they describe the line as follows:

Monster GreenPower™ is a revolutionary new way to automatically reduce energy waste and save you money. Simply plug your computer into the GreenPower Control socket. When it’s turned off or goes to sleep, the other GreenPower sockets switch off, automatically eliminating energy wasted by peripherals, like your monitor and scanner, when you’re not using them. When your computer turns back on, the GreenPower sockets automatically power up again.

The gist is that the surge protector has one “master” socket (labeled above as “computer”), into which you’re meant to plug the “primary device”, and a number of “subordinate” sockets (for the various accessories attached to the computer), which only get juice when the device on the “master” socket is consuming 17 Watts or more of power1. The surge protector also has a single “independent” socket (labeled “modem” in the photo above), into which you can plug a device that isn’t part of the “master / subordinate” equation.

So, following the direction suggested by the labeling, I plugged the Mac Mini into the “master” socket, and plugged the monitor, printer, speakers, and USB hub into the “subordinate” sockets. The “independent” socket remained unused.

Then I turned the computer on. The “subordinate” devices remained off for a few seconds. But once the startup process was in full swing, the monitor came to life, I heard the printer begin to do its “wakeup dance”, and the speakers popped as power flowed to them!

Then the login screen came up, and the monitor, et al lost power.

I figured that I just needed to get past the login and start using the computer, and that this would keep everything juiced up. So I typed my password and hit the ENTER key. Immediately the monitor came back to life, the printer did it’s initialization dance, and the speakers popped to life again, while the Finder launched, my “startup items” got spawned, and Lion restored my application state from before I had shut the computer down in order to replace the old surge protector.

As I reached to the trackpad, however, the monitor and the rest of the devices plugged into the “subordinate” sockets all shut off again; the Mini simply did not consistently draw enough power to meet the 17 Watt minimum required from the “master” socket in order to activate its subordinates.

Remember when I mentioned that i5 Intel CPU back at the top? Apparently they are particularly energy efficient.

No wonder Apple put ‘em in the Air.

I started to wonder, however, if I’d just bought some new but utterly useless thing, destined to merely collect dust.

So I plugged the monitor into the still-free “independent” socket, and managed to safely shut the computer down again. While was clear to me that the Mini couldn’t be the device plugged into the “master” socket, it simply wasn’t safe to plug it into the “subordinate” sockets. So it had to take the “independent” socket, while some other device was to be used to drive the “master” socket.

At first, I tried plugging the monitor into the “master”. It seemed like a reasonable selection, given that putting the computer to sleep would cut the video signal, hence putting the monitor into standby mode.

Switching it on, I learn the monitor had no trouble driving the master socket. At all.

But now I had two devices (the Mini and the Monitor) which would be sipping power 24 hours a day, even in standby mode. My savings were diminishing. I also keep a clamp light next to my desk, which I always turn on when I’m using the computer. I’ve presently got a 60W bulb in it; which uses far more than the 17W minimum required to drive the “subordinate” accessories. And it draws ZERO Watts when switched off.

And so I’d found the winner.

So, in the end, the device powering setup on the surge protector looks like this:

Master Lamp (60W on; 0W off)
Subordinates Monitor, Printer, Speakers, USB hub (various power consumption rates)
Independent Mini (apparently mostly south of 17W on; ~4W in sleep)

There is also no longer a Mac Pro on the floor, claiming 6″ of space between the wall and my desk; and the corner remains much cooler, letting me run the AC at lower levels.

Footnotes

  1. I couldn’t find this official information on Monster’s website, but here’s a Google search which should offer up some reference material for the curious

General Thoughts , , , ,

Comparative Inclines

January 14th, 2011

I found a curious Business Insider post via Daring Fireball, which contained the following chart, visualizing the growth rate of various “smart phone” platforms, across carriers:

Chart [hosted by businessinsider.com]

I’m noticing a significant difference in the angle of elevation that the Android adoption curve is showing, amongst the different carriers. Specifically, I’m looking at how it’s showing the flattest rate of growth on AT&T, the only carrier on that list that’s also offering the iPhone.

General Thoughts , , , ,

The Twelve Year Road

December 20th, 2009

In January of 1998, Netscape — in a last-ditch effort to retaliate against Microsoft’s domination of the browser market with its Internet Explorer browser — took to the strategy of open sourcing the source code for their flagship product, Netscape Navigator. And so the Mozilla Project was born, which has since brought the world the Firefox web browser, and the Thunderbird email client (as well a handful of other things).

And only now, at the end of December 2009, Firefox 3.5 — the latest release of the software open sourced twelve years ago — has at long last eked out ahead of any single version of rival Internet Explorer.

Source: StatCounter Global Stats – Browser Version Market Share

It’s been a long road, Mozilla; congratulations on this hard-earned milestone.

General Thoughts

Climategate: a Case Study in How Not to Conduct Research

November 25th, 2009

Sometimes events arrive with a timing that is both serendipitous and uncanny. Only days after my last post, wherein I state a case for the growing importance of referencing the datasets and algorithms used in the distillation of research conclusions, comes a story about leaked correspondence records (email messages) amongst climate researchers working in affiliation with the East Anglia Climate Research Unit, or CRU.

From the NYT article:

The e-mail messages, attributed to prominent American and British climate researchers, include discussions of scientific data and whether it should be released, exchanges about how best to combat the arguments of skeptics…. Drafts of scientific papers … were also among the hacked data, some of which dates back 13 years.

To say the least, the leak contains some juicy fodder for skeptics of human-driven climate change amongst the leaked materials.

Amongst these leaked emails, for example, are conversations which document various difficulties some of the CRU’s climate researchers have encountered over the years in trying to work with the data collected and managed by the organization. The Times article focuses on a discussion thread in which researcher Phil Jones mentions using a “trick” — originally employed by another colleague, Michael Mann — to “hide [a] decline” in temperatures apparently shown in some set of data.

In an interview about the leaked emails, Dr. Mann attempts to defuse the statement as a poor choice of words. Unfortunately, whether he’s being sincere or not, his is frankly a response that’s to be expected.

The article continues:

Some skeptics asserted Friday that the correspondence revealed an effort to withhold scientific information. “This is not a smoking gun; this is a mushroom cloud,” said Patrick J. Michaels, a climatologist who has long faulted evidence pointing to human-driven warming and is criticized in the documents.

This is also a statement that you’d expect from a climatologist building a career on a body of work disagreeing with the idea of human-driven warming. These emails are naturally material that skeptics of the human-driven climate change argument will latch onto (and, frankly, they certainly should; it’s just how scientific work is tested — through dispute).

The next several days sees a flurry of activity throughout the media and the blogosphere.

Before long, the name “Climategate” (kitschy but concise) gets attached to the discussions about the leaked materials. And since there’s a bit of both data and program source code in the mix, techies from around the world immediately jump into the fray.

One of the most popular files from the leak discussed most heavily in techie circles is called HARRY_READ_ME.txt (copies available in both original format and more structured edition). The story that unfolds in this file reveals the plight of a programmer named Harry who had struggled for three years, attempting to reproduce some research results with a collection of data and the source code for an algorithm created to calculate research conclusions.

Sadly, this man’s three-year effort to reproduce the published results with the given material never succeeded. Here’s an excerpt from the file, for a glimpse at this poor fella’s mounting frustrations along the way:

getting seriously fed up with the state of the Australian data. so many new stations have been introduced, so many false references.. so many changes that aren’t documented. Every time a cloud forms I’m presented with a bewildering selection of similar-sounding sites, some with references, some with WMO codes, and some with both. And if I look up the station metadata with one of the local references, chances are the WMO code will be wrong (another station will have it) and the lat/lon will be wrong too. I’ve been at it for well over an hour, and I’ve reached the 294th station in the tmin database. Out of over 14,000. Now even accepting that it will get easier (as clouds can only be formed of what’s ahead of you), it is still very daunting. I go on leave for 10 days after tomorrow, and if I leave it running it isn’t likely to be there when I return! As to whether my ‘action dump’ will work (to save repetition).. who knows?

Yay! Two-and-a-half hours into the exercise and I’m in Argentina!

Pfft.. and back to Australia almost immediately :-( .. and then Chile. Getting there.

Unfortunately, after around 160 minutes of uninterrupted decision making, my screen has started to black out for half a second at a time. More video cable problems – but why now?!! The count is up to 1007 though.

I am very sorry to report that the rest of the databases seem to be in nearly as poor a state as Australia was. There are hundreds if not thousands of pairs of dummy stations, one with no WMO and one with, usually overlapping and with the same station name and very similar coordinates. I know it could be old and new stations, but why such large overlaps if that’s the case? Aarrggghhh! There truly is no end in sight.

Assuming the original conclusions he was attempting to reproduce were all based on this data (and, there’s frankly no reason not to), it’s impossible to invest much confidence in their validity.

Martin points out that the data and algorithms with which Harry was working were “inherited” from a previous researcher (or researchers), and came in a poorly-organized bundle with poor documentation. And what’s worse, he didn’t have access to anyone who had originally derived the conclusions he was tasked to reproduce.1

The real egg in the face of this anecdote is the fact that CRU has clearly done an atrocious job at properly archiving their data, and documenting the work their researchers produce. Naturally this level of disorganization is a serious problem anywhere it may occur, but it’s a particularly glaring issue in the field of scientific research, where the validity of research results lies squarely upon the ability of independent third parties to reliably reproduce those results on their own. Yet here we find that the CRU is demonstrated to have either managed their data so poorly as to prevent its own scientists from being able to reproduce the organization’s own published results (in which case “embarrassing” doesn’t even begin to describe the situation), or to have manipulated the data and produced false results. And the fact is that either story tells a horrible tale about the CRU.

Charlie Martin, in a post to the Pajamas Media blog, writes:

I think there’s a good reason the CRU didn’t want to give their data to people trying to replicate their work.

It’s in such a mess that they can’t replicate their own results.

This is not, sadly, all that unusual. Simply put, scientists aren’t software engineers. They don’t keep their code in nice packages and they tend to use whatever language they’re comfortable with. Even if they were taught to keep good research notes in the past, it’s not unusual for things to get sloppy later. But put this in the context of what else we know from the CRU data dump:

  1. They didn’t want to release their data or code, and they particularly weren’t interested in releasing any intermediate steps that would help someone else

  2. They clearly have some history of massaging the data… to get it to fit their other results….

  3. They had successfully managed to restrict peer review to … the small group of true believers they knew could be trusted to say the right things.

As a result, it looks like they found themselves trapped. They had the big research organizations, the big grants — and when they found themselves challenged, they discovered they’d built their conclusions on fine beach sand.

I won’t belabor the discussion of the implications these leaked documents offer; there is no shortage of people writing about exactly that. In case you’re interested in some of the more detailed coverage of the tech community’s review of the leaked data and algorithms, I would point you to the following pieces:

There’s also some great ongoing coverage at Devil’s Kitchen.

Regardless whether or not there’s any merit to any of the CRU’s climate research, however, this little drama leaves me unable to resist repeating an argument from my last post:

But with all these arguments and assertions about corollaries, trends, and predictions that this number crunching activity will generate, it will become increasingly crucial to have a mechanism by which the results claimed to have been derived from the number-crunching can be accounted for.

It must … become incumbent upon anybody publishing findings derived from mining such data to share both the sources and processes used to derive their results or conclusions. In cases of claims rooted in the fruits of data mining endeavors, it is specifically important that results indicate:

  1. exactly which data sets it draws from, and

  2. precisely which algorithm(s) processed the data in question.

At this point, the specific implications this debacle has for the CRU’s research is irrelevant. For, whether by deceit or incompetence, this leaked data has left their published research about climate change completely unreliable.

Yet developing a confident clarity around the subject of their research remains of critical importance, for climate change is a real challenge that humankind must cope with. Regardless whether or not human industrial activity is a driving factor for climate change, the fact is that the ice at our poles is melting at an accelerating rate. Decades worth of satellite photos and other survey data sufficiently demonstrate this fact. We similarly have data collected over the last several decades by the world’s meteorologists that global mean temperatures seem to be rising, as well as increasing levels of extreme weather (from droughts and famines to floods and more) around the world.

The climate debate isn’t over whether these events are occurring, but instead whether human industrial activity accounts for a relevant piece of it.

Governments around the planet will be forced to take some sort of action to deal with the prospective repercussions of these changes (e.g., rising sea levels, expansion of the Sahara, and the rest). The consideration at stake, therefore, is how each country will individually and collectively direct their efforts and invest their resources in dealing with it.

If human industrial activity has bearing on the matter, we’ll have to make some serious policy changes and invest heavily in developing alternative methods of production, lest we imperil our own (and other) species. But if, on the other hand, our industrial activity is not a determining factor in climate change, our efforts are best spent trying to figure out how we’re going to deal with the realities of a changing climate that we cannot mitigate simply by being more responsible with our emissions.

In any case, everyone needs to make informed decisions about where they’re investing their money and efforts.

And so a number of the world’s governmental and industrial leaders (including US President Barack Obama) are scheduled to meet — along with members of the climate research community — at the United Nations Climate Change Conference in Copenhagen this December in an attempt to work out policy directions to deal with climate change. I’m hoping the event will focus on methods to improve and reinforce confidence in the remainder of the climate research work being conducted around the world, and that it won’t turn into a political food fight.

Fingers crossed.

I am left hoping that some real good can rise from this mess. And so I call on climate change researchers and institutions around the world to take this opportunity develop the practice of providing full disclosure on the sources of their data sets and the functionality of their algorithms. There will likely be many political, legal, and logistical obstacles to address and overcome in this effort, but failure to do so carries stakes that are simply too high.

Footnotes

  1. I personally have plenty of experience attempting to work with poorly-documented code and data inherited from some previous person’s work, and can directly attest to the maddening up-hill battle of that situation.

General Thoughts , , , ,

Don’t Ask Me for My Email Address

October 18th, 2009

These days, anyone organizing competent promotional efforts (events, organizations, themselves, etc) invests various degrees of their attentions to online efforts. One reason for this is economics: efforts to “spread the word” online has the potential to reach more people at the expense of fewer resources and, therefore, less money.

One of the most commonly-leveraged contact points has become the email inbox.

Nearly everyone has an email address, and many of us have several – one for work, one personal. I presently have four, for example.

Generally speaking, people have largely become very comfortable communicating over email. It doesn’t carry the “burden” of requiring an immediate response, unlike a phone call, and can be whatever length the author thinks is appropriate for the correspondence.

It’s also easy to share information around the conversation in emails, by including a URL that points to further information on some website, or by attaching photos or other small files. This capability allows promoters to keep their message concise (if they’re clever), and yet provide leads to supplemental information for those with interest in pursuing the deeper details of the message.

Finally, it allows the author to write up a single message that can be delivered to a (theoretically) limitless number of people.

For all these reasons, one of the most common techniques that promoters adopt is the email campaign. They focus efforts on accumulating email addresses of people that could potentially be interested in their product, services, performances, or whatever it is they’re on a mission to promote.

Some years ago, I would share my email address with people and organizations whose news I’d have interest in following: bands, artists, pro-social organizations, and more.

But after a while, I noticed my inbox just blowing up.

The more I gave my email address out, the more emails I’d have to deal with every day.

I’m not really interested in anyone’s ideas on how I can be making millions from home, offers for debt reduction, or substances that promise me the ability to drive nails through wooden boards with my penis (promise me the same for granite, however, and maybe we’ll talk).

Read more…

General Thoughts , , ,