Mathematica 11 Release

Mathematica 11 is now out and ready to compute! Since the release of Version 10 two years ago, Mathematica has grown by leaps and bounds, with 500+ new functions. This version introduces both enhancements to computations across the board and completely new areas of functionality, continuing Mathematica’s growth as the state-of-the-art technical platform—and we are very excited to share these developments with the world. Some of the most notable features include:

3D Printing

Computational Audio

audioplot.png

Neural Networks

  • Define network topologies with NetGraph or with a chain of layers with NetChain.
  • Train your neural nets with NetTrain.
  • Train networks on either CPUs or NVIDIA GPUs.
  • Are your training sets of images too large to hold in-memory? The neural network functions support out-of-core image datasets.

Improved Machine Learning

CumberbatchMachineLearning.png

And these are only just a sample of the new features, including the Wolfram Channel Framework, enhanced notebook processing, cloud-aware WolframScript, improved symbolic and numeric calculus and so much more.

To read more about what’s new in Mathematica 11, read Stephen Wolfram’s release-day blog post and check out the New in 11 page.

11 Likes

I was missing this plot, that always shows up at every release…

    funcs = WolframLanguageData[];
    versions = WolframLanguageData[funcs, "VersionIntroduced"];
    out = SortBy[Tally[versions], First];
    out[[All, 2]] = Accumulate[out[[All, 2]]];
    out = {#1, {If[IntegerQ[#1], 100, 50], #2}} & @@@ out;
    blue = RGBColor[0.37, 0.51, 0.71];
    cols = If[IntegerQ[#], blue, Lighter[blue]] & /@ out[[All, 1]];
    RectangleChart[Labeled[#2, Rotate[#1, \[Pi]/4], Below] & @@@ out, 
     BarSpacing -> 0, ImageSize -> 600, ChartStyle -> cols, Frame -> True,
      GridLines -> Automatic, 
     FrameTicks -> {{Automatic, Automatic}, {None, None}}]

5 Likes

Examples in which the MMA 11.0 gives incorrect or strange solutions.

Example1:

Sum[Floor[5/5^k], {k, 1, \[Infinity]}](* It should be 1 *)

Example2:

eq = y[n] - 1 - 1*Sqrt[y[n]] - y[n + 1];
sol = First@RSolve[{eq == 0, y[0] == 1}, y[n], n];
Table[(y[n] /. sol), {n, 10}] // N
RecurrenceTable[{eq == 0, y[0] == 1}, y, 
    {n, 10}] // N(*Answers not the same *)

Example3:

eqn5 = (y'[x])^2 + y'[x]*y[x] - x == 0;
DSolve[{eqn5}, y[x], x](* strange results *)

Example4:

 FourierTransform[Exp[a*t ]/t, t, \[Omega]](*incorrect answer *)

Example5:

InverseLaplaceTransform[Coth[s], s, t]
InverseLaplaceTransform[Tanh[s], s, t]
InverseLaplaceTransform[Sech[s], s, t]
InverseLaplaceTransform[Csch[s], s, t]
(* strange results *)

Example6:

 Integrate[Sqrt[Exp[I*t]^2 - 1], {t, 0, Pi}](*incorrect answer *)

Example7:

 << Quaternions`
 Exp[Quaternion[1, 0, 0, 0]]
 (*bug or errors*)

Example8:

 Integrate[Sin[q]^2/Sinh[q]^2, {q, 0, \[Infinity]}](*incorrect answer *)
5 Likes

Example 1:

But

In[1]:= Sum[Floor[5/5^k], {k, 0, \[Infinity]}]

Out[1]= 6

In[2]:= Sum[Floor[5/5^k + 10^-1000000], {k, 1, \[Infinity]}]

Out[2]= 1

The bug is because of Sum[] function:

In[3]:= Table[Floor[5/5^k], {k, 1, 10}]

Out[3]= {1, 0, 0, 0, 0, 0, 0, 0, 0, 0}
1 Like

Nice finds you two, now that’s something to report ( Contact Wolfram Support by Email or Phone )

1 Like

Are you a ‘prerelease’-tester (beta-tester)? If not, perhaps you can sign up; send them an email prerelease@wolfram.com I’d bet they would have liked to know about this before release. They intend to resume the prerelease program for version 11.1

No I’m not a Beta tester. A lot of Bugs can be found on this Website,only need to test(for Bugs) them for MMA 11.0.

From my experience: they respond much faster to problems found in beta-versions…

Thanks. Maybe I’m send them a e-mail. :slight_smile:

Advice to pre-release testers. In order to use the activation code for version 11 from the user portal, you’ll need to delete the pre-release versions from your license file. If you don’t, the activation code will not be asked for and your license will remain as the pre-release license.

2 Likes

These are not regressions. They were known before, as I remember several of these examples from StackExchange. I think what Mariusz meant was that even though these were known problems, they were still not fixed in version 11.

To be fair, I should note that my subjective impression was that symbolic math related bugs like these got fixed with higher frequency than other problems. This is based on going through a few random bugs-tagged questions on StackExchange and seeing which got fixed.

The first sum starts at 0, the second one starts at 1

Yes!

No need to delete your license file manually:

Aah ok, because it was a reply to this thread I assumed they were ‘fresh’ bugs :wink: nonetheless, submitting bugs to wolfram gives it a good(better?) chance of having them fixed…

Or –
You just use the menu item and enter the new activation code. You can delete the old one if you like, but it is not necessary.

You can check to see if the activation is yours or the pre-release by looking at About Wolfram Mathematica. If the Registered name is your name, then you have successfully entered your activation code. If it is (still) Arnoud Buzing (sp??), you need to enter your activation key using the Help/Enter Activation Key… menu item. You get the key itself from your user portal.

If you ever look at the file that contains the activation keys (use a text editor), it can have lots of keys. Mathematica uses the first on in the list that ‘works’.

1 Like

Hi,

Before even trying the recent version 11, I would need to know whether the following bugs have been fixed :

  1. Graphs with multiple edges and problems with edges layouts and colouring

In fact, this is a direct question to Szabolcs Horvat, since he knows well the multiple edges issue and, I guess, can give a definitive answer.

  1. Problems with ‘Hyperlink[“label”,(“notebook.nb”’,“celltag”}]

Thank you

Martin.

I used notepad++ to delete the prerelease lines from the license file.

It would have been nice if they had told the pre-release testers about the menu item.

No!

None of them has been solved in Version 11.

Another two bugs left behind.