The Big Picture has another great photo essay on Earth Hour 2010, with some of the big cities that decided to turn off their lights for one hour on Saturday. Some of the images are amazing, as you can actually see the stars start to show up (like on the acropolis).
NEW YORK – Patents on genes associated with hereditary breast and ovarian cancer are invalid, ruled a New York federal court today. The precedent-setting ruling marks the first time a court has found patents on genes unlawful and calls into question the validity of patents now held on approximately 2,000 human genes. The ruling follows a lawsuit brought by a group of patients and scientists represented by the American Civil Liberties Union and the Public Patent Foundation (PUBPAT), a not-for-profit organization affiliated with Benjamin N. Cardozo School of Law.
“Today’s ruling is a victory for the free flow of ideas in scientific research,” said Chris Hansen, a staff attorney with the ACLU First Amendment Working Group. “The human genome, like the structure of blood, air or water, was discovered, not created. There is an endless amount of information on genes that begs for further discovery, and gene patents put up unacceptable barriers to the free exchange of ideas.”
I’m sure this is going to end up in the supreme court eventually, but for today I’ll take this as a small victory for sanity when it comes to intellectual property.
Last night I was fortunate enough to get out to a free screening of the Hubble IMAX movie out in Norwalk, Connecticut, which also included both an engineering and a science lecture up front about the Fine Guidance Sensors, which were designed and built (along with a lot of the other parts of the telescope) in Danbury, Connecticut. This was all put on by Western Connecticut State University as part of their 20 years of Hubble celebration this year.
It was a really neat evening. There were a lot of folks in the audience who were engineers that worked to build the Hubble in Danbury, at least a dozen folks were called out by name and stood up to roaring applause by the crowd for all their hard work. The engineering talk on the FGS probably was more than I ever thought I’d know about interferometry, and did go through some of the basics the challenge of building the Hubble. The FGS are effectively the star tracking sensors that ensure the hubble can stay stable and pointed as it’s moving between -100 C / +45 C temperature swings every 90 minutes as it flies around Earth.
The science talk followed which specifically talked about some of the extra science they got out of the FGS, including finding planets, doing atmosphere analysis of Neptune’s moon Triton, and allowing for the Hubble Ultra Deep Field view, one of the most amazing pictures that has ever been taken.
After the talks, we went straight into the Hubble IMAX film. It was 2D only, but totally immersive none the less. The entire film is incredible, get out and see it if you can. One part at the beginning is going to stick with me forever though, which is the fly out to the Orion Nebula. Because Hubble has taken such detailed measurements of the Orion Nebula they were able to construct a 3D fly through of the stellar nursery there. Except for the very last part on the forming solar system, this isn’t a simulation, this is images brought to life. It’s completely breath taking.
The Hubble is a great instance of the things we can create, and the discoveries we can make, when we come together with open minds trying to ask a seemingly simple question, what’s out there in the universe, and how does it work. The Hubble turns 20 in April, and because of this final servicing mission it hopefully has many great years ahead of it.
Thanks again to WCSU for pulling the night together, and Paul Granich from the Mid Hudson Astronomical Association for letting us know about it and organizing the dozen of us to make our way down.
From the youtube blog:
For years, Viacom continuously and secretly uploaded its content to YouTube, even while publicly complaining about its presence there. It hired no fewer than 18 different marketing agencies to upload its content to the site. It deliberately “roughed up” the videos to make them look stolen or leaked. It opened YouTube accounts using phony email addresses. It even sent employees to Kinko’s to upload clips from computers that couldn’t be traced to Viacom. And in an effort to promote its own shows, as a matter of company policy Viacom routinely left up clips from shows that had been uploaded to YouTube by ordinary users. Executives as high up as the president of Comedy Central and the head of MTV Networks felt “very strongly” that clips from shows like The Daily Show and The Colbert Report should remain on YouTube.
Viacom’s efforts to disguise its promotional use of YouTube worked so well that even its own employees could not keep track of everything it was posting or leaving up on the site. As a result, on countless occasions Viacom demanded the removal of clips that it had uploaded to YouTube, only to return later to sheepishly ask for their reinstatement. In fact, some of the very clips that Viacom is suing us over were actually uploaded by Viacom itself.
This is so absurd you’d be hard to come up with a better “who’s on first” plan yourself.
It’s been 2 years since I got my Proliphix thermostat, and while I did some early hacking on it, largely the whole effort just sat around for the last 2 years. However, with the fun of connecting up my weather sensors, I went back in this weekend and beat the code into a much more sane interface.
Thermostat.rb 1.1.1 was released yesterday. It provides a concise interface to the Proliphix web services API. An example of the usage is something like:
thermostat = Thermostat.new("hostname", "admin", "password") # get the current temperature current_temp = thermostat.temp # get the current setback heat value current_target_temp = thermostat.heat_to # set the thermostat to 69F (units are set in the thermostat) thermostat.heat_to = 69
I’ve got support under the covers for everything in the Proliphix API. I’ve only mapped about 1/2 of it to the user visible interface, starting with all the functions I’ve tended to need or use. I was a good little agile developer and built unit tests for everything here. Using the new module, I added the thermostat to my homegraph code, with some pretty reasonable results:
All this is released under the MIT license.
Over the weekend I was working on revamping a whole set of older ruby projects, some having to do with my Proliphix Thermostat. I had this crufty Rakefile from the icalendar project that I’d been copying and modifying for new projects, and it was slowly degrading. I thought that there had to be a better way. There is, it’s called newgem.
Newgem is like h2xs in the Perl world, something to stub out a new module with all the right files and structures. But, as the Ruby folks tend to do, it ups the ante in the process. In addition to the basic build, packaging, testing, and coverage results you’d expect, you also get a targets for: creating you rubyforge website, publishing your gems to rubyforge and gemcutter, posting release announcements on rubyforge, and even posting blog posts about your release (though I haven’t configured that one yet).
The release cycle is now:
rake release rake website rake post_news
The Rakefile created is loading these features from base modules, so it’s only ~ 30 lines, a heck of a lot easier to maintain than the 300 line Rakefiles I had which provided about 1/2 these features inline.
If you are doing Ruby development, you should really check out newgem.
Robert Wright provides a nice analysis on the current Toyota recall:
Let’s do the math.
My back-of-the-envelope calculations (explained in a footnote below) suggest that if you drive one of the Toyotas recalled for acceleration problems and don’t bother to comply with the recall, your chances of being involved in a fatal accident over the next two years because of the unfixed problem are a bit worse than one in a million — 2.8 in a million, to be more exact. Meanwhile, your chances of being killed in a car accident during the next two years just by virtue of being an American are one in 5,244.
So driving one of these suspect Toyotas raises your chances of dying in a car crash over the next two years from .01907 percent (that’s 19 one-thousandths of 1 percent, when rounded off) to .01935 percent (also 19 one-thousandths of one percent).