# \#background

**URL:** https://www.rubin.community/tag/background/18.md

[Latest](https://www.rubin.community/latest.md) · [Categories](https://www.rubin.community/categories.md) · [Tags](https://www.rubin.community/tags.md)

---

## [Difference in py2 and py3 background models](https://www.rubin.community/t/difference-in-py2-and-py3-background-models/1240)

<div class="topic-metadata">

**Author:** [@mrawls](https://www.rubin.community/u/mrawls)\
**Replies:** 4\
**Last updated:** [October 18, 2016, 7:51pm UTC](https://www.rubin.community/t/difference-in-py2-and-py3-background-models/1240 "2016-10-18T19:51:17Z")

</div>

The background model being used by pipe\_tasks (I believe this is the job of meas\_algorithms) apparently has gradients that are being quantified differently in python2 vs python3. The following series of images illustrate…

---

## [Advanced methods for background subtraction](https://www.rubin.community/t/advanced-methods-for-background-subtraction/817)

<div class="topic-metadata">

**Author:** [@rpmunoz](https://www.rubin.community/u/rpmunoz)\
**Replies:** 2\
**Last updated:** [May 29, 2016, 6:12pm UTC](https://www.rubin.community/t/advanced-methods-for-background-subtraction/817 "2016-05-29T18:12:52Z")

</div>

Dear all, I'm interested in collaborating in the background modelling and subtraction. I know that subtractBackground.py in lsst.meas.algorithms contains the functions and classes for doing the background subtraction. …