ugjy SrSSKJr SSKJrJr SSKJr SSKJ r SSK J r SSK J r \\\\\4r\\\\\4rS SjrS S jrSS jrg )aBoxes, in the three frames the scan workflow has to speak. A scan returns a box as `{left, top, right, bottom}`, each 0..1 with the page's top-left as origin. The page it scanned was the real page, so that box is already a source coordinate and needs no mapping back. The parse states a box in PDF points, usually with the page's bottom-left as origin. The table pipeline states a box in PDF points bottom-left too, and states a region normalized top-left. These convert between them so no caller writes the arithmetic twice. ) annotations)OptionalTuple) CoordOrigin)DocItem)camelot_bbox_to_norm)BoxcU(dgUSUSUSUS4upp4[X5[X$5[X5[X$54$![a gf=f)zOA returned box (0..1, top-left origin, keyed left/top/right/bottom) as a tuple.Nlefttoprightbottom)KeyErrorminmax)boxr r r rs 9/home/mande/repo/quber/src/quber/core/figures/geometry.pynorm_boxrsi #&v;E CL#h-#W 5  c#.D0@#cBR SS sA AAcV[U5nUcgUupEpgXA-SU- U-Xa-SU- U-4$)zA returned box as PDF points with the page's bottom-left as origin. That is the frame the table pipeline measures in, so a cell box read off a scan lands in the same frame as one Camelot measured. Ng?)r)rwidthheight normalizedx1y1x2y2s r point_boxr*sD #JNBB JrV+RZ#(f9L MMcxUR(dgURSRnUR[R:Xa:UR U- UR U- URU- URU- 4$[UR URURUR 4X5$)z=An element's provenance box in the normalized top-left frame.Nr) provbbox coord_originrTOPLEFTltrbr)itemrrr!s rprov_boxr)7s 99 99Q<  D K///%&QQ  @% PPrN)r Optional[Box]returnOptional[NormBox])rr*rfloatrr-r+zOptional[PointBox])r(rrr-rr-r+r,)__doc__ __future__rtypingrrdocling_core.types.doc.baserdocling_core.types.doc.documentr5quber.core.extractors.camelot.correspondence.geometryrquber.core.figures.modelsr r-NormBoxPointBoxrrr)rrr8sZ #"33V) ueU* + ue+ ,T NQr