Others have already answered the actual question ...

But in part, because I'm a bit of a file-formats snob, and in part because I've been dealing with an e-mail discussion for the last month or so on trying to come up with standards on describing these sort of text files as used in space physics for time tagged data for event lists (vs. time series at a fixed cadence) ... as you mention you're in the astronomy field, have you considered spitting out VOTable? None of the perl libraries comply with the 1.2 spec unfortunately (and only the version in Astro::Catalog is actually in CPAN), but you should then be able to hand off the plotting work to dedicated tools like VOPlot (docs/examples).

(and I say this *only* because you're in astronomy; if you were in earth sciences, I'd recommend HDF; CDF for space physics; NetCDF for storage for atmospheric sciences (with an OPeNDAP service for distribution). There's also Google's Dataset Publishing Language to document CSV files so that some of Google's tools can be used to visualize them, and there's lots of other standards out there for all of the various javascript visualization tools.


In reply to Re: Base script behavior on presence (or non-) of a module by jhourcle
in thread Base script behavior on presence (or non-) of a module by chexmix

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.