Aasemoon'z Cluster

Clearly the most attractive super hero power for nanotechnology at the moment is invisibility. Last month we had a nano-enabled coating that managed to make aircraft invisible to radar. Now we have a metamaterial consisting of fishnet-like film containing holes about 100 nanometers in diameter that could serve as an invisibility cloak. While I personally might be persuaded to choose Spider-like climbing abilities for my nano-enabled super hero power, invisibility does pose an attractive option. However, invisibility is far from the point of this research conducted at the Birck Nanotechnology Center, Purdue University and appears in the August 5th edition of the journal Nature.

If you had a dinner invitation in Utah's Escalante Valley almost 10,000 years ago, you would have come just in time to try a new menu item: mush cooked from the flour of milled sage brush seeds.

Researchers from Leeds University are working on a camera and drill-weilding robot known as Djedi to solve the mystery of the blocked shafts inside the Great Pyramid at Giza. In 1992 and 2002, remote cameras were sent through the shaft under the watchful eye of antiquities master Dr. Zahi Hawass only to be stopped by limestone doors. Dr. Robert Richardson of the Mechanical Engineering department said their goal is to find out what is beyond the blocks and go as far as possible to discover the purpose of the shafts, all while doing minimal damage to the structure. Final preparations are being made now with hopes of sending the robot in before year's end. Place your bets now!

Perhaps the most difficult control problem for a drive servo is that of going down a ramp. Any back drivable drive servo will exhibit a freewheeling velocity on a given ramp. This is the speed at which the robot will roll down the ramp in an unpowered state. At this speed, the surface drag and internal drag of the servo are equal to the gravitational force multiplied by the sine of the slope. The freewheeling speed is thus load dependent.

Last week Wim Jongman bloged about the Nebula Oscilloscope widget. It’s just an awesome widget for monitoring activity. See Wim’s post to form an opinion yourself. So, for me as a RAP developer, the first question I always ask myself when seeing such a cool thing is: “Will it run on RAP?”. I followed the steps Wim described to get the Oscilloscope running, changed the target to RAP, commented out one line of code and started the application. You can see the result in the screencast below.

