Peter,
That looks good.
> Keoe is expected sometime in September 2006, and will consists of binary
> releases for key operating systems, although it will also be possible to
> download the tagged source files from the Starlink repository and build the
> Starlink elements of the release.
Can we say that its release will be announced on (at least) the STARMAN
and STARLINK lists? They may wonder where to look for further info.
> Applications
> ------------
>
> There are many changes to these, mostly supporting cube analysis, efficient
> data access and maintainability. Packages with major changes are, KAPPA,
> GAIA, CONVERT, DATACUBE, EXTRACTOR, SPLAT-VO and ORAC-DR.
>
> The release will also include all previous major Starlink packages, required
> by UKIRT and JCMT, i.e. FIGARO, POLPACK, CCDPACK, FLUXES, SPECX, SURF etc.,
> but note it will not contain any software that depends on licensed libraries,
> such as MEMSYS and NAG.
>
> It will also include the complete STARJAVA set of applications and libraries,
> notably TOPCAT (1.4), STILTS & TREEVIEW.
A mention of CUPID may be appropriate here since CUPID is completely new.
"An entirely new package called CUPID for identifying clumps of emission
in 1D, 2D or 3D data arrays has been included in the release. Whilst
primarily targetted at the needs of the SCUBA2 advanced data products
pipeline, it follows the Starlink pattern of being instrument-independent."
or some such thing...
> AST has had a lot of major new classes added such as
> TimeFrame, DSBSpecFrame, FluxFrame and SpecFluxFrame and support for
> representing IVOA Space-Time-Coordinate structures.
For the sake of clarity it may be best to avoid the use of class names.
So something like "AST has had a lot of major new classes added such as
Frames for describing time, dual-sideband spectra, and various flux
systems. It also now includes experimental support for representing IVOA
Space-Time-Coordinate regions, plus a variety of new Mappings."
> Support
> -------
>
> Everyone should be aware that full support can only be given to JACH users
> reducing JACH data. All others will be supported at a best-efforts level. Bug
> reports are welcome, patches even more so, as the long-term future clearly
> depends on larger contributions from a community of interested people. All
> reports should be made via the [log in to unmask] list. Developers use
> the [log in to unmask] list.
Is a note needed that support, even for JACH users, is only currently
funded until next summer? Just to avoid them feeling complacent about the
UK software situation.
David
|