bboxSize & alert cutout size

Hi, I was looking through the DP1 schema and I noticed that there is a DiaSource field called bboxSize - “Bounding box of diaSource footprint”. Is there any further detail in the documentation as to what this is and how it is calculated?

I am also wondering how it might relate to the expected cutout size in (future) alerts? Would it be fair to assume the the alert cutouts would be the maximum of (bboxSize, 30), where 30 is the minimum cutout size in the DPDD?

The bboxSize column contains the minimum square box size (in pixels) required to fully contain the DETECTED footprint of the diaSource. You are correct that the alert cutout size is precisely the greater of this cutout size and the configured minimum cutout size (up to a very large maximum cutout size).

3 Likes

Great thanks Ian! Just out of curiosity is there a rough estimate of the max cutout size? I had a very quick look at https://dmtn-102.lsst.io/ and section 2.3 says that there are no requirements on the overall alert packet size but I can imagine there will be a practical limit imposed at some point.

The default maximum cutout size is 102 pixels, which is set by the size of a cutout needed to contain a trailed source moving 10 degrees per day. It can be configured as large as 1000 pixels if there was a custom pipeline that needed that.

1 Like