First, right off the top here: Scala has true blue Java-like null; any reference may be null. Its presence muddies the water quite a bit. But since Beust's article explicitly talks about Haskell he's clearly not talking about that aspect of Scala because Haskell doesn't have null. I'll get back to Scala's null at the end but for now pretend it doesn't exist.Second, just to set the record straight: "Option" has roots in programming languages as far back as ML. Both Haskell's "Maybe" and Scala's "Option" (and F#'s "Option" and others) trace their ancestry to it.

platform :   Linux   Windows   MacOSX Intel type :   diskmag release date : august 2010 release party : Evoke 2010

The science behind gecko toes holds the answer to a dry adhesive that provides an ideal grip for robot feet. Stanford mechanical engineer Mark Cutkosky is using the new material, based on the structure of a gecko foot, to keep his robots climbing.

EARL (that would be, Enhanced Automated Robotic Launcher) is a second generation bowling robot. Let me explain to you why a bowling robot is necessary at all: apparently, EARL is “invaluable in the many studies necessary to keep up with the ever-changing bowling ball industry… [EARL is] the future of bowling research.” Hmm. That’s worth pondering for a minute or two. Well, I won’t pretend to understand it, but that doesn’t mean I’m not impressed with the fact that EARL can throw bowling balls at 24 MPH and spin them up at 900 RPM, much faster than a human is capable of, which I guess is why people seemed to assume that the robot would win… Does it say something about the state of robotics, or something about the sport? Either way, bowling seems like a game with an extremely limited amount of random variables, and sooner or later (probably sooner) the only thing worthy of a news story will be a robot arm not bowling a perfect 300.

SLAM ( Simultaneous localization and mapping ),  PID ( Proportional integral derivative ) controller & ODOMETRY ( hodos, meaning “travel“, “journey” and metron, meaning “measure“)

Scientists at the Johns Hopkins University Applied Physics Laboratory (APL) were awarded no less than $34.5 million by the Defense Advanced Research Projects Agency (DARPA) to continue their outstanding work in the field of prosthetic limb testing, which has seen them come up with the most advanced model yet. Their Modular Prosthetic Limb (MPL) system is just about ready to be tested on human subjects, as it has proved successful with monkeys. Basically, the prosthetic arm is controlled by the brain through micro-arrays that are implanted (gently) in the head. They record brain signals and send the commands to the computer software that controls the arm. To be honest, it will be interesting to see just how these hair-chips are attached to the brain, but the APL say clinical tests have shown the devices to be entirely harmless. The monkeys didn’t mind them too much, at least.

As many long time readers know, I am an enthusiast of the F# programming language.  I make no apologies for the fact that, if you are developing software on the .NET platform, F# is one of the better choices you can make for numerous reasons.  It is one of the reasons I proudly contributed as a co-author to the book, Professional F# 2.0, which is being published by Wrox in October. Some of the oft cited benefits of F# are that, to distill them quickly, it is good at doing intensely mathematical operations, it is built for parallelism, and it is good at helping define domain specific languages.  Those benefits are so often cited by speakers on the F# speaker circuit that they pretty much seem cliche to me at this point (note, yours truly is proud to call himself a member of said circuit, and often gives this talk!)  As great as these features are, there are a couple features, that in my more mundane F# experiences, seem to stand out as things that “save my ass”, for lack of a better phrase, more often than not.

The MATLAB team at MathWorks tested performance scaling of the backslash ("\") matrix division operator to solve for x in the equation A*x = b. In their testing, matrix A occupies far more memory (290 GB) than is available in a single high-end desktop machine—typically a quad core processor with 4-8 GB of RAM, supplying approximately 20 Gigaflops. Therefore, they spread the calculation across machines. In order to solve linear systems of equations they need to be able to access all of the elements of the array even when the array is spread across multiple machines. This problem requires significant amounts of network communication, memory access, and CPU power. They scaled up to a cluster in EC2, giving them the ability to work with larger arrays and to perform calculations at up to 1.3 Teraflops, a 60X improvement. They were able to do this without making any changes to the application code. Here's a graph showing the near-linear scalability of an EC2 cluster across a range of matrix sizes with corresponding increases in cluster size for MATLAB's parallel backslash operator:

Oracle made a big noise in the Linux community yesterday by announcing its own spin on the Linux kernel on top if its so-called Unbreakable Linux. Oracle presented the announcement as offering a "modern" Linux kernel on top of its own clone of Red Hat. Underneath the hype, what's Oracle really offering, and what does it mean for Linux? For years, Oracle has ridden Red Hat's coattails and tried to present it as a good thing to its customers. Oracle rebrands Red Hat Enterprise Linux (RHEL), slaps its own support package on it, and lets Red Hat do all the heavy development lifting while it tries to poach Red Hat's customers. All perfectly legal according to the licenses that RHEL is shipped under, but a bit skeezy nonetheless. Or perhaps parasitic might be a better word.

Dave Megginson (who drove the development of the SAX API that will be familiar to many XML developers who use Java) recently wrote Java is dead. Java stood out as a programming language (though not as a platform) in that Sun had refused to standardize it through an independent and reputable standards organization (a lot of the hard work had been done in one attempt to put it through ECMA and one to put it through ISO, both times Sun pulled out and eventually made their highly unsatisfactory JCP Java Community Process system.) Without the ability to alter Java significantly in ways that might go against their druthers, Java suffered two major forks (Microsoft's J++ then its C#, and IBM's SWT) where significant players disagreed with a major component (the graphics library). Java succeeded in middleware, and but failed to take advantage of the rise of browsers on the deskop: their HTML parser was great for the middle 1990s but was deliberately neglected to the point of being unusable: it is hard not to see this as a deliberate attempt by Sun to leave the browser market to its friends and enemies. I really liked Java, and bet my company on it (in a sense): I would not do that today.

Japan’s Explay Ltd recently announced that it has begun to ship its pico projector engines to developers around the world. The Explay Projector Engine is only 6.7 cubic centimeters in size and just 7mm thick (~1/4 of an inch). Despites its tiny dimensions, the pico projector generates 14 lumens laser light on just 1.3 Watts of power (1.8 with control circuits) and can produce images 7 to 70 inches in size. Resolution is a respectable 852×480 and with a laser based system it should stay in sharp focus over a wide range (20 to 200cm). While Explay has yet to announce which manufacturers will be using their projector they did say that they expect it to appear in devices as early as February of 2011. Looks like we’ll need to watch for it at CES. Explay plans on improving their projector engine further. They hope that the end of 2011 will see the arrival of a 25 lumens WXGA 1366×768 version. A member of the R&D team in Israel (part of XDM Ltd) shows off the 14 lumens pico projector in a prototype testing rig in the video below. Not a bad image for the world’s smallest laser projector.

Earlier in this series, we touched on one problem that can arise when sampling an analog signal, namely the problem of aliasing. There are three other issues with signal sampling to which we now turn our attention: digitization effects, finite register length effects, and oversampling. So far, weve assumed that all of the signals were measuring are continuous analog values; i.e., our measurements are completely accurate. Even in the cases in which we have noise, the underlying assumption is that the measurement itself, for example the noisy sensor output voltage, is known precisely.

This article features an example chapter from a new *Hot-off-the-Press* book on FPGA Design that just recently hit the streets in August 2010. This chapter is reproduced here with the kind permission of the publisher – Springer. This book -- FPGA Design: Best Practices for Team-Based Design -- describes best practices for successful FPGA design. It is the result of the author’s meetings with hundreds of customers on the challenges facing each of their FPGA design teams. By gaining an understanding into their design environments, processes, what works and what does not work, key areas of concern in implementing system designs have been identified and a recommended design methodology to overcome these challenges has been developed.

In this session, Don McCrady discusses how C++ programmers can fully utilize multicore in their applications using the Concurrency Runtime (ConcRT), the Parallel Pattern Library (PPL), and the Asynchronous Agents Library that ship with Visual Studio 2010.

IBM's light-powered links overcome the greatest speed bump in supercomputing: interconnect bandwidth