I wonder a bit about the 10000 iterations, which, whereas this will certainly be accurate, it makes me wonder how you plan to output the results. The problems with too much accuracy are that it can't be rendered in an animation and there is of course no such thing as absolute accuracy for the Mandelbrot set. Some reasons to consider having less iterations (say 200 instead of 10000) include:

1) for a zoom sequence you will enhance the output to an arbitrarily greater accuracy anyway as you go along, (update: store the last term and iteration count for each seed and increase iteration count by say 8 iterations per frame for a 25 fps zoom, so that after the first frame, only 8 extra iterations are needed per member pixel; garbage collect zoomed-out seeds)

2) there is no point in having a greater accuracy than you can either render or see (as accuracy increases, the detail will tend to disappear when rendered, although too low iterations, e.g. only 50 would produce blotchiness) and raw numeric output has limited usefulness given the limitations of digital processing versus infinite detail

3) you want to stop iterating as soon as you practically can for performance reasons.

One world, one people

In reply to Re: Why openMP is not taken into account by XS and inline::C by anonymized user 468275
in thread Why openMP is not taken into account by XS and inline::C by jmricher70

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.