There is, I think, something ethereal about i —the square root of minus one. I remember first hearing about it at school. It seemed an odd beast at that time—an intruder hovering on the edge of reality.

Usually familiarity dulls this sense of the bizarre, but in the case of i it was the reverse: over the years the sense of its surreal nature intensified. It seemed that it was impossible to write mathematics that described the real world in …

I and i

The term photonic crystals appears because of the analogy between electron waves in crystals and the light waves in artificial periodic dielectric structures. During the recent years the investigation of one-, two-and three-dimensional periodic structures has attracted a widespread attention of the world optics community because of great potentiality of such structures in advanced applied optical fields. The interest in periodic structures has been stimulated by the fast development of semiconductor technology that now allows the fabrication of artificial structures, whose period is comparable with the wavelength of light in the visible and infrared ranges.

http://ieeexplore.ieee.org/iel5/6354/16969/00781867.pdf

Photonic crystals

From the Book:
“Clean code that works” is Ron Jeffries’ pithy phrase. The goal is clean code that works, and for a whole bunch of reasons:
Clean code that works is a predictable way to develop. You know when you are finished, without having to worry about a long bug trail.Clean code that works gives you a chance to learn all the lessons that the code has to teach you. If you only ever slap together the first thing you think of, you never have time to think of a second, better, thing. Clean code that works improves the lives of users of our software.Clean code that works lets your teammates count on you, and you on them.Writing clean code that works feels good.But how do you get to clean code that works? Many forces drive you away from clean code, and even code that works. Without taking too much counsel of our fears, here’s what we do—drive development with automated tests, a style of development called “Test-Driven Development” (TDD for short). 
In Test-Driven Development, you:
Write new code only if you first have a failing automated test.Eliminate duplication.

Two simple rules, but they generate complex individual and group behavior. Some of the technical implications are:You must design organically, with running code providing feedback between decisionsYou must write your own tests, since you can’t wait twenty times a day for someone else to write a testYour development environment must provide rapid response to small changesYour designs must consist of many highly cohesive, loosely coupled components, just to make testing easy

The two rules imply an order to the tasks ofprogramming:
1. Red—write a little test that doesn’t work, perhaps doesn’t even compile at first
2. Green—make the test work quickly, committing whatever sins necessary in the process
3. Refactor—eliminate all the duplication created in just getting the test to work


Red/green/refactor. The TDD’s mantra.

Assuming for the moment that such a style is possible, it might be possible to dramatically reduce the defect density of code and make the subject of work crystal clear to all involved. If so, writing only code demanded by failing tests also has social implications:
If the defect density can be reduced enough, QA can shift from reactive to pro-active workIf the number of nasty surprises can be reduced enough, project managers can estimate accurately enough to involve real customers in daily developmentIf the topics of technical conversations can be made clear enough, programmers can work in minute-by-minute collaboration instead of daily or weekly collaborationAgain, if the defect density can be reduced enough, we can have shippable software with new functionality every day, leading to new business relationships with customers


So, the concept is simple, but what’s my motivation? Why would a programmer take on the additional work of writing automated tests? Why would a programmer work in tiny little steps when their mind is capable of great soaring swoops of design? Courage.
Courage
Test-driven development is a way of managing fear during programming. I don’t mean fear in a bad way, pow widdle prwogwammew needs a pacifiew, but fear in the legitimate, this-is-a-hard-problem-and-I-can’t-see-the-end-from-the-beginning sense. If pain is nature’s way of saying “Stop!”, fear is nature’s way of saying “Be careful.” Being careful is good, but fear has a host of other effects:
Makes you tentativeMakes you want to communicate lessMakes you shy from feedbackMakes you grumpy

None of these effects are helpful when programming, especially when programming something hard. So, how can you face a difficult situation and:
Instead of being tentative, begin learning concretely as quickly as possible.Instead of clamming up, communicate more clearly.Instead of avoiding feedback, search out helpful, concrete feedback.(You’ll have to work on grumpiness on your own.) 

Imagine programming as turning a crank to pull a bucket of water from a well. When the bucket is small, a free-spinning crank is fine. When the bucket is big and full of water, you’re going to get tired before the bucket is all the way up. You need a ratchet mechanism to enable you to rest between bouts of cranking. The heavier the bucket, the closer the teeth need to be on the ratchet.

The tests in test-driven development are the teeth of the ratchet. Once you get one test working, you know it is working, now and forever. You are one step closer to having everything working than you were when the test was broken. Now get the next one working, and the next, and the next. By analogy, the tougher the programming problem, the less ground should be covered by each test.

