Closed LuletterSoul closed 8 months ago
Hi @LuletterSoul, the LVIS AP in pre-training log is the standard LVIS val v1.0
AP, and we report both the LVIS minival
(30.0) and LVIS val v1.0
AP (23.5) in the README.
Hi @LuletterSoul, the LVIS AP in pre-training log is the standard LVIS
val v1.0
AP, and we report both the LVISminival
(30.0) and LVISval v1.0
AP (23.5) in the README.
coco_val_dataset = dict(
_delete_=True,
type='MultiModalDataset',
dataset=dict(type='YOLOv5LVISV1Dataset',
data_root='data/coco/',
test_mode=True,
ann_file='lvis/lvis_v1_minival_inserted_image_name.json',
data_prefix=dict(img=''),
batch_shapes_cfg=None),
But it seems that the current version of val_dataloader used by the project seems to be lvis v1.0 minival
, not lvis v1.0 val
? I would like to know if the bbox_AP printed in the yolo_world_v2_m_o365_goldg_pretrain_part_2.log
is v1.0 minival
or v1.0 val
.
Hi @LuletterSoul, we pre-train YOLO-World based on our local configs (evaluated on LVIS val v1.0
), and release the configs with LVIS minival
. If you are confused and you can run an evaluation with the two validation sets.
Hi @LuletterSoul, we pre-train YOLO-World based on our local configs (evaluated on LVIS
val v1.0
), and release the configs with LVISminival
. If you are confused and you can run an evaluation with the two validation sets.
Ok, I got it, thanks for your quick response.
Thanks to the authors for open sourcing such a excellent project. When I reproduce YOLO-World-v2-L, the last lvis/bbox_AP in
yolo_world_v2_m_o365_goldg_pretrain_part_2.log
, is 23.50, but AP_mini in ReadMe is 30.0. Am I understanding this wrong?