# How is a diaSource associated to a diaObject/ssObject?

**URL:** <https://www.rubin.community/t/how-is-a-diasource-associated-to-a-diaobject-ssobject/10829>\
**Category:** Alerts & Brokers\
**Tags:** solarsystem\
**Created:** [August 18, 2025, 6:42pm UTC](https://www.rubin.community/t/how-is-a-diasource-associated-to-a-diaobject-ssobject/10829 "2025-08-18T18:42:04Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![ireyes](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/ireyes/32/1179_2.png) [@ireyes](https://www.rubin.community/u/ireyes)\
**Post date:** [August 18, 2025, 6:42pm UTC](https://www.rubin.community/t/how-is-a-diasource-associated-to-a-diaobject-ssobject/10829/1 "2025-08-18T18:42:04Z")

</div>

Hi! I’m trying to understand the logic of the solar system object association in the alert pipeline. Some of that is explained in [https://ldm-151.lsst.io](https://ldm-151.lsst.io/) but it would be great to have a flow chart where you receive a new diaSource and then make the decision about object matching to produce the alert.  
I’m trying to build the logic from the broker side about how a source is associated to a diaObject and/or ssObject, if it has to be updated over time, if a source from a previous alert now belongs to a ssobject (and not to a diaobject?), if diaObject.validityStart (and validityEnd?) is related to this, etc.  
Cheers,

Ignacio

---

<div class="post-metadata">

**Author:** ![ireyes](https://sea2.discourse-cdn.com/flex002/user_avatar/www.rubin.community/ireyes/32/1179_2.png) [@ireyes](https://www.rubin.community/u/ireyes)\
**Post date:** [September 5, 2025, 1:35pm UTC](https://www.rubin.community/t/how-is-a-diasource-associated-to-a-diaobject-ssobject/10829/2 "2025-09-05T13:35:23Z")

</div>

Any updates? Having a clear understanding of this is really important for the community brokers.