For instance, if I am not happy about the errorbar plots, I can execute the command "edit errorbar" to get an idea what I have to change. Like Mathematica, it also has some maddening idiosyncrasies and is mostly closed source, but it let's me inspect its high level functions. Over the years I have come to appreciate Matlab. > Conversely, does other software do better, on average, in 'doing what one wants'? Which software? Classify and Predict, or FormFunction, or Interpreter, or Nearest? Do those all not do quite what you need?Ĭertainly, there are many functions that do what I need - but in my experience, the "higher" the level of the function is, the smaller the chances that it fullfills my needs. > 'Never' seems like quite a generalization. So at least this bug will only have been around for 0.0.2 versions :-) Unfortunate, but fixed within a day of being reported! 10.0.2 has passed many weeks of SQA and will ship shortly. Either way, Alpha shouldn't change its interpretation from under you, that's definitely a bug. But the distinction is apparently important, although I don't want to "get you started" :-). ![]() I think Quantities should probably gain a little box, like DateObjects have, that lets you mouse-over for more information, which should make this problem easier to diagnose. Kelvins thing, which are both represented by the same symbol to maximize your confusion when your unit conversions are failing. > Don't get me started on the KelvinsDifference vs. Although it is frustrating you can't just go in there and tweak the source code yourself, I agree. Anyway, clearly DateListPlot should learn about error bars, and I'm sure in a year or two it will. And having users report to us what they want lets us prioritize those things. Still, the scope of visualization functionality is so vast that it's not surprising there are gaps (which we continue to plug, the whole language is a never ending project). My pet peeve, for example, is that it is unnecessarily difficult to map colors and sizes onto graph vertices based on vertex properties, which I needed to do for. There are gaps, definitely, one small example you've pointed out. Classify and Predict, or FormFunction, or Interpreter, or Nearest? Do those all not do quite what you need? Conversely, does other software do better, on average, in 'doing what one wants'? Which software? 'Never' seems like quite a generalization. time with errorbars around the data? Sorry, no function for this completely exotic use case, please hack a DateListPlot on top of an ErrorListPlot. > The high level functions, while nice for demos, never quite do what you need. Don't get me started on the KelvinsDifference vs. A few weeks ago it evaluated to "1 KelvinsDifference", but now has changed to "1 Kelvins". However is interpreted "transparently" by Wolfram Alpha. Is interpreted by Mathematica itself and yields an object equivalent to "1 Kelvins". And, if I want to impress someone, for demos. Now I vowed to use it only for small hacks. community, I would have quit Mathematica completely. Had it not been for the awesome support by the mathematica. Currently I am battling file corruption of notebooks that are saved on network drives and open while the drive is disattached/reattached. The bugs I encountered were severe: One of the output function swallows the "-" sign if the result is between -1 and 0. This interpretation can change any day and leaves you guessing why your notebook doesn't run anymore. The WolframAlpha integration "transparently" interprets code for you in the background. ![]() The high level functions, while nice for demos, never quite do what you need. But I recently tried to get actual work done with Mathematica and found the experience utterly ridiculous.
0 Comments
Leave a Reply. |