Skip to content

Questions about encoder proposal selection #4

@zhangchbin

Description

@zhangchbin

Hi @ZhuYuChenNO1 @ChengShiest ,

Thanks for this excellent work! I have some questions about the model design as follows:

  1. As shown in this line, the object proposals are selected according to the similarity to the first class (like "person" in the coco dataset). I think these class-agnostic proposals follow the design of the original deformable-detr++, but in PlainDet, the class_embed for proposals is not learnable (which is initialized with text embedding and frozen). Would you be able to provide some explanations here? Have you tried using maximum scores among all classes to select proposals as commented in the next line?
  2. About the procedure of building query embeddings, the description in the paper, like Equation 7, is different from the code.
  3. What is the difference between PlainDet and typical open-vocabulary object detection regarding the training paradigm?

Thanks! Looking forward to your reply!

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions