MHDRWWTEXEC(1)

💫 mHdrWWTEXEC — bestie edition 💫

okay so this is mHdrWWTExec, part of the Montage fam (that's the manual we're in, hi 👋), and it's basically the lil helper that mass-produces header template files for your WWT TOAST tiles. short king of a page, huge slay energy. let's get into it 🫶

---

🌸 NAME 🌸

mHdrWWTExec — literally nothing else, the original just says None. iconic minimalism, no notes 💅

---

✨ SYNOPSIS ✨

mHdrWWTExec [-d level] tileLevel hdrDir

---

🦋 DESCRIPTION 🦋

It runs mHdrWWT over and over so you don't have to 😭 — building out every single header template file you need for WWT TOAST tiles, all the way down to whatever level you asked for.

---

💅 OPTIONS 💅

• -d level — flips debugging ON, at the level you specify. yes bestie, you pick how loud it yells 📢

---

🎀 ARGUMENTS 🎀

• tileLevel — how deep the tiles go. Level 0 gives you just the all-sky header, 1 is that plus the four main quadrants, etc. Level 4 produces files like "tile3102.hdr". it's giving fractal core 🌀
• hdrDir — the output directory where all the header files land 🏠

---

⭐ RESULT ⭐

The whole set of header files. that's the gift. the set of header files 🎁

---

📢 MESSAGES 📢

• OK — [struct stat="OK", level=n, nheader=nheader] ✅
• ERROR — Problem creating output header directory. 😵
• ERROR — Problem with output header directory. 😵
• ERROR — [hdrDir] is not a directory. 🙈
• ERROR — mHdrWWT error message

---

🌈 EXAMPLES 🌈

$ mHdrWWTExec 4 hdrs
       [struct stat="OK", level=4, nheader=341]

ate. 341 headers, no crumbs 🔥

---

💀 BUGS 💀

okay listen, these are important, read them fr fr

• The drizzle algorithm has been implemented but has not been tested in this release. so like… it's there. it's just ✨untested✨. be careful bestie.
• If a header template contains carriage returns (i.e., created/modified on a Windows machine), the cfitsio library will be unable to read it properly, resulting in the error: [struct stat="ERROR", status=207, msg="illegal character in keyword"]. the CRLF jumpscare 😭
• 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 -l flag in mBgModel). not me telling you to read the fine print but… read the fine print 🫶

---

👑 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 💖 go make some tiles. this was Montage 5, Dec 2016 — mHdrWWTExec(1) — signing off, mwah 🎀✨