Skip to content
GitLab
  • Menu
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in / Register
  • Nektar Nektar
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 91
    • Issues 91
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
  • Merge requests 62
    • Merge requests 62
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Releases
  • Packages & Registries
    • Packages & Registries
    • Container Registry
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Code review
    • Insights
    • Issue
    • Repository
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • Nektar
  • NektarNektar
  • Merge requests
  • !1343

Feature/high order vtu output

  • Review changes

  • Download
  • Email patches
  • Plain diff
Merged Edward Laughton requested to merge feature/High-order-VTU-output into master May 31, 2022
  • Overview 34
  • Commits 69
  • Pipelines 33
  • Changes 31

Issue/feature addressed

VTK output was manually written, which is slow and results in large uncompressed files

Proposed solution

Adds a VTK output option using the VTK library

Implementation

Renamed old output to OutputVtkLegacy, implemented a new OutputVtk which makes use of the VTK library to achieve a number of things such as custom compression levels 1-9, high order VTK output, multiblock output, cached mesh when using filters.

Supports:

  • Old linear: Whatever it was before
  • New linear: 1D, 2D, 3D, 3DH1D (cached mesh when filter FieldConvert)
  • High order: 1D, 2D, 3D except pyramids (cached mesh when filter FieldConvert)
  • Multi-block: 1D, 2D, 3D

Tests

Notes

Please add any other information that could be useful for reviewers. Fixes #215 (closed)

Checklist

  • Functions and classes, or changes to them, are documented.
  • User guide/documentation is updated.
  • Changelog is updated.
  • Suitable tests added for new functionality.
  • Newly added files are correctly formatted.
  • License added to any new files.
  • No extraneous files have been added (e.g. compiler output or test data files).
Edited Jul 27, 2022 by Edward Laughton
Assignee
Assign to
Reviewer
Request review from
Time tracking
Source branch: feature/High-order-VTU-output