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

How the search_area_factor and output_sz are calculated? #11

Open
OOHAN-zxy opened this issue Feb 18, 2024 · 1 comment
Open

How the search_area_factor and output_sz are calculated? #11

OOHAN-zxy opened this issue Feb 18, 2024 · 1 comment

Comments

@OOHAN-zxy
Copy link

Thank you for your contribution to the MOT community. I have some questions about how to crop the current frame with a certain scale, may I ask how the size parameters search_area_factor and output_sz are calculated, but they are not clearly found in the code, looking forward to your reply!
Mix

@ret-1
Copy link
Collaborator

ret-1 commented Feb 21, 2024

Hi @OOHAN-zxy ,

These parameters are set using this function:

def update_settings(settings, cfg):
settings.print_interval = cfg.TRAIN.PRINT_INTERVAL
settings.search_area_factor = {'template': cfg.DATA.TEMPLATE.FACTOR,
'search': cfg.DATA.SEARCH.FACTOR}
settings.output_sz = {'template': cfg.DATA.TEMPLATE.SIZE,
'search': cfg.DATA.SEARCH.SIZE}
settings.center_jitter_factor = {'template': cfg.DATA.TEMPLATE.CENTER_JITTER,
'search': cfg.DATA.SEARCH.CENTER_JITTER}
settings.scale_jitter_factor = {'template': cfg.DATA.TEMPLATE.SCALE_JITTER,
'search': cfg.DATA.SEARCH.SCALE_JITTER}
settings.grad_clip_norm = cfg.TRAIN.GRAD_CLIP_NORM
settings.print_stats = None
settings.batchsize = cfg.TRAIN.BATCH_SIZE
settings.scheduler_type = cfg.TRAIN.SCHEDULER.TYPE

and the cfg is loaded from MixViT/experiments/mixformer_deit/track.yaml

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