Showing posts with label research. Show all posts
Showing posts with label research. Show all posts

Saturday, May 15, 2021

The lightbulb machine: How to come up with new research ideas

 

 

"It seems necessary to me, then, that all people at a session be willing to sound foolish and listen to others sound foolish." ~Isaac Asimov in his essay titled On Creativity
 
Most researchers are learners trying to understand their field, and beyond, as best as they can using the tools at their disposal. But of course research is about pushing the frontiers of knowledge a tad outside of what is already known to humanity. This is beautifully expounded as a dent in the circle of human knowledge in The Illustrated Guide To A Ph.D. by Matt Might, University of Alabama at Birmingham. Although Might's depiction shows this phenomenon in an academic context where the game is explicitly sytematised, a lot of people are (often anonymously) denting the circle outside of the typical grad school setting and without the fancy hats and badges. In our efforts to make those dents, we are always on the lookout for ways to generate new research ideas.

The central question then is: How can I come up with an idea that no human has come up with before? I cannot seem to will them into existence, ideas seem to come out of the blue, often at odd times. In most cases, after arriving on an idea, the initial feeling of triumph is promptly damped by a Google search that throws up a 1990s paper (hopefully not earlier) that already proposed the idea, and they probably went above and beyond what you had envisaged. No wonder, the key to having good and new ideas is to have many many ideasharness the power of combinatorial success. If we need so many ideas, what are our methods for idea generation? I thought of compiling a few of my tricks here so I can come back to it when I am sans inspiration. May be some of these work for you too.

1. Combine two (or more) disparate ideas

Entrepreneur and leadership speaker Joel Hilchey says, "Many new ideas come from combining two distinct ideas. E.g. combining a phone and a computer, we have a smartphone." He has a point. The process of ideation is a lot like chemistry. Ideas are like atoms and molecules. We come up with new ideas by bringing together and combining existing ones. If you have a lot of 'elementary ideas' and you keep shuffling them around, rearranging them in different ways, ultimately some of them will naturally snap together to form new ideas. You can then further explore these newly formed compound ideas putting them under the microscope to discover their properties and potential. Some tools that facilitate this task of continuously rearranging ideas are writing, making tables and lists, drawing graphs and curves (by hand AND by computers), mind-maps, sorting your notes by keywords (Tiddlywiki is excellent for this), and of course the good old Socratic method with an honest interlocutor.

Another good way of ensuring regular combinations of disparate ideas is for an individual to have at least two fields of study, say a major and a minor, and to keep smuggling ideas from one field to the other. As an engineer, a clear manifestation of this method is 'from science lab to engineering lab'. Take recent scientific advances and use them in engineering applications. These could be new devices, components, materials, configurations etc. E.g. Robert Middlebrook took William Shockley’s transistor idea, and used it in circuits to spawn the area of power electronicswhich is central to technologies like renewable energy, electric vehicles, and smart grids today. This 'translation story' is laid out in illuminating detail in a 1998 Middlebrook interview by K. Kit Sum. Another stalwart in power electronics, Fang Z. Peng from Michigan State University, sometimes recruits grad students with absolutely no background in power engineering citing the rationale, “Great ideas in a particular research area come from outside the field.”

We've been focusing on bringing together separate fields of study in our quest for new ideas. Sometimes, however, theoretical and practical aspects of the SAME field can get siloed into being like separate fields. This is where opportunity is rife for switching back and forth between the two sides in order to shuttle ideas. Make the divide between industry and academia porous. If you are not yourself able to switch sides, invite people over from the other side. Build bridges, open doors.

 
2. Marry complementary problems

A bad effect of one system can serve as a good effect for another system. Put them together to get integrated solutions. E.g. Cooling requirements are highest when it is sunniest i.e. the available solar energy is maximum. Hence explore solar-powered air-conditioning, and solar-driven peltiers for cooling photovoltaic cells. Food for storage needs cooling while a home, or at least its water supply, might need heating. Instead of investing resources separately into each of these problems, what is a good way to integrate their complementary needs into a single solution? I go crazy when I see my refrigerator working hard to keep my ice-cream frozen while the room-heater tries to heat the space around the refrigerator.   

