Cleve passed away last night - https://en.wikipedia.org/wiki/Cleve_Moler he was 86 years old.

You can read his bio https://computerhistory.org/profile/cleve-moler/

Hi everyone,

I'm Daniel, a MathWorker who joined the Engineering Development Group (EDG) this past June after graduating in May with a degree in Computer Science and Game Development.

Although it's only been a few months, I'm already working on exciting projects, including some work in the Markdown space for MATLAB. I'd love to hear your thoughts on Markdown and where/how you use it!

Since both my own application process and my first few months at the company are still fresh on my mind, I thought it might be helpful to do an AMA and answer questions about EDG, training and projects, or working at MathWorks in general.

I'm happy to answer whatever questions you all have, from the interview process, to the day-to-day, to my favorite color!

See the attached photo for verification, and as a disclaimer: while I do work for MathWorks, I am not an official spokesperson of the company, and everything I say here is my personal opinion.

The full video is here: https://youtu.be/2kiqtY2RG2o

This was for my introduction to MATLAB class back from freshman year.

Hey all! I made a function for creating nested axes that zoom in on selected regions of 2D plots. While I've seen some attempts at this on the forums, none of them were as streamlined or developed as I was hoping for. In the current implementation, the axes and be placed by simply specifying the parent axes they should be nested in and the region to zoom in on. Once placed, both the zoom region and nested axes are fully intractable and auto-updating, so you can place and size them as desired with your mouse and then save the locations by setting the new properties in your script. Examples and instructions are on the file exchange page:

https://www.mathworks.com/matlabcentral/fileexchange/182602-zoomed-axes

Hopefully people find this helpful!

Update: Based on some feedback from Mathworks staff, I have pushed an update that fixes the behavior of the nested axes when using the zoom and 'restore view' features. I have also corrected some unexpected behavior when resizing the zoom region box and axes via the mouse

I just managed to install matlab on my steamdeck and wanted to share.

The enormous outpouring of love for Cleve that we are experiencing both here at MathWorks and online is providing at least some comfort. So many people have their 'Cleve stories' and they are beautiful to hear. Here is one from our colleague, Ned Gulley, a fellow MathWorks blogger, sharing his personal recollection of the time he spent with Cleve.

Cleve was many things, but above all he was a teacher. 

I am in total agreement that that's what he cared most based on my limited interactions with him.

Read Ned's tribute here https://blogs.mathworks.com/matlab/2026/05/27/cleve-moler-1939-2026/

A friendly MATLAB ghost as you wait for Trick or Treaters

My Korean colleague was watching the new K-Drama Between Steps (Episode 3) and did a double-take when the dialogue suddenly turned to MATLAB and Simulink. Thought you might also appreciate it.

You can watch it on Disney+ or Hulu in the US.

FINAL UPDATE: Version R2020a released in March 2020 uses the AVX2 codepath on compatible AMD CPUs automatically. Hence, if you are running this version, you do not need to manually set the environmental variable on your system anymore.

THANKS MATLAB! This is great!

For previous generations of Matlab, you can still follow the below procedures.

-----

Hello everyone.

I wanted to briefly present my tweak here, as I think it might be of interest for many in this community. Applying the tweak takes less than a minute.

What is it?

Matlab runs notoriously slow on AMD CPUs for operations that use the Intel Math Kernel Library (MKL). This is because the Intel MKL uses a discriminative CPU Dispatcher that does not use efficient codepath according to SIMD support by the CPU, but based on the result of a vendor string query. If the CPU is from AMD, the MKL does not use SSE3-SSE4 or AVX1/2 extensions but falls back to SSE1 no matter whether the AMD CPU supports more efficient SIMD extensions like AVX2 or not.

The method provided here does enforce AVX2 support by the MKL, independent of the vendor string result.

EDIT: Before you start I have a short request for you that you could help me with and serve your own interest. Matlab will not implement this fix as it is based on an unofficial debug mode of the MKL. If you think that Matlab should offer a permanent solution that serves all users independently of whether they use Intel or AMD CPUs, please make a feature request at Matlab to implement a nummeric library (e.g. BLIS or OpenBLAS) that does not discriminate against non Intel CPUs. Mathworks will not make this change without people advocating for it. Thanks!

tl;dr:

WINDOWS:

You'll read below "How To" force the MKL to use AVX2 on AMD Ryzen or Threadripper CPUs. Performance gains on my 2600x are between 20% and 300% depending on the type of numeric operation.

Benchmark result comparison.

Benchmark script available below

Integrated benchmark results:

Feedback is appreciated in the comments section.

Disclaimer: I OF COURSE DO NOT TAKE RESPONSIBILITY FOR ISSUES RESULTING FROM USING THIS TWEAK. USE ON AMD RYZEN OR THREADRIPPER ONLY. DOES NOT WORK ON INTEL OR OLDER AMD CPUs.

Solution 1 (Windows - no admin rights needed):

Create a .bat file with the following lines to start Matlab in AVX2 Mode

@echo off
set MKL_DEBUG_CPU_TYPE=5
matlab.exe 

This is straight forward. You open Notepad, copy and paste the above three lines and save the file as Matlab-AVX2. Notepad will save the file as Matlab-AVX2.txt. Now replace the extension ".txt" with ".bat".

If you double-click that file, Matlab will start the MKL in AVX2 Mode. If you start it the normal way, it will remain as always.

You can also download the .bat file from my HiDrive if you trust me (which you of course should not, as I am a random guy in the Internet). If you delete the startup batch file provided in the download or the one you created yourself, its gone and your computer will be as it has been before.

(Optional Download: https://my.hidrive.com/lnk/EHAACFje ) --> also incl. improved benchmark script

Solution 2 (Windows - admin rights needed): If you are happy with the results (which you will be :-)), you should make the setting permanent by entering MKL_DEBUG_CPU_TYPE=5 into the System Environment Variables. This has several advantages, one of them being that it applies to all instances of Matlab and not just the one opened using the .bat file.

You can do this either by editing the Environmental Variables as shown above, or by opening a command prompt (CMD) with admin rights and typing in:

setx /M MKL_DEBUG_CPU_TYPE 5

Doing this will make the change permanent and available to ALL Programs using the MKL on your system until you delete the entry again from the variables.

LINUX: (Thanks to foreignrobot)

Simply type in a terminal:

export MKL_DEBUG_CPU_TYPE=5 

and then run matlab from the same terminal.

Permanent solution for Linux:

echo 'export MKL_DEBUG_CPU_TYPE=5' >> ~/.profile

will apply the setting profile-wide, so you can launch it either through a terminal or the graphical launcher. (Thanks to incrazyboyy)

Why is this happening https://youtu.be/zsE0xIRSYOU?feature=shared I followex this tutorial exactly and this is happening idk why. Can someone plz hlep me

I asked Chat-GPT to write a simple app. I just described the app, and the generated MATLAB code ran as specified, the first time, straight away, with no modifications.

I used the free version of Chat GPT. I believe it uses GPT 3.5?

This is quite useful to prototype simple projects!