FIINFO(1)

๐Ÿ’– FIINFO โ€” bestie edition ๐Ÿ’–

okay so real talk, this is the manpage for fiinfo, and it's genuinely iconic. it lives in the User Commands section of the manual (section 1, for the nerds keeping score ๐Ÿ“–) and it's here to tell you literally everything about how to pull info and image stamps out of images. stay with me, it's giving useful.


๐ŸŒธ NAME ๐ŸŒธ

fiinfo โ€” providing information or image stamps for images โœจ


๐ŸŽ€ SYNOPSIS ๐ŸŽ€

fiinfo [options] [-i <input>] <outputs>

๐Ÿฆ‹ DESCRIPTION ๐Ÿฆ‹

so the whole main character purpose of the fiinfo program is to give you some information about your FITS files. primarily that's FITS images, but ngl, output dump is supported for tables and binary tables also. it's versatile, it's talented, it ate ๐Ÿ’…


โœจ OPTIONS โœจ

๐Ÿ’œ General options

  • -h, --help โ€” gives you a general summary about the command line options. quick lil vibe check of what's available.
  • --long-help, --help-long โ€” gives you a detailed list of command line options. the full tea โ˜•
  • --wiki-help, --help-wiki, --mediawiki-help, --help-mediawiki โ€” gives you a detailed list of command line options but in Mediawiki format. for when you need it wiki-fied.
  • --version, --version-short, --short-version โ€” gives some version information about the program. who are you, really? ๐Ÿชž
  • -i, --input <image file> โ€” name of the input FITS image file. your source material bestie.
  • --summary, --long-summary โ€” give a summary about the content structure of the FITS file. namely, the main characteristics and dimensions of the primary image, followed by the list of optional extensions and their main properties. it's like a little recap episode of your FITS file ๐Ÿ—‚๏ธ
  • -s, --statistics <list of statistics> โ€” calculate basic statistics for the image. see "Statistics options" below for available statistics methods. the statistics itself contains four numbers: the total number of pixels involved in the calculations, the final number of pixels used for the statistics (which might be smaller than the previous one if the outliers are rejected), an average value and a scatter. four numbers, no cap ๐Ÿ“Š
  • -d, --data <list of derived image data> โ€” calculate some other more quantities related to astronomical images. this option should be followed by a comma-separated list of quantities. see "Image characteristics" below for more details about these.
  • -b, --box <number of blocks> โ€” this option specifies the number of blocks, which is used to divide the input image. some quantities (see "Image characteristics") can be derived on a per block basis either. chop chop ๐Ÿ”ช
  • -a, --order <order> โ€” order of polynomial spatial variations in some derived image characterization quantities (see also "Image characteristics"). math girlies rise ๐Ÿงฎ
  • -n, --newline โ€” in the output, each quantity should be written in separate lines. by default, the output is a single line, containing the desired quantities or statistics. one line is the default vibe, but you can โœจspread outโœจ
  • --ignore-mask โ€” completely ignore the mask associated to the input image. mask? never heard of her ๐Ÿ™ˆ
  • --output-dump <file> โ€” name of an output file in which a raw image dump is written. each line of this file contains 3 or 4 columns: X, Y coordinates and flux, optionally followed by the associated mask flag (see also "-m|--dump-mask").
  • -m, --dump-mask โ€” the raw image dump specified by "--output-dump" should contain the masking information beyond the coordinates and intensities.
  • --output-pnm, --output-ppm, --output-pgm โ€” name of an output file in which the image is stored in a variant of PNM format. these images are intended to be a kind of "human visible" images, appropriately scaled for normal displays. these images are stored in PNM format, which is an easily parseable (thus raw, uncompressed) format, supported by many graphic programs (and by the NETPBM package). such an image conversation always results data loss. see also options "--pgm" or "--ppm" for further details.
โš ๏ธ real talk: that conversion always results in data loss. it's a glow-up for your eyeballs, not for your data. the original is prettier, sorry ๐Ÿ’€
  • --pgm <PGM specific conversion options> โ€” this command line argument is followed by a comma-separated list of options, which specifies the scaling and other properties of the output image. the resulted image will be a grey-scale (PGM) image, even if a color palette is requested. see "PNM specifications" below.
  • --ppm <PPM specific conversion options> โ€” this command line argument is followed by a comma-separated list of options, which specifies the scaling and other properties of the output image. the resulted image will be a true-color (PPM) image, even if a greyscale colormap is requested. see also "PNM specifications" below for more details.

