Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
  • C climix
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 53
    • Issues 53
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 4
    • Merge requests 4
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar
  • climix
  • climix
  • Issues
  • #124

Closed
Open
Created Nov 04, 2019 by Klaus Zimmermann@a002160Owner

Fix dask setup to *not* prescribe local directory

The dask setup for local cluster at the moment prescribes a fixed location on a ram disk. While the use of a ram disk might be beneficial and certainly not all (HPC) file systems are equally suited for the task, the prescription of one particular directory is to restrictive and creates problems on shared environments. For now, let's revert to dask choosing the directory, possibly giving a configuration option later on.

Assignee
Assign to
Time tracking