fitscheck(1)
β¨ fitscheck(1) β¨
okay bestie, gather round, because we're talking about fitscheck from astropy 1.0.2 and honestly? it's giving unsung hero π
this is the script that keeps your FITS files from being a whole mess.
π NAME π
fitscheck β a script that sniffs out FITS standards violations and, like, fixes them too π οΈβ¨
π¦ SYNOPSIS π¦
fitscheck [OPTION]... [FILE]...
πΈ DESCRIPTION πΈ
so fitscheck is a command line script built on top of pyfits, and what it does is verify and update the CHECKSUM and DATASUM keywords in your FITS files. that's the main character job π but it can also detect and often fix other FITS standards violations, because it's generous like that.
the whole point? it helps you re-write the non-standard checksums that pyfits originally generated into standard checksums, so they'll actually interoperate with cfitsio. periodt. π
β οΈ okay important, no cap: fitscheck will refuse to write new checksums if the checksum keywords are missing or if their values are bad. it's not being difficult, it's being responsible.
so if you want to override that:
- use
--forceto write new checksums regardless of whether they currently exist or pass π₯ - use
--ignore-missingto tolerate missing checksum keywords without comment π
π OPTIONS π
-h,--helpβ shows you a terse usage message (help). short and sweet, just like it should be π«Ά-k [standard | nonstandard | either | none],--checksum=[standard | nonstandard | either | none]β picks the FITS checksum mode, ornonefor no checksum mode at all. defaults tostandardβ-w,--writeβ writes out file checksums and/or FITS compliance fixes. this is the one that actually touches your files βοΈ-f,--forceβ does the file update even if the original checksum was bad π€-c,--complianceβ does FITS compliance checking, and fixes it if possible π-i,--ignore-missingβ ignores missing checksums. pretend you didn't see them π«£-v,--verboseβ generates extra output. more words! more info! π
π EXAMPLES π
verify and update checksums, tolerating non-standard checksums, updating to standard checksum:
% fitscheck --checksum either --write *.fits
write new checksums, even if existing checksums are bad or missing:
% fitscheck --write --force *.fits
verify standard checksums and FITS compliance without changing the files:
% fitscheck --compliance *.fits
verify original nonstandard checksums only:
% fitscheck --checksum nonstandard *.fits
only check and fix compliance problems, ignoring checksums:
% fitscheck --checksum none --compliance --write *.fits
verify standard interoperable checksums:
% fitscheck *.fits
delete checksum keywords:
% fitscheck --checksum none --write *.fits
π§ reminder bestie: if you're not passing --write, you're just looking, not touching. the file stays exactly how it was. iykyk π
and that's the whole page!! this lil manual was written by the fitscheck crew back in April 2015 β the source is fitscheck itself, version vibes from the astropy 1.0.2 era, and the manual section is fitscheck(1) πβ¨ go forth and checksum responsibly, queen ππ
π¦ where this page comes from
- debian bookworm: astropy-utils 5.2.1-2+deb12u1 Β· BSD-3-Clause
- debian trixie: astropy-utils 7.0.1-3 Β· BSD-3-Clause
- ubuntu jammy: astropy-utils 5.0.2-1 Β· BSD-3-Clause
- ubuntu noble: astropy-utils 6.0.0-1ubuntu2 Β· BSD-3-Clause
- ubuntu questing: astropy-utils 7.0.1-3
- ubuntu resolute: astropy-utils 7.2.0-1build1 Β· BSD-3-Clause
- ubuntu stonking: astropy-utils 8.0.1-3 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms