This problem manifests when I create a Dendrogram with Dendrogram.compute and include the wcs parameter. The wcs information only populates the header of the first layer of the output fits file (the portion usually referred to as hdul[0].header in python) - the layer holding the dendrogram itself. This means that when I display the second layer of the fits file output (referred to as hdul[1].header) - the layer holding the original data from which the dendrogram was made - in glueviz or ds9, the astrometry does not load.
If I manually enter the astrometry keywords from hdul[0].header into hdul[1].header, the astrometry loads properly in ds9. However, nothing I've done yet has allowed the astrometry information to load in glueviz. Further, when I attempt to view the header for any of the fits file layers in glueviz, the header appears to be empty - even when loading the same file into ds9 correctly shows the header.
This problem manifests when I create a Dendrogram with Dendrogram.compute and include the wcs parameter. The wcs information only populates the header of the first layer of the output fits file (the portion usually referred to as hdul[0].header in python) - the layer holding the dendrogram itself. This means that when I display the second layer of the fits file output (referred to as hdul[1].header) - the layer holding the original data from which the dendrogram was made - in glueviz or ds9, the astrometry does not load.
If I manually enter the astrometry keywords from hdul[0].header into hdul[1].header, the astrometry loads properly in ds9. However, nothing I've done yet has allowed the astrometry information to load in glueviz. Further, when I attempt to view the header for any of the fits file layers in glueviz, the header appears to be empty - even when loading the same file into ds9 correctly shows the header.