Skip to content

GitLab

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in / Register
D
dorie
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 31
    • Issues 31
    • List
    • Boards
    • Labels
    • Service Desk
    • Milestones
  • Merge Requests 9
    • Merge Requests 9
  • Operations
    • Operations
    • Incidents
    • Environments
  • Analytics
    • Analytics
    • Repository
    • Value Stream
  • Wiki
    • Wiki
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Create a new issue
  • Commits
  • Issue Boards
  • dorie
  • dorie
  • Issues
  • #130

Closed
Open
Opened Dec 18, 2018 by Santiago Ospina De Los Ríos@sospinarMaintainer0 of 1 task completed0/1 task

Switch to vertex data evaluation on system tests

Description

The following discussion from !128 (merged) should be addressed:

  • @lriedel started a discussion:

    This requires an update of all system tests. The Python scripts only work with cell data. This is the only reason why vertexData is not set to True by default.

    I have a Python implementation ready which can also evaluate vertex VTKs, based on Oles dune-vtkdiff, see https://ts-gitlab.iup.uni-heidelberg.de/dorie/dorie/snippets/16. I'll probably use that to update the Python test evaluators "soon"_

Proposal

...

How to test the implementation?

...

Related issues

See #...

To upload designs, you'll need to enable LFS and have admin enable hashed storage. More information
Assignee
Assign to
None
Milestone
None
Assign milestone
Time tracking
None
Due date
None
Reference: dorie/dorie#130