# Run ap\_pipe on existing calexps/wcs

**URL:** <https://www.rubin.community/t/run-ap-pipe-on-existing-calexps-wcs/4246>\
**Category:** Support\
**Created:** [July 9, 2020, 1:36pm UTC](https://www.rubin.community/t/run-ap-pipe-on-existing-calexps-wcs/4246 "2020-07-09T13:36:52Z")\
**Posts on this page:** 1\
**Showing post:** 2

<div class="post-metadata">

**Author:** ![racine](https://avatars.discourse-cdn.com/v4/letter/r/85e7bf/32.png) [@racine](https://www.rubin.community/u/racine)\
**Post date:** [July 10, 2020, 4:43pm UTC](https://www.rubin.community/t/run-ap-pipe-on-existing-calexps-wcs/4246/2 "2020-07-10T16:43:50Z")

</div>

Hi again,

I managed to go around reprocessing `calexps` by linking the outputs of `singleFrameDriver` in the output of `ap_pipe` before running.  
It’s not ideal, but it works…  
The problem with this is that I still don’t have an option to use the `wcs` from `jointcal`.

As an alternative I was wondering if it is possible to use a ref catalog coming from `jointcal` instead of panstarrs. That would have better astrometry than panstarrs when reprocessing the calexp, and the wcs created in that process would be kind of equivalent to the one returned by `jointcal`.

As an additional follow up, I was wondering if there is a way to turn off the alert production. So far, it created files, like `alerts/*.avro` that are really heavy. I don’t need them in my current analysis, so I would love to have an option to turn it off.  
I see in the config file that there is `config.diaPipe.alertPackager.alertWriteLocation` but that is only a way to decide where to output, I don’t see a way to turn it off…

Best,

Ben

---

_[View the full topic](https://www.rubin.community/t/run-ap-pipe-on-existing-calexps-wcs/4246)._
