MPROJWWTEXEC(1)

💖 MPROJWWTEXEC 💖

okay bestie, welcome to the Montage manual page for mProjWWTExec — yes that's the whole name, and yes it's a mouthful, we love her anyway 🫶

---

✨ NAME ✨

mProjWWTExec — None (that's literally what the name section says, no cap, it's giving mysterious main character energy 💅)

---

🌈 SYNOPSIS 🌈

mProjWWTExec [-d level] tileLevel input.fits baseName hdrDir tileDir

---

🦋 DESCRIPTION 🦋

So what does she do? She runs mProjectQL for every single tile you need for a WWT TOAST set. Iconic. Obsessed.

Heads up tho: the headers for the reprojection should already have been generated, and you do that with mHdrWWTExec. Do that first, bestie, don't skip steps 🙈

Also, plot twist: the base names for all the tiles in a WWT TOAST set are the same — so yeah, that's why baseName has to be an argument too. It's giving "one name to rule them all" 👑

---

🎀 OPTIONS 🎀

• -d level — turns on debugging, up to some level. Crank it when you wanna see what's going on under the hood 🔍

---

🌸 ARGUMENTS 🌸

• tileLevel — the depth of WWT TOAST tiles you want. Important: this should be no bigger than the depth to which the header files were created. Don't go deeper than your headers, bestie, that's a vibe check you will fail 💀
• input.fits — the input image that's getting reprojected into WWT TOAST tile FITS images. The star of the show ✨
• baseName — the base name for the tiles. For example, an output tile named "planck3102.fits" has the base name "planck". See how that works? Chef's kiss 👩‍🍳
• hdrDir — the directory with your header templates. These will have names like "tile3102.hdr".
• tileDir — the directory where the output images go. Your little tile nursery 🍼

---

💜 RESULT 💜

ngl, this utility has two limitations, and we're gonna be upfront about them because that's what real ones do:

1. She assumes that all the tiles are reprojections of a single input FITS file. Montage actually has all the functions you'd need to use multiple inputs — even coadding across multiple images for any tile. So the power exists, this tool just isn't using it fr fr.
2. All the output files get dumped into a single directory. Which, if your tiles go deep enough, may become unworkable. Total "my Downloads folder" energy 😭

Both of these shortcomings can be easily overcome, but the details depend on the details of your input data, so the choice was to opt for a simple initial approach. Fair enough, we respect the minimalism 💅

---

😭 MESSAGES 😭

• OK [struct stat="OK", level=level, nimage=count] — we love a happy ending 🎉
• ERROR Problem with FITS file. — something's wrong with the FITS file, bestie
• ERROR Cannot find/address header directory [dir]. — can't find or address that header directory
• ERROR [dir] is not a directory. — plot twist: that thing is not a directory
• ERROR Problem creating output tile directory. — couldn't make the output tile directory
• ERROR Problem with output tile directory. — the output tile directory is having issues
• ERROR mProjectQL error message — an error straight from mProjectQL, passing along the message

---

🔥 EXAMPLES 🔥

Look at her go:

$ mProjWWTExec 4 Planck857.fits planck hdrs fits
       [struct stat="OK", level=4, nimage=341]

341 images, level 4, status OK. She ATE and left no crumbs 👑

---

💀 BUGS 💀

okay so here's the tea, and you need to hear all of it:

• The drizzle algorithm has been implemented but has not been tested in this release. Untested code, bestie. Proceed accordingly 🫣
• If a header template contains carriage returns (like if it was created or modified on a Windows machine), the cfitsio library will be unable to read it properly, and you'll get this error: [struct stat="ERROR", status=207, msg="illegal character in keyword"]. Windows line endings ruining lives since forever, no cap 💀
• 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. So the recommendation is: use an expanded header for the reprojection and background modeling steps, then return to the originally desired header size for the final coaddition. The default background matching assumes there are no non-linear background variations in the individual images (and therefore in the overlap differences). If there's any uncertainty about that, it's safer to turn on the "level only" background matching — that's the "-l" flag in mBgModel. Periodt. 🎀

---

👑 COPYRIGHT 👑

2001-2015 California Institute of Technology, Pasadena, California

If your research uses Montage, please include the following acknowledgement, fr fr:

"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. Slay 🧚

---

aaaand that's the whole page, bestie 💖 this one's from Montage 5, dated Dec 2016 — she's a vintage queen and she still hits. go reproject some tiles, ily, bye 🌈✨🦋