Readers of Extreme Programming Explained will notice a difference in tone between XP and TDD. TDD isn’t an absolute like Extreme Programming. XP says, “Here are things you must be able to do to be prepared to evolve further.” TDD is a little fuzzier. TDD is an awareness of the gap between decision and feedback during programming, and techniques to control that gap. “What if I do a paper design for a week, then test-drive the code? Is that TDD?” Sure, it’s TDD. You were aware of the gap between decision and feedback and you controlled the gap deliberately.

That said, most people who learn TDD find their programming practice changed for good. “Test Infected” is the phrase Erich Gamma coined to describe this shift. You might find yourself writing more tests earlier, and working in smaller steps than you ever dreamed would be sensible. On the other hand, some programmers learn TDD and go back to their earlier practices, reserving TDD for special occasions when ordinary programming isn’t making progress.

There are certainly programming tasks that can’t be driven solely by tests (or at least, not yet). Security software and concurrency, for example, are two topics where TDD is not sufficient to mechanically demonstrate that the goals of the software have been met. Security relies on essentially defect-free code, true, but also on human judgement about the methods used to secure the software. Subtle concurrency problems can’t be reliably duplicated by running the code.

Once you are finished reading this book, you should be ready to:
Start simplyWrite automated testsRefactor to add design decisions one at a time

This book is organized into three sections.
An example of writing typical model code using TDD. The example is one I got from Ward Cunningham years ago, and have used many times since, multi-currency arithmetic. In it you will learn to write tests before code and grow a design organically.An example of testing more complicated logic, including reflection and exceptions, by developing a framework for automated testing. This example also serves to introduce you to the xUnit architecture that is at the heart of many programmer-oriented testing tools. In the second example you will learn to work in even smaller steps than in the first example, including the kind of self-referential hooha beloved of computer scientists.Patterns for TDD. Included are patterns for the deciding what tests to write, how to write tests using xUnit, and a greatest hits selection of the design patterns and refactorings used in the examples.

I wrote the examples imagining a pair programming session. If you like looking at the map before wandering around, you may want to go straight to the patterns in Section 3 and use the examples as illustrations. If you prefer just wandering around and then looking at the map to see where you’ve been, try reading the examples through and refering to the patterns when you want more detail about a technique, then using the patterns as a reference.

Several reviewers have commented they got the most out of the examples when they started up a programming environment and entered the code and ran the tests as they read.

A note about the examples. Both examples, multi-currency calculation and a testing framework, appear simple. There are (and I have seen) complicated, ugly, messy ways of solving the same problems. I could have chosen one of those complicated, ugly, messy solutions to give the book an air of “reality.” However, my goal, and I hope your goal, is to write clean code that works. Before teeing off on the examples as being too simple, spend 15 seconds imagining a programming world in which all code was this clear and direct, where there were no complicated solutions, only apparently complicated problems begging for careful thought. TDD is a practice that can help you lead yourself to exactly that careful thought.

Test Driven Development: By Example

Optical quantum states based on entangled photons are essential for solving questions in fundamental physics and are at the heart of quantum information science. Specifically, the realization of high-dimensional states (D-level quantum systems, that is, qudits, with D > 2) and their control are necessary for fundamental investigations of quantum mechanics, for increasing the sensitivity of quantum imaging schemes, for improving the robustness and key rate of quantum communication protocols, for enabling a richer variety of quantum simulations, and for achieving more efficient and error-tolerant quantum computation. Integrated photonics has recently become a leading platform for the compact, cost-efficient, and stable generation and processing of non-classical optical states. However, so far, integrated entangled quantum sources have been limited to qubits (D = 2). Here we demonstrate on-chip generation of entangled qudit states, where the photons are created in a coherent superposition of multiple high-purity frequency modes. In particular, we confirm the realization of a quantum system with at least one hundred dimensions, formed by two entangled qudits with D = 10. Furthermore, using state-of-the-art, yet off-the-shelf telecommunications components, we introduce a coherent manipulation platform with which to control frequency-entangled states, capable of performing deterministic high-dimensional gate operations. We validate this platform by measuring Bell inequality violations and performing quantum state tomography. Our work enables the generation and processing of high-dimensional quantum states in a single spatial mode.

/pdf/on-chip-generation-of-high-dimensional-entangled-quantum-1d1gjgvebv.pdf

On-chip generation of high-dimensional entangled quantum states and their coherent control

