> Unlike Java which makes documentation hard, POD means that yes, it's
> fully documented.
Including overview and tutorial information? My experience is that such
systems (like man pages) often don't encourage the inclusion of such
information.
> We still haven't gotten round to FITS binary tables.
That's essential for astronomical catalogues.
> 2MASS, CMC, GSC, MPC, SIMBAD, Sesame, SuperCOSMOS, USNO-A2
>
> along with "generic" SkyCat and Vizier interfaces which may or may not
> do everything you need depending on which catalogue your querying.
That's good.
> That would be about twenty lines of Perl sitting ontop of the
> Astro::Catalog module. Although I've not heard of "Persson", you'd have
Eric Persson was a pioneer of infrared photometry of galaxies. He has
his own list of JHK standards, the total number being similar to that in
the UKIRT Faint Standards list. ESO and CTIO/Magellan use the Persson
list.
> to add your own Query class to the distribution first. This isn't hard
> as all you need to do is write a skeleton class ontop of a couple of
> inherited classes (it does funky perl multiple inheritance) if you're
> lucky.
If there are examples to work from, that would be good.
Malcolm5A
|