Hot answers tagged

13

The difference between your two examples is that one uses packed arrays and the other doesn't. The lists generated by Range are, by default, packed. << Developer` PackedArrayQ /@ {{1, 2, 3, 4}, Range[4]} (* {False, True} *) There is a bug, where if the sublists in the array fed to TreeForm are packed, then the function doesn't behave properly: ...


8

I think the problem is sloppy documentation, rather than an implementation bug. A lot of current documentation is incomplete, misleading, or just plain wrong. Here is another example of bad documentation taken from HighlightImage. The following wrappers can be used ... $\qquad$Tooltip[e, label] attach an arbitrary tooltip to the element But ...


5

The behavioral discrepancy can be shown with a very simple example. assoc = <|1 -> 1, 2 -> 2|>; {KeyTake[assoc, 1], KeyTake[assoc, Key[1]], KeyTake[assoc, Key[1][assoc]]} {<|1 -> 1|>, <||>, <|1 -> 1|>} {KeyDrop[assoc, 1], KeyDrop[assoc, Key[1]], KeyDrop[assoc, Key[1][assoc]]} {<|2 -> 2|>, <|2 -> ...


5

I tested on 10.2 and 10.4. I recommend just using the tick labels from some other plot and overlaying the data using Show. With minimal changes to your example I got following proof of principle. plist = {#, 1. Log[#! + 1]} & /@ {.1, .5, 1, 5, 10, 50, 100, 500, 1000, 5000, 10000, 50000, 100000}; Show[{LogLogPlot[0, {x, .1, 10^5}, PlotRange -&...


4

Here is one way to convert the ticks into the desired format: ListLogLogPlot[plist, PlotRange -> {{.1, 10^5}, {10^-1, 10^6}}, Joined -> True] /. {v_, t_?NumberQ, l1_, {AbsoluteThickness[0.1]}} :> {v, NumberForm[N@t, NumberFormat -> (Superscript[#2, #3] &), ExponentFunction -> (# &)], l1, {AbsoluteThickness[0.1]}} With ...


4

This IS NOT A BUG but do IS A BUG as well. This is not a BUG at first, but I found a serious BUG while trying to persuade @yode it's not a BUG. I think I've got an explanation for this problem: First thing first, Let's first check our documentation: It said that when setting EdgeCost to Automatic cost per unit flow on an edge is taken to be 1. Thus we ...


4

This turns out to be a bug since v9. v8.0.4 gives the correct result: $Version eqn = D[x[t], t] == a*x[t] + c*t^n; bc = x[0] == x0; sol = Simplify[DSolve[{eqn, bc}, x[t], t], {a > 0, n >= 1, c > 0}] (* "8.0 for Microsoft Windows (64-bit) (October 24, 2011)" *) (* {{x[t] -> a^(-1 - n) E^(a t) (a^(1 + n) x0 + c Gamma[1 + n] - c Gamma[1 + n, a t])}}...


4

It is a bug that the local variable c isn't shared with Condition when the latter appears at the LHS outside of the KeyValuePattern. The following simplified examples demonstrate the bug: gfail1[KeyValuePattern@{"c" -> c_}] /; c == 0 := 0 gfail2[KeyValuePattern@{"c" -> c_} /; c == 0] := 0 gfail1[<|"c" -> 0|>] gfail2[<|"c" -> 0|>] ...


3

$Version (* "10.4.1 for Mac OS X x86 (64-bit) (April 11, 2016)" *) Let m = <pastebin monster>. ns1 = NullSpace[m]; ns2 = NullSpace[m, Method -> "OneStepRowReduction"]; diff = ns1 - ns2; RootReduce[diff] (* {{0, 0, 0, 0, 0, 0, 0, 0}} *) So they're equivalent in V10.4.1. Update: Checking correctness After many minutes, this returns ...


2

This has been confirmed as a bug by Wolfram support.


2

What is the bug? It seems that GeoRegionValuePlot will not work correctly when two or more entities have the exact same value. Consider these examples (and ignore the legend, which is always wrong unless you give an explicit ColorFunction as below): GeoRegionValuePlot[{Entity[ "AdministrativeDivision", {"Arkansas", "UnitedStates"}] -> 1, Entity["...


2

(All observations apply to version 10.1.0.) ErrorListPlot is written in as a rather straightforward post-processing of ListPlot, with error bar values first assigned to and then retrieved from a definition upon ErrorBarPlots`Private`error (hereafter notated error). A definition is made as a side-effect within a replacement rule: {x_?NumericQ, y_?NumericQ, ...


2

The workaround given in comments works. You should set CacheGraphics->False. i.e. Button[ Style[ SetAlphaChannel[ Graphics@Rectangle[], Graphics@Disk[]], CacheGraphics -> False ], Print[1] ] – ihojnicki Jul 13 at 19:59 One can put it in BaseStyle -> {CacheGraphics -> False} too.


2

Consider test[p : KeyValuePattern@{"c" -> c_List}] /; First[p["c"]] == 0 := $Succeeded test[p : KeyValuePattern@{"c" -> c_List}] := $Failed then test[<|"c" -> {0, 1}|>] $Succeeded test[<|"c" -> {1, 1}|>] $Failed Perhaps that is form you are looking for.


2

Using custom tick labels still works, but one has to use the logarithmic label position, as this conversion is no longer done automatically for custom tick labels. ListLogLogPlot[plist, PlotRange -> {{.1, 10^5}, {10^-1, 10^6}}, Ticks -> {Table[{N@Log[10^i], Superscript[10, i]}, {i, -1, 5}], Table[{N@Log[10^i], Superscript[10, i]}, {i, -1,...


1

That's a funky bug. As JasonB points out in the comments, this can be reduced to a two-country example: GeoRegionValuePlot[ { Entity["Country", "UnitedStates"] -> -1, Entity["Country", "India"] -> 0 } , GeoRange -> {{-60, 75}, {-130, 165}} , ColorFunctionScaling -> False , ColorFunction -> (Blend[{{-1, Red}, {0, Yellow}}, #] &) ...


1

This appears to be a bug. Histogram shows result of 100K RV on PascalDistribution[1,1/50] for 100k batch using RandomVariate[...,100000] (blue) and generating a table of 100k single calls (default chicken-poop-and-mud jaundice beige): Thanks to Karsten for verification and Jim for histogram idea.


1

In the t1 case Random`DistributionVector[PascalDistribution[1, 1/50], 10000, ∞] is evaluated and in the t2 case Random`DistributionVector[PascalDistribution[1, 1/50], 10, ∞] The definition of this function contains a Which statement. Its first test is True for 10000 and False for 10. Its second test (there are only two) is True. For your parameters ...


1

Just an extended comment: Rather than a consistent shift for the values in the minimum values for t2, it appears that the distribution is completely different than for t1, t3, and t4. Here's a figure showing that: h[x_, label_] := Histogram[Min /@ x, {1}, "PDF", PlotRange -> {{0, 30}, {0, 0.20}}, PlotLabel -> Style[label, Bold, Larger]] ...



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