Skip to content

  • Projects
  • Groups
  • Snippets
  • Help
    • Loading...
    • Help
    • Support
    • Submit feedback
    • Contribute to GitLab
  • Sign in
D
dune-copasi
  • Project overview
    • Project overview
    • Details
    • Activity
    • Releases
    • Cycle Analytics
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
    • Charts
  • Issues 11
    • Issues 11
    • List
    • Boards
    • Labels
    • Milestones
  • Merge Requests 2
    • Merge Requests 2
  • CI / CD
    • CI / CD
    • Pipelines
    • Jobs
    • Schedules
    • Charts
  • Packages
    • Packages
    • Container Registry
  • Members
    • Members
  • Collapse sidebar
  • Activity
  • Graph
  • Charts
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
  • COPASI
  • dune-copasi
  • Issues
  • #19

Closed
Open
Opened Oct 22, 2019 by Santiago Ospina@santiago.ospina
  • Report abuse
  • New issue
Report abuse New issue

Add more system tests

Proposal

Test more cases that have a known output. For example, the FitzHugh-Nagumo, and the Grey-Scott models.

How to test the implementation?

If an analytical solution is available, construct a grid function to be compared with. If not, use a reference test to know when a modification is changing the results of the solver.

Related issues

See #

Assignee
Assign to
ES1 - First integrated software release
Milestone
ES1 - First integrated software release
Assign milestone
Time tracking
None
Due date
None
5
Labels
Downstream:API:C++ Downstream:UI:config Language:C++ Language:CMake Language:Python
Assign labels
  • View project labels
Reference: copasi/dune-copasi#19