Skip to content
GitLab
Projects Groups Topics Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • W waLBerla
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributor statistics
    • Graph
    • Compare revisions
  • Issues 41
    • Issues 41
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 10
    • Merge requests 10
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Releases
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • waLBerla
  • waLBerla
  • Issues
  • #150
Closed
Open
Issue created May 21, 2021 by Daniel Bauer@he66coqe💬Contributor

DistanceOctree<MeshType>::writeVTKOutput(..) might take very long to complete

I create and output a DistanceOctree as is indicated in Tutorial - LBM 4: Complex Geometry.

Using a mesh with 110k vertices, running my code on the Emmy cluster and writing the VTK-output to $FASTTMP I noticed that the runtime of DistanceOctree<MeshType>::writeVTKOutput(..) can drastically vary from run to run. Anything between 5 minutes and 5 hours has been observed.

Assignee
Assign to
Time tracking