Limiting myself to a naive search of pipe_tasks
(master) itself, this is what I find for apparent uses of the display() method in the Task base class:
$ grep -n 'display *(' *.py calibrate.py:458: self.display('repair', exposure=exposure) calibrate.py:464: self.display('background', exposure=exposure) calibrate.py:506: self.display('PSF_repair', exposure=exposure) calibrate.py:520: self.display('PSF_background', exposure=exposure) calibrate.py:581: self.display('calibrate', exposure=exposure, sources=sources, matches=matches) repair.py:199: self.display('repair.before', exposure=exposure) repair.py:206: self.display('repair.after', exposure=exposure) snapCombine.py:131: self.display('repair0', exposure=snap0) snapCombine.py:132: self.display('repair1', exposure=snap1)
I.e., there are three tasks that currently use the interface.
I assume the migration would be to make them explicitly invoke afw.display?
I agree that we should be looking for more “generic display” capabilities to be added to afw.display so that we can deal with - as you suggested - tabular data and a variety of things besides images.
Gregory