Not a "MATLAB bad" post. The original code is solid and I replicate it bug-for-bug by default. Sharing the trap list for anyone migrating numerical code: round() half-away-from-zero vs numpy's round-half-to-even (inside the nmax series formula, so it changes array lengths), complex auto-promotion that NumPy doesn't do, ' vs .', library functions printing to stdout, and a docstring feature (complex medium index) that turns out to be latently broken. Full findings file, 714-fixture corpus and the verification report: https://github.com/GrednevMSU/mie-scattering-matlab-to-python

Yeah

I have an older version of Mathematica from my university days. I only need it for basic tasks, so I’d prefer not to buy a new license.

My issue is that on Windows 11, the kernel frequently hangs or gets stuck indefinitely—even on simple calculations like 1 + 1.

So far, I’ve tried:

• Enabling Windows compatibility modes (no effect)
• Disabling "Allow Mathematica to access the Internet" in Preferences

Has anyone run into this issue on Windows 11 and found a workaround or fix?

Any ideas of things i could try, even if you don't know if they ll work?

Hi! I’m experimenting with a project Einstoff; it is inspired by einops/einx, but instead of parsing a string with syntax, it uses native WL patterns as a eDSL to describe tensor operations like reshaping, reducing, contracting, joining, and splitting multidimensional arrays.

Any thoughts or comments are much obliged :D

I recently upgraded to Mathematica 15 and, although I installed the full desktop version + documentation, when I ask it to evaluate a simple expression (say, something containing a DSolve, ComplexPlot or a ComplexExpand), it first says it is downloading something from a repository. What is going on? These basic functions are no longer included in the package?

Here is an example:

Does this affect the perpetual licenses for the personal desktop products?

Edit: I believe it only happens the first time the function is evaluated and that it is henceforth cached in the computer.

Last week I learned my university gives me access to Mathematica so I decided to try and learn how to use it as it seems incredibly useful for my typed assignments. Since then, I couldn't manage to type a single sentence without the software freezing for minutes or even crashing.
Mousing over cell styles (like in the attached screenshot) causes Mathematica to freeze for at least a couple of minutes (after taking the screenshot it crashed).

While I'd like to fix this specific issue, it's just one example I can reliably reproduce.

From googling\debugging with and without ai, the only solution i found was disabling all the more advanced features and enabling them one by one.

Is there anyone who can recommend something better? (keep in mind that I don't know much about what things in Mathematica are called as i didn't get to actually use the software).

About my system: I'm running windows 11 on my fairly modern study-laptop (Intel i5-1235U, 16GB ram, Intel Iris Xe Graphics and over 300GB of free storage). Judging by the Wolfram website, each of my parts should be more than enough.

When installing I followed the instructions on my university's website (to get the installation and registration right) and the installer went uninterrupted so the odds for a corrupted installation are slim. I'll update once I'm done reinstalling but I doubt the issue will go away

See title

Each line trace has a vector, which is normal set to [0,0,-1]. However, this doesn't work on slopes. So you calculate the normal vector of it, split that up into its x, y, and z components, multiply them all by -1, and those are what you plug into your line trace! (For example, a 45 degree wall would have a total component of [0.707,0,0.707]. So you take the, multiply it by -1, and use that in your line trace as [-0.707,0,-0.707]) And make sure to have gravity apply in a completely different part of the script from the line trace, otherwise the game will think walking on walls is normal.