Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

In multi_cfg.py, why num_class=1 for extra_head ? #75

Open
praj441 opened this issue Oct 17, 2020 · 1 comment
Open

In multi_cfg.py, why num_class=1 for extra_head ? #75

praj441 opened this issue Oct 17, 2020 · 1 comment

Comments

@praj441
Copy link

praj441 commented Oct 17, 2020

The model configs are mentioned as follow in file config/multi_cfg.py :
model = dict(
type='SingleStageDetector',
backbone=dict(
type='SimpleVoxel',
num_input_features=4,
use_norm=True,
num_filters=[32, 64],
with_distance=False),

neck=dict(
    type='SpMiddleFHD',
    output_shape=[150,440,440],
    num_input_features=4,
    num_hidden_features=64 * 19,
),
bbox_head=dict(
    type='SSDRotateHead',
    num_class=9,
    num_output_filters=256,
    num_anchor_per_loc=2,
    use_sigmoid_cls=True,
    encode_rad_error_by_sin=True,
    use_direction_classifier=True,
    box_code_size=7,
),
extra_head=dict(
    type='PSWarpHead',
    grid_offsets = (0., 2.), #Almost half of the point cloud range
    featmap_stride=.4,
    in_channels=256,
    num_class=1,                                     
    num_parts=28,
)

)

Why num_class=1 in extra_head session, however, this config file is for multiple classes?

@nmll
Copy link

nmll commented Dec 2, 2020

why the featmap_stride=0.4?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants