The MathWorks, Inc. (branded as simply MathWorks) is an American privately held corporation that specializes in mathematical computing software. Its major products include MATLAB and Simulink. As of April 2014, it employed over 3,000 people worldwide with 70% located at the company's headquarters in Natick, Massachusetts, United States.

Wikipedia
The MathWorks
The MathWorks
YouTube Video
  • GPU Coder™ generates optimized CUDA® code from MATLAB® code for deep learning, embedded vision, and autonomous systems. The generated code calls optimized NVIDIA CUDA libraries and can be integrated into your project as source code, static libraries, or dynamic libraries. It can also be used for prototyping on GPUs such as the NVIDIA Tesla® and NVIDIA Tegra®. This lane detection example shows ho...

The MathWorks
The MathWorks
Page Metadata Update

New page title detected.

  • New: Coverage. It's all good. Health care coverage is good. Cell phone coverage is good. Even cloud coverage can provide a nice break from the intensity of the sun's rays sometimes. It should come then as no surprise that good code coverage also gives us that nice warm fuzzy feeling, like a nice warm drink on a cold day....and often for good reason. Code coverage can help us see areas of our code that are not exercised in some form or another, and can be very helpful, in a good-friend-that-can-be-brutally-honest-with-you sort of way. It can point out where we really need to add more testing. Once we react to our good friend's advice and add better testing, we are all the better.A quick aside to add some caution is in order. We (all) should remember that code coverage does not as much show what code is covered as which code is not covered. This is because seeing that a piece of code is covered says nothing about how it was covered, whether it was covered by a test specifically targeting
  • Old: Ah the joys of a new release! R2017b is now out and packed with some great new features. So here I go, heading out to an excitement fueled upgrade-mania when lo and behold, my glee is rudely interrupted when I see my code is broken in the new release.What a drain on an otherwise pleasant experience! It turns out that the error is due to some of my more "creative" and "clever" coding practices that have helped me get my job done in the past, and when I dig in I see that I've been warned about this change coming for years. The problem is I never seem to have the time to comb the release notes as much as I'd like to, and even if I did realizing that my code I wrote 5 years ago has some of the problems mentioned is a tall order.To compound that, even though I'd like to upgrade, when I make the needed adjustments to do so I worry about breaking the users of my code who haven't upgraded yet.What in the world to do?Let's use some continuous integration! Last I checked we were still in ch
The MathWorks
The MathWorks
YouTube Video
The MathWorks
The MathWorks
YouTube Video
  • Image processing and computer vision applications have emerged as some of the key domains for embedded applications. Image sensors in your phones, PDAs, cameras, and smart cameras are examples of this, and we have more in store with the development of advanced driver assistance systems for automotive applications. More and more sophisticated algorithms for new functionality and better performanc...

The MathWorks
The MathWorks
Page Metadata Update

New page title detected.

  • New: Coverage. It's all good. Health care coverage is good. Cell phone coverage is good. Even cloud coverage can provide a nice break from the intensity of the sun's rays sometimes. It should come then as no surprise that good code coverage also gives us that nice warm fuzzy feeling, like a nice warm drink on a cold day....and often for good reason. Code coverage can help us see areas of our code that are not exercised in some form or another, and can be very helpful, in a good-friend-that-can-be-brutally-honest-with-you sort of way. It can point out where we really need to add more testing. Once we react to our good friend's advice and add better testing, we are all the better.A quick aside to add some caution is in order. We (all) should remember that code coverage does not as much show what code is covered as which code is not covered. This is because seeing that a piece of code is covered says nothing about how it was covered, whether it was covered by a test specifically targeting
  • Old: Ah the joys of a new release! R2017b is now out and packed with some great new features. So here I go, heading out to an excitement fueled upgrade-mania when lo and behold, my glee is rudely interrupted when I see my code is broken in the new release.What a drain on an otherwise pleasant experience! It turns out that the error is due to some of my more "creative" and "clever" coding practices that have helped me get my job done in the past, and when I dig in I see that I've been warned about this change coming for years. The problem is I never seem to have the time to comb the release notes as much as I'd like to, and even if I did realizing that my code I wrote 5 years ago has some of the problems mentioned is a tall order.To compound that, even though I'd like to upgrade, when I make the needed adjustments to do so I worry about breaking the users of my code who haven't upgraded yet.What in the world to do?Let's use some continuous integration! Last I checked we were still in ch
The MathWorks
The MathWorks
YouTube Video
The MathWorks
The MathWorks
YouTube Video
  • With Simscape™, you can model multi-domain systems and implement the concept of across and through variables—the product of these variables equates to power for a specific domain. You can also use Simscape to create your own custom domain. Ed Marquez and Christoph Hahn cover the benefits of using Simscape for vehicle modeling. In addition, they customize a shipping demo to show you how you can st...

The MathWorks
The MathWorks
Page Metadata Update

New page title detected.

  • New: Coverage. It's all good. Health care coverage is good. Cell phone coverage is good. Even cloud coverage can provide a nice break from the intensity the sun's rays sometimes. It should come then as no surprise that good code coverage also gives us that nice warm fuzzy feeling, like a nice warm drink on a cold day....and often for good reason. Code coverage can help us see areas of our code that are not exercised in some form or another, and can be very helpful, in a good-friend-that-can-be-brutally-honest-with-you sort of way. It can point out where we really need to add more testing. Once we react to our good friend's advice and add better testing, we are all the better.A quick aside to add some caution is in order. We (all) should remember that code coverage does not as much show what code is covered as which code is not covered. This is because seeing that a piece of code is covered says nothing about how it was covered, whether it was covered by a test specifically targeting th
  • Old: Ah the joys of a new release! R2017b is now out and packed with some great new features. So here I go, heading out to an excitement fueled upgrade-mania when lo and behold, my glee is rudely interrupted when I see my code is broken in the new release.What a drain on an otherwise pleasant experience! It turns out that the error is due to some of my more "creative" and "clever" coding practices that have helped me get my job done in the past, and when I dig in I see that I've been warned about this change coming for years. The problem is I never seem to have the time to comb the release notes as much as I'd like to, and even if I did realizing that my code I wrote 5 years ago has some of the problems mentioned is a tall order.To compound that, even though I'd like to upgrade, when I make the needed adjustments to do so I worry about breaking the users of my code who haven't upgraded yet.What in the world to do?Let's use some continuous integration! Last I checked we were still in ch
The MathWorks
The MathWorks
YouTube Video
  • Alongkrit Chutinan, a development manager within the Simulink Semantics team, shows the latest methods and design patterns in Simulink® for scheduling, partitioning, and integration of software components for simulation, code generation, and system integration. See how you can mix and match export functions and rate-based schedulable components, as well as model startup and shutdown behavior. See ...

The MathWorks
The MathWorks
YouTube Video
  • Jeremy Bell, Angus Keatinge, and James Wagner of The University of New South Wales (UNSW Sydney), join Sebastian Castro of MathWorks to talk about their winning entry to the IEEE Signal Processing Cup 2017. The Signal Processing Cup is an annual competition that began in 2014, in which student teams are presented with a real-world signal processing challenge. The 2017 challenge consisted of imple...

The MathWorks
The MathWorks
YouTube Video
  • Free MATLAB Trial: https://goo.gl/yXuXnS Learn more about MATLAB: https://goo.gl/8QV7ZZ Learn more about Simulink: https://goo.gl/nqnbLe Christoph Hahn and guest presenter Jose Avendano introduce you to options available for accessing the data within your vehicle’s CAN bus. Data obtained through Simulink® data logging or other devices can be directly integrated into virtual CAN channels to be inc...

The MathWorks
The MathWorks
YouTube Video
  • Join Sebastian Castro as he outlines a simulation-based workflow for designing and controlling a two-legged walking robot. In this video, Sebastian shows you how you can leverage MATLAB® and its toolboxes to automate design activities for Simulink® models. Specifically, this demonstration uses the genetic algorithm functionality in Global Optimization Toolbox to find optimal motion trajectories f...

The MathWorks
The MathWorks
YouTube Video
  • Join Sebastian Castro as he outlines a simulation-based workflow for designing and controlling a two-legged walking robot. In this video, Sebastian shows how you can create detailed robot actuator models using Simulink® and Simscape™. In addition to directly defining the motion of the robot actuators, you can use Simulink to design motion planning and closed-loop control algorithms and evaluate t...

The MathWorks
The MathWorks
YouTube Video
  • Using MATLAB Coder™ support for Raspberry Pi™, you can prototype an audio processing application on a Raspberry Pi. This example demonstrates how you can capture live audio feed from a webcam or USB microphone, run the deployed pitch shifting algorithm on the hardware, and play back the modified audio data through the headphone jack of the Raspberry Pi board. Learn more about MATLAB Coder support...

The MathWorks
The MathWorks
YouTube Video
  • Join Sebastian Castro as he outlines a simulation-based workflow for designing and controlling a two-legged walking robot. In this video, Sebastian shows how to model the rigid-body mechanics of a two-legged walking robot using Simscape Multibody™. You can use MATLAB variables to define the geometric and inertial parameters of the robot such that they can be quickly modified. Alternatively, you c...

The MathWorks
The MathWorks
YouTube Video
  • Stephen Cronin from the Robotics Association at Embry-Riddle Aeronautical University (ERAU) joins Connell D'Souza from MathWorks to talk about using MATLAB® to calculate the direction of arrival of an acoustic signal propagating underwater. Data Acquisition Toolbox™: https://goo.gl/4i3vgL Hardware supported with the Data Acquisition Toolbox: https://goo.gl/YrwR7z Visit the MATLAB and Simulink Ro...

The MathWorks
The MathWorks
Page Metadata Update

New page title detected.

  • New: Ah the joys of a new release! R2017b is now out and packed with some great new features. So here I go, heading out to an excitement fueled upgrade-mania when lo and behold, my glee is rudely interrupted when I see my code is broken in the new release.What a drain on an otherwise pleasant experience! It turns out that the error is due to some of my more "creative" and "clever" coding practices that have helped me get my job done in the past, and when I dig in I see that I've been warned about this change coming for years. The problem is I never seem to have the time to comb the release notes as much as I'd like to, and even if I did realizing that my code I wrote 5 years ago has some of the problems mentioned is a tall order.To compound that, even though I'd like to upgrade, when I make the needed adjustments to do so I worry about breaking the users of my code who haven't upgraded yet.What in the world to do?Let's use some continuous integration! Last I checked we were still in ch
  • Old: Ah the joys of a new release! R2017b is now out and packed with some great new features. So here I go, heading out to an excitement fueled upgrade-mania when lo and behold, my glee is rudely interrupted when my see code is broken in the new release.What a drain on an otherwise pleasant experience! It turns out that the error is due to some of my more "creative" and "clever" coding practices that have helped me get my job done in the past, and when I dig in I see that I've been warned about this change coming for years. The problem is I never seem to have the time to comb the release notes as much as I'd like to, and even if I did realizing that my code I wrote 5 years ago has some of the problems mentioned is a tall order.To compound that, even though I'd like to upgrade, when I make the needed adjustments to do so I worry about breaking the users of my code who haven't upgraded yet.What in the world to do?Let's use some continuous integration! Last I checked we were still in char
The MathWorks
The MathWorks
Page Metadata Update

New page title detected.

  • New: Ah the joys of a new release! R2017b is now out and packed with some great new features. So here I go, heading out to an excitement fueled upgrade-mania when lo and behold, my glee is rudely interrupted when I see my code is broken in the new release.What a drain on an otherwise pleasant experience! It turns out that the error is due to some of my more "creative" and "clever" coding practices that have helped me get my job done in the past, and when I dig in I see that I've been warned about this change coming for years. The problem is I never seem to have the time to comb the release notes as much as I'd like to, and even if I did realizing that my code I wrote 5 years ago has some of the problems mentioned is a tall order.To compound that, even though I'd like to upgrade, when I make the needed adjustments to do so I worry about breaking the users of my code who haven't upgraded yet.What in the world to do?Let's use some continuous integration! Last I checked we were still in ch
  • Old: Ah the joys of a new release! R2017b is now out and packed with some great new features. So here I go, heading out to an excitement fueled upgrade-mania when lo and behold, my glee is rudely interrupted when my see code is broken in the new release.What a drain on an otherwise pleasant experience! It turns out that the error is due to some of my more "creative" and "clever" coding practices that have helped me get my job done in the past, and when I dig in I see that I've been warned about this change coming for years. The problem is I never seem to have the time to comb the release notes as much as I'd like to, and even if I did realizing that my code I wrote 5 years ago has some of the problems mentioned is a tall order.To compound that, even though I'd like to upgrade, when I make the needed adjustments to do so I worry about breaking the users of my code who haven't upgraded yet.What in the world to do?Let's use some continuous integration! Last I checked we were still in char
The MathWorks
The MathWorks
Page Metadata Update

