Skip to content
GitLab
Projects Groups Snippets
  • /
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
  • Sign in
  • ExaHyPE-Engine ExaHyPE-Engine
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Locked Files
  • Issues 68
    • Issues 68
    • List
    • Boards
    • Service Desk
    • Milestones
    • Iterations
    • Requirements
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
    • Test Cases
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Analytics
    • Analytics
    • Value stream
    • CI/CD
    • Insights
    • Issue
    • Repository
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar

9.2.2023: Due to updates GitLab will be unavailable for some minutes between 9:00 and 11:00.

  • ExaHyPEExaHyPE
  • ExaHyPE-EngineExaHyPE-Engine
  • Issues
  • #157
Closed
Open
Issue created Jun 12, 2017 by Ghost User@ghostContributor

Plotter variables are not constants

Actually the ExaHyPE runtime treats the number of writtenUnknowns per plotter as a runtime variable, ie.

    plot hdf5::flash ConservedWriter
      variables = 19
      time = 0.0
      repeat = 0.00001
      output = ./hdf5-flash/conserved
    end plot

one can change variables = x without recompiling. However, the toolkit wants this to be a constant:

    plot hdf5::flash ConservedWriter
      variables const = 19
      time = 0.0
      repeat = 0.00001
      output = ./hdf5-flash/conserved
    end plot

otherwise it says ERROR: eu.exahype.parser.ParserException: [71,17] expecting: 'const'

This should not happen, ie. the toolkit grammar should accept without const.

As always, there is assumably no case when somebody wants to do this except benchmarking plotter file formats which is exactly what I'm doing now and the typical generated code by the toolkit is not aware of a non-constexpr number of variables, but all the ExaHyPE/exahype/plotters/ code actually treats the number as runtime constant and I see no reason why to artificially introduce something constexpr here.

Assignee
Assign to
Time tracking

LRZ Homepage | Datenschutz | Dokumentation und Betriebsbedingungen | Impressum