Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
S src
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 61
    • Issues 61
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • CI/CD
    • Code Review
    • Issue
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Members
    • Members
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • OPAL
  • src
  • Issues
  • #502

Closed
Open
Created Apr 07, 2020 by winklehner_d@winklehner_dDeveloper

Geometry: Switch from hardcoded globalInsideP0_m to auto-detect

@gsell, the SAAMG solver still has a hardcoded varible globalInsideP0_m that should automatically be determined by the geometry class during geometry loading. Making it an OPTION could be an intermittent fix, but really the geometry handler should be able to determine a point that is clearly inside the geometry on its own.

from ArbitraryDomain.cpp:

    // TODO: THis needs to be made into OPTION of the geometry.
    // A user defined point that is INSIDE with 100% certainty. -DW
    globalInsideP0_m = Vector_t(0.0, 0.0, -0.13);

@frey_m how does the AMR solver handle this? Or is it not using an imported geometry?

Cheers, Daniel

Assignee
Assign to
OPAL 2.4.0
Milestone
OPAL 2.4.0 (Past due)
Assign milestone
Time tracking