MathWorks’ cover photo
MathWorks

MathWorks

Software Development

Natick, MA 503,296 followers

Accelerating the Pace of Engineering and Science

About us

MathWorks is the leading developer of mathematical computing software. Engineers and scientists worldwide rely on its products to accelerate the pace of discovery, innovation, and development. MATLAB, the language of technical computing, is a programming environment for algorithm development, data analysis, visualization, and numeric computation. Simulink is a graphical environment for simulation and Model-Based Design for multidomain dynamic and embedded systems. MATLAB and Simulink are also fundamental teaching and research tools in the world's universities and learning institutions. Founded in 1984, MathWorks employs more than 6000 people in 16 countries, with headquarters in Natick, Massachusetts, USA.

Industry
Software Development
Company size
5,001-10,000 employees
Headquarters
Natick, MA
Type
Privately Held
Founded
1984

Locations

Employees at MathWorks

Updates

  • View organization page for MathWorks

    503,296 followers

    Need help troubleshooting a model, implementing design changes, or automating repetitive tasks? Simulink Copilot can help you move faster by providing design guidance, explaining error messages with suggested fixes, and executing Process Advisor tasks on your behalf. Spend less time navigating workflows and more time focused on engineering.

    • No alternative text description for this image
    • No alternative text description for this image
    • No alternative text description for this image
  • MathWorks reposted this

    It was enlightening interviewing Shihong Fan about his work doing thermal modeling of the Hyundai IONIQ 5. Shihong is a controls and simulation engineer at Hyundai America Technical Center. He built a digital twin of this electric vehicle with a powertrain and thermal system, validated against on-road vehicle data. His presentation at the MathWorks Automotive Conference in April 2026 covered this, and I got to sit down [virtually] with him to go more in depth. A few weeks ago, I posted a poll asking about the major challenges of modeling battery systems, and the responses and questions that arose from those conversations echoed lessons Shihong shares: Knowing what data matters, and what you can omit from a model. Plus, the importance of real-world validation. His work follows this logic: He didn't build a high-fidelity electrochemical battery model. He used a map-based one including open circuit voltage, battery temperature, and state of charge in, current out. No cell chemistry included. That isn't a shortcut. His question was about the thermal system, and a map-based model answers it. A higher-fidelity model would have demanded far more data and effort without making the answer better. He named this as the most common mistake he sees. People build the most detailed model they can rather than the model their question actually requires. As a battery scientist, I find that hard to do! We are trained to account for everything happening inside the cell. Deciding what to ignore or approximate is a different skill, and it feels more nebulous. Thank you, Shihong, for your generosity with sharing about your work, as well as advice you'd give to a student interested in this topic. And thank you to the MathWorks team for the introduction. For the modelers here: how do you decide what to leave out? Full interview linked in the comments. ⚡️ This video was sponsored by MathWorks. #MathWorksPartner #sponsored #batterytechnology #electricvehicles #simulation #energytransition #thermalmodeling

    • No alternative text description for this image
  • Which line wins the F1 track at Suzuka: shortest path vs smoothest path vs minimum time? We used Simulink to find an optimal lap around Suzuka and see just how fast an algorithm can go. The sound was generated from the simulated speed and RPM profile using signal processing 🔊 What track should we try next? Silverstone? Spa? Let us know in the comments below 🏁

  • What happens when a surgical robot needs to adapt mid-procedure? MinMaxMedical used Robotics System Toolbox, Simulink, Stateflow, and Embedded Coder to build surgical robots that reconfigure in real time, enabling changes without recompiling code. This approach supports procedures where surgeons swap tools, patients may shift, and the surgical team moves around the workspace. Read more in the comments below 👇

    • No alternative text description for this image
  • A small change but a completely different outcome. The double pendulum is a classic example of a chaotic system where even a slightest difference in initial conditions can lead to entirely different motion over time. This simulation of double pendulum trajectories shows how engineers visualize such nonlinear and chaotic systems in MATLAB.

  • Continuous integration (CI) is now a standard practice for engineering organizations developing embedded software. See an overview of how MATLAB, Simulink, and Model-Based Design fit into CI workflows to help teams automate build, test, and design validation 📽️

Affiliated pages

Similar pages

Browse jobs