Tag Info

New answers tagged

3

If you add this to your KeyEventTranslations.tr file it works on Linux (I only tested english keyboard layout): Item[KeyEvent["}", Modifiers -> {Command, Shift}], FrontEndExecute[{ FrontEnd`NotebookWrite[FrontEnd`InputNotebook[], "{", After], FrontEnd`NotebookWrite[FrontEnd`InputNotebook[], "}", Before] }] ], ...


3

Response from support@wolfram.com: Thanks for contacting Wolfram Technical Support and for taking the time to send in the report. This is indeed a wrong behaviour of HighlightImage, specifically for how it deals with regions. I've filed an incidence report and I will keep you posted for any updates on this issue. Thanks again for bringing the issue ...


4

DiscretizeRegion will work in place of ToElementMesh: Jet0[pts_: {{1, 0}, {1.8, 1.8}, {0, 2}}] := Module[{xu, yu, n, m, knots, fx, fy, pr, t, r}, {xu, yu} = Transpose[pts]; n = 2; m = Length[pts]; knots = {ConstantArray[0, n + 1], Range[m - n - 1]/(m - n), ConstantArray[1, n + 1]} // Flatten; fx[t_] = xu.Table[BSplineBasis[{n, knots}, i - 1, ...


5

There is a workaround involving Rationalize. Jet0[pts0_: {{1, 0}, {1.8, 1.8}, {0, 2}}] := Module[{xu, yu, n, m, knots, fx, fy, pr, mesh, t, r}, pts=Rationalize[pts0,0.001]; {xu, yu} = Transpose[pts]; n = 2; m = Length[pts]; knots = {ConstantArray[0, n + 1], Range[m - n - 1]/(m - n), ConstantArray[1, n + 1]} // Flatten; fx[t_] = ...


6

Although this is hardly a debilitating bug I wondered what else might be affected so I decided to trace this further. I found that the bug affects TreeForm by way of TreePlot. Here is a reduced example of the call that originates in the exhibit above: TreePlot[{1 -> 2, 1 -> 3, 1 -> 4}, Top, 1, "VertexNames" -> {List, HoldForm["foo"], ...


4

With Guess who it is' idea, there is a temporary workaround to convert population data to lists and make it work with FindFormula. Assume data has been set like in the question. data2 = Transpose[{(AbsoluteTime /@ List /@ Range[First@#[[1]], First@#[[2]], First@#[[3]]]) &[#[[2]]], #[[1]]}] &[ Flatten[data[[2]][[1 ;; 2]], 1]]; ...


3

I completely agree with halirutan about the worth of a bug tracker system for Mathematica, it is something very useful for developers like us, which spend almost every day on Mathematica. In my experience (about 20 years) of Mathematica's evangelism, I met very few people which were negatively influenced by bugs. Generally speaking, who works with software ...


1

This bug has been fixed partially fixed as of version 10.2.0.


3

As mentioned by user21 in the comments, this bug has been fixed as of version 10.1.0. Table[(RegionUnion[Disk[{0, 0}, 1, {0, Pi}], Disk[{1/2, 0}, 1/2]] // RegionDifference[#,RegionUnion[Disk[{1/2, 0}, 1/6], Disk[{-1/2, 0}, 1/2]]] &) // DiscretizeRegion // AbsoluteTiming // First, {100}] // Mean (* 0.142127 *)


1

neat little work-around, poly[x_] = Normal[Series[E^x, {x, 0, 10}]]; LogPlot[(Abs[E^# - poly[#]] &@N[Rationalize[x, 0], 20]), {x, -1, 1}]


14

The problem appears to be due to a v10.2 bug in the Dataset visualization code that generates the box form of a dataset. It is not correctly distinguishing between Dataset being used as a constructor function and Dataset being used as the head of a constructed dataset. It assumes the latter case unconditionally, giving the exhibited messages for the former ...


8

A work around seems to be to not have Dataset as the first Head encountered... toDataset[table_List]:=Dataset@@{Association/@(Function[r,Thread[First[r]->#]&/@Rest[r]]@table)}; So the first Head the parser sees is Apply and not Dataset.


2

Although Szabolcs warned "I don't think it's worth digging into how LogPlot works, as at this point this clearly seems to be a bug" I thought I would give a go. I found that: System`LogPlot calls Graphics`LogPlotDump`scaledPlot which calls System`Plot which calls System`ProtoPlotDump`iPlot which calls Visualization`Core`Plot which is not readable. We can ...


0

With LogLogPlot[..., WorkingPrecision->_] (or indeed LogPlot[..., WorkingPrecision->_]), what is plotted is in fact the exponential of the function. As a workaround (assuming that's what you're looking for), you can use LogLogPlot[Evaluate@Log[{1/10, 1, 2, 3}], {p, 0.1, 10000}, PlotLegends -> "Expressions", WorkingPrecision -> 16] which ...


9

This is a documentation bug. Our source notebooks do contain documentation for experimental and future features, but they are supposed to be stripped in the process of being bundled with the product. In this case the bug is that the usage statement is marked as not to be included, but is still ending up in the built documentation. We apologize for the ...


4

Posting ilian's comment as an answer. This bug has been fixed in version 10.2.0. $Version Union[<|a -> 1|>, <|a -> 2|>] (* "10.2.0 for Linux x86 (64-bit) (July 6, 2015)" *) (* <|a -> 1|> \[Union] <|a -> 2|> *)


3

To convert my comment into an answer, this bug has been fixed as of version 10.1.0.


1

Summarizing the comments, this bug has been fixed as of version 10.0.1. Limit[(Log[(3+Sqrt[5])/2]/(2*Log[(1+Sqrt[5])/2]))^(-1-2*n), n -> Infinity] (* 1 *)


2

[This is what Wolfram tech support told me when I filed a bug report:] That is because using machine precision (inexact) numbers such 0. (as opposed to exact numbers like 0) forces Eigenvectors[] to seach for eigenvectors numerically and hence the error message. For example, please evaluate and compare the results of the following expression used with ...


1

This bug has been fixed as of version 10.2.0. The example now returns unevaluated without any messages. Integrate[Cos[Sin[x]]^n, {x, 0, Pi}] // InputForm (* Integrate[Cos[Sin[x]]^n, {x, 0, Pi}] *)


5

This bug has been fixed as of version 10.2.0. g[k2_] := (-510 k2 + (25761/4 - 6619 E^-k2) Log[26476/23721])/(-k2 + Log[26476/23721]) ans = Solve[g[k2] == 0, k2, Reals][[1, 1, 2]]; FullSimplify[ans] (* 8587/680 Log[26476/23721] + ProductLog[-(( 10579732023355105126853211737189792087286301059526347 (23721/ 6619)^(427/680) Log[26476/23721])/( ...


1

This issue has been fixed as of version 10.2.0. NIntegrate[1, x ∈ ImplicitRegion[(x > 5 && x < 9) || (x > 11 && x < 13), {x}], Method -> "MonteCarlo"] (* 6.06192 *) The syntax is fine, since x is taken to be a vector variable, similarly to NIntegrate[1, x ∈ Ball[]]


1

Simplify@Eigenvectors[{{Cos[0. + x], Exp[I x]}, {1, 0}}] $\left( \begin{array}{cc} e^{-1. i x} \left(-0.25 \sqrt{1.+2. e^{2 i x}+16. e^{3 i x}+e^{4 i x}}+0.25 e^{2. i x}+0.25\right) & 1. \\ 0.25 e^{-1. i x} \left(\sqrt{1.+2. e^{2 i x}+16. e^{3 i x}+e^{4 i x}}+e^{2. i x}+1.\right) & 1. \end{array} \right)$


3

Until this is fixed in a future version, here is a workaround for now: Unprotect[RegionBoundary]; RegionBoundary /: Area @ RegionBoundary @ SphericalShell[c_, {ri_, r_}] := Area @ Sphere[c, r] + Area @ Sphere[c, ri]; RegionBoundary /: Area @ RegionBoundary @ CapsuleShape[{v1_, v2_}, r_] := 2 π r (2 r + ...


11

how to reproduce the default hashing behaviour when explicitly choosing a method In[1]:= Hash[1, "Expression"] Out[1]= 6568131406215528669 re-create the default hashing behaviour in different versions? Not possible as far as I know. The one-argument Hash implementation may change between versions. The algorithm has been most ...


5

Summarizing the comments, this was a bug in version 10.0.0. It has been fixed as of version 10.0.1. In[1]:= Integrate[ DiracDelta[x]*DiracDelta[y], {x, -Infinity, Infinity}, {y, -Infinity, Infinity}] Out[1]= 1


5

To turn my comment into an answer, this seems to be an evaluation leak coming from the Predictive Interface. I've let the appropriate developers know and they will look into it. A workaround for now would be to turn off the Suggestions bar.


0

As recommended in comment by @ilian acap = Area@ RegionBoundary@DiscretizeRegion@CapsuleShape[{{-1, 0, 0}, {1, 0, 0}}, 1] 25.0897 Round[acap/Pi, 1/10]*Pi 8 Pi ashell = Area@ RegionBoundary@DiscretizeRegion@SphericalShell[{0, 0, 0}, {3, 4}] 313.472 Round[ashell/Pi]*Pi 100 Pi


7

No crash with version 10.2 on Win7 x64 but there definitely is a bug: Here is how the graph is displayed in the FrontEnd: Show[Plot[x, {x, 0, 1}], Graphics[{Rotate[Text[Style["test", 60], {.5, .5}], \[Pi]/4]}]] And here is how the Exported PDF is rendered by Acrobat 11.0.12 (other PDF viewers show the same):


9

A simple workaround is to re-build the graph object by cycling it through some other representation. Here are two possible solutions: rebuildGraph[g_] := Uncompress@Compress[g] (* solution 1 *) rebuildGraph[g_] := Graph[VertexList[g], EdgeList[g]] (* solution 2 destroys properties but it's fine for isomorphism testing purposes *) isomorphicGraphQ[g1_, ...


4

On my system (OS X 10.10.4) it doesn't even display correctly on-screen. This means that rasterization doesn't help. I can confirm the problem in 10.0.2, 10.1.0 and 10.2.0. The problem doesn't exist in 9.0.1. We can trace back this problem to a BezierCurve bug. gr = Show@Graph[{1 <-> 1, 1 <-> 2}, EdgeShapeFunction -> "Line", ...


2

This appears to be fixed in 10.1.0: Integrate[1/(a^2 + b^2 - 2 a b Cos[t]), {t, 0, 2 Pi}, Assumptions -> {a > b > 0}] (* (2 π)/(a^2 - b^2) *) Integrate[1/(a^2 + b^2 - 2 a b Cos[t + t0]), {t, 0, 2 Pi}, Assumptions -> {a > b > 0}] (* ConditionalExpression[(2 π)/(a^2 - b^2), -3 π <= Re[t0] <= -π && Im[t0] == 0] *)


3

This is an issue similar to the one discussed here, as part of the type system operations discussed here. In the case at hand, there are two distinct problems. The first is that in some cases the type system is too restrictive in that it will not accept unrestricted negative index arguments to StringTake. The second is that some forms of association key ...


5

Update This problem has been fixed by a paclet update -- specifically version 10.2.1 of the GeneralUtilities paclet: PacletFind["GeneralUtilities"] // PacletInformation // GeneralUtilities`ToAssociations // Dataset In chat, Arnoud Buzing stated that this patch will normally be loaded automatically during the weekly paclet update. He also offered the ...


5

(Reposting my comment as an answer to take the question off the unanswered list). This Linux-specific crash has been fixed as of version 10.1.0.


5

(Reposting my comment as an answer, just to take the question off the unanswered list) This is a bug and has been fixed in version 10.2. I am not aware of any workarounds that may be applicable in earlier versions.


6

This is a bug (up until version 10.2) in the interpolation code when there are concave curved elements for unstructured query points. Workaround: To work around it one can use the either a "MeshOrder"->1 or set the "ImproveBoundaryPosition"->False both of these get rid of the spikes. Do[ r = 1; rct = Rectangle[{0, 0}, {10, 10}]; rnd[n_Integer] := ...


6

This crash has been fixed in version 10.2. In[1]:= if = NDSolveValue[{D[u[t, x, y, z], t] == 0, u[0, x, y, z] == 0}, u, {x, y, z} \[Element] Ball[], {t, 0, 1}, Method -> "FiniteElement"]; In[2]:= Export["if.wdx", if]; ...


3

Interesting, doing nearly the same thing as @BobHanlon: clist = CoefficientList[ Normal@Series[Log[1/2 (1 + Sqrt[1 - x])], {x, 0, 12}], x]; FindSequenceFunction[clist, n] yields a (Correct) DifferenceRoot expression: DifferenceRoot[ Function[{[FormalY], [FormalN]}, {(-1 + 3 [FormalN] - 2 [FormalN]^2) [FormalY][[FormalN]] + ...


9

Here is a workaround: f[x_] = Log[1/2 (1 + Sqrt[1 - x])]; Generate a sequence from several of the coefficients seq = Table[ SeriesCoefficient[f[x], {x, 0, n}], {n, 8}]; Find the function that generates that sequence coef[n_] = FindSequenceFunction[seq, n] // FullSimplify -(Pochhammer[3/2, -1 + n]/ (4*n*Gamma[1 + n])) For an ...


8

This bug has been fixed in version 10.2. $Version (* "10.2.0 for Linux x86 (64-bit) (July 6, 2015)" *) matchLists[patt_] := MatchQ[#, patt] & /@ {{}, {1}, {1, 2}, {1, 2, 3}, {1, 2, 3, 4}} matchLists[{_ | PatternSequence[]}] matchLists[{x_ | PatternSequence[]}] (* {True, True, False, False, False} *) (* {True, True, False, False, False} *) ...


3

I have found a simple method to mitigate the limit bug: using an intermediate Series[], the Dirichlet coefficients of a function f[x] can be calculated correctly as a Limit[]. The formulas for the coefficients are cD := Module[{}, a[1] = Limit[f[x], x -> ∞]; a[n_] := a[n] = Limit[ Series[n^x (f[x] - Sum[a[k] k^-x, {k, 1, n - 1}]), {x, ∞, ...


6

As mentioned by user21 in the comments, this is now fixed in version 10.2. In[1]:= MinMax[{0.2`, 0.375`, 0.55`, 0.7250000000000001`, 0.9000000000000001`, 1.`, 0.2`, 0.9`, 1}] Out[1]= {0.2, 1.} In[2]:= Needs["NDSolve`FEM`"] In[3]:= MinMax[{0.2`, 0.375`, 0.55`, 0.7250000000000001`, 0.9000000000000001`, 1.`, 0.2`, 0.9`, ...


6

Ilian mentioned that this is fixed in newer version of Mathematica, but if you are not able to update, the following helper function may be of help: toFor[c_] := "(" <> ToString[Re[c]] <> "," <> ToString[Im[c]] <> ")" numbers = RandomComplex[10 + 10 I, 100]; Export["file.in", toFor /@ numbers, "Table"] This exports a list of ...


2

This issue has been fixed in 10.1+


0

Answering to drop this off the list. This still works in 10.2: In[18]:= Remove["Global`*"] Plot[y, {y, -1, 1}]; Names["Global`*"] Out[20]= {"y"}


12

As a stop-gap, one can use Block to turn off Print: Block[{Print}, ds[Transpose]]


9

Now fixed in version 10.2. In[1]:= m = {{0, 1}, {-1, 0}}; In[2]:= {AntihermitianMatrixQ[m], HermitianMatrixQ[m], AntihermitianMatrixQ[m]} Out[2]= {True, False, True} As per the comments, yes, there is information stored in the internal representation of matrices (for example, a symmetry flag) and no, it is not accessible from top level code.


4

Now fixed in version 10.2. In[1]:= Residue[LogisticSigmoid[z], {z, I Pi}] Out[1]= 1 In[2]:= Residue[1/(1 + Exp[-z]), {z, I Pi}] Out[2]= 1 In[3]:= Coefficient[Series[1/(1 + Exp[-z]), {z, I Pi, 0}], 1/(z - I Pi)] Out[3]= 1


7

Now fixed in version 10.2. In[1]:= Catch[NIntegrate[ 1, {x, y} \[Element] Triangle[{{0, 0}, {1, 2}, {2, 1}}], Method -> "MonteCarlo", EvaluationMonitor :> Throw[{x, y}]]] Out[1]= {0.615426, 0.793388} There is also RandomPoint: In[2]:= ...



Top 50 recent answers are included