Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • bob.bio.base bob.bio.base
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 14
    • Issues 14
    • 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.bio.basebob.bio.base
  • Issues
  • #140
Closed
Open
Issue created Oct 19, 2020 by Laurent COLBOIS@lcolboisMaintainer

Dask client is created by user but stopped by vanilla-biometrics

Hello, Currently to use vanilla-biometrics one has to provide an already instantiated Dask client, which is closed by the vanilla-biometrics script at the end of the run. This gives the false impression that one can instantiate a Dask client in a Python script, and then use it for several successive vanilla-biometrics experiment, which is not the case. Should maybe the opening/closing of the Dask client be entirely handled either by the user, or by the vanilla-biometrics script ? In the latter case I guess some configuration dict for the client could be passed instead when calling vanilla-biometrics.

@ydayer

Assignee
Assign to
Time tracking