MiniFAS selection uses the MobileNetV3 inference path #144
Tunahanyrd
started this conversation in
General
Replies: 1 comment 1 reply
|
Could we convert it into an issue? |
1 reply
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
I traced the anti-spoof model selection in 1.4.1 and found that the selected MiniFAS model type is lost before inference.
minifas-v2is registered as a selectable anti-spoof model:biopass/app/src-tauri/src/db.rs
Lines 48 to 59 in aa8c3e2
The inference caller resolves the selected model path, but constructs
FaceAntiSpoofingwith only the path, image size and threshold:biopass/auth/face/antispoofing/antispoof_check.cc
Lines 30 to 42 in aa8c3e2
The omitted fourth argument defaults to
mobilenetv3:biopass/auth/face/antispoofing/face_as.h
Lines 19 to 23 in aa8c3e2
Filename inference only runs when
model_typeis neithermobilenetv3norminifasv2. Since the default is alreadymobilenetv3, the MiniFAS filename is never inspected:biopass/auth/face/antispoofing/face_as.cc
Lines 24 to 34 in aa8c3e2
The loaded file can therefore be
minifas_v2.onnxwhile preprocessing and output handling still follow the MobileNetV3 branch.I would like to send a small PR that passes the selected built-in model type explicitly and adds a regression test. The scoring policy and other anti-spoof behavior would remain unchanged.
All reactions