-
Notifications
You must be signed in to change notification settings - Fork 81
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
Cfg file for running the demo of MobileNetv2 and MobileNetV3 models #47
Comments
Hi, Here is the cfg file of mobilenetv3 on 300W: class Config(): def __init__(self): self.det_head = 'pip' self.net_stride = 32 self.batch_size = 16 self.init_lr = 0.0001 self.num_epochs = 120 self.decay_steps = [60, 100] self.input_size = 256 self.backbone = 'mobilenet_v3' self.pretrained = True self.criterion_cls = 'l2' self.criterion_reg = 'l1' self.cls_loss_weight = 10 self.reg_loss_weight = 1 self.num_lms = 68 self.save_interval = self.num_epochs self.num_nb = 10 self.use_gpu = True self.gpu_id = 0 For get_meanface function, all backbones share the same file, and the data name corresponds to training data, e.g., datat_300W, WFLW, etc. |
I may have confused. |
Will you provid the trained models of MobileNet-V3 and MobileNet-v2 ? It woild be very appreciated. |
I did not provide trained model for mobilenets previously. And the one named '"mobilenet-v3-large model (mobilenetv3-large-1cd25616.pth)" is an ImageNet pretrained model for initialization. |
Thx!!
Is that right ? |
Yes, I think so. The only difference is the number of landmarks. |
First of all, thanks for sharing the excellent models. I've tested the resnet101 based models, it works perfect. And I noticed that you guys also provide the mobilenet-v3-large model (mobilenetv3-large-1cd25616.pth) in
~/PIPNet/lib
.I'd like to test the effect of this model, but can't find the related cfg file, seems that only Resnet related cfg files have been provided.
Could you provide the 'cfg' file and also the 'data_name' which may needed in calculating the
get_meanface
function.The text was updated successfully, but these errors were encountered: