Skip to content

GitLab

  • Menu
Projects Groups Snippets
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • hyteg hyteg
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 36
    • Issues 36
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 3
    • Merge requests 3
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Repository
  • Wiki
    • Wiki
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • hyteg
  • hyteghyteg
  • Issues
  • #136

Closed
Open
Created Sep 28, 2020 by Marcus Mohr@mohrDeveloper

Inconsistent use of PrimitiveStorage inside VTKOutput class

Hi,

at some point we should make our use of the PrimitiveStorage inside VTKOutput more consistent. Currently we pass a PrimitiveStorage to the object in its constructor. However, internally that get's used sometimes, but e.g. not in writeP1() or writeP2(). The latter ask the first of the functions to export for its PrimitiveStorage. This can of course lead to consistency issues, see e.g. this snippet from EdgeDoFFunctionTest [cff70c1c]

auto p1 = std::make_shared< P1Function< real_t > >( "p1", storage2, minLevel, maxLevel );
VTKOutput vtkOutput( "../../output", "interpolate_test", storage );
vtkOutput.add( *p1 );

Also we implicitely assume that all functions that we add in order to write to the same VTK file use the same PrimitiveStorage. Maybe we should make add() check whether the functions have the same storage as the one passed in the constructor?

Cheers
Marcus

Edited Sep 28, 2020 by Marcus Mohr
Assignee
Assign to
Time tracking