Sometimes, it is easier to solve multiple problems with one solution. E.g. shifting to a largely active transportation model, à la Amsterdam, consisting of short-distance trips of walking and biking simultaneously addresses the issues of air pollution, public health, road accidents, and climate emergency. This is the kind of problem solving approach that Elizabeth Sawin calls multisolving. Like the bridging approach of #1 above, multisolving also entails talking to researchers in other fields about the key problems they are trying to solve.

Another way of looking at multisolving is to “overload” existing systems. If something already exists, what can it do in addition to what it was designed to do? Sometimes, with just small modifications, we can make existing systems and components do additional tasks. E.g. (1) Using WiFi to serve as an indoor GPS; (2) Using the motor-drive power converter circuit of an electric vehicle as battery charger.

 
3. Measure everything, then infer

New eyes. This is what a rich variety of sensors and instrumentation allow us today. Observe the system under study from different perspectives, then look at the data to hopefully tell things about its health and surroundings that were previously unknown. Often this involves bringing in types of measurement instruments not typically associated with your system under study. E.g. Electronics engineers are used to probing circuits with multimeters, oscilloscopes, and (for the wealthy ones) spectrum analyzers. How about microphones? Based on audible sound signature of a motor or other electro-magnetic device, can we infer something about the health and/or operating mode? A related tip for young electronics engineers from ISRO's Manoj R. Iyer is to use current probes as we often tend to get locked into using only voltage probes seeing only voltage waveforms. Taking this new-eyes idea into creepy territory, MIT researchers found a way to decipher what someone is speaking based on the vibrations on a Lay’s chips packet near the person.

 
4. Classify and tabulate

I briefly brought this up in #1 above, but the classify-and-tabulate method probably merits a separate mention on its own. This has been a powerful tool from the beginning of science as many humans derive cathartic pleasure in arranging things systematically (Marie Kondo likes this) and then looking for hidden patterns. Exhaustive classification and tabulation provides a bird’s eye view of the field and easy comparison of normally scattered pieces of information by the simple act of juxtaposition. A table tells us what are the things we know quantitatively and what we know qualitatively. A table is a powerful tool for locating gaps in knowledge as depicted below. This is perhaps why you would find lots of tables in technical texts even though we have more aesthetic tools like graphs and plots.


 
5. Draw waveforms and plots by hand

With the ubiquitous computers and simulation tools, it is easy to let them do all our plotting. While that is widely used for good reason, I would draw attention to drawing waveforms and other plots by hand. Drawing by hand makes you think in ways that simulation doesn't, simply because the latter is sometimes a bit like watching a football match rather than playing it. Drawing by yourself is akin to running your own mental simulation. Let us say you try to draw an XY plot. Immediately you have to first label the axes and think about the typical range of numbers for each axis for the chosen units. As you put down the pen on paper, where do you start and end the curve? What are the initial conditions and boundary conditions that define the constraints for what you draw. What is the slope in different parts of the curve? You will need to know about dynamics, rate of change, and sensitivity. Is the function monotonic, is it continuous, is it differentiable? As you put ink on the seemingly dead piece of paper, it comes alive with many questions. You are having a rich conversation with dead plant tissue.

6. Eye for detail

The prolific Isaac Asimov wrote these insightful lines: "The most exciting phrase to hear in science, the one that heralds new discoveries, is not 'Eureka!' but rather, 'hmm... that's funny...'" While it is easy to look for things that you want to see, seek out details that are not as per your expectation even if they are fleeting. That is where new ideas and potential problems hide. The Davis Dictum says, "Problems that go away by themselves come back by themselves." There is this category of bugs that show up only intermittently and are hard to reproduce. These types of bugs are the toughest little scoundrels to understand and debug. And often, their genesis lies in the ignored details that have always been there, albeit not always in plain sight. And so, keep an eye for detail not just in your mind put perhaps also in your notes and reports. Further expanding this 'tell everything, hide nothing' philosophy, Richard Feynman writes in 'Surely You're Joking, Mr. Feynman!':

