Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • FS FS
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 97
    • Issues 97
    • List
    • Boards
    • Service Desk
    • Milestones
  • Deployments
    • Deployments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • Repository
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
Collapse sidebar

Be aware that the dune-project.org domain and its name server will have some updates between February 6, 8:00 UTC (9:00 CET) and 10:00 UTC (11:00 CET) as we will be performing services relocation during this time.

  • flysprayflyspray
  • FSFS
  • Issues
  • #1698
Closed
Open
Issue created Jul 19, 2015 by Jö Fahlke@joeReporter

#1698 Improve GmshReader interface

Metadata

Property Value
Reported by Jö Fahlke (jorrit@jorrit.de)
Reported at Jul 19, 2015 10:26
Type Bug Report
Version 2.3
Operating System Unspecified / All

Description

The GmshReader interface has some really counter-intuitive aspects.

For instance, it allows you to read physical entities, even though you did not specify a grid factory. This makes it impossible to later access the physical entities, since you need the grid factory used for creation of the grid to determine the indices into the vectors of physical entities. Users have run into this a few times, they usually try to index the vector with whatever looks like an index to them (e.g. IndexSet, Map, the index induced by the iteration order) and wonder why their physical entity numbers are all garbled.

As another example, (e.g. #1696 (closed)): why is it possible to specify insertBoundarySegments=false together with a vector to store the boundary physical entities into? You won't be able to access this vector, even if you specified a gridfactory, because automatically generated boundary intersections do not have an insertion index.

Assignee
Assign to
Time tracking