Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob.pad.base bob.pad.base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 0
    • Issues 0
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 0
    • Merge requests 0
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Packages and registries
    • Packages and registries
    • Package Registry
    • Infrastructure Registry
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • bobbob
  • bob.pad.basebob.pad.base
  • Issues
  • #36
Closed
Open
Issue created Dec 07, 2020 by Tiago de Freitas Pereira@tiago.pereiraOwner

One-Shot vulnerability analysis

Hi,

Today the workflow to do vulnerability analysis is:

  1. To have a database with two protocols, one licit (zero-effort impostors vs bonafides) and one called spoof (presentation attacks vs bonafides).
  2. run bob bio pipelines vanilla-biometrics licit....
  3. run bob bio pipelines vanilla-biometrics spoof....
  4. run bob pad vulnerability .... {licit,spoof}/scores-{dev,eval}

I understand the reasons why this was made like this, but now with bob bio pipelines vanilla-biometrics --write-metadata .... we can have score files where metadata is available:

probe_key,probe_path,probe_reference_id,bio_ref_path,bio_ref_reference_id,is_bonafide,score
devel/real/client003_session01_webcam_authenticate_adverse_1,devel/real/client003_session01_webcam_authenticate_adverse_1,3,3,3,1,0.9919710755348206

Therefore, we can afford to have one protocol containing both zero-effort impostors and presentation attack probes, and the job of the tools inside of bob pad vulnerability would take care of selecting these two types of probes and do the correct analysis.

I think this is wiser.

What do you think @amohammadi @ydayer?

Thanks

Edited Dec 08, 2020 by Tiago de Freitas Pereira
Assignee
Assign to
Time tracking