Strawman?

Hardly.

The age old problem with first (and second) deritives -- along with many other numerical methods -- is that they have a tendency to discover values that don't exist in the dataset. Ie. calculated values that fall between the discrete values that are actually in the dataset.

Whilst this is fine for theoretical discussion -- rounded to some number of sig.fig. -- it leaves real-world applications with the need to fall back upon heuristics -- ie. guesses -- in order to "correct" calculated values and align them with the actual data.

Imagine the dataset represents clock-speed (or power drain) from a deep-bin sort of newly minted cpus. -- ie. when cpus are manufactured, there is some considerable variability in their electrical performance; and manufacturers can sort the parts by their actual performance, and charge premium prices for the better ones.

In the many all-too-real scenarios like this that crop up in manufacturing every day, having calculated maxima and minima that fall at theoretical points on the curve; between the actual values that are there, isn't very useful for the selection processes that are the reason for performing the calculation in the first place.

So no, not a strawman. A legitimate and relevant discussion in context.

I accept that my original graph was, as presented, difficult to interpret. But I anticipated that anyone interested would

  1. produce their own graph to verify the accuracy of my quick plots and conclusions.

    Which you did.

  2. Inspect their own plots carefully and notice the obvious discrepancies that I noticed in mine.

    Which you did not.

That's the trouble with "pretty graphs". People get so impressed by the pictures, they forget to inspect them closely and take note of why they produced them in the first place.


With the rise and rise of 'Social' network sites: 'Computers are making people easier to use everyday'
Examine what is said, not who speaks -- Silence betokens consent -- Love the truth but pardon error.
"Science is about questioning the status quo. Questioning authority".
In the absence of evidence, opinion is indistinguishable from prejudice.

The start of some sanity?


In reply to Re^9: Any idea for predicting the peak points in the graph by perl by BrowserUk
in thread Any idea for predicting the peak points in the graph by perl by Anonymous Monk

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.