Tuesday, April 12, 2011

'Solar fuel' research mimics photosynthesis

NEW HAVEN, Conn.--In an ambitious attempt to replicate nature, various researchers are seeking to create fuels from water and sunlight, much the way plants do.

California Institute of Technology professor Nate Lewis on Saturday gave a snapshot of the "swing for the fences" research his lab is pursuing to make fuels directly from water and sunlight. Caltech last year was picked as the lead for a newly created Joint Center for Artificial Photosynthesis (JCAP) to run the Department of Energy's Fuels from Sunlight Energy Innovation Hub.

Researchers at the Joint Center for Artificial Photosythesis are designing arrays of microwires coated with catalysts that can split water to make hydrogen or liquid hydrocarbon fuels.
(Credit: CalTech)

The center is one of many so-called solar fuels efforts that seek to bypass the traditional biofuel method of growing plants and then convert biomass to a transportable, liquid fuel. Other researchers and companies are seeking to genetically engineer microbes that secrete fuels or develop cheaper methods for splitting water to make hydrogen fuel.

During a talk at the Yale Climate & Energy Institute's annual conference, Lewis described the concepts driving his research and what form a solar fuel generator could take.

The sun is the largest source of energy, but storing solar energy with conventional means, such as batteries, is very expensive, he said. The notion behind his research is to store solar energy in the chemical bonds of fuels. Light-duty transportation will move toward electric vehicles because they are more efficient than internal combustion engines, but there is still a need for liquid fuels in other forms of transportation or to generate power when there is no sun.

"It's inevitable that we will find a way to efficiently take the biggest energy source we have in the sun and store it in chemical fuels, thereby obviating the storage problem, thereby having a drop-in replacement fuel, and thereby solving the (fuel) infrastructure problem," he said. "We are going to do this. The question is how fast and how soon."

The center's solar fuel generator is designed around tiny wires of silicon placed in a solution. Traditional solar cells also use silicon, which releases a flow of electrons, or electricity, when hit by light. But the work at Lewis' lab diverges from the solar cell form and function in significant ways.

Using nanotechnology, the design calls for rods of silicon "microwires," which allows the material to absorb more light. Rather than only create electricity, these fibers are treated with a catalyst to use the sun's energy for fuel production. A catalyst can react with water to produce hydrogen gas, which can be used as a fuel. A longer-term goal is to discover catalysts that use carbon dioxide from the air in the production of a liquid hydrocarbon fuel such as methanol.

The design intentionally copies the process of photosynthesis, where leaves split water and use carbon dioxide from the air to make sugars. But researchers like Lewis are seeking to greatly increase the efficiency of converting sunlight to stored energy. Plants spend much of the sun's energy on growing.

Lewis said that arrays of these microfibers could be placed on a flexible polymer so that they would resemble a "solar carpet" where the fibers are like tiny trees in a forest. How an entire fuel-producing system would be designed and what fuel is more economical to produce is still not clear, he said.

"We don't actually know whether or not it's cheaper to wick out gas at low pressure or to wick out liquid (fuel). It depends on how we plumb it and the only way to find out is to build a few and cost them," he said.

Research in artificial photosynthesis has been going on for decades. One of the biggest technical challenges is finding materials that are robust enough to sit in the sun for several years, yet are cheap and efficient at converting sunlight to electrical energy, he said. The goal is to be robust, cheap, and efficient, but scientists now can get only two of the three.

The Fuels from Sunlight research is a long-term effort, but Lewis said a prototype solar carpet could be ready in two years and he is confident that the efficiency can ultimately be as good at many of today's solar panels in converting sunlight to usable energy.

Artificial leaf
Outside the Fuels from Sunlight lab are many other research and commercial programs, which could also be called solar fuels.

Notably, there are a number of biotech-oriented efforts to use genetically manipulated microorganisms such as bacteria to make fuels directly from sunlight and water. Joule Unlimited, for example, is a start-up that is designing a bioreactor in the shape of a flat plastic pane that grows cyanobacteria from water, nutrients, carbon dioxide, and sunlight. The cyanobacteria are genetically engineered to make diesel fuel directly.


A picture of the tiny silicon wires that would be put in water to create hydrogen from sunlight.
(Credit: Caltech)

