Skip to content
Novus Examples
fits8.4 KB

FITS Long Header — Cards Across Several 2880-Byte Blocks (.fits)

A header of 47 cards, so END lands well past the first 2880-byte block, alongside repeated HISTORY and COMMENT cards that legally share a keyword. A parser that reads one block and stops never sees END and truncates the metadata.

Preview — schema + first 6 rowsfits
FieldValue
Total cards (incl. END)47
Cards per 2880-byte block36
Header blocks used2
HISTORY cards8
COMMENT cards6
Trapa reader that assumes one header block stops before END
The END card is not in the first block — that is the entire point of this file.

Specifications

Cards
47
Header Blocks
2
Cards Per Block
36
History Cards
8
Comment Cards
6
Bitpix
16

Testing contract

Expected to pass
Scenario
Parse the primary header to the END card and count how many distinct keywords, HISTORY lines and COMMENT lines it holds.
Expected result
You read 47 cards across 2 blocks, with 8 HISTORY and 6 COMMENT entries preserved in file order rather than collapsed to one each.

What is a .fits file?

FITS (.fits, Flexible Image Transport System) is the standard binary format in astronomy. It pairs human-readable 80-character header cards (in 2880-byte blocks) with binary image or table data, storing pixel arrays, coordinates, and instrument metadata. It has been the astronomical archive format for decades.

How to use this file

Use an example .fits file to test FITS readers (astropy, CFITSIO, DS9), header-card parsing, and image or table extraction, or to verify block-alignment handling.

How to use this file for testing

“FITS Long Header — Cards Across Several 2880-Byte Blocks (.fits)” is a deterministic Novus Examples fixture for Scientific data, Serialization testing. Citation catalogs (BibTeX, RIS), chemistry structures (MDL Molfile, PDB), and gridded binary data (NetCDF, FITS) — for testing reference managers, molecule viewers, and scientific-data loaders.

Documented properties for this file: FITS · 8,640 bytes. Compare results against paired or grouped companions on this page when present (clean↔damaged, searchable↔scanned, or format twins) so scores stay reproducible across runs.

Download the file once, keep the path stable in CI or local scripts, and treat the spec table as the contract: dimensions, seeds, field lists, and roles are intentional. Corrupt or invalid samples are labelled as such — expect parsers to fail loudly rather than silently accept them.

Scientific fixtures are small, valid, and fully synthetic — no real organism, patient, sample, or observation. Point your parser or loader at the file and check it reads the documented records, variables, or headers; binary formats ship a readable twin or metadata listing for comparison.

Generated by generation/scientific.py. Free for any use, no attribution required — license.