MATLAB → Julia 😊 | Thomas | JuliaCon 2024

[@martinsanchez-hw4fi]

We need an alternative to simulink

[@dallywang6143]

@@martinsanchez-hw4fi cppsim

[@SomeTechGuy666]

THIS.

[@MarkKittisopikul]

juliahub.com/products/juliasim

[@SomeTechGuy666]

@@MarkKittisopikul Not open source.

[@baggepinnen]

@@SomeTechGuy666 neither is simulink?

[@SomeTechGuy666]

TLDW: Julia isn't the same as MATLAB. Learning a new language takes time. I wonder who pays for his MATLAB subscription and how responsive Mathworks is to his requests for new features ?

[@zorglub20770]

that would be amazing if you could port the MatLab function ismembertol to Julia with the same efficiency and performance as in MatLab

[@cedrickhayat971]

16'28'' i was troubled with this overall value update in pluto. Because i like overwriting variables not to create too many of them. Did not find a way to workaround that. Any suggestion ?

[@aaronkaw4857]

I also found it annoying at first. Pluto is designed for reactivity, so each of your variables are defined once and available everywhere (in dependency order), so you can't overwrite variables in the global scope. One partial workaround is `let` blocks. The variables you define in that scope will take priority over the global scope. Also, those variables defined that scope only exist in that scope. You can't use `let` blocks for global value updates for other cells to use though. I also liked overwriting variables, but that only works for top-down evaluations, of which Pluto is not a top-down evaluation system. Its trade-off is that your cells can be in any order, and there is a smart detection of dependencies between cells so that everything dependent computationally reacts immediately as you save/execute a cell. Though, some more specific detail is provided by the author of Pluto: "In Pluto, assignments to values (e.g. a = 1) will 'trigger' reactivity, but assignments to properties (e.g. `a.start = 2` or `a[5] = 3`) will not. This means that you can use a `Ref` to create 'non-reactive' variables."

[@Kruglord]

One of the major design elements of Pluto is that, if your notebook worked when you saved it, it should work the next time you run it. And, because other cells react when a variable they depend on is updated, you can't redefine a variable other than in the place that it was declared. Otherwise, which version of the variable should the cells react to? So, yeah you'll probably end up with a lot of variables, unless you write things in a way that expects you to update variables, and you don't mind tossing the older definitions. Otherwise, just make new variables as you need them, and consider pruning the ones you don't need once in a while.

[@temporary9508]

And the beef begins

[@aaronkaw4857]

I am all about this beef.