IPP Software Navigation Tools IPP Links Communication Pan-STARRS Links

Ignore:
Timestamp:
Jul 17, 2008, 12:38:15 PM (18 years ago)
Author:
Paul Price
Message:

The FPA format in psastroDataSave was bad: the GPC1 inputs (which is used for the output) had HDUs in the chips, but the output format is supposed to have an HDU in the FPA. It comes down to a pmFPAfileSuitableFPA not being called at the right place. To fix this, I've sprinkled calls to pmFPAfileSuitableFPA in all the FITS writing functions. This provides the HDU in the right place to these functions. pmFPAfileSuitableFPA should now automatically take care of header conformity, updating concepts, etc. Now, if adding a function to write FITS data, you should make sure that you call pmFPAfileSuitableFPA to get the right format, HDU, header keywords, etc.

File:
1 edited

Legend:

Unmodified
Added
Removed
  • trunk/psModules/src/camera/pmFPAfileFitsIO.h

    r18364 r18601  
    55 * @author PAP, IfA
    66 *
    7  * @version $Revision: 1.14 $ $Name: not supported by cvs2svn $
    8  * @date $Date: 2008-06-30 00:53:45 $
     7 * @version $Revision: 1.15 $ $Name: not supported by cvs2svn $
     8 * @date $Date: 2008-07-17 22:38:15 $
    99 * Copyright 2004-2005 Institute for Astronomy, University of Hawaii
    1010 */
     
    8686bool pmFPAviewWriteFitsTable(const pmFPAview *view, ///<  View specifying level of interest
    8787                             pmFPAfile *file, ///< FPA file to write
    88                              const char *name ///< Name of table
     88                             const char *name, ///< Name of table
     89                             pmConfig *config ///< Configuration
    8990                            );
    9091
     
    9798pmFPA *pmFPAfileSuitableFPA(const pmFPAfile *file,///< File containing the fpa
    9899                            const pmFPAview *view, ///< View at which to produce the fpa
    99                             const pmConfig *config ///< Configuration
     100                            pmConfig *config, ///< Configuration
     101                            bool pixels ///< Worry about copying the pixels?
    100102                           );
    101103
Note: See TracChangeset for help on using the changeset viewer.