Status update time. I built at least some HiTS2014 good seeing coadds, for use as templates. I broke it down into a 2-step process (with an intermediate "step 1.5" to do consolidateVisitSummary since some of the dataIds fail to find a bias or flat to use in ISR which is a whole other thing I haven't looked into yet). Anyway, the coadds are in /repo/main in the collection u/mrawls/
I had to be extremely careful about which input collections and data queries I used to get selectGoodSeeingVisits, makeWarp, and assembleCoadd to run without spending days in the quantum-graph-building stage with a zillion-line sql query. In particular, once I'm past single frame processing, I specified only the exact RUN collections I know I need instead of using any CHAINED collections besides refcats and skymaps. I also specified the skymap name in the data query.
A quick inspection of a handful of the coadds and the N-images suggests some tracts look fine while others have big regions where only 1 warp was selected. (Overall the 'hsc_rings_v1' default /repo/main skymap has much smaller tracts and patches than the skymap I am used to for HiTS, and this will undoubtedly cause problems along the lines of
DM-29310 when I get to the difference imaging step since there are many tracts involved).
I started a first attempt at running the actual AP Pipeline this evening. There was a minor hiccup in which my postgres APDB default schema appeared to be `public` instead of `mrawls` (see IHS-4861) but I think it was an easy fix. Here's hoping the quantum graph takes less than 24 hours to build and the bps run actually kicks off. The bps submit file I used is /project/mrawls/repo-main-logs/ApPipe_bps.yaml and with any luck the output collection will be u/mrawls/