Another high-profile researcher in artificial photosynthesis is Daniel Nocera from the Massachusetts Institute of Technology. He co-founded a company called Sun Catalytix that is using a relatively inexpensive catalyst to split water to make hydrogen and oxygen. The company plans to make a system that can make the hydrogen, store it, and then run it through a fuel cell to make electricity or burn it for heat and power. It envisions the technology would first be suited for distributed energy systems in developing countries.

Two weeks ago at the National Meeting of the American Chemical Society, Nocera presented results from an effort to make an "artificial leaf." Sun Catalytix has already made a prototype system where a photovoltaic solar cell, coated with a catalyst and placed in water, can make hydrogen and oxygen.

Microsoft is back in the browser game


After a three-week IE9 immersion, I've concluded that Microsoft once again has a competitive Web browser.

And even though Internet Explorer remains the most-used browser on the Net today, convincing me that Internet Explorer 9 is a real browser was quite an accomplishment. Here's why.

IE6, now a decade old, is loathed by Web developers the world over for its lack of standards support, and it's the focus of a Microsoft effort that's trying to get the companies and people using the browser to modernize. After a five-year hiatus, IE7 emerged with some handy features, such as tabbed browsing and a search box, but it was mostly about trying to catch up with rivals such as Firefox and Opera that hadn't idled away the years.

IE8 took the major step of trying to conform to Web standards, using a "compatibility view" mode only as a fallback to show sites that had been crafted for earlier versions of IE. But it still lagged other browsers in the breadth of standards it supported, and it crawls when executing the ever-more-important Web-based JavaScript programs.

Even though IE is built into Windows, the most widely used personal computer operating system on the planet, its share of usage steadily diminished as people realized there was a better answer. Microsoft had competed fiercely with Netscape in the 1990s and won, but then it sat back and left the innovation to others.

Thus, the world of Web developers and technical enthusiasts can be forgiven for being skeptical about IE9.

But as I see it, Microsoft has fully awoken here. No doubt the influence of Apple's Safari and Google's Chrome helped ring the alarm bells and shake loose funding for programmers and marketing, but Microsoft's grasp of the importance of the Web is much more than a knee-jerk reflex to catch up to rivals.

My life with IE9
The browser itself worked well for me, for the most part. My top pick is still Chrome, with Firefox 4 a close second, but IE9 got the job done.

After an initial week of kicking the tires, I took the plunge and set it as default browser. I spend most of my working day, and a lot of my off hours, in a browser, so that's actually a big step. Slow browsers drive me nuts.

I compiled a list of 38 complaints as I was testing IE9. That may sound like a lot, but many are petty ones such as occasionally blank full-screen YouTube videos or wonky page rendering on Picplz and Apple's online store. The proof that IE9 had passed the test was that after I had set it as default browser, I rarely cringed as I contemplated the prospect of clicking a link, the way I had with IE8.