New page title detected.

  • New: Ah the joys of a new release! R2017b is now out and packed with some great new features. So here I go, heading out to an excitement fueled upgrade-mania when lo and behold, my glee is rudely interrupted when I see my code is broken in the new release.What a drain on an otherwise pleasant experience! It turns out that the error is due to some of my more "creative" and "clever" coding practices that have helped me get my job done in the past, and when I dig in I see that I've been warned about this change coming for years. The problem is I never seem to have the time to comb the release notes as much as I'd like to, and even if I did realizing that my code I wrote 5 years ago has some of the problems mentioned is a tall order.To compound that, even though I'd like to upgrade, when I make the needed adjustments to do so I worry about breaking the users of my code who haven't upgraded yet.What in the world to do?Let's use some continuous integration! Last I checked we were still in ch
  • Old: Ah the joys of a new release! R2017b is now out and packed with some great new features. So here I go, heading out to an excitement fueled upgrade-mania when lo and behold, my glee is rudely interrupted when my see code is broken in the new release.What a drain on an otherwise pleasant experience! It turns out that the error is due to some of my more "creative" and "clever" coding practices that have helped me get my job done in the past, and when I dig in I see that I've been warned about this change coming for years. The problem is I never seem to have the time to comb the release notes as much as I'd like to, and even if I did realizing that my code I wrote 5 years ago has some of the problems mentioned is a tall order.To compound that, even though I'd like to upgrade, when I make the needed adjustments to do so I worry about breaking the users of my code who haven't upgraded yet.What in the world to do?Let's use some continuous integration! Last I checked we were still in char
The MathWorks
The MathWorks
Page Metadata Update

New page title detected.

  • New: Ah the joys of a new release! R2017b is now out and packed with some great new features. So here I go, heading out to an excitement fueled upgrade-mania when lo and behold, my glee is rudely interrupted when I see my code is broken in the new release.What a drain on an otherwise pleasant experience! It turns out that the error is due to some of my more "creative" and "clever" coding practices that have helped me get my job done in the past, and when I dig in I see that I've been warned about this change coming for years. The problem is I never seem to have the time to comb the release notes as much as I'd like to, and even if I did realizing that my code I wrote 5 years ago has some of the problems mentioned is a tall order.To compound that, even though I'd like to upgrade, when I make the needed adjustments to do so I worry about breaking the users of my code who haven't upgraded yet.What in the world to do?Let's use some continuous integration! Last I checked we were still in ch
  • Old: Hello readers, today we have another post from Amy, who is here to share more of her valuable experience deploying toolboxes. Take note of some of these tips after you have thoroughly enjoyed any eclipse observations you have been lucky enough to witness this time around. Just like looking at an eclipse directly is something you want to avoid, so are these packaging anti-patterns. Take it away Amy! What are some common pitfalls when packaging a toolbox? In one of my previous posts, I described how to set up your development environment in MATLAB when developing and packaging a MATLAB toolbox. In this post, I'll share ways to avoid common pitfalls which can cause the toolbox packaging process to fail. Toolbox project file contains absolute paths to files It's important to understand how the project file (.prj) handles paths to ensure that they function correctly irrespective of the absolute sandbox path. In my other post, I recommend that the toolbox content sits below the folder
The MathWorks
The MathWorks
YouTube Video
  • R2017b includes new releases of MATLAB® and Simulink® as well as updates and bug fixes to all other products. The latest release makes deep learning more accessible to everyone, even if you're not an expert. ‌Learn more about the latest features in Release 2017b: https://goo.gl/pgGtod It includes: ‌•Expanded deep learning capabilities such as an image labeling app and the ability to work with lo...

The MathWorks
The MathWorks
YouTube Video
  • BEST Robotics and VEX Robotics are the two largest competitions that require teams to use the VEX® Cortex® Microcontroller to program their robots. The Simulink Coder™ hardware support package for VEX Cortex Microcontroller offers built-in, limited support for specific hardware, schedulers, and compilers. Get the support package here: https://goo.gl/a1HxT7 The support package includes: • A lib...

The MathWorks
The MathWorks
Page Metadata Update

New page title detected.

  • New: Ah the joys of a new release! R2017b is now out and packed with some great new features. So here I go, heading out to an excitement fueled upgrade-mania when lo and behold, my glee is rudely interrupted when I see my code is broken in the new release.What a drain on an otherwise pleasant experience! It turns out that the error is due to some of my more "creative" and "clever" coding practices that have helped me get my job done in the past, and when I dig in I see that I've been warned about this change coming for years. The problem is I never seem to have the time to comb the release notes as much as I'd like to, and even if I did realizing that my code I wrote 5 years ago has some of the problems mentioned is a tall order.To compound that, even though I'd like to upgrade, when I make the needed adjustments to do so I worry about breaking the users of my code who haven't upgraded yet.What in the world to do?Let's use some continuous integration! Last I checked we were still in ch
  • Old: Hello readers, today we have another post from Amy, who is here to share more of her valuable experience deploying toolboxes. Take note of some of these tips after you have thoroughly enjoyed any eclipse observations you have been lucky enough to witness this time around. Just like looking at an eclipse directly is something you want to avoid, so are these packaging anti-patterns. Take it away Amy! What are some common pitfalls when packaging a toolbox? In one of my previous posts, I described how to set up your development environment in MATLAB when developing and packaging a MATLAB toolbox. In this post, I'll share ways to avoid common pitfalls which can cause the toolbox packaging process to fail. Toolbox project file contains absolute paths to files It's important to understand how the project file (.prj) handles paths to ensure that they function correctly irrespective of the absolute sandbox path. In my other post, I recommend that the toolbox content sits below the folder
