In the Palazzo Vecchio in Florence, Italy, a feverish search occurs seemingly in slow motion. In order to make progress in the search, a team of researchers from the University of California/San Diego has been inventing a brand new field of work called art forensics. Armed with innovative new portable sensing devices and Intel technology, they are searching for a lost masterpiece by Leonardo da Vinci called The Battle of Anghiari . This impressive painting, considered by some to be da Vinci’s greatest artistic accomplishment, was lost more than 450 years ago. Lost: The Masterpiece of the Renaissance The great mural was painted by da Vinci in 1505 to commemorate a battle in 1440. His artistic rival, Michaelangelo, was commissioned to paint a mural on the opposite side of the hall. (Imagine these two artists in the same room, not just two of their masterpieces in the same room!). Michaelangelo did not finish his project. He had sketched his painting out, but had just begun the painting when he was invited back to Rome to build the tomb of Pope Julius II. A rival artist, Bartolommeo Bandinelli, destroyed Michaelangelo’s sketch in a fit of jealousy in 1512. Peter Paul Rubens's copy of The Battle of Anghiari (from Wikipedia). Da Vinci did not finish his painting either, but he got much further than Michaelangelo. His painting depicted the power, fury, and intense emotions of four horsemen engaged in battle. Always experimenting with new techniques, da Vinci tried to apply oil colors to the wall. The result was less than satisfactory. The paint dripped and only the lower part of the painting could be dried quickly enough to achieve the desired result. Da Vinci subsequently abandoned the project. Nevertheless, da Vinci’s painting was considered the masterpiece of the Renaissance. Numerous copies of The Battle of Anghiari were made over the course of the next 50 years and others praised the work in commentaries and diaries. Many sketches by da Vinci (“cartoons”) that served as studies for the mural still exist. An engraving made in 1553 by Lorenzo Zacchia was used in 1603 by Peter Paul Rubens as the basis for a copy of the central section of the mural. Rubens’ second-hand copy of da Vinci’s painting is in the Louvre. Eventually, the hall was enlarged and remodeled by Giorgio Vasari and Vasari painted six new murals over the east and west walls of the hall. It is assumed that the famous, unfinished works of da Vinci and Michaelangelo were lost during this process, as they were not seen again. Seek and Ye Shall Find Scaffolding covers a wall in the Hall of Five Hundred in the Palazzo Vecchio where a team of researchers are searching for a lost painting by Leonardo da Vinci Some people, included UCSD’s Maurizio Seracini, believe that the da Vinci masterpiece might still exist. Vasari, who painted the murals that now adorn the hall, had high praise for the da Vinci fresco, so Seracini thinks it is unlikely that Vasari destroyed the mural during the hall’s renovation. A clue to this effect is in the Vasari mural, 12 meters above the ground. The only text on the entire painting is on a green flag held by a Florentine soldier. The text says “Cerca trova”—”He who seeks, finds.” Seracini has taken this advice to heart. An initial non-destructive 3D survey of the hall used surface penetrating radar and thermographic cameras to create a three-dimensional model of the space. This process led to the discovery of a wall built by Vasari in front of the east wall where The Battle of Anghiari was located. A gap of a couple of centimeters was discovered between the two walls, supporting the theory that the lost masterpiece is still intact and located behind Vasari’s mural. Of course, Vasari’s mural is a more-than-400 year-old masterpiece too, so there is understandable reticence by the involved government and cultural agencies to do anything that would cause irreversible damage. This is where the UCSD researchers and Intel technology come into play. 21st Century Technology Aids Search As part of its Visual Computing Academic Program, Intel’s University Program Office supplied 50 quad-core Intel Core i7 Extreme 3.33 GHz processors to Falko Kuester of UCSD. The parallel processing performance of these powerful processors has allowed UCSD to tackle a series of unique and transformative visual computing projects. Kuester’s team is currently using these CPUs to “Create (Compute) a Future for the Past” as part of its cultural heritage diagnostics research and its field sites in Italy and Jordan. Multiple nodes loaded with Intel CPUs are on-site in Palazzo Vecchio driving UCSD’s visual analytics/visual computing environment. Small holes drilled through the Vasari mural to the back wall have revealed fragments of pigment on the far wall that might be part of the da Vinci mural. The UCSD team is therefore developing new non-invasive sensing and analysis techniques to try to “peer through” the front wall and visualize the surface of the back wall. Maurizio Seracini, Falko Kuester, and the other members of the UCSD cultural heritage diagnostics research team on site in Florence, Italy The National Geographic Society is also sponsoring the search and is documenting the entire process. Our UCSD colleagues indicate that National Geographic will air a documentary on the project on January 15 (but I don’t yet see this program on the guide for the National Geographic channel). The search for a lost da Vinci masterpiece…it is a riddle wrapped in an enigma shrouded in mystery. Intel technology is at the heart of the search. And the results will of the search will soon be revealed in a National Geographic TV special. Further information Home page for UCSD’s cultural heritage diagnostics effort National Geographic’s blog for The Battle of Anghiari Project CBS 60 Minutes 2008 story on Maurizio Seracini’s search Wired magazine’s 2007 interview with Seracini
Posts Tagged ‘intel’
AES-NI in Laymen’s Terms
What is AES-NI – first answer AES-NI are a set of six new instructions introduced by Intel when we introduced the new 2010 Intel® Core™ processor family code named Westmere. AES-NI stands for Advanced Encryption Standard – New Instructions. These instructions implement hardware accelerated versions of certain compute intensive steps used in the AES (RijnDael) algorithm. Okay – so what is the Advanced Encryption Standard (AES)? AES is a standard that defines how to encrypt plain text using an encryption key. It is implemented with the RijnDael (pronounced Rhine Dahl) algorithm. One cool thing about AES is that even though this algorithm is completely open for examination, it is possible to encrypt a plain text message with it that is very, very difficult to break. This is possible because the algorithm takes the plain text message you want to encyrpt, and merges it in a certain way with a secret key. As long as the key is kept private, the encrypted message has proven to be safe from being broken, at least to this point in time. So the algorithm is completley known, but as long as the key is protected, messages encoded with it are virtually safe from eves dropping. So who cares? So what kind of software developers might use AES? and who might benefit from the new AES-NI? There may be more than you think at first: developers who write code that that use secure socket layer (SSL), database engines, whole disk encryption applications, files compression applications, VoIP, instant messaging, email, virtualization software, electronic payment systems, virtual private networks, and list goes on. To learn more about who might use AES see this wiki article on AES instruction set or this article on AES-NI analysis on Tom’s Hardware . So how does AES (Rijndael) work? To understand how the AES (Rijndael) algorithm works I highly recommend that you look at Jeff Moser’s “A Stick Figure Guide to the Advanced Encryption Standard (AES) – A play in 4 acts” . This creative, stick figure, cartoon approach is the best method I have seen for communicating how AES works – five stars Mr. Moser! My stick figure image below is an icon tribute to the excellent efforts of Mr. Moser in laying bare the essense of AES. Thanks Mr. Moser! What is AES-NI – second answer Now consider that the six AES-NI from Intel provide two instructions to accelerate encrypting a round, two instructions for decryping a round, and two more instructions to accelerate the generation of round keys. In summary, the six new instructions provide a faster way to crunch through the Rijndael algorithm (AES). Curious to know more? Read more about it in my friend, Jeff Rott’s, blog. Jeff wrote an excellent blog on Intel® Advanced Encryption Standard Instructions (AES-NI) , in which he introduces the six instructions, describes the benefits, and introduces ways to actually implement these in your code (plus references). So how can you implement AES-NI in your code? As long as you are using one of the following compilers (or later) you can get direct access to the instructions: AES-NI are supported by version 11 of the Intel C/C++ compiler, and also by Microsoft* Visual Studio* 2008 Service Pack 1 and by gcc version 4.4. You can implement it the hard way using MASM or inline assembly. Or you can make it easier on yourself and use compiler intrinsics (just be sure to include wmmintrin.h or intrin.h). See Martyn Corden’s Post here on Compiling with AES-NI . Another approach is to use a library such as OpenSSL or Intel’s IPP to implement AES-NI – Jeff has references
If you really want to dig in and see the reference and code snippets read Intel’s Shay Gueron’s in-depth whitepaper called “Intel® Advanced Encryption Standard (AES) Instructions Set”. See Shay’s abstract and whitepaper link here . Finally – if you want a complete understanding of AES, much more than you will find in a Wiki article or blog, then check out the following book. ” The Design of Rijndae l” is the definitive book on the subject, written by the Rijndael creators.
Jeff’s Notebook: Intel® vPro™ Developer Community – A resource for developing PC manageability & security software
Well, 2012 is here and with the New Year, you’ll be seeing some new topic areas for my blogs. This year, I’m going to be exploring the additional areas of PC manageability and security software. This is an area that continues to gain attention by IT managers and software developers that are trying to address the needs of efficiently managing PC’s, addressing malware/viruses and the security of data on PC’s. Intel has been addressing these concerns for some years with its Intel vPro technology that has been built into various Intel processor-based desktops and laptops. So, if you are a software developer of IT manageability and security software and you want to learn more about vPro technology and how to enable your software to take advantage of it, recently a new community has been launched to provide you with the information that you may want. This is the Intel vPro Developer Community . Check out this new community and discover more about Intel vPro technology.
Show 13 – From Netbooks to Ultrabooks: Apps that Scale Well
The Intel AppUp show for developers “Show 13″: in this segment of AppUp RoundUp, Host Bob Duffy showcases four applications that scale up well from Netbooks to Ultrabooks– Shufflr, Ancient Frog, Fandango, and Pinball HD. And, in the TweetCap segment, Host Rhonda Peters shares the buzz on HTML5 and posts regarding developers being business savvy when developing apps.
Taking a look at Intel Anti Theft & Identity Protection Technologies
I wanted to start a new blog introducing myself in a new role at Intel. As part of my new role I will be explaining Intel’s Security, Manageability, and Virtualization features to a broad base of ISV’s through our scale enabling team and associated platform communities. In my new role, I have been learning about many of Intel’s security technologies and am excited about bringing these technologies to light in my blogs, and Intel Software Network TV. To see why I am excited, and a little daunted with my new tasks, take a look at a couple of clips of Mooly Eden at Intel’s recent Intel Developer Conference. These technologies are amazing ,…but there is so much ground that they span! The first clip showcases Intel’s Anti Theft technologies (starting at 31:10 mark and ending at 34:57). Here Mooly invited McAfee co president, Todd Gebhart, to the stage to discuss McAfee’s Anti Theft which allows a user to lock their laptop or even wipe their data by issuing a poison pill in the event that their laptop is stolen. Then Mooly introduced a new technology called Intel Identity Protection Technology (IPT) . To showcase this technology, Mooly had a hacker, garbed in a ninja costume, attempt to use a key logger and frame grabbing software to attempt to hack, demo presenter, Mark’s bank transaction. In this amazing clip, the hacker successfully grabs the username and password to Mark’s bank account, using a nefarious keylogger. BUT – the hacker cannot capture or generate a third authentication token which has been set up between Mark & his bank. The hacker is thwarted from any mischievous activity by IPT. Using this IPT technology, a random layout pin pad is generated and displayed to Mark, which allows Mark to send an additional credential to the bank in order to authenticate the transaction. Mark’s bank account is safe! See this part of the clip at 35:08 to 38:44 . If you want to learn even more, see Intel’s Ned Smith’s IPT foils at 2011 Kerberos conference. I plan to be interviewing experts from various corners of Intel to help describe these technologies in more detail. We will also be working to bring API’s to light with Software Developer Guides, tech briefs, and whitepapers, videos and more. I also hope to keep one eye on new developments in the security space in the rest of industry to help articulate security, virtualization and manageability trends that I see developing.
New Consumer ID & In-App Unlock Purchase APIs for AppUp developers
The holiday season is always full of cheer and giving, and in that spirit the Intel AppUpSM developer program has a few presents under the tree for our developers.
My 5 Favorite New Intel® Software Development Product Features of 2011
It’s been a big year for us in the Intel Developer Products Division. We released Intel® Cluster Studio XE and Intel® Parallel Studio XE Service Pack 1 . We continued to plan and design our products to provide support for the compute continuum. And of course we worked to grow our community of developers. Throughout the year there have been several new features and developments in some of my favorite products – below I list my personal top 5 and tell you why. This list is of course heavily biased by my particular area of expertise (performance) and is by no means a complete list of all the new products or features that went into Intel® Software Development products in 2011! So, without further ado, my favorites: 5. Intel® Cilk Plus open source port to GCC – Intel® Cilk Plus was announced in 2010, and an open source specification has been out since late 2010 as well. However this year we began, along with the open source community, to port Cilk Plus to GCC. Some of the first items ported were the parallelism keywords, which is significant to me because it makes our Cilk Plus parallelism model available to a greater audience. 4. Intel® VTune™ Amplifier XE and Intel® Inspector XE MPI Support – In the new Cluster Studio XE product, VTune Amplifier XE and Inspector XE are now MPI-enabled. This is important because we are beginning to see more hybrid programming in the HPC and cluster world – which means the applications use a combination of MPI and another threading model (such as OpenMP, Cilk Plus, or Intel® Threading Building Blocks ). We have an existing product, Intel® Trace Analyzer and Collector , that analyzes MPI efficiency for a cluster app, but analyzing performance of an individual process running on an MPI rank was more difficult. Now we make it easier to use VTune Amplifier XE or Inspector XE to analyze the threading model used within a rank, which helps us support more cluster customers. 3. Intel® Threading Building Blocks Flow Graph – I was introduced to flow graph this year, when I worked with my colleague Victoria Gromova to create some TBB labs for Intel Developer Forum. Victoria wanted to highlight flow graph as one of the new features of TBB 4.0 . Flow graph is a new construct that supports many more types of control algorithms, like dependency graphs, event-based models or reactive-based flows. In short, it opens up TBB to more customers while maintaining or improving the TBB performance we have come to expect. 2. VTune Amplifier XE attach to running process on Linux* – This is a great example of our development team responding to customer feedback. Being able to analyze a running process for a defined period of time (instead of launching it) has been requested by many of our clients. We first got this implemented on Windows*, then this September provided the feature for Linux* in Intel® Parallel Studio XE Service Pack 1 . I have already been visiting some users who requested this and it is great to be able to share that the feature they have been asking for is here! 1. VTune Amplifier XE interface for Intel® Microarchitecture Codename Sandy Bridge – For readers of my blog this one should not be a surprise! I have created quite a bit of training material on these new Sandy Bridge features. We now provide an analysis type for Sandy Bridge that helps users easily identify the most common software performance issues at the microarchitectural level, and it includes pre-coded metrics, thresholds, and issue highlighting for usability. This is my favorite new feature because, even though I am not a developer, I got to help a little with making this interface by helping define some performance metrics and thresholds and validating them on workloads. It is very cool to see my contributions in the product. There you have it! I hope you have a chance to try out some of our new product features now or in the coming year. Let us know your favorites, or your requests.
JavaScript Gaming Framework Webinar – January 24, 2012
Interested in developing games or have an existing game you want to monetize?
Looking Ahead to 2012
Well, I reflected on 2011 in my last blog , so now it’s time to look ahead. My basic role will remain unchanged – I help users of our Intel® Software Development Products to achieve better performance on their applications. I will still be updating our training materials and videos for the latest mainstream Intel processors. And I will be helping customers to discover the latest Intel® VTune™ Amplifier XE features. And, since parallelism is a common path to performance, I will still be a big advocate of Intel® Threading Building Blocks (TBB) . In fact, I plan to create some new training around TBB 4.0 and the flow graph feature. But I will also be ramping up on some new focus areas for me: • Intel® Many Integrated Core Architecture (MIC) MIC (pronounced “Mike”) is a new architecture that uses many low-power, single-threaded Intel® processor cores working together to provide a high degree of parallelism. As more customers begin using the Knights Ferry development kit and the developer tool package we currently have available for MIC, I will start studying the architecture and conducting some experiments too. My first project will be to try to identify the most important performance aspects of MIC applications and how our tools can help developers measure them. • Vectorization Vectorization is parallelism within one CPU core, using special hardware that can work on more than one piece of data at once. First off I plan to write a series of blogs explaining what vectorization is, who should be interested in it, how to achieve it, and why it’s important. Then I hope to work with some customers directly on this. One reason why vectorization will be of big interest to me is that it will definitely be a big help to performance on the MIC architecture. • Intel® Cilk Plus Fitting hand in hand with the 2 focus areas above is Intel® Cilk Plus, our open source parallelism model that also includes vectorization support. Although I have worked with and evangelized Cilk Plus a lot this past year, I had mainly been looking at the parallelism part. Next year, I will spend more time on the vectorization part of Cilk Plus. The other reason to focus here is that Cilk Plus code, like TBB code, will also run on the MIC architecture. So get ready to hear more from me on the above topics! And Happy Holidays!



Posted in
Tags: