Seth on Simulink

June 18th, 2009

Sneak Peek At The Next Release!

Many people talk about the anticipation of the next iPhone, Kindle or some must-have techno gadget. I am looking forward to the next release of MATLAB. I downloaded the prerelease last week and now I am evaluating the new Simulink modeling features.

Currently licensed users can log in to their MathWorks account and see this:

MathWorks account page announcing the R2009b Prerelease.

The prerelease is a great opportunity to get a sneak peak at the new capabilities in MATLAB and Simulink. You can evaluate the new features and decide if it is time to pressure your team to upgrade when R2009b becomes available this fall.

If you have a base of existing models and code, this is a great chance to try it against the next release. If something doesn't work, contact technical support. This is an important mechanism to ensure compatibility, and your feedback is important.

By Seth Popinchalk

02:00 UTC | Posted in What's new? | Permalink |

You can follow any responses to this entry through the RSS 2.0 feed. You can skip to the end and leave a response. Pinging is currently not allowed.

One Response to “Sneak Peek At The Next Release!”

  1. ABindemann replied on June 25th, 2009 at 19:50 UTC :

    Seth,

    I have an idea for a topic that you might consider in a future post. Here goes…

    What strategies can you recommend when developing large scale Simulink projects that utilize the following features:

    - Libraries
    - Multiple Developers
    - Revision Control (Such as Subversion or CVS)

    Libraries are nice, however once they grow beyond a certain size in a multi-developer environment people can start stepping on each other’s changes.

Leave a Reply

Wrap code fragments inside <pre> tags, like this:

<pre class="code">
a = magic(3);
sum(a)
</pre>

If you have a "<" character in your code, either follow it with a space or replace it with "&lt;" (including the semicolon).

About

Seth Popinchalk is an Application Engineer for The MathWorks. He writes here about Simulink and other MathWorks tools used in Model-Based Design.

Subscribe


Recent Comments

  • Ashish Sadanandan: @wei, I was talking about the case where the compiler would perform the ‘model_Xdim...
  • wei: @Ashish, I agree with your observation on compiler optimization but fail to see why Han’s code would be...
  • Ashish Sadanandan: Han, Sorry for butting in with a reply, but the modification to the for-loop you’ve...
  • arun kumar: dear seth i have been involved in developing and simulating asynchronous systems for my VLSI lab. in...
  • Han Geerligs: Hi Aarti, thanks for providing the example! I was just wondering why the lines model_YDim = model_XDim;...
  • Seth: @Han - Aarti’s response is in a post titled Generated Code for Variable Size Signals.
  • garla: what is advantage of exporting the bus object with the format as “cell” and “object” ....
  • J.r: @ Guy - Example sent to your account. Thank you.
  • Guy: @ J.r - The ability for atomic subsystems and Model Reference to remove the “fake algebraic loop”...
  • J.r: Sorry to hit an old thread, but this seems like the best place to solicit help on this topic. Is there supposed...

Blog Admin

These postings are the author's and don't necessarily represent the opinions of The MathWorks.