OK. I've implemented a system to do this. Not quite like I imagined
because of limitations caused by fixed-size buffers, etc., and not
wanting any direct inter-dependency between NDF and GRP. It involves
using the new functions ndgBeggh and ndgEndgh to create a "GRP NDF
History" block, within which any uses of kpg1_gtgrp etc are recorded.
A new type of NDF event is used to record each NDF to which default
history is written, and when ndgEndgh is called, all these NDFs are
modified to include the expanded group contents in their history.
I've modified cupid_mon.c and smurf_mon.c to use these facilities.
David
2009/10/5 Tim Jenness <[log in to unmask]>:
> In SMURF some of the commands use big config files that are read using
> kpg1Kymap and kpg1Gtgrp. The main problem we have is that the HISTORY
> written out simply reports the name of the config file (with a "^") and not
> its contentns. Usually the name is irrelevant and the contents are
> important. I'm wondering whether anyone has ideas for a general solution to
> this problem (maybe in NDF or KAPLIBS) before embarking on some
> smurf-specific hack for dumping the AST keymap into an additional history
> record (or even dumping the whole thing in a SMURF extension). There are
> many places where this sort of thing would be useful (I'm thinking of IN/OUT
> parameters that read a GRP file but then don't write the filenames into the
> parameters). Recognizing GRP inputs automatically would be really useful.
>
> --
> Tim Jenness
> Joint Astronomy Centre
>
|