Results for

20 - 39 of 519

Steve Eddins
Last activity on 20 Feb 2025

Issues with Add-On Versioning

General observations on practical implementation issues regarding add-on versioning

I am making updates to one of my File Exchange add-ons, and the updates will require an updated version of another add-on. The state of versioning for add-ons seems to be a bit of a mess.

First, there are several sources of truth for an add-on’s version:

The GitHub release version, which gets mirrored to the File Exchange version
The ToolboxVersion property of toolboxOptions (for an add-on packaged as a toolbox)
The version in the Contents.m file (if there is one)

Then, there is the question of how to check the version of an installed add-on. You can call matlab.addon.installedAddons, which returns a table. Then you need to inspect the table to see if a particular add-on is present, if it is enabled, and get the version number.

If you can get the version number this way, then you need some code to compare two semantic version numbers (of the form “3.1.4”). I’m not aware of a documented MATLAB function for this. The verLessThan function takes a toolbox name and a version; it doesn’t help you with comparing two versions.

If add-on files were downloaded directly and added to the MATLAB search path manually, instead of using the .mtlbx installer file, the add-on won’t be listed in the table returned by matlab.addon.installedAddon. You’d have to call ver to get the version number from the Contents.m file (if there is one).

Frankly, I don’t want to write any of this code. It would take too long, be challenging to test, and likely be fragile.

Instead, I think I will write some sort of “capabilities” utility function for the add-on. This function will be used to query the presence of needed capabilities. There will still be a slight coding hassle—the client add-on will need to call the capabilities utility function in a try-catch, because earlier versions of the add-on will not have that utility function.

I also posted this over at Harmonic Notes

View Full Post

Generative AI

imad
Last activity on 14 Feb 2025

The Future of Simulink in MATLAB

Simulink has been an essential tool for modeling and simulating dynamic systems in MATLAB. With the continuous advancements in AI, automation, and real-time simulation, I’m curious about what the future holds for Simulink.

What improvements or new features do you think Simulink will have in the coming years? Will AI-driven modeling, cloud-based simulation, or improved hardware integration shape the next generation of Simulink?

Generative AI

Mike Croucher
Last activity on 4 Feb 2025

Run DeepSeek models on your own machine and interact with them using MATLAB

You've probably heard about the DeepSeek AI models by now. Did you know you can run them on your own machine (assuming its powerful enough) and interact with them on MATLAB?

In my latest blog post, I install and run one of the smaller models and start playing with it using MATLAB.

How to run local DeepSeek models and use them with MATLAB » The MATLAB Blog - MATLAB & Simulink

Larger models wouldn't be any different to use assuming you have a big enough machine...and for the largest models you'll need a HUGE machine!

Even tiny models, like the 1.5 billion parameter one I demonstrate in the blog post, can be used to demonstrate and teach things about LLM-based technologies.

Have a play. Let me know what you think.

Meta Cody

Brent
Last activity on 18 Feb 2025

Problem 723: QWERTY Shift Encoder

My following code works running Matlab 2024b for all test cases. However, 3 of 7 tests fail (#1, #4, & #5) the QWERTY Shift Encoder problem. Any ideas what I am missing?

Thanks in advance.

keyboardMap1 = {'qwertyuiop[;'; 'asdfghjkl;'; 'zxcvbnm,'};

keyboardMap2 = {'QWERTYUIOP{'; 'ASDFGHJKL:'; 'ZXCVBNM<'};

if length(s) == 0

se = s;

end

for i = 1:length(s)

if double(s(i)) >= 65 && s(i) <= 90

row = 1;

col = 1;

while ~strcmp(s(i), keyboardMap2{row}(col))

if col < length(keyboardMap2{row})

col = col + 1;

else

row = row + 1;

col = 1;

end

se(i) = keyboardMap2{row}(col + 1);

elseif double(s(i)) >= 97 && s(i) <= 122

row = 1;

col = 1;

while ~strcmp(s(i), keyboardMap1{row}(col))

if col < length(keyboardMap1{row})

col = col + 1;

else

row = row + 1;

col = 1;

end

se(i) = keyboardMap1{row}(col + 1);

else

se(i) = s(i);

end

% if ~(s(i) = 65 && s(i) <= 90) && ~(s(i) >= 97 && s(i) <= 122)

% se(i) = s(i);

% end

end