MMAKEIMG(1)
π MMAKEIMG β mMakeImg π
okay bestie, welcome to the Montage manual page for mMakeImg β yes it's the Montage one, the manual name you keep seeing in the corner is literally just Montage, and this whole page is about generating synthetic FITS images. sit down, hydrate, let's go β¨
πΈ NAME πΈ
mMakeImg β Generate synthetic FITS images
like. that's the whole job description. it makes fake-but-real FITS images π¦
β¨ SYNOPSIS β¨
mMakeImg [-d level] [-n noise_level] [-b bg1 bg2 bg3 bg4] [-t tbl col
width epoch mag] template.hdr out.fits
π« DESCRIPTION π«
So here's the vibe: mMakeImg generates synthetic FITS images, with varying levels of noise, from a table of provided point sources. that's the whole thing. you hand it a table, it hands you an image. iconic behavior honestly π
Each source is treated independently β no group chat drama between them β and its flux gets distributed on a source-specific point-spread function. every star gets its own lil glow. periodt π
π OPTIONS π
-dlevel β turns on debugging to the specified level (1-4). detective mode, bestie π-nnoise_level β random noise equal to noise_level gets added to the image background. specified random noise, exactly that amount, no cap.-bbg1 bg2 bg3 bg4 β specifies the four corners for a 'tilted' background for the image. each value is a floating point number specifying the background height at the corner. four corners, four numbers, tilted gradient, slay.-fβ use a uniform flat disk for sources rather than gaussians. flat disk era π«-rβ replace pixel values rather than adding to them. no blending, full override, main character energy.-ttbl col width epoch mag β specifies a table of sources to be added to the raw image. breaking it down for you:- tbl is the table filename
- col is the column name which contains the source fluxes
- width is a floating point number determining the point spread of each source
- epoch is the coordinate system reference year
- mag is the reference magnitude of the source list
In addition, the source table should have ra and dec columns for the image positions. (yes, you need them. the source needs to know where it lives π)
Several input tables can be specified if desired through repeated use of the -t flag and arguments. stack 'em up, bestie π
π§ ARGUMENTS π§
template.hdrβ FITS header template, used to indicate the desired parameters of the output image. this is the blueprint, the mood board, the vision β¨out.fitsβ Path of FITS image to be generated. where your baby gets written π
π RESULT π
Synthetic FITS output image; sources in image will represent the values from the input table(s). literally what you asked for, delivered π
π MESSAGES π
- OK β
[struct stat="OK"]π - ERROR β
Can't open table table tblπ - ERROR β
Can't find lon, lat columnsπ - ERROR β
Can't find flux/magnitude column 'col'π - ERROR β
Template file [template.hdr] not foundπ - ERROR β
Output wcsinit() failed. Exiting.πͺ - ERROR β
FITS library errorπ΅
π EXAMPLES π
$ mMakeImg -n 0.01 -b 0 1.0 1.0 0 -t sources.tbl J_MAG 5.0 2000 10.0 template.hdr out.fits
[struct stat="OK"]
and yes bestie, it returns [struct stat="OK"]. we love a success story π«Ά
π BUGS π
okay this is the serious part, pay attention, no scrolling past π
- The drizzle algorithm has been implemented but has not been tested in this release. so. it exists. that's all we can promise.
- If a header template contains carriage returns (i.e., created/modified on a Windows machine), the
cfitsiolibrary will be unable to read it properly, resulting in the error:[struct stat="ERROR", status=207, msg="illegal character in keyword"]. windows line endings really said "not today" π - It is best for the background correction algorithms if the area described in the header template completely encloses all of the input images in their entirety. If parts of input images are "chopped off" by the header template, the background correction will be affected. We recommend you use an expanded header for the reprojection and background modeling steps, returning to the originally desired header size for the final coaddition. The default background matching assumes that there are no non-linear background variations in the individual images (and therefore in the overlap differences). If there is any uncertainty in this regard, it is safer to turn on the "level only" background matching (the
-lflag inmBgModel).
π COPYRIGHT π
2001-2015 California Institute of Technology, Pasadena, California
If your research uses Montage, please include the following acknowledgement:
"This research made use of Montage. It is funded by the National Science Foundation under Grant Number ACI-1440620, and was previously funded by the National Aeronautics and Space Administration's Earth Science Technology Office, Computation Technologies Project, under Cooperative Agreement Number NCC5-626 between NASA and the California Institute of Technology."
The Montage distribution includes an adaptation of the MOPEX algorithm developed at the Spitzer Science Center.
and that's the whole page bestie!! this was Montage 5, dated Dec 2016, and you just read MMAKEIMG(1) β go make some synthetic images, you absolute icon ππ byeeee π¦
π¦ where this page comes from
- debian bookworm: montage 6.0+dfsg-7+b8 Β· BSD-3-Clause
- debian trixie: montage 6.1+dfsg-1+b1 Β· BSD-3-Clause
- ubuntu jammy: montage 6.0+dfsg-7build5 Β· BSD-3-Clause
- ubuntu noble: montage 6.0+dfsg-9 Β· BSD-3-Clause
- ubuntu questing: montage 6.1+dfsg-2
- ubuntu resolute: montage 6.1+dfsg-2build2 Β· BSD-3-Clause
- ubuntu stonking: montage 6.1+dfsg-2build2 Β· BSD-3-Clause
- π girlified by deepseek-ai/DeepSeek-V4.1-Flash on : a language model's rewrite of the original, under its terms