Tag Info

Hot answers tagged

15

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 ...


12

There is the as yet undocumented FEM function (see this answer, or read the user-interface with Definition after clearing the ReadProtected attribute) ElementMeshPlot3D[valuesOnMeshCoordinates, elementMesh, options] We can use this to plot the surface (note Head[slv] is just the pure InterpolatingFunction of the solution so we can apply to methods; see ...


12

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


12

how to reproduce the default hashing behaviour when explicitly choosing a method Hash[1, "Expression"] (* 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 recently ...


11

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"], ...


10

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 ...


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_, ...


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.


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 ...


9

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.


9

Somehow the AbsolutThickness you specified gets replaced by a default value of AbsoluteThickness[0.2]. This misbehavior can be corrected by replacing the incorrect value with your specification. Needs["GeneralUtilities`"] PlotLegends; (*preload definitions*) Cell[BoxData[ MakePasteBox@ BarLegend[{"SunsetColors", {0, 1}}, LabelStyle -> ...


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} *) ...


8

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 ...


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):


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]:= ...


7

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

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 ...


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]; ...


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.


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.


5

The solution or rather "fix" to the problem seems to be to raise the MaxPlotPoints: data = RandomReal[{0, 1}, {21, 500}]; MatrixPlot[ data, AspectRatio -> Full, FrameTicks -> Automatic, ColorFunction -> (Hue[1 - #] &), ColorFunctionScaling -> True, MeshStyle -> Blue, Mesh -> {Table[j, {j, 0, 25, 5}], ...


5

This started out as a long comment, but in the meantime I think I found the solution to this problem which is clearly a bug in MatrixPlot. My initial analysis follows and the conclusion and a solution are at the bottom. First, this is not typical to 10.1. I see identical behavior in versions 8 and 9. Second, your example can be simplified to reduce the ...


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])/( ...


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_] = ...


5

The workaround is to put an \[InvisibleSpace] between the degree symbol and the C. Plot[x, {x, 0, 1}, FrameLabel -> {"x", "temperature / \[Degree]\[InvisibleSpace]C"}, Frame -> True] Note that the ImagePadding isn't very good in this case, but the C does indeed have the right baseline.


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


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", ...



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