“If you’re doing an experiment, you should report everything that you think might make it invalid—not only what you think is right about it: other causes that could possibly explain your results; and things you thought of that you’ve eliminated by some other experiment, and how they worked—to make sure the other fellow can tell they have been eliminated. Details that could throw doubt on your interpretation must be given, if you know them. You must do the best you can—if you know anything at all wrong, or possibly wrong—to explain it. If you make a theory, for example, and advertise it, or put it out, then you must also put down all the facts that disagree with it, as well as those that agree with it. There is also a more subtle problem. When you have put a lot of ideas together to make an elaborate theory, you want to make sure, when explaining what it fits, that those things it fits are not just the things that gave you the idea for the theory; but that the finished theory makes something else come out right, in addition. In summary, the idea is to try to give all of the information to help others to judge the value of your contribution; not just the information that leads to judgment in one particular direction or another. The first principle is that you must not fool yourself—and you are the easiest person to fool.”

7. Old books, new ideas

Research today tends to fall into the habit of limiting itself to recent references, and clean and searchable PDFs. There are many brilliant ideas in old books and documents. When I say old, I mean yellowed-pages old, possibly even tattered. Some of these ideas might have died because the context in which they came up was not conducive, or because there weren't tools to implement them. Delve into the archives, and this will perhaps also make you a steward for their preservation. This is why I have great respect for libraries, and online archives like Internet Archive and Project Gutenberg. In his book Chaos, James Gleick writes about physicist Albert Libchaber:
 
"His colleagues joked about his obsession with old books. He had hundreds of original editions of works by scientists, some dating back to the 1600s. He read them not as historical curiosities but as a source of fresh ideas about the nature of reality, the same reality he was probing with his lasers and his high-technology refrigeration coils."


8. Ideas from the trashcan

Outside my office at CERN, there is an e-waste trashcan. Hardware aficionados are often seen digging into these bins like sea gulls in search of a prize catch. Some of the kaput gizmos there are quite old and rare. Leaving aside their antique value, a piece of broken equipment is an invitation to read the designer's mind. What made them chose these components placed in that particular configuration? What were the limits of the technology of the day? Can it be repaired? Are there parts of the system that would still work perfectly well? What can you salvage from these tech fossils? As the legendary analog designer Jim Williams puts it, "The inside of a broken, but well-designed piece of test equipment is an extraordinarily effective classroom." The trashcan also inspires me to practice my French (because it sounds so much more dramatic): La poubelle est le meilleur endroit pour trouver quelque chose de valeur. Translation: The trashcan is the best place to find something of value.

I would close this essay with a caveat. In a discussion with Ashwin Khambadkone from National University of Singapore, he laments that academics are often bitten by the 'novel virus'. The fascination for the novel can lead away from the good. It is far more important to have good ideas than it is to have new ones.

Monday, November 16, 2020

Breaching the wall when stuck in a project


Often we find ourselves stuck in our projects. You put in the time and effort, yet there is no perceptible progress. You've hit a wall and you crouch beside it in defeat. Through experience, each of us comes up with our own tools to breach or circumvent the wall. Here is my getting-unstuck toolkit that seems to work reasonably well in projects ranging from lab research and writing articles/theses to designing and developing prototypes and products, largely in engineering contexts. Some of these tools are just repackaged clichés and others that I can pretend to be a pioneer in until someone corrects my illusion. If you have some tools that you do not see in my kit yet, I would be happy to hear from you.

1. Look at the wall from afar
Constantly looking at the same problem from the same vantage point tends to produce similar thought processes. You can break the thinking loop by changing your perspective which is essentially comprised of two aspects: proximity and angle of approach. By proximity I mean the distance between you and the problem. Are you looking at it at a very microscopic scale, considering only local features? Take a step back, see the bigger picture. Zoom out, observe your subject, and then zoom in again. The key is the time you spend afar. If you do not spend enough time observing from the farther distance, you might find yourself falling back into familiar thinking loops.

2. Change your angle of approach
The other way to change your perspective is to change the angle of approach. If you were previously going head on into the wall, try going at a slant. For example, if you were trying a hands-on experimental approach, may be it is time to look at the theory again, or try a computer simulation instead. If you were tackling a phenomenon in your lab prototype, may be it is worth looking for similar problems in some industrial products. If your approach is too technical, may be it is time to try a more layman approach, agnostic of many of the details.

3. Go around
With all due respect to walls, some of them just do not need breaching. Do you really need to solve that problem? Sometimes, going to the other side is a mere matter of going around the wall, trying a different route, or even locating the door. Ask yourself if you are being that fly banging against the same glass window when the adjacent one is open?

