§
    à©ºj  ã                  ó6   — d Z ddlmZ ddlmZmZmZmZ g d¢ZdS )ut  Detection metrics â€” AP, AR, and the detection diagnostic suite.

hotcoco is growing from a COCO evaluation library into a perception evaluation
toolkit, with one namespace per metric family. This is the first of them; the
panoptic, tracking, and concepts families follow the same shape.

Nothing here is new, and nothing is going away. ``hotcoco.detection.COCOeval``
*is* ``hotcoco.COCOeval`` â€” the same object, re-exported under the family name so
that code evaluating several families reads consistently::

    from hotcoco import detection, panoptic   # panoptic lands in 1.1

    det = detection.COCOeval(gt, dt, "bbox")
    det.run()

The top-level names are permanent. ``hotcoco.COCOeval``, ``hotcoco.mask``, and
the ``pycocotools``/LVIS drop-in surface are compatibility guarantees, not
deprecated aliases â€” if you are replacing ``pycocotools``, keep importing from
the top level and ignore this module entirely.

The LVIS helpers (``LVISeval``, ``LVISResults``, ``LVIS``) deliberately stay at
the top level: they exist to mirror ``lvis-api``'s import paths, so moving them
under a family namespace would defeat their purpose.
é    )Úannotationsé   )ÚCOCOevalÚ	HierarchyÚParamsÚcompareN)	Ú__doc__Ú
__future__r   Úhotcocor   r   r   r   Ú__all__© ó    úa/root/private/project/pallet_detection_v2/.venv/lib/python3.11/site-packages/hotcoco/detection.pyú<module>r      sV   ððð ð2 #Ð "Ð "Ð "Ð "Ð "à 9Ð 9Ð 9Ð 9Ð 9Ð 9Ð 9Ð 9Ð 9Ð 9Ð 9Ð 9à
8Ð
8Ð
8€€€r   