Introduction: Project overview
Creating the EleFits package: Installation and configuration guide
A FITS primer: What's a FITS file?
Programming guidelines
- Definitions: not relevant
- Current Header Data Unit (CHDU): not relevant
- Function names and variable datatypes: On types
- Support for unsigned integers and signed bytes: On types
- Dealing with character strings: not relevant
- Implicit data type conversion: On types
- Data scaling: On types
- Support for IEEE special values: same as CFITSIO
- Error status values and the error message stack: Exceptions
- Variable-length arrays in binary tables: not supported
- Multiple access to the same FITS file: same as CFITSIO
- When the final size of the FITS HDU is unknown: not relevant
- Size limitations: same as CFITSIO
Basic and specialized services
- Exceptions: Exceptions
- FITS file access: File handlers
- HDU access and creation: File handlers
- Header keyword records read/write: Header unit handlers
- Primary array or image extension: Image data unit handlers
- Image compression: Image compression
- ASCII table extension: not supported
- Binary table extension: Binary table data unit handlers
The iterator function: not supported
World Coordinates System (deprecated): not relevant
Hierarchical grouping: not supported
Extended file name syntax: not supported
Template Files: not supported
Local FITS Conventions
- 64-bit long integers: not relevant
- Long string keyword record values: Record
- Arrays of fixed-length strings in binary tables: Column
- Keyword record units strings: Record
- HIERARCH convention for extended keyword record names: Record
- Tile-compressed image format: Image compression
Optimizing programs: Optimization and good practices