# Jointcal output can now be used to make coadds

**URL:** <https://www.rubin.community/t/jointcal-output-can-now-be-used-to-make-coadds/3436>\
**Category:** Data Management\
**Tags:** coadd, jointcal, calibration\
**Created:** [November 27, 2018, 1:38am UTC](https://www.rubin.community/t/jointcal-output-can-now-be-used-to-make-coadds/3436 "2018-11-27T01:38:42Z")\
**Posts on this page:** 1\
**Page:** 1

<div class="post-metadata">

**Author:** ![parejkoj](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/parejkoj/32/138_2.png) [@parejkoj](https://www.rubin.community/u/parejkoj)\
**Post date:** [November 27, 2018, 1:38am UTC](https://www.rubin.community/t/jointcal-output-can-now-be-used-to-make-coadds/3436/1 "2018-11-27T01:38:42Z")

</div>

With the completion of [DM-15751](https://jira.lsstcorp.org/browse/DM-15751), you can now use jointcal’s output to build coadds. Once you’ve run `jointcalTask` on your data to produce the `jointcal_wcs` and `jointcal_photoCalib` datasets, you can build coadds as you normally would, setting the `doApplyUberCal` config option to `True`.

I’m announcing this here for those who aren’t following the epic about replacing meas\_mosaic with jointcal for HSC ([DM-11783](https://jira.lsstcorp.org/browse/DM-11783)).

Feel free to post any questions about using jointcal for coadds in this thread.