Skip to content

[DOCS]: Add documentation about default behaviors for FITS files #77

@teald

Description

@teald

Contact Details

No response

What is up with the docs?

The default structure of a FITS file, such as what expected extension names are, is currently not well documented (in many cases, undocumented).

Code of Conduct

  • I agree to follow this project's Code of Conduct

Metadata

Metadata

Assignees

Labels

documentationImprovements or additions to documentationmaintenanceFor maintenance tasks

Type

No type
No fields configured for issues without a type.

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions