# Tag Info

## Hot answers tagged version-11

31

data = WolframLanguageData[{"Select", "FileNames", "StringContainsQ", "Or", "StringJoin", "ToString"}, {"Name", "DateIntroduced", "DateLastModified", "VersionIntroduced", "VersionLastModified"}]; TableForm[data, TableHeadings -> {None, {"Name", "DateIntroduced", "DateLastModified", "VersionIntroduced", "VersionLastModified"}}] So ...

19

No need to modify a stylesheet, it is sufficient to evaluate SetOptions[$FrontEnd, StyleHints -> {"CodeFont" -> "Courier"}] or equivalently CurrentValue[$FrontEnd, {StyleHints, "CodeFont"}] = "Courier"; for permanently setting the default font to "Courier New" system-wide in Mathematica 11. Note that the undocumented StyleHints option is new in ...

19

As already stated elsewhere, versions 11.3 and earlier simply cannot run on Catalina because Apple removed support for 32-bit applications. And, unfortunately, creating a 64-bit 11.3.1 impossible, because the 11.3 FrontEnd is a "Carbon" application, rather than a "Cocoa" application. We've been working on rewriting the FrontEnd in Cocoa for several years, ...

18

No, unfortunately there are no easy workarounds - MacOS Catalina simply doesn't support 32-bit apps, and the Mathematica frontend for 11.3 and earlier is a 32-bit app. To solve this, you must either upgrade your license or downgrade your version of MacOS. You may also have some luck contacting Wolfram Support and seeing if they can help you.

15

Straight from the proverbial horse's mouth: Default font changed to Source Code Pro on Mac, Consolas on Windows, and Bitstream Vera Sans Mono on Linux.

11

Following the lead from J.M., and then some comments therein from User18 and QuantumDot, the following is working: In the common StyleSheet, under Notebook options, I added the option: StyleHints->{"CodeFont" -> "Courier"} So, for example, the options now read: Cell[StyleData["Notebook"], Saveable->False, ShowAutoSpellCheck->False, ...

10

When the first message is generated, the message formatting code is autoloaded from .mx files. This may cause the attributes of certain symbols to be reset, or rather replaced with what has been stored in one of those .mx files. A minimal example that can also be run in a standalone kernel In[1]:= Unprotect[Element]; Attributes[Element] Out[1]= {} In[2]:=...

10

On my Windows 7 system, CurrentValue[{StyleHints, "CodeFont"}] gives Consolas. A perhaps more intuitive way to find it is to simply highlight a piece of text/output/input/etc. the font of which you're interested in, then go to Format->Font..., and you'll see the font highlighted. Having said that, I am a bit surprised, too, that they use the somewhat dated ...

10

Yes, the metadata import causes the performance regression in version 11.0. If you don't need Exif, IPTC and XMP metadata, then you can disable it using IncludeMetaInformation option: In[1]:= \$Version Out[1]= "11.0.0 for Microsoft Windows (64-bit) (July 28, 2016)" In[2]:= RepeatedTiming[images = Import["f:\\SampleImages\*"];] Out[2]= {0.380, Null} In[3]:=...

9

This is a long comment. I can reproduce the problem on OS X with version 11.0.0. I have not found a fix. I know that image import was changed in version 11 for all common formats and that a lot of metadata is now imported. This metadata is also stored in the Image objects as the MetaInformation option (can be retrieved with Options). I don't know if the ...

8

As part of its algorithm, RandomPoint attempts to determine the region dimension by calling RegionDimension[region1] In version 10.4, the above gives up quickly without returning a result, and RandomPoint proceeds by using a heuristic estimate. But in version 11.0, RegionDimension tries harder to compute the dimension, which is a rather costly symbolic ...

8

1) The complete failure of Make Template with formatted usages is fixed in our next release. I can't promise you it will look 100% beautiful in all cases, but the number of templates will match the number in the usage message and you'll at least recognize it as something related to what you put in there. I'm sorry it's taken so long to be addressed--it ...

8

The answer to your question is in the error, NDSolve::ntdv: Cannot solve to find an explicit formula for the derivatives. Consider using the option Method->{"EquationSimplification"->"Residual"}. s = NDSolve[eqs, {θ3, θ4}, {t, 0, 50},MaxSteps -> 1000000000, Method -> {"EquationSimplification" -> "Residual"}]; Plot[{θ3[t], θ4[t]} /. s, {t, ...

8

I received a response from Wolfram Cutomer Support today regarding this question. The answer was to update to Version 12 !!! I think this is completely shameless. I have Version 11.3, which is Wolfarm's second most recent version of its software, which it apparently refuses to update even though Apple has long announced that 32-bit programs will not work. ...

7

My experience is different. As new versions come out, I think two things happen: Bugs in earlier versions generally (but not always) get fixed. In this sense, as time goes on, the number of bugs decreases, and Mma gets better and better with time. New functions are introduced. And when functions are new, there are always issues and quirks that need to get ...

7

WolframLanguageData has the answers you are looking for - specifically, versions in which symbols were introduced or modified! symbols = EntityValue[ "WolframLanguageSymbol", {"Name", "FullVersionsModified", "VersionIntroduced"}] This gives a list of the name of each symbol, the version numbers within which they were modified, and the versions in which ...

6

The difference arises when using Gridlines -> Automatic, so it might be a stretch to consider this a bug, since the behavior when using Automatic isn't necessarily expected to stay the same between versions. The version 11 behavior might actually be considered superior in this situation -- in version 10, when ticks are specified manually, the Automatic ...

5

See wolfram community : Here is the link

5

After looking at my personal use license installation of Mathematica 11, I was able to get wolframscript to run by modifying the the configuration file at %APPDATA%\Roaming\Wolfram\WolframScript.conf. Remove the comment prefix and add the path to wolfram.exe as follows: WOLFRAMSCRIPT_KERNELPATH=C:/Program Files/Wolfram Research/Mathematica/11.0/wolfram.exe ...

5

It seems that the Resource folder is not available in the cloud installation directory, which should contain the icon. But here is the icon from my installation.

5

See http://reference.wolfram.com/language/guide/SummaryOfNewFeaturesIn11.html and the related pages on the bottom. This will tell you that StringContainsQ has been altered going from 10 to 11. This is probably the cause of the problem. These pages seem to be the best sources on the changes (although they are not very good). (If someone knows a more ...

4

Please refer to: Prompt a set of possible options Make a backup, then open Reduce.m Edit it to read: {Cubics -> {"True", "False"}, GeneratedParameters -> {}, Quartics -> {"True", "False"}, Backsubstitution -> {"True", "False"}} Save the file Restart Mathematica Enjoy the result

4

I ran into the same problem and solved it by removing the configuration file associated with emojione-color. The font's substitution mechanism seemed to interfere with Mathematica's. Just fyi, the file I removed was /etc/fonts/conf.d/56-emojione-color.conf.

4

I can reproduce the problem on OS X with versions 10.0-11.1. It seems to happen because the default line cap setting is CapForm["Square"]. This means that each line segment making up the dashed line will visually extend beyond their endpoints. A fix that works on OS X is using CapForm["Butt"] which ensures that the line segments only extend to their ...

4

Try this DateListPlot[ Tooltip[#, {DateString[#[[1]], {"Month", "/", "Day", "/", "YearShort"}], #[[2]]}] & /@ pListCurrYr, PlotTheme -> "Classic", AspectRatio -> 0.8, PlotLabel -> Style[Framed[ "CME Block Cheese Prices from " <> DateString[pListCurrYr[[1, 1]], {"MonthName", " ", "DayShort"}] <> " to " &...

4

To explain the difference between the OP's and QuantumDot's comment examples, consider the V11 automatic exclusions expansions: VisualizationExpandExclusions[Re[PolyLog[2, 1/(1 - x)]], {x}, Automatic] (* OP *) VisualizationExpandExclusions[Re[Log[1/(1 - x)]], {x}, Automatic] (* comment *) (* {{Im[1/(1 - x)] == 0, Re[1/(1 - x)] >= 1}, {1 - x =...

4

Thanks to the commenters I now realize that the order of the values in GeoProjectionData has changed in V11, and that I should be directly using the projection name instead of indexing into the array. Here is code that works correctly in V11: Image[ GeoGraphics[ GeoModel -> Entity["PlanetaryMoon", "Moon"], GeoProjection -> "GallIsographic" ...

3

As of his writing the latest Nvidia driver is for Quadro K2100M is 377.11 (Enterprise) 378.66 (New Feature) However CUDADriverVersion is reporting 368.39 on your machine. Update to the latest Nvidia drivers. I have a laptop with both an Intel integrated GPU and a Nvidia GeForce GTX 860M. Although it is a newer card it can be said that NetTrain will work ...

3

Weird. I can sometimes reproduce this, but only on Windows, and only some of the time. If I take a cell which suffers from this, copy and paste it, and try again, it will disappear. This is a bug in the FE. The debug mode is implemented by wrapping pieces of the cell with an extra TagBox so the FE knows where to go when it stops. In the cases where it ...

3

In version 11.1.0 output is as in version 10.4.1: PlotRange /. AbsoluteOptions[Plot[Sin[x] x, {x, 0, \[Pi]}, PlotRange -> All]] {{6.41141*10^-8, 3.14159}, {4.11062*10^-15, 1.81971}} Here is output from version 11.0.1: PlotRange /. AbsoluteOptions[Plot[Sin[x] x, {x, 0, \[Pi]}, PlotRange -> All]] {{0., 1.}, {0., 1.}} So this particular feature ...

Only top voted, non community-wiki answers of a minimum length are eligible