Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • P pyod
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 144
    • Issues 144
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 16
    • Merge requests 16
  • 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
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Yue Zhao
  • pyod
  • Issues
  • #385
Closed
Open
Issue created Apr 06, 2022 by Administrator@rootContributor

Bias in DeepSVDD

Created by: psorus

If you read Lukas Ruffs Paper (https://ls9-www.cs.tu-dortmund.de/publications/ICML2018.pdf ) he writes in 3.3 Proposition 2 that "Proposition 2 implies that networks with bias terms can easily learn any constant function" and thus suggests not using a bias term in the definition of a DeepSVDD paper. Also, his code (https://github.com/lukasruff/Deep-SVDD-PyTorch/blob/1901612d595e23675fb75c4ebb563dd0ffebc21e/src/networks/mnist_LeNet.py#L16 ) disables these bias terms. Is there any reason I am not aware of why pyod's version of deep svdd uses biases in its network definition?

Assignee
Assign to
Time tracking