@J.M. I don't know why, but reading it I reminded me of an old anecdote. An old physics prof was asked why Latin was prevalent in science books when it has been already a "dead" language for many years. And he answered "They wanted knowledge in the hands of those able to read, for example, history".
Mac users, if you find you cannot use CompilationTarget -> "C" anymore, this is probably because you downloaded new Xcode command line tools and you have yet to agree with the license. In order to agree, simply start Xcode and agree. Clang also suggested I run it under sudo to accept the license (in case you don't have Xcode, but somehow do have the tools).
@ShutaoTANG One way of solving them is through discretization on a grid. That leads to the problem of solving large, banded linear systems.
Sometimes, one enforces periodicity in the solution, like in wave-related equations. That leads to the problem you presented.
After folding over, you might end up with entries in the lower left corner, upper right corner, or both (depending on the details). That's how you enforce the periodicity.
@ShutaoTANG I hope you now appreciate the effort that goes into writing mathematical programs; you really can't avoid experimenting and making mistakes.
Mathematica is really a huge huge system. It's just impossible to know each function. I still keep finding very basic functions that I didn't know of. If people asked about those, they would get reprimanded and their question would immediately get closed as "easily found in the documentation". But it's not really that easy!
We should be more tolerant with these question.
So now here's my naive question that I'm embarrassed to post on the main site.
Histogram is bloody slow so I'm forced to use alternatives such as BinCounts or LibraryLink functions. My end goal is a visualization like that output by Histogram. Is there a simple way to get from something like the output of HistogramList to the graphics Histogram would produce?
Requirement: 1. Bin boundaries must have correct plot coordinates 2. I need both linear and logarithmic vertical scales.
Building from Rectangles and handling the log case, plus figuring out the best lower boundary for the bars in the logarithmic case is a lot of work and it's painful. I don't see how this can be done in 2 minutes. But I really hope I just missed some simple builtins (like when I missed the ScalingFunctions option of BarCharts).
@Szabolcs Some fiddling around with ChartElementFunction seems to be the only way to position bars. But, you've seen that HistogramList[] can do logarithmic binning?
@J.M. The binning I use is uniform. It is the vertical scale that needs to be logarithmic. For good visualization, this mean having to use log-ticks and having to automaticlly select a reasonable bar-origin (which is flexible for log-plots). It's just the visualization part that right now seems like a lot of work.
@Szabolcs In that case, nothing looks obvious to me, even after combing through the docs of BarChart[] and HistogramList[]. :( Maybe risk some embarrassment and ask it on main?
I have a large data set consisting of $\mathcal{O}(10^9)$ two-dimensional points. In order to save memory and time I have pre-binned these into a uniform grid of $500 \times 500$ bins using Fortran. When imported into Mathematica 8.0 as a table the resulting data look like:
data = {{0.3883...
I would love it if it said in the docs whether any given syntactic-sugar function was optimised in any way. SubstitutionSystem, for example, is just a wrapper to a NestList, according to PrintDefinitions.
I have a 2013 Retina MacBook Pro, and I really want to install Debian on it. I have the know-how and have had at least three Debian systems before this. I am very knowledgable with the command-line and Linux's inner workings, and partitioning isn't an issue for me. So, I just have one question be...
@belisariusisforth You could golf it further with AnglePath[] in 10.2 and later. I know you're on 9, but I did write an equivalent for older versions. :)
My version is
In[2]:= $Version
Out[2]= "10.3.0 for Microsoft Windows (64-bit) (October 9, 2015)"
A fun thing that I think it is.The bug is introduced in 10.0.0,but it's still now.You can reproduce it via use any button in Image-Tool like this:
The Mathematica will pop up a error message win...
Of course this is not the place to report bugs. We're not Wolfram.
But then I don't want a clearly spelt out policy about disallowing this either, for many reasons ... it's very easy to get into a blurry territory between a bug report, a question about whether it is a bug and asking for workarounds. Just knowing about some bugs can be useful too sometimes. Still, this is not even a question, and when posted like this I see no other choice than to close it.
Then there's another thing: I'm sure many people use a pirated version (especially students in developing countries like China where piracy is rampant and universities won't or can't purchase a license ...) They can't contact support. But it's still best if WRI learns about all bugs. I'm hoping people wanting to do this will go to W Community instead of SE though.
the (ahem) joke is that it's a log, which is slower than any polynomial. ha-ha.
@J.M. When I read things like
> Some Apple hardware has been known to have issues under ALL other operating systems (not just Linux Kernel based ones) - due to Apple's proprietary hardware and more specifically their proprietary fan controllers
I just want to pick my monitor up and start banging it against the wall in a rage until it breaks up into small pieces, then burn them.
@JacobAkkerboom I know. I guess is the classic XY problem. I have the list {a1,{b1,b2,{c1,c2,c3}}} and I'd like to view it as a tree. I've tried TreeForm but it displays all the headers.
@Szabolcs There is nothing preventing anyone from contacting support. You can file a bug report without giving a license number or activation key
4
Very often, people will send an email that's somewhere inbetween asking for help and reporting an issue. That you can't do without an actual activation key. But if you want to report a bug, you just have to send an email to [email protected] and say "hey I think this is a bug"