๐ŸŒˆ Statistics options

  • mean โ€” the mean value of the pixel intensities.
  • median โ€” the median value of the pixel intensities.
  • iterations โ€” reject the outlier pixels before doing any statistics. bye outliers, we don't know them ๐Ÿ‘‹
  • lower=<sigma>, upper=<sigma>, sigma=<sigma> โ€” lower, upper or common rejection level, in the units of standard deviation (which is derived around the mean or median value, depending on the request of the user).

โญ Image characteristics

  • min, max โ€” minimal and maximal pixel intensities on the image.
  • mean โ€” mean intensity level.
  • stddev โ€” standard deviation.
  • sky โ€” sky background level.
  • skysigma โ€” sky background scatter.

๐Ÿงš PNM specifications

  • linear โ€” use a linear intensity scaling.
  • log โ€” use a logarithmic intensity scaling.
  • squared โ€” use a squared intensity scaling.
  • sqrt โ€” use a square root intensity scaling.
  • histequ โ€” use a histogram equalized intensity scaling.
  • minmax โ€” use the minimal and maximal pixel intensities for scaling boundaries.
  • percentage=<%> โ€” use the minimal and maximal values of the innermost specified percent of the pixel intensities.
  • min=<min>, max=<max> โ€” use the specified minimal and maximal values for scaling boundaries.
  • zscale โ€” use the "zscale" algorithm to determine scaling boundaries.
  • zmax, zmin โ€” use the "zmax" or "zmin" algorithm to determine scaling boundaries.
  • zcontrast=<zcontrast> โ€” use the specified contrast value to determine the scaling boundaries in the case of "zscale", "zmax" or "zmin" methods. the default value is 0.25.
  • reverse โ€” use an inverted color map. flip it ๐Ÿ”„
  • contrast=<C>, brightness=<B> โ€” use the specified values for adjusting the final contrast and brightness. the default values are 1 and 0.5, respectively, according to the standard image contrast and brightness level definitions.
  • 8, 8bit โ€” create an 8-bit PGM or PPM output. this is the default.
  • 16, 16bit โ€” create a 16-bit PGM or PPM output instead of the default 8-bit.
  • palette=<color1>:<color2>:<color3>:... โ€” specify an alternate color map. each color should be a hexadecimal representation of a given color, i.e. it should be in one of the forms of G, GG, GGGG, RGB, RRGGBB or RRRRGGGGBBBB, denoting 4 bit grey, 8 bit grey, 16 bit grey, 3x4 bit truecolor, 3x8 bit truecolor or 3x16 bit truecolor representation, respectively. the color map gradient will be continuous if the colors are separated by colons. jumps in the gradient can be defined by separating the successive colors by a slash, "/" instead of colons. ๐ŸŽจ this is where you get to be the artist fr fr
๐Ÿ“Œ note that the syntax followed by the "--pgm" or "--ppm" command line arguments is exactly the same for both options. however, color images will be converted to greyscale if "--pgm" is specified, and vice versa, "--ppm" always yields a PPM format, even if the color gradient is merely a grayscale one. the default palette is 0:F for both PGM and PPM formats, i.e. a pure black - white gradient. ๐Ÿ–ค๐Ÿค

๐Ÿซถ REPORTING BUGS ๐Ÿซถ

found a bug? report bugs to <apal@szofi.net>, see also https://fitsh.net/. don't be shy, they want to know ๐Ÿ’Œ


Copyright ยฉ 1996, 2002, 2004-2008, 2010-2016, 2018-2020; Pal, Andras <apal@szofi.net>


and that's the whole thing bestie, you're officially fluent ๐Ÿ’– this was fiinfo version 0.9.4 (dated 2021.01.24), from January 2021 โ€” the manual page itself is FIINFO(1) and yes she's iconic, no notes ๐ŸŒŸ

๐Ÿ“ฆ where this page comes from