[lsst-dm-stack-users] Problem visualizing astrometry matches; getX() fails

[Paul Price]

On Jun 22, 2014, at 3:35 PM, Michael Wood-Vasey wrote:
> * Question to list: Has anyone succeeded in visualizing astrometry matches using display('astrometry', ...)?

Dominique Boutigny has been down a similar path recently (in the "CFHT reprocessing" room on HipChat; the log is there to read), so I hope he will chime in with his experience.  You might be able to access his writeup on his wiki: http://lsst.in2p3.fr/wiki/index.php/CFHT_data_processing_with_LSST_stack

Please be aware that the displays (i.e., lsstDebug) were originally put together for developers to debug code that they're looking at.  The design and implementation are both on the table for reworking in the near future.  The layer that's built into the Tasks (calling Task.display) was my attempt to standardise some things, but it hasn't really been exercised much, and clearly some of it hasn't survived the multiple transitions it's gone through over the past few years.  I'll have a look at this particular instance to see what needs to be fixed.

I think you would be better served using the debugging features in lsst.meas.astrom.determineWcs.  Put in your debug.py:

import sys
try:
    import lsstDebug
    print "Importing debug settings..."
    def DebugInfo(name):
        di = lsstDebug.getInfo(name)        # N.b. lsstDebug.Info(name) would call us recursively
        if name in (
            "lsst.meas.astrom.determineWcs",
            ):
            di.display = 3
            di.showLinear = True
            di.verbose = True
            di.frame1 = 1
            di.frame2 = 2
            di.frame3 = 3
        return di
    lsstDebug.Info = DebugInfo
except ImportError:
    print >> sys.stderr, "Unable to import lsstDebug;  not setting display intelligently"


P.