The MathWorks
The MathWorks
Page Metadata Update

New page title detected.

  • New: Ah the joys of a new release! R2017b is now out and packed with some great new features. So here I go, heading out to an excitement fueled upgrade-mania when lo and behold, my glee is rudely interrupted when I see my code is broken in the new release.What a drain on an otherwise pleasant experience! It turns out that the error is due to some of my more "creative" and "clever" coding practices that have helped me get my job done in the past, and when I dig in I see that I've been warned about this change coming for years. The problem is I never seem to have the time to comb the release notes as much as I'd like to, and even if I did realizing that my code I wrote 5 years ago has some of the problems mentioned is a tall order.To compound that, even though I'd like to upgrade, when I make the needed adjustments to do so I worry about breaking the users of my code who haven't upgraded yet.What in the world to do?Let's use some continuous integration! Last I checked we were still in ch
  • Old: Hello readers, today we have another post from Amy, who is here to share more of her valuable experience deploying toolboxes. Take note of some of these tips after you have thoroughly enjoyed any eclipse observations you have been lucky enough to witness this time around. Just like looking at an eclipse directly is something you want to avoid, so are these packaging anti-patterns. Take it away Amy! What are some common pitfalls when packaging a toolbox? In one of my previous posts, I described how to set up your development environment in MATLAB when developing and packaging a MATLAB toolbox. In this post, I'll share ways to avoid common pitfalls which can cause the toolbox packaging process to fail. Toolbox project file contains absolute paths to files It's important to understand how the project file (.prj) handles paths to ensure that they function correctly irrespective of the absolute sandbox path. In my other post, I recommend that the toolbox content sits below the folder
The MathWorks
The MathWorks
YouTube Video
  • Free MATLAB Trial: https://goo.gl/yXuXnS Request a Quote: https://goo.gl/wNKDSg Contact Us: https://goo.gl/RjJAkE Learn more about MATLAB: https://goo.gl/8QV7ZZ Learn more about Simulink: https://goo.gl/nqnbLe Christoph Hahn and guest presenter Jose Avendano introduce you to a remote-control model racecar programmed using Simulink® hardware support packages. They showcase how Simulink developed ...

The MathWorks
The MathWorks
Page Metadata Update

New page title detected.

  • New: Ah the joys of a new release! R2017b is now out and packed with some great new features. So here I go, heading out to an excitement fueled upgrade-mania when lo and behold, my glee is rudely interrupted when I see my code is broken in the new release.What a drain on an otherwise pleasant experience! It turns out that the error is due to some of my more "creative" and "clever" coding practices that have helped me get my job done in the past, and when I dig in I see that I've been warned about this change coming for years. The problem is I never seem to have the time to comb the release notes as much as I'd like to, and even if I did realizing that my code I wrote 5 years ago has some of the problems mentioned is a tall order.To compound that, even though I'd like to upgrade, when I make the needed adjustments to do so I worry about breaking the users of my code who haven't upgraded yet.What in the world to do?Let's use some continuous integration! Last I checked we were still in ch
  • Old: Hello readers, today we have another post from Amy, who is here to share more of her valuable experience deploying toolboxes. Take note of some of these tips after you have thoroughly enjoyed any eclipse observations you have been lucky enough to witness this time around. Just like looking at an eclipse directly is something you want to avoid, so are these packaging anti-patterns. Take it away Amy! What are some common pitfalls when packaging a toolbox? In one of my previous posts, I described how to set up your development environment in MATLAB when developing and packaging a MATLAB toolbox. In this post, I'll share ways to avoid common pitfalls which can cause the toolbox packaging process to fail. Toolbox project file contains absolute paths to files It's important to understand how the project file (.prj) handles paths to ensure that they function correctly irrespective of the absolute sandbox path. In my other post, I recommend that the toolbox content sits below the folder

Out-Market Your Competitors?

Get complete competitive insights on over 2.2 million companies to drive your marketing strategy.

Create Free Account Log in

By signing up, you agree to the Terms of Service and Privacy Policy.

Out-Market Your Competitors

Get complete competitive insights on over 2.2 million companies to drive your marketing strategy.

Create Free Account

Already a user?  Log in

By signing up, you agree to the Terms of Service and Privacy Policy.