My biggest problem using IE9 was that it chained me to a deskbound quad-core Dell Windows PC (it's a laptop, but five cables tether it down). I missed the lumbar-preserving stand-up arrangement I use for my other main machine, a MacBook Pro. In other words, it was an issue that had nothing to do with the browser itself.



Neither IE9's list of tabs across the top of the browser window nor the list that appears when hovering over the taskbar icon are very useful for navigating large numbers of tabs. In fairness, it's a problem all browsers have.
(Credit: screenshot by Stephen Shankland/CNET)

I did have some complaints I think are worth mentioning. Chief among them:

• Tab management--I often have dozens open--was no better than with most browsers today, and often worse. The integration with the taskbar probably helps people who use mice to navigate a smaller number of tabs, but I use keyboard shortcuts (ctrl-tab), and a long list of text wasn't much better than a long list of tabs. I'm glad Microsoft added the option to add a new row of tabs below the combined search/address bar, but I wish there was a way to activate that option only when tabs in the ordinary configuration get too narrow. IE groups tabs by color, but I find this organizational scheme marginally useful sometimes and a hidrance at other times, so I shut it off. When I hold down ctrl-tab to zing past a large number of tabs, many intermediate tabs don't get highlighted in the tab strip, requiring me to guess how far I've gone and when to stop. Finally, IE9 often didn't pick up a site's favicon correctly, and I find those tiny graphics very useful for quickly locating the tab I want.

• Google Docs is hobbled. I spend a lot of time with Google's online word procesor and spreadsheet, and both suffered performance lags, despite the speed boost of IE9's Chakra engine for running JavaScript. The word processor was fine until documents got moderately long--one or two thousand words--then it started dragging. The spreadsheet seemed to have trouble even earlier. Perhaps Google bears some of the responsibility here, but Firefox, Safari, and Chrome don't suffer from this same drawback. I also had a temporary showstopper: when my display was zoomed to 125 percent and the Google Docs page was shrunk, the cursor would be misplaced. Changing the zoom settings back to 100 percent all around fixed it.

• IE9 just didn't have quite as light a feel as Chrome or Firefox. When there's that little bit of lag when you repeat the same action over and over--Ctrl-T to spawn a new tab or Ctrl-L to start typing a search term or Web address--it just wears you down. For all the vaunted hardware acceleration in IE9, its user interface response was just a bit poky.

• Is it the browser or the OS? Antitrust settlement notwithstanding, IE9 still feels enmeshed with Windows. This time the installation didn't require a reboot, an improvement over IE8 and over Safari upgrades on Mac OS X, but the trade-off is that for installation, you must first quit any application that gets within a mile of HTML rendering. For me that was Photoshop, Avast antivirus, Firefox, Chrome, Google Talk Plugin, HP Digital Imaging Monitor, Java SE binary, Java Update Scheduler, Skype, Synaptics Touchpad Enhancements, Tweetdeck, Windows Desktop Gadgets, Windows Explorer, Windows Host Process (Rundll32), Windows Live Mesh, Yahoo Messenger. To its credit, the installer restarted my antivirus software afterward. I also still dislike seeing "Internet options" and "Windows Update" in IE9 menus. These are operating system actions, but Microsoft probably is leery of removing them after so many people have learned to find them in IE.

But overall, IE9 was a capable, competent browser. Its gradual arrival will liberate Web developers hobbled by old browsers--especially as Windows 7 finally replaces Windows XP at corporations wedded to IE6.

The ever-expanding Web

Today's Web is a vastly more powerful platform for software than a decade ago. Graphical elements and formatting are richer and more dynamic with modern Cascading Style Sheets technology, and JavaScript has come into its own with higher performance in browsers and libraries such as jQuery that make it easier to use. HTML5's vaunted video tag and the coming WebSocket specification can make pages even more active, while storage technologies can let Web applications work even when there's no network connection.

It's a world where Google Docs can be a viable replacement for Microsoft Office for some fraction of the

The W3C's new HTML5 logo

market, and where programmers can contemplate massively multiplayer online games built from Web standards.


With IE9, Microsoft has embraced this vision, even though it undermines two other important programming foundations from Microsoft, the company's Windows operating system and its Silverlight technology that serves both as a browser plug-in and as Windows Phone 7's native application technology.

That internal competition must have made for some heated meetings, but really, Microsoft had little choice. Powerful rivals were moving together down the Web-app path, and developers were following. It's a classic cannibalization story: sometimes a company is better off embracing a popular technology that hurts its own products, because the alternative is letting competitors inflict the pain.

Thus, at the same time it was building IE9, Microsoft re-engaged with Web standards work with HTML, CSS, Scalable Vector Graphics, typography, and more. Many of these standards are present in IE9, one indicator that Microsoft isn't faking its support for the new Web merely with marketing bafflegab.

Microsoft also embraced many healthy practices developing IE9. Publicly released platform preview editions let Web developers test the browser as it evolved, and Microsoft responded to feedback.

To be sure, IE9 still lacks support for a number of Web standards. But I'd rather see an IE9 in its present state and released than an IE9 supporting all those standards but arriving sometime at the end of 2011. I don't expect Microsoft to adopt Google's six-week update cycle, but I do think successors to IE9 are under active development, and I see no reason why animated (and hardware-accelerated) CSS transitions and transformations aren't on the to-do list.

WebGL--the hardware-accelerated 3D graphics interface all the other browser makers have embraced--is a big question mark for IE. Microsoft has a competing interface in Silverlight 5, which goes into beta testing this week, not to mention native Windows apps using DirectX. But judging by IE9, it's not unthinkable that Microsoft would support it somehow, if enough developers used it on the Web.

After all, Microsoft clearly has decided it's time for an IE it can be proud of.
 
{nama-blog-anda} is proudly powered by Blogger.com | Template by Agus Ramadhani | o-om.com