4. Take a break
This one is much too trite, yet seldom not right. You know you are utterly stuck, and it is not the time to push harder. Changing your physiology and your surroundings can change the way you think. Get out of the desk and walk, run, bike, play, shower (colds ones can really kick you out of your brains)whatever activity suits your taste. During my PhD days, playing cricket a couple of hours a day was my preferred release. I remember Professor Arindam Ghosh, an accomplished condensed matter physicist, being one of the few faculty members at the Indian Institute of Science who would 'play and break the thinking loop.'

5. You are not alone
As much as the wall might seem personal, it is probably not. People have been there before you. So you google your problem and despite your best keyword game and your clicks on the forty-second search page, this devious specific wall has somehow avoided mention in any forum. Thankfully, there are people other than strangers on the internet. Ask someone you know, discuss with a colleague or friend with relevant or related experience. Even if they do not have an direct solution, they might point you towards an alley you did not know about. In the words of Rolf-Dieter Heuer, former director general of CERN, "You just have to look around. Then you will see all the others who have the same difficulties." Sometimes, the very act of trying to articulate your problem triggers a possible solution. As astrophysicist James Guillochon says, "If you are stuck on a problem, write a long email/message to someone who can help (as detailed as possible) but don’t send it. Very often you’ll figure it out in the process of writing that message." A similar method used in the software engineering world is called rubber duck debugging, and we all need our rubber ducks.

6. Ping-pong between walls
It is good to have two (or more) brick walls (e.g. research problems for a graduate student) to bang your head against, so that you can ping-pong between them, all the while making some progress without losing your sanity. The core idea of ping-ponging is to hit different walls which is possible only when there are more than one of them. From this perspective, it is probably not a good idea to have only one problem to hit your head against. Diversity in the nature of problems you handle can help in honing your problem solving skills even while it seems that you are continuously failing at various altars. Author Stephen Birmingham underlines this approach in his practice, "I always work on two things at a time. When one goes flat, I turn to the other."

7. Skip step three
If a task has 10 steps and you are stuck in step-3 for a long time, jump ahead to get started on any of steps 4-10. Many a time, they don't necessarily need the earlier step to be completed and you make some headway while you're still stuck on step-3. Sometimes doing steps 4-10 can facilitate getting unstuck from step-3. Turkish writer Orhan Pamuk seems to endorse this approach: "When I’m blocked, which is not a grave thing for me, I continue writing whatever takes my fancy. I may write from the first to the fifth chapter, then if I’m not enjoying it I skip to number fifteen and continue from there."

8. Small is big
It could be unfair on yourself to directly target a big hurdle when you haven't had experience tackling smaller ones. Mathematician George Polya said it better than I can, "If you can't solve a problem, then there is an easier problem you can solve: find it." Sometimes, there are smaller walls hidden inside the big one. The largest of walls is made up of bricks. Chip away at the smallest scale, one splinter at a time. This is the opposite of zooming out. You have zoomed in so much that you can see individual grains of sand that you are capable of tackling. "Do the good that’s in front of you, even if it feels very small," says American author Sharon Salzberg. 

Sometimes it is not that the wall is insurmountable, but that you do not seem to find time enough to address the wall. English author Fay Weldon furnishes the required inspiration here, "I write in short paragraphs because when I began there were always children around, and it was the most I could do to get three lines out between crises." Professor Richard Felder provides further clarification on this idea, "Don't wait for that 'block of time' to get things done. Do the task in short bursts with whatever time slots are available."

9. When stuck in a sinkhole, write
I was once visiting the Dead Sea when the tour guide took us past some large sinkholes and brought up an intriguing story of an Israeli geologist Eli Raz who fell into one of these ditches. While he was stuck there for fourteen hours, waiting for the rescue team, he wrote a diary entry on his
observations and experience of being inside a sinkhole. Lesson: When stuck in a sinkhole, write about your experience. Someone will later find solace, if not solutions, in reading it.

Friday, February 6, 2015

The PhD Experience

Yesterday I gave a talk titled "The PhD Experience: Lessons learnt in five and half years." I narrated my personal experiences, thoughts and the lessons I learnt while pursuing a PhD at the Department of Electronic Systems Engineering, Indian Institute of Science. 

