I know replying to oneself is bad, but a cursory glance at ircampack
indicates that there are only two commands provided that are not part of
kappa. The following actions exist:
calpol.ifl KAPPA
errclip.ifl KAPPA
ircamset.ifl IRCAM-specific
segment.ifl KAPPA
vecplot.ifl KAPPA
check_ndfname.ifl IRCAM-specific
irchelp.ifl Generic
tnorm.ifl IRCAM-specific
ie TNORM and CHECK_NDFNAME are it. They are the whole net-functionality
provided by this application. [and CHECK_NDFNAME is simply a helper
routine for scripts to make sure that -e works by using NDF calls rather
than the shell]. ie TNORM is the only routine not duplicated elsewhere.
Wow.
I assume that the kappa routines were originally in ircampack and then
moved to kappa because they were generically useful.
Unless David explains that the kappa-but-not-kappa routines are useful.
I'll remove them from "ircampack" and leave it in the CVS "applications"
dir but just providing tnorm and check_ndfname.
Tim
On Sun, 8 Aug 2004, Tim Jenness wrote:
>
> Can ircampack be treated as "obsolete" (ie can I put it in
> applications/obsolete rather than applications)?
>
> Can I also assume that the vecplot and segment commands can be removed
> completely, even from the obsolete import? Why do they exist? They seem to
> be the old kappa versions.
>
> Does anyone actually use ircampack? The build is complicated by its desire
> to link against libkapsub BUT that requirement disappears if SEGMENT is
> binned.
>
> David - can you remember why there are private versions of SEGMENT and
> VECPLOT in ircampack?
>
>
--
Tim Jenness
JAC software
http://www.jach.hawaii.edu/~timj
|