Fix Version/s: None
Sprint:AP F20-4 (September), AP S21-3 (February), AP F21-1 (June), AP F21-2 (July)
The obs_decam README file gives instructions that are not really necessary (since we distribute the package along with the rest of the stack) and misleading (since a git clone of master will not likely run against a non-master stack). A user had problems trying to follow them and was also confused about whether the package contained the data referenced in the README.
Please correct the instructions and make them more friendly to new users.
Maybe worth adding — I agree with Kian-Tat Lim that these instructions may not really be necessary. They are certainly more elaborate than we provide with other camera packages. If this material is actually useful, it would probably be better on pipelines.lsst.io than stuffed in this README.
In short — please don't feel you have to simply update these instructions to describe the current situation, but rather feel free to significantly trim or move material that you don't feel is helpful.
This might make the most sense to complete after
DM-24253 and DM-25124 while that is fresh in your mind. It could be focused on using the LSST stack for the full processing, as opposed to using the community pipeline calibration products. Since it is often used, the instructions (here or preferably with a link to them in pipelines.lsst.io) could include simple recipes for processing raw images + calibrations through processCcd.py
One more thing to pile on to this embarrassingly overdue ticket. I should remove all the things in obs_decam/pipelines, since I ported them to ap_pipe/pipelines as part of
John Parejko, would you please review this ticket? I've put it off for a while (as you can see...) but it's finally less confusing!
Ready for your re-review. I built the docs and caught several syntax errors, and discovered doc/conf.py and friends needed updating. I ran Jenkins and it passed. https://ci.lsst.codes/blue/organizations/jenkins/stack-os-matrix/detail/stack-os-matrix/34604/pipeline. Amusingly, the issue I encountered with documenteer was the exact problem Zach Langford encountered 2 months ago, so thanks for encouraging him to post on Slack about it!
I left a handful more comments, but this looks good. Thanks for cleaning up these docs!
Hey Meredith Rawls — would you be able to spend a few minutes cleaning up these instructions, please? Thank you very much!