Skip to Main content Open mobile menu Close mobile menu
Faculty Profile: Emily Mower Provost
  1. Faculty Profile: Emily Mower Provost

    Mower Provost talks about getting awards, doing industry research, understanding human behavior – and Star Wars.

  2. Research team takes on food insecurity in Detroit in the face of coronavirus limitations

    Researchers are working with the city on two key initiatives to address food availability for elderly and low-income populations.

  3. Building better coronavirus databases with automatic quality checks

    The team will build high-quality datasets to enable automatic quality checking and fraud detection of the new coronavirus data.

  4. Computer scientists employ AI to help address COVID-19 challenges

    Five multidisciplinary research teams are working on projects to assist with the coronavirus outbreak and to help find solutions to pressing problems.

  5. Emily Mower Provost named Toyota Faculty Scholar

    Her work uses machine learning to measure mood, emotion, and other aspects of human behavior for purposes of providing early or real-time interventions for people in managing their health.

  6. Undergraduate research on speeding up data centers earns ACM first prize

    The student’s project targets critical moments where the next instruction in a program is only available in a slower type of memory.

  7. Guidance on decontaminating face masks: U-M researchers contribute to national effort

    Collaborative website launched while U-M researchers continue advanced testing.

  8. Rackham Predoctoral Fellowship for design of robust, reliable and repairable software systems

    Subarno Banerjee uses program analysis to improve software systems’ safety and security.

  9. Predoctoral Fellowship for mathematically provable hardware design

    Goel designs algorithms that can automatically demonstrate the correctness of hardware systems.

  10. Researchers to use brain scans to understand gender bias in software development

    The team will use fMRI to identify some of the underlying processes that occur when a code reviewer weighs in on a piece of software and its author.