Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
tnl-dev
tnl-dev
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 32
    • Issues 32
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 1
    • Merge Requests 1
  • Operations
    • Operations
    • Incidents
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • TNL
  • tnl-devtnl-dev
  • Issues
  • #53

Closed
Open
Opened Oct 25, 2019 by Matouš Fencl@fenclDeveloper

Bug in analytic functions

Analytic functions as input MeshFunction in Hamilton-Jacobi solver with MPI on GPU give bad values.

Generated function from tnl-init is passed into tnl-direct-eikonal-solver. TNL devides input MeshFunction into blocks, which number depends on number of processes. Devided MeshFunction that we get in file tnlDirectEikonalProblem_impl.h in function Solve() has invalid values.

Starting script is attached.

tnl-run-dir-eik-solver

Edited Nov 07, 2019 by Matouš Fencl
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: tnl/tnl-dev#53