iraf.net

I'm currently writing a framework to do all my reductions with pyraf. One task uses apphot and then daophot. This is done over multiple files. So when the way it is executed is apphot - daophot - apphot -daophot ....
The first time I run apphot it uses apphot's datapars. when I run daophot it uses daophot's datapars. when running apphot aghain it does not switch to apphot's datapars but instead uses daophot's datapars.
This can be easily tested in a pyraf environment.
type:
apphot
daophot
apphot
epar apphot.phot and click on datapars you will see daophot's datapars.does anyone know how to unload a package in pyraf? or how to elevitate this problem.thanks in advance
Wolfgang

As far as I know, PyRAF doesn't have the concept of packages and everything is a flat space. So, once-loaded, always-loaded.-Mike

If I understood correctly, it sounds like support for unlearning may have been added in the latest release of PyRAF:http://www.stsci.edu/resources/software_hardware/pyraf/Pyraf1.1ReleaseNotesCheers,James.

If you're referring to:[quote:f23ace236d]Added unlearn method to IrafPkg class so that all tasks in package can be unlearned if the package is loaded.[/quote:f23ace236d]Then this refers to task parameter unlearning in the package, i.e. unlearn all tasks in a package rather than single tasks individually. Package unloading is different in that it requires that the context defined for the package (e.g. resets of environment definitions, task re-definitions, etc) be "undone". Packages often will define the same task in multiple packages, however it's possible for instance that a CL script defined in one package is defined in another package that has a special <task>.par file to reset the default parameters when the task is used in the second package.The uparm directory keeps these straight by using part of the package name in the uparm file and so by accessing daophot.datapars.param you can distinguish it from apphot.datapars.param explicitly. The normal parameter "search path" is task->package->rest_of_the_CL, in the case of PSETs the task assumes the pset is part of the currently loaded package, but without a concept of loaded package you get the confusion.One this to try is to explicitly define the pset in your task to be daophot.datapaars or apphot.datapars so you refer to the right one, otherwise be sure to set the critical values each time you need them.-Mike