The key question that I try to address is, "What are the processes and tasks that get the best out of a researcher?" Considering the researcher as a system, I discuss the inputs (information and experiences), outputs (hardware, software, knowledge) and processes of this system. The presentation is targeted primarily at present and prospective graduate students. However, anybody with an interest in learning and productivity might resonate with aspects of the talk.

Here's the video of the talk [video credits: Abhijit Kshirsagar]

The pdf file of my presentation is available here.

P.S. During the talk, I mentioned the importance of developing verb vocabulary.
The Thesis Whisperer has compiled a useful verb cheat sheet that is available here.

Saturday, July 30, 2011

Energetic consequences of doing things slowly

From charging capacitors to filling up water tanks.

Electrical engineers are familiar with the idea that when you try to charge a capacitor from a step voltage source, only half of the energy coming from the source gets into the capacitor while the other half is dissipated in the circuit resistances and/or lost as radiated electromagnetic energy. In other words, the efficiency is only 50%. Does it always have to happen that way? How can we do better?

The answer lies in shaping the applied voltage. If the rate of rise of the applied voltage is of the order of the time-constant of the circuit, the efficiency is much better than 50%. If it is very slow compared to the time-constant of the circuit, the efficiency approaches 100%. This is proved analytically as well as validated by circuit simulation in this article.

Even if we did not shape the voltage, if the capacitor doesn't have a linear relation between charge and voltage (in other words, it is a non-linear capacitor), the efficiency can still be very different from 50%.

The case of a step current source feeding an inductor is also analogous to the above scenario and gives similar results.

Taking a step back and applying this concept to any other domain (other than electrical engineering) can give some interesting insights. Pumping water into an overhead tank through a pipe having finite resistance (due to friction) is an example of an effort source feeding a potential energy storage element much like a voltage source charging a capacitor. Hence, it will take lesser energy if we were to pump the water slowly (trickle pumping) over several hours rather than doing it fast (gushing water) in fifteen minutes flat!

On a philosophical note, a very nice example is that of a teacher teaching a student. If the teacher goes far too fast beyond the grasping speed of the student, much of the knowledge doesn’t get transferred to the student’s brain.

Wednesday, April 27, 2011

Importance of stupidity in research


“If we knew what it was we were doing, it would not be called research, would it?” –Albert Einstein

Every time I manage to take a small step forward in my research, a plethora of new doubts and questions crop up. There are so many of these questions that I don’t seem to have an answer for – at least in the present. My collected PhD notes seem to be littered with more questions than answers. They expose my ignorance and probably prove my stupidity. 

That turns out to be quite a normal and happy disposition for a researcher. Martin Schwartz discusses about the importance of stupidity in scientific research in a heartening article for researchers. “The more comfortable we become with being stupid, the deeper we will wade into the unknown and the more likely we are to make big discoveries”, he writes.

Questions are the very things that drive the researcher and his/her research. You can’t seek answers if you don’t have questions. Does that make questions more important than answers? Possibly yes. The amazing human brain can come up with endless questions. Answers for questions that have been answered before come from prior art and learned men/women. For the unanswered questions, answers could come from various sources – deep thought by the brain itself, nature, experiment and, in some cases, a computer. 

Quite interestingly, Pablo Picasso once said "Computers are useless. They can only give you answers." They are after-all garbage-in, garbage-out machines. If the questions are meaningless, so shall be the answers. So if you've been thoughtful enough to pose the right question, it's acceptable to feel stupid about not knowing the answer so long as you're still seeking. In other words, feeling stupid is okay, being stupid is not.

Wednesday, September 15, 2010

The Art of Teaching

Much of our competence, and for that matter even the interest we have, in a subject is down to how well we were taught that subject. A good teacher has a profound influence on the capabilities and performance of his pupils in life. Science and engineering education is no exception. With my sights set on taking up teaching and research as a career, I'm always impressed when I come across someone who is exceptional and creative in his pedagogical methods. 

Recently, thanks to YouTube, I stumbled upon a few lectures from one such gifted teacher, Professor Walter Lewin, who teaches Physics at MIT. His methods are truly worth emulating as the following video would testify.


With several universities across the world opening up their lecture halls to the world, by providing free access to recorded lectures, the enthusiastic student of today has an invaluable resource to tap from.

Here are a few such links from generous universities: