MARCHIVEEXEC(1)

✨ MARCHIVEEXEC 💅

okay bestie, you're looking at the mArchiveExec page from the Montage manual (section 1, the user commands one, iykyk) 🫶

---

🌸 NAME 🌸

mArchiveExec — the girl who goes and calls mArchiveGet on every single image, one after another, in sequence. no cutting the line. periodt. 👑

---

🦋 SYNOPSIS 🦋

mArchiveExec [-d level] region.tbl

---

💖 DESCRIPTION 💖

so here's the vibe: you hand her a table of archive images (the kind of table that mArchiveList makes, bestie, not just any table), and she goes down the list and calls mArchiveGet on each one in sequence until every single file has been pulled down into the current directory. that's it. that's the whole job. she's a pipeline girlie and she ate. 🔥

---

⭐ OPTIONS ⭐

• -d level — prints out extra debugging tea 🍵. in this version the only supported level is 1. like, one (1). that's it. don't come at her with a 2, she will not know her.

---

🎀 ARGUMENTS 🎀

• region.tbl — the table of archive images, generated by mArchiveList. this is the whole meal ticket, no tbl no party. 🌈

---

👑 RESULT 👑

[struct stat="OK", count=num-images, failed=num-failed]

so num-images from region.tbl get retrieved into the current directory. and num-failed is the count of attempts that did not survive — if you wanna see the actual errors that mArchiveGet was throwing, turn on debugging (-d 1, bestie, see above 💅).

---

💜 MESSAGES 💜

• OK — [struct stat="OK", count=num-files, failed=num-failed] ✨ everything slayed.
• ERROR — Table region.tbl needs column 'URL' and can optionally have columns 'fname'/'file' and pixel ranges 'imin'...'jmax' 😭 she needs the URL column, periodt. the fname/file columns and the imin...jmax pixel ranges are optional little extras. no URL = no vibe check passed.

---

🧚 EXAMPLES 🧚

first up: run mArchiveList to cook up a table of image metadata, URLs included obviously:

$ mArchiveList 2mass j m31 0.5 0.5 2mass_m31_j.tbl
       [struct stat="OK", count=18]

next: call mArchiveExec on that metadata table and let her fill up the current directory with all the files mArchiveList found. she's obsessed with efficiency fr fr:

$ mArchiveExec 2mass_m31_j.tbl
       [struct stat="OK", count=18, failed=0]

and then the moment of truth, ls:

$ ls

       2mass-atlas-001016n-j1030232.fits

       2mass-atlas-001016n-j1030244.fits

       2mass-atlas-001025n-j0740021.fits

       2mass-atlas-001025n-j0740033.fits

       2mass-atlas-001025n-j0740044.fits

       2mass-atlas-971024n-j0080021.fits

       2mass-atlas-971024n-j0080033.fits

       2mass-atlas-971024n-j0080044.fits

       2mass-atlas-971024n-j0090232.fits

       2mass-atlas-971024n-j0090244.fits

       2mass-atlas-981123n-j0720021.fits

       2mass-atlas-981123n-j0720033.fits

       2mass-atlas-981123n-j0720044.fits

       2mass-atlas-981204n-j0420021.fits

       2mass-atlas-981204n-j0420033.fits

       2mass-atlas-981204n-j0420044.fits

       2mass-atlas-981204n-j0430232.fits

       2mass-atlas-981204n-j0430244.fits

       2mass_m31_j.tbl

eighteen files plus the table itself. main character energy, truly. 🎀

---

💀 BUGS 💀

bestie. listen. the tea is not all cute here. 🙈

• the drizzle algorithm has been implemented but has not been tested in this release. it is giving "we wrote it and walked away." 💀
• if a header template contains carriage returns (i.e. 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"]. so. yeah. windows line endings stay losing. 😭
• 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, and then return 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 — that's the -l flag in mBgModel. no cap, just turn it on if you're unsure. 💅

---

🌈 COPYRIGHT 🌈

2001-2015 California Institute of Technology, Pasadena, California

if your research uses Montage, please include the following acknowledgement — yes, the whole thing, it's the rules bestie 🫶:

"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. iconic of them honestly. ⭐

---

okay and that's the whole page, you're done, you understood the assignment 🎓💖

Montage 5 — Dec 2016 🌸 that's the version and date on this one, mwah, go forth and archive bestie 💅✨