# Issues with ingestCalib.py using DECAM images

**URL:** <https://www.rubin.community/t/issues-with-ingestcalib-py-using-decam-images/5602>\
**Category:** Support\
**Tags:** decam, ingestion\
**Created:** [July 2, 2021, 10:28pm UTC](https://www.rubin.community/t/issues-with-ingestcalib-py-using-decam-images/5602 "2021-07-02T22:28:32Z")\
**Posts on this page:** 1\
**Showing post:** 13

<div class="post-metadata">

**Author:** ![timj](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/timj/32/10_2.png) [@timj](https://www.rubin.community/u/timj)\
**Post date:** [July 7, 2021, 9:56pm UTC](https://www.rubin.community/t/issues-with-ingestcalib-py-using-decam-images/5602/13 "2021-07-07T21:56:50Z")

</div>

> [@Paula](#):
>
> `DECam/calib`

Use that as a second input collection for your `pipetask` run. The graph builder needs to know where to find the inputs so you need to tell it what raws to use and what calibrations to use. Your previous command only specified the raw location.

---

_[View the full topic](https://www.rubin.community/t/issues-with-ingestcalib-py-using-decam-images/5602)._