Category: Research & Academia

  • What Exactly Is Systems Ethology?

    What Exactly Is Systems Ethology?

    Introduction

    Systems Biology was first proposed in 1998.
    In recent years, I feel that the concept of systems biology has gradually gained acceptance.

    For an excellent and very accessible overview of systems biology, see Tetsuya J. Kobayashi’s article What exactly was systems biology?.

    I apologize if I am mistaken, but if systems biology had to be summed up in a single phrase, it would be “understanding life as a system.”

    My sense is that this introduced a new perspective across biology as a whole, and particularly into a wide range of fields such as molecular biology, developmental biology, and chronobiology.

    I myself work in neuroethology, or more broadly in the study of behavior.
    In recent years, neuroethology has also seen a broad wave of computational work that treats animals as systems, including neural simulations, connectome data analysis, and machine learning tools for analyzing animal behavior.

    Honestly, I do not know whether these developments in neuroethology were anticipated when systems biology was first proposed, or whether the current situation falls within the scope of Systems Ethology.

    Even so, it is a fact that this trend is advancing in neuroethology as well, and in that sense the proposal of systems biology feels remarkably prescient.

    The beginnings of Systems Ethology

    One question that naturally arises is this: if the current trends in behavioral research are already being absorbed into systems biology, why bother coining a separate term like Systems Ethology?

    That’s a fair point, and I do think so myself. But there is a background that led me to deliberately propose Systems Ethology anyway.

    This comes largely from a personal wish of mine: I wanted a place where researchers who study behavior could come together.

    Behavioral research today is pursued from a wide variety of perspectives. It spans the goal of neuroethology—understanding how neural circuits control behavior—as well as the ecological question of what function a behavior serves in its environment, the evolutionary question of how a behavior evolved, and the information-science question of what strategy and what kind of system underlie a behavior. Behavior is being studied across disciplinary boundaries.

    Within neuroethology itself, the range is broad as well, from circuit-level work using model organisms such as fruit flies and mice to studies of unique behavioral mechanisms in non-model organisms, and the field goes by different names such as neuroethology or behavioral neurobiology.

    Compounding this, the approaches used to study behavior have also diversified: genetic manipulation of neural activity, recording of neural activity by electrophysiology and calcium imaging, behavioral quantification with machine learning, mathematical descriptions of behavior and the search for behavioral strategies via reinforcement learning, and more classical, detailed observation of behavior. These approaches, too, cross disciplinary boundaries.

    As a result, my personal impression is that people attend whichever conference is closest to the scope of their own research, and somewhere along the way I found myself wondering: wait, where is my home conference?

    Behavioral research is being pursued from increasingly diverse perspectives, and as things stand it is quite possible to want to learn about a given research method yet have no way to do so.
    It struck me as a real missed opportunity, and I imagined that if there were a venue where all of these people gathered in one place, behavioral research might advance further. That was the intention behind creating such a venue.

    This is purely my own view, and I do not assume that everyone who has been collaborating with me shares the same motivation, nor that this rests on my own agenda alone. But the desire for a place where everyone could gather was something I heard repeatedly in conversations with various people at conferences.

    And so, with the aim of creating such a venue, I set out to propose Systems Ethology. In September 2024, at SWARM2024, I

    Toward Understanding the Principles of Animal Behaviors: Systems Ethology
    Hayato M Yamanouchi, Yusuke Notomi, Ryoya Tanaka, Shumpei Hisamoto, Shigeto Dobata

    submitted the following paper,

    Systems Ethology: Toward Elucidating the Design Principles of Animal Behavior

    and organized the following session.

    Below is the abstract of this organized session, quoted from the SWARM2024 website.

    The exploration of biology plays a crucial role in elucidating the behavioral mechanisms of individual agents and their collective behavior as swarms, owing to the complex and diverse nature of animal behavior. In particular, recent remarkable advances in information processing technology have helped to elucidate their complex behavioral patterns. Furthermore, these technological innovations also enable detailed investigations into non-model species where established research tools are lacking, thereby contributing to a broader understanding of various biological phenomena. 
     Currently, methods for animal behavior analysis are highly diversified, necessitating opportunities for integrated discussions where specialists with cutting-edge knowledge can share their techniques. We therefore propose a framework called “Systems Ethology” to elucidate the design principles of animal behavior. With the overarching goal of understanding animal behavior as a system, we aim to facilitate the exchange of information regarding various approaches to elucidating the mechanisms underlying each behavior. Such cross-disciplinary interactions among researchers can assist in performing more efficient and meaningful research.
     In this session, we aim to gather biological insights from various disciplines such as ecology, ethology, and neuroscience. Additionally, proposals for diverse behavioral analysis approaches, incorporating insights from information science and engineering, are also encouraged.

    For this session we invited researchers who study behavior from a variety of perspectives, and we were able to put together a very well-attended and lively organized session.

    At present, I am exploring whether we can realize a long-held wish of mine: launching a Systems Ethology study group.

    The ideas behind Systems Ethology

    Next, I would like to discuss what Systems Ethology actually is and how I define it as a discipline.

    Ethology has long centered on “Tinbergen’s four questions,” proposed by Niko Tinbergen.

    There are various ways of phrasing and framing them, but here I will take the four perspectives to be “survival value,” “ontogeny,” “evolution,” and “causation.”

    Niko Tinbergen argued that behavior must be examined from these four perspectives, and they remain an important guiding framework for ethology today, and by extension for neuroethology.

    However, each of these perspectives is currently pursued by research that focuses on it in isolation.

    To take clear examples, neuroethology focuses on how neurons control behavior from the standpoint of causation, ecology centers on survival value, and evolutionary biology centers on evolution.

    Answering each of these questions matters, but these perspectives have tended to exist in isolation, with whatever fell outside a given focus treated as a black box.

    In other words, I feel there has not yet been a discipline that focuses simultaneously on the causation and the survival value of behavior and satisfies both scopes. (At the level of individual studies, of course, work combining these views is becoming more common.)

    Truly understanding behavior requires all four perspectives—”survival value,” “ontogeny,” “evolution,” and “causation“—so why have they not been integrated? No one really knows, but one factor is surely that it is hard for researchers in these areas to understand one another.

    Put the other way around: why not make mutual understanding possible?
    Here, using the notion of a system as a common medium may offer a solution.

    That is, if systems can serve as a kind of shared language linking these perspectives, researchers should be able to incorporate one another’s ideas.

    Here I define this system as the behavioral system.

    There are many ways of conceptualizing behavior, and no single definition fits them all, but for simplicity I define behavior here as follows:

    The internally coordinated responses (actions or inactions) of whole living organisms (individuals or groups) to internal and/or external stimuli, excluding responses that are more easily understood as developmental changes

    Japanese translation: 生物全体(個体または群れ)が内部および/または外部からの刺激に対して内部的に調整した反応(行動または不行動)であり、発達上の変化としてより容易に理解できる反応は除く。
    ~Source: Levitis et al. (2009)~

    That is the definition adopted here.

    Recast in systems terms, the output of the system corresponds to behavior.
    The part of the system responsible for input and processing is therefore treated as the behavioral system.

    A behavioral system can be examined at multiple levels: the individual, the neuron, or the molecule.
    Given this diversity of levels, understanding behavior requires working across them and making sense of behavior at several levels at once.

    Because this is so complex, however, fully understanding a single system within one study becomes impossible.
    That is precisely why we need a venue for sharing diverse approaches and findings across disciplinary boundaries.

    Returning to “Tinbergen’s four questions,” Systems Ethology proposes the following four guiding principles for answering them.

    1) System structure: Static structure represented by nodes and edges. It includes discovering the behavior and the pathways by which the behavior is formed from inputs. It also elucidates the system’s components and how they are connected. 

    2) System dynamics: The dynamic structure is represented by nodes and edges. This perspective includes dynamics of the system (structure changes of the systems) and dynamics on the system (inner-statements transition of the nodes in the system). Dynamic system structure changes as a result of learning, development, and other parameters. 

    3) The control method: Methods for controlling the system’s states and behaviors. This method includes behavioral changes caused by intervention on the system’s nodes or edges. 

    4) The design method: Meaning and principles of the system. This method includes understanding the system’s adaptive and evolutionary significance. 

    ~Source: Yamanouchi et al. SWARM2024, (2024)~

    These principles specify which aspects of a system we set out to elucidate, and they are based on the four principles of systems biology.

    No one is certain what the future of Systems Ethology holds, and as things stand the details have yet to be unified.

    That is exactly why I want to build Systems Ethology into a forum for thinking about the future of the study of behavior.

    The Future of Systems Ethology

    At present, Systems Ethology has only been proposed as a new framework, and so far only in a conference paper.

    Eventually I hope to present it to a wider audience, for example as an opinion piece in a journal.

    My more immediate hope is to realize the original aim: a place where people who study behavior can come together.

    As a first step, I would like to organize a Systems Ethology research meeting here in Japan.

    Closing Note

    This article reflects my own personal views and is not meant to define Systems Ethology definitively.

    Please bear in mind that others may see things differently, and that I may well be mistaken on some points.

  • What Exactly Is YORU, a New Behavior Analysis Tool Powered by Object Detection?

    What Exactly Is YORU, a New Behavior Analysis Tool Powered by Object Detection?

    In November 2024, a preprint was posted on bioRxiv describing YORU, a behavior analysis tool that takes a different approach from existing behavior analysis tools.
    In this post, I’d like to explain what kind of tool it is.

    The YORU preprint

    The YORU documentation

    What is YORU?

    YORU is a deep learning-based tool for analyzing animal behavior.

    YORUのサイトより引用


    A number of deep learning-based tools, such as DeepLabCut and SLEAP, have already been released.
    These tools use deep learning to track body parts of animals and estimate their posture (here I’ll refer to them as tracking tools).

    By estimating posture, they reveal what posture an animal is in and use that for behavior analysis.

    YORU, by contrast, recognizes behavior using an object detection algorithm.
    In short, it does not track body parts; instead, it defines behavior directly from the appearance of the animal as it behaves.

    When people tell an apple from a mandarin orange, they rely on cues such as shape and color.
    Object detection excels at classifying objects, so it makes exactly this kind of appearance-based distinction.

    Applying this to animal behavior analysis means classifying animal behavior from its appearance.
    Within YORU, we call this a “behavior object.”

    Whereas tracking tools represent behavior as points and lines, YORU analyzes behavior by enclosing it in a bounding box.

    Advantages of defining behavior with object detection

    The advantages of object detection-based behavior analysis include:

    ・Errors are less likely as the number of individuals increases

    ・Less sensitive to the orientation of the animal

    ・Fast analysis speed

    ・Can capture behaviors that are hard to capture by tracking (such as a mouse crouching)

    and so on.

    It makes it easy to analyze the behavior of multiple individuals—a weak point of tracking tools—at a considerably lower computational cost.
    It can also easily analyze behaviors that are difficult to define from the positional information of body parts.

    Consider, for example, the act of opening and closing a hand.
    With a tracking tool, you would track the fingertips with a camera and define the hand as open or closed, but if the fingertips become hidden when the hand closes, tracking fails and the positional information can no longer be computed accurately.

    With object detection, however, the model looks at the overall shape of the open and closed hand, so it can capture the state accurately even when part of the hand is hidden.

    The same logic explains its robustness to larger numbers of individuals: with a tracking tool, as the number of individuals grows, you must assign each body part to the correct individual to capture each individual’s behavior accurately, whereas YORU analyzes only the shape of each individual and therefore requires no individual identification or assignment.

    Because analysis is fast, real-time analysis is possible, allowing you to control equipment when a particular behavior occurs and thus automate behavioral experiments.

    Disadvantages of defining behavior with object detection

    Of course, there are disadvantages as well:

    ・Cannot capture a sequence of behaviors

    ・Cannot identify individuals

    ・Cannot capture unknown behaviors

    ・Cannot capture behaviors that are hard to distinguish by appearance

    ・Provides no detailed information about the defined behavior

    These are precisely the strengths of tracking tools; rather than one approach being superior, the two complement each other’s advantages and disadvantages.

    Experimenters therefore need to choose the method appropriate to their situation.

    What makes YORU special?

    Having described the advantages and disadvantages of the object detection-based behavior analysis that underlies YORU, what exactly makes YORU special?

    Everything runs through a GUI

    YORU lets you perform behavior analysis without any programming.

    The same is true of tools like DeepLabCut and SLEAP, and it goes a long way toward making these analyses accessible to biologists.

    Design


    Unlike previous tools, YORU’s design doesn’t really feel like a research tool.

    Built-in real-time analysis

    Unusually for tools of this kind, YORU comes with a full GUI for real-time analysis.

    Building a real-time analysis system isn’t that difficult if you can program to some extent, but otherwise the barrier is quite high.

    With YORU, however, real-time analysis and even external triggering can all be done without any programming.

    Adaptable to a wide range of experimental setups

    The biggest hurdle in real-time analysis is figuring out how to combine the code that drives your own experimental apparatus with the analysis itself.

    YORU adopts a plugin system, letting you choose the program that controls your external device.

    In other words, you simply select the plugin that matches your own system.

    You can also write your own plugins: by wrapping the control program for your own apparatus in a plugin, you can easily link it to YORU’s real-time analysis.

    This makes for a remarkably easy-to-use system that no other tool offers.

    Closing remarks

    YORU has only just been released, and there are still rough edges in usability as well as gaps in the documentation.

    That said, as these are addressed over time, I am very much looking forward to seeing how it comes to be used.

  • Improving Your JSPS Research Fellowship (DC1, DC2) Application [Advice from a Successful FY2024 DC Applicant]

    The results for the JSPS Research Fellowships (DC1 and DC2) were announced at 14:00 on Wednesday, September 27, 2023.

    I was one of the students who applied, and I am happy to report that I was selected.
    Word going around on X (formerly Twitter) was that this year’s acceptance rate was lower than usual.

    Apparently the initial acceptance rate was around 14%, or about 17% including the second round of selections.

    I had heard that the rate is usually close to 20%, so when I saw the numbers my first thought was, “Seriously?”

    Through this application cycle I read a number of other people’s JSPS applications and wrote my own, so here I’d like to summarize the things worth keeping in mind to improve your chances even a little.

    I think this applies not only to JSPS applications but to grant proposals, job application essays, and any writing meant to be read by others, so I hope you’ll read on.

    What matters is what lies beyond the application

    First, the key to writing an application is conveying what you want to say within a limited amount of space.

    An application explains your research and argues for its importance: this is who I am, these are the things I can do, and therefore I can achieve this goal. So please fund me.

    In other words, you need to keep sight of what your writing is ultimately for.

    While writing, it’s easy to get caught up in immediate concerns—producing elegant prose, writing something your advisor won’t complain about—and lose sight of what an application fundamentally is.

    It isn’t self-satisfaction: there are people who read and evaluate it, and score it accordingly.
    That is what clearly distinguishes it from an exam, and it’s precisely why there is no single correct answer.

    My impression is that many people who have spent their lives taking tests with right answers suddenly hit a wall when faced with an application, unsure what to write or what counts as correct.

    Even while writing, you need to keep in mind who the application is written for.
    For that reason, writing a few applications to other funding bodies before the JSPS one and having people read them makes a striking difference in how readable your writing becomes.

    The keywords are “logic” and “specificity”

    Logic

    The two things I paid the most attention to when writing my JSPS application were logic and specificity.

    Logic means that your argument is consistent and that each topic connects to the next.
    You need to think about these connections at multiple scales: between sentences, between paragraphs, and across the application as a whole.

    To put it in more practical terms,
    logical writing is writing in which the reader finds what they want to know, in the order they want to know it.
    When this is done well, the content flows effortlessly into the reader’s mind.

    The point is to think from the reader’s perspective.
    No matter how logical you think your argument is, that logic may not land with your reader.

    Guides to writing JSPS applications often recommend inserting phrases like “in other words” or “the details are described below,” but the essential purpose of these is to give the reader signposts that make the connections in your text easy to follow.

    Opinions differ widely on whether such phrases are necessary, but one thing I can say is this: if leaving them out makes your structure unclear, put them in, even at the cost of precious character count.

    Specificity

    Specificity means, quite literally, providing exactly as much information as the reader needs.

    You’ve probably heard people say, about applications or research talks,
    “My research requires so much background that I just can’t keep it short.”

    I’ve thought the same thing myself many times before a ten-minute conference talk—there’s no way this fits in ten minutes.

    But even in a talk you’ve confidently packed with content, it often turns out that there was a lot of information the audience didn’t need and almost none of what they actually wanted to know.

    In other words, you haven’t decided what to keep and what to cut.

    To make those decisions, first determine the single thing you most want to convey.
    Then keep whatever is needed to explain that core point and discard whatever isn’t. That is how you achieve specificity.

    Applications like the JSPS one require you to describe your research and yourself in a genuinely tiny amount of text.
    People often say you should divide the JSPS funding amount by the character count of the application to calculate the value of a single sentence.

    I think the point of that exercise is to get you asking: is this sentence really worth that much money? If not, rewrite it.

    Background explanation is a third-person account, and while it’s necessary to make your own work stand out, the text itself describes other people’s research and is therefore low in value.
    Whether you keep it to a minimum or find some other value in it is up to you.

    Through this kind of revision, the content becomes refined.

    So far I’ve talked about specificity while only discussing cutting material, but the real point is to condense the content and raise the specificity of each sentence to just the right level—no more, no less.

    Throughout the process I kept logic and specificity constantly in mind, periodically stopping to reread and rewrite.

    Show it to others early

    One of the most important points is to have other people read your application early.

    Some people wait until it’s finished and they’re satisfied with it, then show it to someone a week before the deadline—but honestly, that’s a waste.

    Showing your draft to others is about confirming that you’re heading in the right direction and getting feedback, not just getting corrections.

    As people often say, the quality of a JSPS application depends on how many people have read it: you gain new insights, and sometimes your fundamental way of thinking changes.

    Ideally, aim to have someone other than your supervisor read it at least three weeks before the deadline.

    Don’t stare at your application nonstop

    When application season comes around, I often saw people put their experiments on hold to focus entirely on their proposals.
    It’s true that you need to invest a fair amount of time, and since you revise it over and over, it ends up eating up an enormous number of hours.

    That said, once you’ve written a decent draft, there’s no point in endlessly rereading it and burning time for nothing.
    In fact, you should leave the draft alone for a while before you go back and revise it.

    An application is an important document with your career riding on it.
    But it doesn’t get better in proportion to the time you pour into it. The real challenge is producing the best possible document as efficiently as you can.

    Rather than being glued to your computer, keep your experiments moving along, or even take a break to clear your head. You’ll write with a much cooler eye.

    I didn’t just write at the university; I would take my laptop to cafes and other places, changing the setting often as I wrote.

    Closing thoughts

    This year’s provisional acceptance rate is said to be around 14% at the first round of screening.
    Put another way, 86% of applicants were not selected for a JSPS fellowship.

    Since the vast majority of applicants aren’t selected, there’s no need to be more discouraged than necessary about not making the cut.

    At the same time, those who were selected got their place at the expense of many other people’s dreams and livelihoods.
    Of course, the selection reflects a real evaluation of your research as it stands, but beyond that, it carries the responsibility to work twice as hard from here on.

    I want to keep this in mind myself and keep pushing forward with my research.

  • How to Search for Papers in the Life Sciences [A Graduate Student’s Guide]

    Once you join a lab, chances are you’ll be asked to present a paper at a journal club sooner or later.

    The format of journal clubs varies from lab to lab, but in many cases you’re expected to find a paper yourself, read it yourself, and present it.
    Even outside of journal clubs, doing research means getting to know the prior literature, so you’ll be searching for papers a lot.

    Here I’d like to introduce some tools that come in handy for that.

    Google Scholar

    The first one is Google Scholar.

    It’s so well known that there’s probably not a single researcher who hasn’t heard of it.

    Basically you search just as you would on Google, but everything that comes up is literature—papers, books, and so on.

    Since it’s the tool you reach for when you just want a rough look at the literature, I suspect it’s the most widely used search tool of all.
    I use Google Scholar too: I throw in some rough keywords and use the results as a first screening pass.

    The flip side of being good for broad searches is that there aren’t many options for narrowing things down.

    Still, the main filters are there—publication date range, relevance, and so on—so it covers most needs.
    And when you want to restrict the search to a particular journal, you can just put the journal name in the keywords; it really works the same way as a Google search.

    PubMed

    The next one is PubMed.

    PubMed is probably the best-known literature search tool in the life sciences.

    What’s impressive about it is the sheer number of ways you can search.

    Author, journal, editor—you can search by just about any field you can think of.

    It’s an extremely useful tool when you already know the journal, the author, or whatever other details you want to search by.

    Web of Science

    The last one I’ll introduce is Web of Science.

    It’s a paid service in principle, but if you’re affiliated with a university you can generally access it through the campus wifi, so students can use it for free.

    Where this tool really shines is that it lets you look up what’s known as the impact factor (IF).

    The IF is a kind of journal ranking—a number that indicates how strong a given journal is.

    You can find impact factors by googling “journal name IF” as well, but the numbers you get are often not the official ones.

    Web of Science is the source that officially issues IFs, so you can find the correct value there.

    I use Web of Science as my IF lookup tool when deciding which journal to submit to, or when I want to gauge how impressive one of my advisor’s papers is.

    Closing thoughts

    Google Scholar is what I use most of the time, but knowing about the other tools comes in handy when you need to look something up in a specific way.


  • Writing My First Paper: A Personal Account

    Writing papers is one of the most important things a researcher does—it is how research gets reported to the world.

    Writing a paper takes far more time than you would imagine; it is unglamorous work that demands real persistence.
    That is exactly why the first paper you write yourself leaves such a strong impression.

    I myself had the experience of writing a paper from scratch in my first year of the master’s program, under my supervisor’s guidance.
    It varies by field, but in biology it is quite rare for a master’s student to write the text of a paper themselves.
    After all, most students never publish a paper at all at that stage.

    I am grateful to have been given such a rare opportunity, and I want to write down that experience here so I don’t forget how it felt.

    The Time Scale of Writing a Paper

    In biology, it generally takes about a year from deciding to write a paper to actually seeing it published.
    It depends on the format and scale of the paper, but from my own experience, the big difference from fields like chemistry and engineering is the sheer volume of content a paper must contain.

    Unlike reporting the discovery of a compound or a protein, neuroethology—the field I work in—requires demonstrating something like “this neuron contributes to this behavior in this way,” so it is not at all unusual for a paper to have more than five figures (each containing multiple graphs).

    For that reason, gathering all that data, writing the paper, and getting it published is said to take longer than in other fields.

    Below is a rough outline of the steps leading up to submission.

    • Write the manuscript (1 month to over a year). All sorts of things can happen while writing, so it often doesn’t go smoothly.
    • Have others read the manuscript (1–3 months). This step happens sometimes and not others: you ask a colleague who isn’t involved in the project to read it and see whether the content makes sense.
    • English proofreading (about 1 month)
    • Submission!!! (2 days to over 4 months). A rejection can come back in two days, whereas if it goes out for review you may hear nothing for months.
    • Revision (1–6 months). You receive reviewer comments, add missing data, revise the content, and resubmit to the journal. Revisions come as major or minor, and you are often asked to make changes that alter the overall structure of the paper.
    • Acceptance!!! Once you have handled the revisions and the journal gives the green light, the paper is accepted. Only at this point does the work finally count as an achievement.
    • Formatting for publication (1 week to 1 month). This is the final round of work, getting the paper formatted for posting online or printing in the journal.
    • Publication, writing a press release, and so on. After acceptance, all kinds of things happen in quick succession and life gets busy.

    You don’t just write a paper and press a button to publish it. A paper is evaluated by many people, examined by third parties for logical soundness, and only then accepted and released to the world.

    My Own Experience

    First of all, the published paper is here.

    After giving my undergraduate thesis presentation in my fourth year, my supervisor suggested at the end of February that we write a paper.

    I started writing in March, submitted to the journal iScience in December, and the paper was formally accepted in April.
    It was published almost exactly a year after we decided to write it—an unusually smooth submission process.

    That March, I was thrilled to be told we would write a paper, and I was determined to finish it as fast as I could.
    But even though I was told to go write it, I had no idea how, so I looked up published papers and imitated them as best I could while writing up my own results.

    My English was weak, which didn’t help, and I kept getting sent back with “I don’t understand this—please fix it.”
    Rather than being handed a corrected version, I was told which parts were unclear and asked to rewrite them myself. At the time it was genuinely painful and I kept thinking, just teach me! But looking back, having to research and think through how to write on my own is exactly what serves me today.

    What my supervisor told me was this: if you intend to become a researcher, you will have many chances to write papers in the future, and if I write it for you, you’ll never be able to write one yourself—so write it yourself.

    Still, hard is hard. Around that summer I couldn’t eat, and my stomach was completely worn down.
    (Personally I found it puzzling—why would just writing text be so stressful?—but apparently my body felt it.)

    Why was it so tough? Because while you’re writing a paper, you basically stop doing experiments and focus entirely on writing.
    Meanwhile, conferences, classes, and personal life all keep coming at you.

    The paper isn’t going well and the experiments aren’t moving either, so you start to feel like you’re accomplishing nothing—especially when everyone around you is making progress.
    At the lab’s biannual progress meetings, I was the only one with nothing to report, which was nerve-wracking.

    And the final blow was having no one to talk to about it.
    Writing a paper as a first-year master’s student is unusual, and from the outside it looks enviable.
    Because of that, there was no one in the lab I could discuss the paper with, and people outside research just think “it’s only writing.” I felt misunderstood, as if I had to do it all alone.

    Around September, when things got especially hard, I turned to a programming-based project as a distraction and wrote a short paper for an international conference.
    That turned out to be a great change of pace: it eased my anxiety about research not moving forward, and because it was a short paper it was easier to write. I could feel myself improving, and the success gave me real confidence.

    With all that, I had finished a rough draft of the manuscript by around October.
    I thought we were ready to submit, but then my advisor said,
    “Shall we have some other faculty members read it too?”
    “Whaaat?!?! We’re not done yet??”
    — I still remember thinking exactly that.

    The faculty members who read it gave me very sharp advice, and the paper improved enormously.
    I learned firsthand that having other people read your manuscript is a crucial part of the process, and that this applies not only to papers but to research in general.

    In December, I made the initial submission to iScience.

    iScience is not an extremely high-ranking journal, but it is by no means a low-ranking one either — it is a solid journal, good enough that doctoral work gets published there.

    For me, choosing iScience was a stretch goal; I figured the odds were 7:3 against acceptance.
    So I was waiting for the rejection notice, but nothing came, and about a week later I was told the manuscript had been sent out for review. I was thrilled and surprised at the same time.
    My advisor seemed surprised too.

    After responding to the reviewers’ comments, I resubmitted, and following some minor revisions the paper was formally accepted.
    After submission, things went fairly smoothly and simply followed the flow.

    Personally, the initial submission was the most exciting moment and the one that gave me the greatest sense of accomplishment.

    I realized how naive my thinking about the process of writing a paper had been, and I also came to feel that writing a paper is an extremely valuable experience for the research that follows.

    People say that if you want to become a researcher, the first thing you should do is write a paper — and now I understand why. It’s not about the results themselves. The process of writing taught me the importance of building the logic of my own research, thinking ahead, and moving forward with the perspective of someone who is going to write a paper.

    It was an experience from which I learned a great deal, and I think it was a wonderful way to begin my life as a researcher.

    I’m also hoping to post something more practical later on about how I actually went about writing the paper, so please look forward to it.

  • Why Are Fruit Flies Used in Research?

    What is a model organism?

    When you think of animals used in research, mice and guinea pigs probably come to mind.
    The usual picture is that a drug’s efficacy or structure is tested in these animals first, and only then does the work move on to clinical trials.

    That picture isn’t wrong, but there are many other organisms used in research.
    Medaka, zebrafish, nematodes, E. coli, yeast, Drosophila melanogaster, Xenopus laevis, Arabidopsis thaliana, silkworms, and so on…
    These organisms are called model organisms, and a huge variety of research is carried out with them.

    A model organism is one that the research community studies exhaustively, so that by coming to know that single organism inside and out, we can understand features and principles shared with other organisms.

    What is Drosophila melanogaster?

    Some of the organisms on that list may come as a surprise, but Drosophila melanogaster is probably the most unexpected of all.
    Wait, a fly? The kind that shows up in your kitchen?

    Exactly!
    The scientific name of the fruit fly is Drosophila melanogaster.
    It has been central to research recognized by several Nobel Prizes and is used widely across biology.

    Fly researchers gather at meetings such as the Japanese Drosophila Research Conference (JDRC), and there are also fly conferences in the Americas, Europe, and Asia. On top of that, meetings focused specifically on the fly nervous system, such as NeuroFly and Neurobiology of Drosophila, show just how global this research community is.

    The advantages of working with flies include:
    ・They have a central nervous system
    ・A rich toolkit of genetic techniques
    ・The existence of balancer chromosomes
    ・A short generation time
    ・They are easy to rear
    ・They show stereotyped behavioral patterns

    and many more. Because researchers around the world have converged on Drosophila melanogaster, enormous databases have been built, and in the brain nearly the entire network of connections between neurons is now known.

    At this point you might wonder whether there is anything left to study. It’s true that we know the wiring, but in many cases we still don’t know what functions that wiring serves.

    Beyond that, in areas such as immunity and developmental patterning, there remain a great many open questions, including which molecules are involved.

    You might ask what all this effort is for. The answer is that it is precisely by going this far that we can uncover principles universal to living things!
    That is what a model organism is for.

    And these mechanisms can be applied to drug development, safe genetic engineering, and more.

    A brief history of Drosophila research

    The story goes that it all began in 1901, when a well-known figure (Charles W. Woodworth) suggested the fly to another researcher (William Ernest Castle) as material for genetics.
    The reason: it is easy to rear in large numbers.

    Thomas Hunt Morgan later became famous for his genetic studies using Drosophila. His discovery of mutants and his demonstration that genes reside on chromosomes had an enormous impact on genetics.

    Another landmark was the discovery of homeotic genes, which have a profound influence on development.
    Fly work also played a major role in the discovery of clock genes.

    Being rearable in large numbers, being an insect, and allowing mutants to be generated easily are advantages no other organism offered, which is exactly why the fly was such an outstanding material for genetics research.

    Today, applications of the GAL4/UAS system, balancer chromosomes, and a wide array of other tools have all been developed and refined.

    A few extra notes

    Labs that study Drosophila rear the flies in cylindrical containers called vials, about 3 cm in diameter and 10 cm tall.
    Most labs also have a dedicated rearing room where large numbers of these vials are kept.

    You might imagine flies to be dirty, but their food is a jelly-like medium containing yeast, not raw meat, so bacteria don’t proliferate.

    Flies are fairly hardy and relatively easy to keep.
    That is surely part of why they have been studied for so long.

    Dissections are done by hand with forceps under a stereomicroscope.
    You are dissecting a fly roughly 2.5 mm long with forceps.

    Behavioral experiments are possible too, and researchers have devised all sorts of ingenious apparatus for them.

    Another wonderful thing about flies is that stock centers exist in several places around the world. They maintain large numbers of fly lines carrying specific genetic manipulations made in labs everywhere, and you can order whatever line you need from them.

    That means you don’t have to build the line yourself and can start experiments right away.
    (Doing the genetic manipulation yourself would take at least three months.)
    Truly standing on the shoulders of giants.

    Biologists often say that once you start working on Drosophila, you can’t go back to any other organism, which says a great deal about how well suited the fly is to research.

  • How to Write a JST Application [Internal University Application Form]: A Memorandum

    How to Write a JST Application [Internal University Application Form]: A Memorandum

    Introduction

    One task that follows researchers everywhere is the grant application. For anyone aiming at a research career, applications are unavoidable—and yet they are often overlooked.

    I suspect many people struggle with them. I certainly do. I went into the School of Science precisely because I was bad at Japanese language arts, and now, of all things, the very career I am pursuing confronts me with a language problem….

    In recent years, support for doctoral students has become substantial. Beyond the JSPS Research Fellowship (DC), there are university-internal grants funded by JST programs, WISE Programs (Doctoral Program for World-leading Innovative & Smart Education), JASSO, and others—existing schemes have been strengthened and new ones keep appearing. If you can secure this kind of support, you can cover nearly all of your living expenses during the doctoral program and receive tuition assistance as well.

    I myself have faced and submitted several university-internal applications.

    How they differ from the JSPS application

    Basically, university-internal applications tend to closely resemble the JSPS one. The reason is simple: passing the JSPS review is the ultimate goal. Also, writing in a different format would only add to the students’ burden, so most programs match the JSPS format and build in a process that lets you refine the same document.

    Selection is based mainly on the research content and on the applicant’s ability and future promise. What matters is presenting these clearly so that they get through to the reader. There is absolutely no need to write elegant, literary prose.

    Although the JSPS and university-internal applications have much in common, there are differences. The kind of person each is looking for is somewhat different.

    The application materials state what kind of candidate the program is seeking, so you need to write in a way that matches that.

    The biggest difference from the JSPS application, though, is who reads it. The JSPS application is assigned to a field, and reviewers with some degree of relevant expertise read it. With university-internal applications, however, the readers are basically people from within the university, so even within the life sciences, someone working on plants may end up reading your animal research proposal. On top of that, each reviewer often has to handle more applications than in the JSPS review.

    In other words, keep the content more general so that its appeal comes across even to someone in a different field—and make sure the content and its appeal register at a glance.

    As a rule, assume the reviewers have no desire to read your application, and write something that catches their interest and makes them read it. Use figures and highlighting appropriately so that the important points are obvious at a glance.

    Tips for writing

    The keys to a good application are logical flow and specificity.

    Logical flow means giving readers the information they want, at the moment they want it, in the order they want it. In other words, you create logical flow by connecting each sentence to the next and writing what the reader has vaguely started to anticipate.

    For example:
    “During my undergraduate years I belonged to several student organizations and took part in running each of them. Through this, I developed leadership and the ability to work smoothly with others.”

    Running an organization → leadership and the ability to work smoothly with others

    When sentences connect like this, with no jarring gaps between them, we can say the writing has logical flow.

    Next, specificity. Adding specificity to the example above:
    “During my undergraduate years I belonged to several student organizations that planned events and social gatherings for students, and in each one I took the lead in running those events. Through this, I developed leadership and the ability to work smoothly with others.”

    Adding specifics strengthens the logic of how you were involved in the organization and what exactly you did, and therefore what abilities you gained from it.

    The catch, however, is the character limit. Limits are set quite tightly, and the moment you try to describe something concretely you run out of room.

    That is exactly why, in the rush to cram in content, these two elements tend to get neglected.

    Summarize the content concisely and clearly—yet also be logical and specific. This tension is a central problem when writing an application.

    The key to striking this balance is asking what kind of person the program wants to select. Most applications specify which items they want you to address and what sort of content they expect.

    The reviewer must be able to see clearly where in your text each of those items is addressed. Don’t leave it to be inferred or read between the lines—make it unmistakable.

    If you keep this front and center, it becomes clear which sentences you need and which you can cut.

    A writing strategy

    When writing an application, start by listing the points you want to make as bullet points, then write out the text without worrying about length. Then fill in the content with logical flow and specificity in mind.

    At this stage you will usually be well over the limit, so the next job is trimming. Rephrase and reword until you are only slightly over the character count.

    At that point, have someone else look at your application. This step is extremely important. Getting feedback early and often keeps you from drifting far off course and helps you learn your own way of writing applications.

    Showing your work to others is daunting, and pride often gets in the way, but take the plunge, set your pride aside, and show it. In my experience, the more academically accomplished someone is, the more they tend to keep working alone and delay showing it to anyone.

    Once you get feedback, reread your own draft with it in mind, identify what needed improvement, and rewrite.

    Having others read your draft is the single most important step. Nobody writes a perfect application on the first try, and criticism is not a rejection of you—take it as advice that you are capable of more.

    Summary

    An application exists to be read by someone else. Never fall into the complacency of assuming the reviewers will read it, or of thinking it outrageous that they might not.

    If people won’t read it, then write something that makes them want to read.
    No matter how good the content is, it means nothing unless people actually read it and the message gets across.

    A common piece of advice is to take the total amount of funding a grant application could bring in, divide it by the number of lines in the proposal, and work out how much each single line is worth.

    This gives you a clear yardstick for judging whether what you have written is worth that much to the reader.
    If you don’t think a sentence carries that much value, it may need to be rewritten.

    Further reading

  • Side Effects of COVID-19 Vaccines: A Science Student’s Careful Review of the Evidence — Based on Japan’s Ministry of Health, Labour and Welfare Website

    Side Effects of COVID-19 Vaccines: A Science Student’s Careful Review of the Evidence — Based on Japan’s Ministry of Health, Labour and Welfare Website

    With misinformation circulating about the side effects of COVID-19 vaccines, and media coverage that often stokes anxiety, it can be hard to know which information to trust.

    The most reliable source of COVID-19 vaccine information in Japan is, I believe, the content posted on the Ministry of Health, Labour and Welfare (MHLW) website.
    However, materials such as the health status surveys are quite difficult to follow, so few people are likely to read them.

    The MHLW’s Q&A on COVID-19 vaccines is written very clearly, so I will quote from it here.

    Vaccine basics

    First, two COVID-19 vaccines are currently being administered in Japan: the Pfizer vaccine and the Moderna vaccine.

    Both are mRNA vaccines that work through essentially the same mechanism, and their efficacy in preventing symptomatic COVID-19 is nearly identical: about 95% for Pfizer and about 94% for Moderna.

    Both are given as intramuscular injections.
    Intramuscular injection may look painful because the needle goes in fairly deep, but in practice most people I know said it hurt about the same as a subcutaneous injection such as a flu shot, or even less.

    There are some other minor differences, but fundamentally both offer comparable efficacy, and current data indicate that neither is superior to the other.

    Main side effects of the vaccines

    Side effects that may occur with both the Pfizer and Moderna vaccines include fever, headache, joint and muscle pain, pain at the injection site, fatigue, and chills.
    Injection-site pain more often appears the day after vaccination than immediately afterward, and side effects can be somewhat delayed, so take good care of yourself on the day after your shot.

    In rare cases, serious reactions such as shock or anaphylaxis (a severe allergic reaction) may occur.
    Very rarely, mild myocarditis and pericarditis have been reported after vaccination.

    If a health problem arises from side effects after vaccination, you may be able to use the Relief System for Injury to Health with Vaccination; contact your local municipality for details.

    A common side effect of the Moderna vaccine is what is popularly known as “Moderna arm.”
    This refers to pain and swelling at the injection site appearing about a week after vaccination.

    In general, side effects subside within a day to a few days.

    Side effects are also said to be more likely after the second dose than after the first.

    Health survey reported by the MHLW (as of July 7)

    The link to the health survey is here

    Pfizer vaccine

    Please see the link for the detailed data.
    Here I will give a rough summary of what the data show.

    As for local reactions at the injection site, the proportion of people with redness or swelling did not differ greatly between the first and second doses, at roughly 10–12%.

    However, about 90% of people reported pain at the injection site after both the first and second doses, so nearly everyone experiences some pain.
    The proportion reporting a sensation of heat at the injection site was about 10% after the first dose and about 16% after the second.

    These symptoms peak on the day after vaccination, and the proportion affected roughly halves on day 3 and again on day 4.

    Regarding systemic reactions, fever above 37.5°C occurred in under 10% of people after the first dose, compared with about 40% after the second.
    Fever was more common in younger people (about 50% among those in their 20s), and roughly 5 percentage points more common in women than in men.

    Fever peaks on day 2, but by day 3 the proportion affected drops to about one-quarter or less, and by day 4 it has resolved in nearly everyone—so it clears up quickly for most people.

    General fatigue occurred in about 25% of people after the first dose and about 70% after the second, while headache occurred in about 20% after the first dose and about 55% after the second. As with fever, the trend is that younger people are more likely to experience these symptoms, and women more so than men.

    The Moderna vaccine

    The rates of side effects for the Moderna vaccine were largely the same as for Pfizer, as were the symptoms themselves.

    As for “Moderna arm,” which is characteristic of the Moderna vaccine, it occurs in about 5% of people after the first dose.
    Five percent may sound rare, but it works out to one in twenty people, so most of us probably know one or two people who have experienced it.

    Summary

    I have covered a lot of ground on the rates of side effects, so let me summarize here.

    • Almost everyone experiences pain at the injection site
    • Local symptoms such as pain, redness, and swelling at the injection site occur at roughly the same rate after the first and second doses
    • Systemic reactions occur more often after the second dose than the first
    • Fever and fatigue can occur in many people
    • Side effects are more common in younger people, and more common in women than in men
    • Side effects peak the day after vaccination, and for most people symptoms subside within one to three days

    A great deal of media coverage is framed in ways that stoke anxiety.
    By looking at the actual data with your own eyes, you can get a clearer sense of what the concerns about COVID-19 vaccines really amount to.

    I hope this article is helpful to you.

  • From a Talk People Sit Through to a Talk People Listen To!

    From a Talk People Sit Through to a Talk People Listen To!

    One thing you can’t avoid in university life is giving presentations.
    Not only in classes, but also in the lab, in seminars, and in club activities, there are many occasions when you have to stand up in front of people and present.

    From elementary school through high school, you mostly just sit and listen in class, and there are few chances to give a long presentation. Yet
    the moment you enter university, you are suddenly put in front of an audience again and again.

    That said, it’s also true that many people around you dislike presenting or feel they’re bad at it,
    and unfortunately there are plenty of presentations that leave the audience thinking “that was poorly done” or “that was boring.”

    So I’m going to keep posting the presentation know-how I’ve picked up during my university years.

    This time, the topic is the mindset behind giving a presentation.

    A typical trait of poor presenters is that they give a talk that the audience is made to sit through.
    For example:
    ・spending too long on a single slide
    ・leaving dead air during the talk
    ・using too many slides
    ・failing to make the connections between points clear
    and so on.

    As a rule, you should assume that the people listening have almost no motivation to listen to your talk.
    Nobody starts out interested in your presentation.

    The audience feels the way you did in middle school, sitting in the gym listening to a 30-minute speech from the principal.
    Few of us listened to those speeches with genuine curiosity every time.

    If you give a self-centered talk to an audience with no desire to listen, you may come away satisfied, but the audience will be bored.

    Some people, seeing that the audience looks unengaged, is checking their phones, or has dozed off, will fall into self-loathing and conclude that their presentation is hopeless.

    To avoid that, you need to give a talk that people actually want to listen to.

    Presentation technique matters, but what matters most for a talk people want to hear is how you yourself think about presenting.
    Once that mindset changes, your talk will naturally become audience-oriented.

    The key points for a talk people want to hear are:
    ・be clear about the single most important message of your talk
    ・keep the talk simple and minimal
    ・eliminate anything that even you find confusing or distracting
    That’s it.

    Suppose your talk contains ten points.
    If you deliver all ten with the same emphasis, the audience will retain nothing at all; but if you present just one as clearly important, the other nine may amount to zero while that one point will at least stick in their minds.

    Narrow down what you want to say, keep it short and to the point, and make it easy to follow

    Aim for a talk that people listen to naturally, rather than one that forces your views on them.
    If you keep that in mind, your presentations will improve on their own.

    If you know someone who is a good presenter, ask them all sorts of questions.
    If you don’t, watch the talks that are so often held up as models—Steve Jobs, President Obama, and the like.
    They can reach a huge number of people with words alone.
    Their technique is impressive, but above all, they are perfectly clear about what they want to convey.