Research efforts addressing spin waves (magnons) in micro- and nanostructured ferromagnetic materials have increased tremendously in recent years. Corresponding experimental and theoretical work in magnonics faces significant challenges in that spin-wave dispersion relations are highly anisotropic and different magnetic states might be realized via, for example, the magnetic field history. At the same time, these features offer novel opportunities for wave control in solids going beyond photonics and plasmonics. In this topical review we address materials with a periodic modulation of magnetic parameters that give rise to artificially tailored band structures and allow unprecedented control of spin waves. In particular, we discuss recent achievements and perspectives of reconfigurable magnonic devices for which band structures can be reprogrammed during operation. Such characteristics might be useful for multifunctional microwave and logic devices operating over a broad frequency regime on either the macro- or nanoscale.

https://iopscience.iop.org/article/10.1088/0953-8984/26/12/123202/pdf

Review and prospects of magnonic crystals and devices with reprogrammable band structure

to Magnetism.- Quantum Theory of Spin Waves.- Magnetic Susceptibilities.- Electromagnetic Waves in Anisotropic-Dispersive Media.- Magnetostatic Modes.- Propagation Characteristics and Excitation of Dipolar Spin Waves.- Variational Formulation for Magnetostatic Modes.- Optical-Spin Wave Interactions.- Nonlinear Interactions.- Novel Applications.

/pdf/spin-waves-theory-and-applications-2id9fyhi6y.pdf

Spin Waves: Theory and Applications

In this paper, we propose a standard micromagnetic problem, of a nanostripe of permalloy. We study the magnetization dynamics and describe methods of extracting features from simulations. Spin wave dispersion curves, relating frequency and wave vector, are obtained for wave propagation in different directions relative to the axis of the waveguide and the external applied field. Simulation results using both finite element (Nmag) and finite difference (OOMMF) methods are compared against analytic results, for different ranges of the wave vector.

/pdf/proposal-for-a-standard-micromagnetic-problem-spin-wave-577die9q6u.pdf

Proposal for a Standard Micromagnetic Problem: Spin Wave Dispersion in a Magnonic Waveguide

Absorbing boundary layers for spin wave micromagnetics

Automatic identification of bird calls without manual intervention has been a challenging task for meaningful research on the taxonomy and monitoring of bird migrations in ornithology. In this paper we apply several techniques used in speech recognition to the automatic identification of bird calls. A new technique which computes the ensemble average on the FFT spectrum is proposed for identification of bird calls. This ensemble average is computed on the FFT spectrum of each bird and is called the Spectral Ensemble Average Voice Print (SEAV) of that particular bird. The SEAV of various birds are computed and are found to be different when compared to each other. A database of bird calls is created from the available recordings of fifteen bird species. The SEAV is then used for the identification of bird calls from this database. The results of identification using SEAV are then compared against the results derived from common classifiers used in speech recognition like dynamic time warping (DTW), Gaussian mixture modeling (GMM). A one level and two level classifier combination is also tried by combining SEAV classifier with the DTW classifier. The SEAV is computationally less expensive when compared to DTW or the GMM based classifiers while performing better than the DTW technique. Several new possibilities in automatic bird call identification using SEAV are also listed.

Automatic identification of bird calls using Spectral Ensemble Average Voice Prints

In this paper, we estimate the stiction force from electrical (current-voltage) measurements on surface micromachined polysilicon cantilever beams A bias voltage was applied between the beam and the substrate At the pull-in voltage, the beam collapsed to the substrate and the current rose rapidly from zero Similarly, at the pull-out voltage during bias sweep back, the current dropped rapidly to zero when the contact between the beam and the substrate was broken An analytic model for the stiction force was developed in terms of the pull-in and pull-out voltages and was used to estimate a stiction force of about 70 nN from the measured electrical characteristics This method of characterization is suitable for use in packaged devices An analytic model was developed to estimate stiction force from optical surface-profile measurements of the curvature of long collapsed cantilever beams in a cantilever-beam array, in the absence of any electrostatic actuation The force per unit length of about 14 nN/m thus obtained was used to compare the effects of surface roughness on stiction

Anil Prabhakar

Papers

Spin Waves: Theory and Applications

Proposal for a Standard Micromagnetic Problem: Spin Wave Dispersion in a Magnonic Waveguide

Absorbing boundary layers for spin wave micromagnetics

Automatic identification of bird calls using Spectral Ensemble Average Voice Prints

Estimation of Stiction Force From Electrical and Optical Measurements on Cantilever Beams