MHDRWWT(1)

πŸŽ€ mHdrWWT(1) β€” the Montage girlies' guide to header templates πŸŽ€

okay bestie, sit down, we're doing mHdrWWT from the Montage suite. yes the name is cursed. yes it's giving "someone fell asleep on the shift key". we love her anyway. πŸ’…

✨ NAME ✨

mHdrWWT β€” literally just None. that's what the manpage says, that's what I'm telling you. no cap. πŸ™ˆ


🌸 SYNOPSIS 🌸

mHdrWWT tileID hdrFile

πŸ¦‹ DESCRIPTION πŸ¦‹

so what she does is: she creates the header template for a specific WWT/TOAST tile. that's the whole gig. πŸ’–

now β€” and I need you to hear me on this β€” these tiles are not usually of any use except in serving the WWT interface. like, they're not for you, they're for the interface, iykyk. however, the files are standard FITS and PNG, so you can view them that way if you so desire. the option is there, bestie. 🫢

tiles are identified by WWT tile ID, which is a Z-ordered quandrant digits string. (yes, "quandrant". that's the original's spelling. I don't make the rules, I just vibe with them. ✨)


πŸ‘‘ ARGUMENTS πŸ‘‘

  • tileID β€” for the top-level (all-sky) TOAST tile, the tileID is an empty string. literally nothing. silence. the void. πŸ•³οΈ then for the next level down, the sky gets divided into four "quadrants" and the tileID is "0", "1", "2" and "3". and it just keeps going finer and finer β€” tiles at the fifth level down have IDs like "3102". recursion queen πŸ‘‘
  • hdrFile β€” the output header file, normally with a name that includes the tileID (e.g. "planck.hdr", "planck3102.hdr"). name her after her tile, it's only right πŸŽ€

πŸ’« RESULT πŸ’«

she generates the specified header file, which then gets used by mProjectQL to reproject input data into TOAST tile FITS files β€” which in turn are converted by mViewer into TOAST tile PNG files. it's a whole pipeline, bestie, everyone's doing their part. πŸ’…

and normally? all of this is only used in conjunction with the WWT interface. so if you're out here using it for something else... interesting choice, main character energy, but okay. 🌈


πŸ“¬ MESSAGES πŸ“¬

  • OK β€” [struct stat="OK", level=level, xtile=i, ytile=j] ✨
  • ERROR β€” Invalid character in ID string (must be in [0,1,2,3])
  • ERROR β€” Cannot open output header file.

🌟 EXAMPLES 🌟

Tile IDs are in the form of a Z-ordered recursion. for informational purposes (because she's thoughtful like that πŸ’–), the program also outputs the location of the tile in the "x" and "y" location it has in the array of tiles for its tile level.

$ mHdrWWT "3102" planck3102.hdr
       [struct stat="OK", level=4, xtile=12, ytile=6]

look at her go. level 4, xtile 12, ytile 6. she ate and left no crumbs. πŸ”₯


πŸ’€ BUGS πŸ’€

okay this is the part where we get real. 🫢

The drizzle algorithm has been implemented but has not been tested in this release.

she's built different but she hasn't been tested different. proceed accordingly, 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"]

windows jumpscare fr fr. πŸ™ˆ

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.

no chopping. we don't chop. βœ‚οΈπŸš«

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.

so: big header for the middle steps, tiny header for the finale. glow up in reverse. πŸ’…

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).

when in doubt, -l it out. 🌸


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 β€” blowing you kisses from the terminal, mwah πŸ’‹βœ¨πŸ¦‹ no cap, stay tiled. πŸŽ€